Unnamed: 0 int64 0 832k | id float64 2.49B 32.1B | type stringclasses 1
value | created_at stringlengths 19 19 | repo stringlengths 5 112 | repo_url stringlengths 34 141 | action stringclasses 3
values | title stringlengths 1 1k | labels stringlengths 4 1.38k | body stringlengths 1 262k | index stringclasses 16
values | text_combine stringlengths 96 262k | label stringclasses 2
values | text stringlengths 96 252k | binary_label int64 0 1 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
117,197 | 17,439,350,408 | IssuesEvent | 2021-08-05 01:05:58 | samq-ghdemo/ori-kit | https://api.github.com/repos/samq-ghdemo/ori-kit | opened | CVE-2021-32804 (High) detected in tar-2.2.2.tgz | security vulnerability | ## CVE-2021-32804 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tar-2.2.2.tgz</b></p></summary>
<p>tar for node</p>
<p>Library home page: <a href="https://registry.npmjs.org/tar/-/tar-2.2.2.tgz">https://registry.npmjs.org/tar/-/tar-2.2.2.tgz</a></p>
<p>Path to dependency file: ori-kit/package.json</p>
<p>Path to vulnerable library: ori-kit/node_modules/node-gyp/node_modules/tar/package.json</p>
<p>
Dependency Hierarchy:
- sqlite3-5.0.2.tgz (Root Library)
- node-gyp-3.8.0.tgz
- :x: **tar-2.2.2.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>
The npm package "tar" (aka node-tar) before versions 6.1.1, 5.0.6, 4.4.14, and 3.3.2 has a arbitrary File Creation/Overwrite vulnerability due to insufficient absolute path sanitization. node-tar aims to prevent extraction of absolute file paths by turning absolute paths into relative paths when the `preservePaths` flag is not set to `true`. This is achieved by stripping the absolute path root from any absolute file paths contained in a tar file. For example `/home/user/.bashrc` would turn into `home/user/.bashrc`. This logic was insufficient when file paths contained repeated path roots such as `////home/user/.bashrc`. `node-tar` would only strip a single path root from such paths. When given an absolute file path with repeating path roots, the resulting path (e.g. `///home/user/.bashrc`) would still resolve to an absolute path, thus allowing arbitrary file creation and overwrite. This issue was addressed in releases 3.2.2, 4.4.14, 5.0.6 and 6.1.1. Users may work around this vulnerability without upgrading by creating a custom `onentry` method which sanitizes the `entry.path` or a `filter` method which removes entries with absolute paths. See referenced GitHub Advisory for details. Be aware of CVE-2021-32803 which fixes a similar bug in later versions of tar.
<p>Publish Date: 2021-08-03
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-32804>CVE-2021-32804</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.2</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/npm/node-tar/security/advisories/GHSA-3jfq-g458-7qm9">https://github.com/npm/node-tar/security/advisories/GHSA-3jfq-g458-7qm9</a></p>
<p>Release Date: 2021-08-03</p>
<p>Fix Resolution: tar - 3.2.2, 4.4.14, 5.0.6, 6.1.1</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"tar","packageVersion":"2.2.2","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"sqlite3:5.0.2;node-gyp:3.8.0;tar:2.2.2","isMinimumFixVersionAvailable":true,"minimumFixVersion":"tar - 3.2.2, 4.4.14, 5.0.6, 6.1.1"}],"baseBranches":["main"],"vulnerabilityIdentifier":"CVE-2021-32804","vulnerabilityDetails":"The npm package \"tar\" (aka node-tar) before versions 6.1.1, 5.0.6, 4.4.14, and 3.3.2 has a arbitrary File Creation/Overwrite vulnerability due to insufficient absolute path sanitization. node-tar aims to prevent extraction of absolute file paths by turning absolute paths into relative paths when the `preservePaths` flag is not set to `true`. This is achieved by stripping the absolute path root from any absolute file paths contained in a tar file. For example `/home/user/.bashrc` would turn into `home/user/.bashrc`. This logic was insufficient when file paths contained repeated path roots such as `////home/user/.bashrc`. `node-tar` would only strip a single path root from such paths. When given an absolute file path with repeating path roots, the resulting path (e.g. `///home/user/.bashrc`) would still resolve to an absolute path, thus allowing arbitrary file creation and overwrite. This issue was addressed in releases 3.2.2, 4.4.14, 5.0.6 and 6.1.1. Users may work around this vulnerability without upgrading by creating a custom `onentry` method which sanitizes the `entry.path` or a `filter` method which removes entries with absolute paths. See referenced GitHub Advisory for details. Be aware of CVE-2021-32803 which fixes a similar bug in later versions of tar.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-32804","cvss3Severity":"high","cvss3Score":"8.2","cvss3Metrics":{"A":"N/A","AC":"N/A","PR":"N/A","S":"N/A","C":"N/A","UI":"N/A","AV":"N/A","I":"N/A"},"extraData":{}}</REMEDIATE> --> | True | CVE-2021-32804 (High) detected in tar-2.2.2.tgz - ## CVE-2021-32804 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>tar-2.2.2.tgz</b></p></summary>
<p>tar for node</p>
<p>Library home page: <a href="https://registry.npmjs.org/tar/-/tar-2.2.2.tgz">https://registry.npmjs.org/tar/-/tar-2.2.2.tgz</a></p>
<p>Path to dependency file: ori-kit/package.json</p>
<p>Path to vulnerable library: ori-kit/node_modules/node-gyp/node_modules/tar/package.json</p>
<p>
Dependency Hierarchy:
- sqlite3-5.0.2.tgz (Root Library)
- node-gyp-3.8.0.tgz
- :x: **tar-2.2.2.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>
The npm package "tar" (aka node-tar) before versions 6.1.1, 5.0.6, 4.4.14, and 3.3.2 has a arbitrary File Creation/Overwrite vulnerability due to insufficient absolute path sanitization. node-tar aims to prevent extraction of absolute file paths by turning absolute paths into relative paths when the `preservePaths` flag is not set to `true`. This is achieved by stripping the absolute path root from any absolute file paths contained in a tar file. For example `/home/user/.bashrc` would turn into `home/user/.bashrc`. This logic was insufficient when file paths contained repeated path roots such as `////home/user/.bashrc`. `node-tar` would only strip a single path root from such paths. When given an absolute file path with repeating path roots, the resulting path (e.g. `///home/user/.bashrc`) would still resolve to an absolute path, thus allowing arbitrary file creation and overwrite. This issue was addressed in releases 3.2.2, 4.4.14, 5.0.6 and 6.1.1. Users may work around this vulnerability without upgrading by creating a custom `onentry` method which sanitizes the `entry.path` or a `filter` method which removes entries with absolute paths. See referenced GitHub Advisory for details. Be aware of CVE-2021-32803 which fixes a similar bug in later versions of tar.
<p>Publish Date: 2021-08-03
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-32804>CVE-2021-32804</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.2</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/npm/node-tar/security/advisories/GHSA-3jfq-g458-7qm9">https://github.com/npm/node-tar/security/advisories/GHSA-3jfq-g458-7qm9</a></p>
<p>Release Date: 2021-08-03</p>
<p>Fix Resolution: tar - 3.2.2, 4.4.14, 5.0.6, 6.1.1</p>
</p>
</details>
<p></p>
<!-- <REMEDIATE>{"isOpenPROnVulnerability":false,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"tar","packageVersion":"2.2.2","packageFilePaths":["/package.json"],"isTransitiveDependency":true,"dependencyTree":"sqlite3:5.0.2;node-gyp:3.8.0;tar:2.2.2","isMinimumFixVersionAvailable":true,"minimumFixVersion":"tar - 3.2.2, 4.4.14, 5.0.6, 6.1.1"}],"baseBranches":["main"],"vulnerabilityIdentifier":"CVE-2021-32804","vulnerabilityDetails":"The npm package \"tar\" (aka node-tar) before versions 6.1.1, 5.0.6, 4.4.14, and 3.3.2 has a arbitrary File Creation/Overwrite vulnerability due to insufficient absolute path sanitization. node-tar aims to prevent extraction of absolute file paths by turning absolute paths into relative paths when the `preservePaths` flag is not set to `true`. This is achieved by stripping the absolute path root from any absolute file paths contained in a tar file. For example `/home/user/.bashrc` would turn into `home/user/.bashrc`. This logic was insufficient when file paths contained repeated path roots such as `////home/user/.bashrc`. `node-tar` would only strip a single path root from such paths. When given an absolute file path with repeating path roots, the resulting path (e.g. `///home/user/.bashrc`) would still resolve to an absolute path, thus allowing arbitrary file creation and overwrite. This issue was addressed in releases 3.2.2, 4.4.14, 5.0.6 and 6.1.1. Users may work around this vulnerability without upgrading by creating a custom `onentry` method which sanitizes the `entry.path` or a `filter` method which removes entries with absolute paths. See referenced GitHub Advisory for details. Be aware of CVE-2021-32803 which fixes a similar bug in later versions of tar.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-32804","cvss3Severity":"high","cvss3Score":"8.2","cvss3Metrics":{"A":"N/A","AC":"N/A","PR":"N/A","S":"N/A","C":"N/A","UI":"N/A","AV":"N/A","I":"N/A"},"extraData":{}}</REMEDIATE> --> | non_priority | cve high detected in tar tgz cve high severity vulnerability vulnerable library tar tgz tar for node library home page a href path to dependency file ori kit package json path to vulnerable library ori kit node modules node gyp node modules tar package json dependency hierarchy tgz root library node gyp tgz x tar tgz vulnerable library found in base branch main vulnerability details the npm package tar aka node tar before versions and has a arbitrary file creation overwrite vulnerability due to insufficient absolute path sanitization node tar aims to prevent extraction of absolute file paths by turning absolute paths into relative paths when the preservepaths flag is not set to true this is achieved by stripping the absolute path root from any absolute file paths contained in a tar file for example home user bashrc would turn into home user bashrc this logic was insufficient when file paths contained repeated path roots such as home user bashrc node tar would only strip a single path root from such paths when given an absolute file path with repeating path roots the resulting path e g home user bashrc would still resolve to an absolute path thus allowing arbitrary file creation and overwrite this issue was addressed in releases and users may work around this vulnerability without upgrading by creating a custom onentry method which sanitizes the entry path or a filter method which removes entries with absolute paths see referenced github advisory for details be aware of cve which fixes a similar bug in later versions of tar 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 tar isopenpronvulnerability false ispackagebased true isdefaultbranch true packages istransitivedependency true dependencytree node gyp tar isminimumfixversionavailable true minimumfixversion tar basebranches vulnerabilityidentifier cve vulnerabilitydetails the npm package tar aka node tar before versions and has a arbitrary file creation overwrite vulnerability due to insufficient absolute path sanitization node tar aims to prevent extraction of absolute file paths by turning absolute paths into relative paths when the preservepaths flag is not set to true this is achieved by stripping the absolute path root from any absolute file paths contained in a tar file for example home user bashrc would turn into home user bashrc this logic was insufficient when file paths contained repeated path roots such as home user bashrc node tar would only strip a single path root from such paths when given an absolute file path with repeating path roots the resulting path e g home user bashrc would still resolve to an absolute path thus allowing arbitrary file creation and overwrite this issue was addressed in releases and users may work around this vulnerability without upgrading by creating a custom onentry method which sanitizes the entry path or a filter method which removes entries with absolute paths see referenced github advisory for details be aware of cve which fixes a similar bug in later versions of tar vulnerabilityurl | 0 |
26,292 | 2,684,295,503 | IssuesEvent | 2015-03-28 21:00:28 | ConEmu/old-issues | https://api.github.com/repos/ConEmu/old-issues | opened | conemu and fantom language | 1 star bug imported Priority-Medium | _From [switch...@gmail.com](https://code.google.com/u/114776128219996438927/) on February 17, 2013 00:17:53_
Required information! OS version: Win8x64 ConEmu version: 130212
Far version (if you are using Far Manager): Far3 *Bug description* http://www.644634.com/conemu.htm on conemu start input method swithing to nonpresent language.
_Original issue: http://code.google.com/p/conemu-maximus5/issues/detail?id=944_ | 1.0 | conemu and fantom language - _From [switch...@gmail.com](https://code.google.com/u/114776128219996438927/) on February 17, 2013 00:17:53_
Required information! OS version: Win8x64 ConEmu version: 130212
Far version (if you are using Far Manager): Far3 *Bug description* http://www.644634.com/conemu.htm on conemu start input method swithing to nonpresent language.
_Original issue: http://code.google.com/p/conemu-maximus5/issues/detail?id=944_ | priority | conemu and fantom language from on february required information os version conemu version far version if you are using far manager bug description on conemu start input method swithing to nonpresent language original issue | 1 |
322,127 | 9,813,270,116 | IssuesEvent | 2019-06-13 07:33:10 | HabitRPG/habitica-android | https://api.github.com/repos/HabitRPG/habitica-android | closed | Habits: Yellow habits should show with 'Weak' filter, not 'Strong' | Priority: medium Status: issue: in progress Type: Bug | Right now when you filter habits to 'Strong', yellow habits will show. Those should be grouped with the 'Weak' habit filter | 1.0 | Habits: Yellow habits should show with 'Weak' filter, not 'Strong' - Right now when you filter habits to 'Strong', yellow habits will show. Those should be grouped with the 'Weak' habit filter | priority | habits yellow habits should show with weak filter not strong right now when you filter habits to strong yellow habits will show those should be grouped with the weak habit filter | 1 |
348,097 | 31,466,637,017 | IssuesEvent | 2023-08-30 02:54:47 | TencentBlueKing/bk-nodeman | https://api.github.com/repos/TencentBlueKing/bk-nodeman | closed | [BUG] 项目启动卡住 | for test | ## 问题描述
> 简明扼要地描述bug是什么
MySQL 出现死锁：`pipeline/component_framework/base.py` Line
### 截屏
请提供截屏来解释你的问题，当然这也能更好地帮助我们理解问题。
### 请提供以下信息
- [x] bk-nodeman 版本 (发布版本号 或 git
tag)： <!-- `示例： V3.1.32-ce 或者 git sha. 请不要使用 "最新版本" 或 "当前版本"等无法准确定位代码版本的语句描述` -->
- [ ] 蓝鲸PaaS 版本：<!-- `<示例：PaaS 3.0.58、PaaSAgent 3.0.9` -->
- [ ] bk-nodeman 异常日志：
## 重现方法
> 列出如何重现的方法或操作步骤
## 修复
### 建议的修复方案
### 修复方案
### 功能自测
> 代码变更覆盖功能点需要自测并截图
#### 功能点 1
描述代码变更涉及功能点及自测截图
#### 功能点 2
描述代码变更涉及功能点及自测截图
#### ...
| 1.0 | [BUG] 项目启动卡住 - ## 问题描述
> 简明扼要地描述bug是什么
MySQL 出现死锁：`pipeline/component_framework/base.py` Line
### 截屏
请提供截屏来解释你的问题，当然这也能更好地帮助我们理解问题。
### 请提供以下信息
- [x] bk-nodeman 版本 (发布版本号 或 git
tag)： <!-- `示例： V3.1.32-ce 或者 git sha. 请不要使用 "最新版本" 或 "当前版本"等无法准确定位代码版本的语句描述` -->
- [ ] 蓝鲸PaaS 版本：<!-- `<示例：PaaS 3.0.58、PaaSAgent 3.0.9` -->
- [ ] bk-nodeman 异常日志：
## 重现方法
> 列出如何重现的方法或操作步骤
## 修复
### 建议的修复方案
### 修复方案
### 功能自测
> 代码变更覆盖功能点需要自测并截图
#### 功能点 1
描述代码变更涉及功能点及自测截图
#### 功能点 2
描述代码变更涉及功能点及自测截图
#### ...
| non_priority | 项目启动卡住 问题描述 简明扼要地描述bug是什么 mysql 出现死锁： pipeline component framework base py line 截屏 请提供截屏来解释你的问题，当然这也能更好地帮助我们理解问题。 请提供以下信息 bk nodeman 版本 发布版本号 或 git tag ： 蓝鲸paas 版本： bk nodeman 异常日志： 重现方法 列出如何重现的方法或操作步骤 修复 建议的修复方案 修复方案 功能自测 代码变更覆盖功能点需要自测并截图 功能点 描述代码变更涉及功能点及自测截图 功能点 描述代码变更涉及功能点及自测截图 | 0 |
407,124 | 27,600,986,670 | IssuesEvent | 2023-03-09 09:57:16 | Apicurio/apicurio-registry | https://api.github.com/repos/Apicurio/apicurio-registry | closed | Able to set additional Java properties for Docker images | Documentation Discussion | It would be nice to have extra java options which will concatenated with predefined Java options to be able provide custom Java parameters. This applicable for all standards Java and native images.
This case can be implemented within custom build process #67 | 1.0 | Able to set additional Java properties for Docker images - It would be nice to have extra java options which will concatenated with predefined Java options to be able provide custom Java parameters. This applicable for all standards Java and native images.
This case can be implemented within custom build process #67 | non_priority | able to set additional java properties for docker images it would be nice to have extra java options which will concatenated with predefined java options to be able provide custom java parameters this applicable for all standards java and native images this case can be implemented within custom build process | 0 |
84,103 | 10,475,352,403 | IssuesEvent | 2019-09-23 16:09:25 | cityofaustin/techstack | https://api.github.com/repos/cityofaustin/techstack | closed | Document management UX | Author Interface Feature: Document management Joplin Alpha Team: Design + Research | ### As a content editor, I want to be able to upload and manage documents in Joplin, so that I can easily add documents to the pages I'm publishing.
**Is your feature request related to a problem? Please describe.**
We're already uploading docs for OPO official document list pages, and soon we'll want to upload documents for guides.
**Describe the solution you'd like**
@briaguya stood up a proof of concept of document management on this branch: http://joplin-pr-2811-play-with-docum.herokuapp.com/admin/documents/
Let's review the user experience. What works for MVP? What doesn't?
**Describe alternatives you've considered**
**Additional context**
Add any other context or screenshots about the feature request here.
| 1.0 | Document management UX - ### As a content editor, I want to be able to upload and manage documents in Joplin, so that I can easily add documents to the pages I'm publishing.
**Is your feature request related to a problem? Please describe.**
We're already uploading docs for OPO official document list pages, and soon we'll want to upload documents for guides.
**Describe the solution you'd like**
@briaguya stood up a proof of concept of document management on this branch: http://joplin-pr-2811-play-with-docum.herokuapp.com/admin/documents/
Let's review the user experience. What works for MVP? What doesn't?
**Describe alternatives you've considered**
**Additional context**
Add any other context or screenshots about the feature request here.
| non_priority | document management ux as a content editor i want to be able to upload and manage documents in joplin so that i can easily add documents to the pages i m publishing is your feature request related to a problem please describe we re already uploading docs for opo official document list pages and soon we ll want to upload documents for guides describe the solution you d like briaguya stood up a proof of concept of document management on this branch let s review the user experience what works for mvp what doesn t describe alternatives you ve considered additional context add any other context or screenshots about the feature request here | 0 |
203,966 | 23,203,383,681 | IssuesEvent | 2022-08-02 01:03:07 | jgeraigery/Singularity | https://api.github.com/repos/jgeraigery/Singularity | opened | logback-classic-1.2.3.jar: 1 vulnerabilities (highest severity is: 6.6) | security vulnerability | <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>logback-classic-1.2.3.jar</b></p></summary>
<p>logback-classic module</p>
<p>Library home page: <a href="http://logback.qos.ch">http://logback.qos.ch</a></p>
<p>Path to dependency file: /SingularityS3Downloader/pom.xml</p>
<p>Path to vulnerable library: /epository/ch/qos/logback/logback-classic/1.2.3/logback-classic-1.2.3.jar,/epository/ch/qos/logback/logback-classic/1.2.3/logback-classic-1.2.3.jar,/epository/ch/qos/logback/logback-classic/1.2.3/logback-classic-1.2.3.jar,/epository/ch/qos/logback/logback-classic/1.2.3/logback-classic-1.2.3.jar,/epository/ch/qos/logback/logback-classic/1.2.3/logback-classic-1.2.3.jar,/epository/ch/qos/logback/logback-classic/1.2.3/logback-classic-1.2.3.jar,/home/wss-scanner/.m2/repository/ch/qos/logback/logback-classic/1.2.3/logback-classic-1.2.3.jar,/epository/ch/qos/logback/logback-classic/1.2.3/logback-classic-1.2.3.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 | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | --- | --- |
| [CVE-2021-42550](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-42550) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.6 | logback-classic-1.2.3.jar | Direct | 1.2.8 | ✅ |
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2021-42550</summary>
### Vulnerable Library - <b>logback-classic-1.2.3.jar</b></p>
<p>logback-classic module</p>
<p>Library home page: <a href="http://logback.qos.ch">http://logback.qos.ch</a></p>
<p>Path to dependency file: /SingularityS3Downloader/pom.xml</p>
<p>Path to vulnerable library: /epository/ch/qos/logback/logback-classic/1.2.3/logback-classic-1.2.3.jar,/epository/ch/qos/logback/logback-classic/1.2.3/logback-classic-1.2.3.jar,/epository/ch/qos/logback/logback-classic/1.2.3/logback-classic-1.2.3.jar,/epository/ch/qos/logback/logback-classic/1.2.3/logback-classic-1.2.3.jar,/epository/ch/qos/logback/logback-classic/1.2.3/logback-classic-1.2.3.jar,/epository/ch/qos/logback/logback-classic/1.2.3/logback-classic-1.2.3.jar,/home/wss-scanner/.m2/repository/ch/qos/logback/logback-classic/1.2.3/logback-classic-1.2.3.jar,/epository/ch/qos/logback/logback-classic/1.2.3/logback-classic-1.2.3.jar</p>
<p>
Dependency Hierarchy:
- :x: **logback-classic-1.2.3.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In logback version 1.2.7 and prior versions, an attacker with the required privileges to edit configurations files could craft a malicious configuration allowing to execute arbitrary code loaded from LDAP servers.
<p>Publish Date: 2021-12-16
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-42550>CVE-2021-42550</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.6</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- 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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=VE-2021-42550">https://cve.mitre.org/cgi-bin/cvename.cgi?name=VE-2021-42550</a></p>
<p>Release Date: 2021-12-16</p>
<p>Fix Resolution: 1.2.8</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details>
***
<p>:rescue_worker_helmet: Automatic Remediation is available for this issue.</p> | True | logback-classic-1.2.3.jar: 1 vulnerabilities (highest severity is: 6.6) - <details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>logback-classic-1.2.3.jar</b></p></summary>
<p>logback-classic module</p>
<p>Library home page: <a href="http://logback.qos.ch">http://logback.qos.ch</a></p>
<p>Path to dependency file: /SingularityS3Downloader/pom.xml</p>
<p>Path to vulnerable library: /epository/ch/qos/logback/logback-classic/1.2.3/logback-classic-1.2.3.jar,/epository/ch/qos/logback/logback-classic/1.2.3/logback-classic-1.2.3.jar,/epository/ch/qos/logback/logback-classic/1.2.3/logback-classic-1.2.3.jar,/epository/ch/qos/logback/logback-classic/1.2.3/logback-classic-1.2.3.jar,/epository/ch/qos/logback/logback-classic/1.2.3/logback-classic-1.2.3.jar,/epository/ch/qos/logback/logback-classic/1.2.3/logback-classic-1.2.3.jar,/home/wss-scanner/.m2/repository/ch/qos/logback/logback-classic/1.2.3/logback-classic-1.2.3.jar,/epository/ch/qos/logback/logback-classic/1.2.3/logback-classic-1.2.3.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 | Remediation Available |
| ------------- | ------------- | ----- | ----- | ----- | --- | --- |
| [CVE-2021-42550](https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-42550) | <img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Medium | 6.6 | logback-classic-1.2.3.jar | Direct | 1.2.8 | ✅ |
## Details
<details>
<summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> CVE-2021-42550</summary>
### Vulnerable Library - <b>logback-classic-1.2.3.jar</b></p>
<p>logback-classic module</p>
<p>Library home page: <a href="http://logback.qos.ch">http://logback.qos.ch</a></p>
<p>Path to dependency file: /SingularityS3Downloader/pom.xml</p>
<p>Path to vulnerable library: /epository/ch/qos/logback/logback-classic/1.2.3/logback-classic-1.2.3.jar,/epository/ch/qos/logback/logback-classic/1.2.3/logback-classic-1.2.3.jar,/epository/ch/qos/logback/logback-classic/1.2.3/logback-classic-1.2.3.jar,/epository/ch/qos/logback/logback-classic/1.2.3/logback-classic-1.2.3.jar,/epository/ch/qos/logback/logback-classic/1.2.3/logback-classic-1.2.3.jar,/epository/ch/qos/logback/logback-classic/1.2.3/logback-classic-1.2.3.jar,/home/wss-scanner/.m2/repository/ch/qos/logback/logback-classic/1.2.3/logback-classic-1.2.3.jar,/epository/ch/qos/logback/logback-classic/1.2.3/logback-classic-1.2.3.jar</p>
<p>
Dependency Hierarchy:
- :x: **logback-classic-1.2.3.jar** (Vulnerable Library)
<p>Found in base branch: <b>master</b></p>
</p>
<p></p>
### Vulnerability Details
<p>
In logback version 1.2.7 and prior versions, an attacker with the required privileges to edit configurations files could craft a malicious configuration allowing to execute arbitrary code loaded from LDAP servers.
<p>Publish Date: 2021-12-16
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-42550>CVE-2021-42550</a></p>
</p>
<p></p>
### CVSS 3 Score Details (<b>6.6</b>)
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- 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>
<p></p>
### Suggested Fix
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://cve.mitre.org/cgi-bin/cvename.cgi?name=VE-2021-42550">https://cve.mitre.org/cgi-bin/cvename.cgi?name=VE-2021-42550</a></p>
<p>Release Date: 2021-12-16</p>
<p>Fix Resolution: 1.2.8</p>
</p>
<p></p>
:rescue_worker_helmet: Automatic Remediation is available for this issue
</details>
***
<p>:rescue_worker_helmet: Automatic Remediation is available for this issue.</p> | non_priority | logback classic jar vulnerabilities highest severity is vulnerable library logback classic jar logback classic module library home page a href path to dependency file pom xml path to vulnerable library epository ch qos logback logback classic logback classic jar epository ch qos logback logback classic logback classic jar epository ch qos logback logback classic logback classic jar epository ch qos logback logback classic logback classic jar epository ch qos logback logback classic logback classic jar epository ch qos logback logback classic logback classic jar home wss scanner repository ch qos logback logback classic logback classic jar epository ch qos logback logback classic logback classic jar vulnerabilities cve severity cvss dependency type fixed in remediation available medium logback classic jar direct details cve vulnerable library logback classic jar logback classic module library home page a href path to dependency file pom xml path to vulnerable library epository ch qos logback logback classic logback classic jar epository ch qos logback logback classic logback classic jar epository ch qos logback logback classic logback classic jar epository ch qos logback logback classic logback classic jar epository ch qos logback logback classic logback classic jar epository ch qos logback logback classic logback classic jar home wss scanner repository ch qos logback logback classic logback classic jar epository ch qos logback logback classic logback classic jar dependency hierarchy x logback classic jar vulnerable library found in base branch master vulnerability details in logback version and prior versions an attacker with the required privileges to edit configurations files could craft a malicious configuration allowing to execute arbitrary code loaded from ldap servers publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high 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 rescue worker helmet automatic remediation is available for this issue rescue worker helmet automatic remediation is available for this issue | 0 |
393,154 | 26,977,031,613 | IssuesEvent | 2023-02-09 10:18:03 | DD2480-group14/Assignment-2 | https://api.github.com/repos/DD2480-group14/Assignment-2 | closed | Write documentation for Notifier class | documentation | The grader randomly opens application files (not test files) to check that all public classes and methods are well documented, so we need to write somthing. | 1.0 | Write documentation for Notifier class - The grader randomly opens application files (not test files) to check that all public classes and methods are well documented, so we need to write somthing. | non_priority | write documentation for notifier class the grader randomly opens application files not test files to check that all public classes and methods are well documented so we need to write somthing | 0 |
172,705 | 14,379,988,657 | IssuesEvent | 2020-12-02 01:42:05 | codewars/docs | https://api.github.com/repos/codewars/docs | opened | Create HOWTO on adding images to the description | documentation | Motivated by this post: https://www.codewars.com/kata/5fc5e74d8c53ff0027f00ace/discuss#5fc6cac41da1040023327e7d
I prepared some examples here: http://snippi.com/s/g4a6emp
And this kumite: https://www.codewars.com/kumite/5fc6e48caa10e60018543723?sel=5fc6e48caa10e60018543723 but it turns out not to work too well as a presentation of things related to descriptions :(
If you have any ideas what should (or should not) end up in such article, let me know. | 1.0 | Create HOWTO on adding images to the description - Motivated by this post: https://www.codewars.com/kata/5fc5e74d8c53ff0027f00ace/discuss#5fc6cac41da1040023327e7d
I prepared some examples here: http://snippi.com/s/g4a6emp
And this kumite: https://www.codewars.com/kumite/5fc6e48caa10e60018543723?sel=5fc6e48caa10e60018543723 but it turns out not to work too well as a presentation of things related to descriptions :(
If you have any ideas what should (or should not) end up in such article, let me know. | non_priority | create howto on adding images to the description motivated by this post i prepared some examples here and this kumite but it turns out not to work too well as a presentation of things related to descriptions if you have any ideas what should or should not end up in such article let me know | 0 |
519,934 | 15,075,203,572 | IssuesEvent | 2021-02-05 01:30:45 | ossia/libossia | https://api.github.com/repos/ossia/libossia | closed | [ossia-max] dynamic address fail in nested models | bug ossia-max priority::high | Example showing wrong model's address incrementation and parent prefix in nested models.
Open testing-ossia-devices.maxpat.
Tested with build c20ef116
[Archive.zip](https://github.com/ossia/libossia/files/5925824/Archive.zip)
| 1.0 | [ossia-max] dynamic address fail in nested models - Example showing wrong model's address incrementation and parent prefix in nested models.
Open testing-ossia-devices.maxpat.
Tested with build c20ef116
[Archive.zip](https://github.com/ossia/libossia/files/5925824/Archive.zip)
| priority | dynamic address fail in nested models example showing wrong model s address incrementation and parent prefix in nested models open testing ossia devices maxpat tested with build | 1 |
294,515 | 22,154,125,587 | IssuesEvent | 2022-06-03 20:17:06 | JhericoS/TF-201920341-201920431-202019644 | https://api.github.com/repos/JhericoS/TF-201920341-201920431-202019644 | opened | Hito 2 - actividad a b c (general ) | documentation | a. Actividades relacionadas a agregar información adicional al grafo como coordenadas
de intersecciones, información de tráfico por hora de calles o segmentos de calle.
b. Actividades de implementación de algoritmo de cálculo de peso de arista en función
de su longitud y factor de tráfico calculado.
c. Actividades de implementación de algoritmos para actualizar pesos de aristas en
función a la hora del día. | 1.0 | Hito 2 - actividad a b c (general ) - a. Actividades relacionadas a agregar información adicional al grafo como coordenadas
de intersecciones, información de tráfico por hora de calles o segmentos de calle.
b. Actividades de implementación de algoritmo de cálculo de peso de arista en función
de su longitud y factor de tráfico calculado.
c. Actividades de implementación de algoritmos para actualizar pesos de aristas en
función a la hora del día. | non_priority | hito actividad a b c general a actividades relacionadas a agregar información adicional al grafo como coordenadas de intersecciones información de tráfico por hora de calles o segmentos de calle b actividades de implementación de algoritmo de cálculo de peso de arista en función de su longitud y factor de tráfico calculado c actividades de implementación de algoritmos para actualizar pesos de aristas en función a la hora del día | 0 |
497,968 | 14,398,128,452 | IssuesEvent | 2020-12-03 09:11:09 | pingcap/tispark | https://api.github.com/repos/pingcap/tispark | closed | [BUG] count(*) doesn't return number of retrieved rows containing null | priority/P0 type/bug | **Describe the bug**
<!-- A clear and concise description of what the bug is. -->
count(*) doesn't return number of retrieved rows containing null
**What did you do**
<!--
If possible, please provide a code receipt to produce this issue.
e.g.,
1. run `spark-shell --jars xxx.jar`
2. in spark-shell, run
```
val df = spark.sql(“select sum(b) from t where a = 1”)
df.show(20)
```
3. update some data through TiDB
4. in spark-shell, run
```
val df = spark.sql(“select sum(b) from t where a = 1”)
df.show(20)
```
-->
1. execute in tidb
```sql
create table t1(a int,b char(2),c enum('a','b','c'),d datetime)
insert into t1 values(10,'1','c','2020-10-10')
insert into t1 values(9,'1ࠀ','b','2020-10-10')
insert into t1 values(9,'15','b','2020-10-10')
insert into t1 values(9,'1🧑','b','2020-10-10')
insert into t1 values(null,'0','b','2020-10-10')
insert into t1 values(null,'-','b','2020-10-10')
insert into t1 values(null,null,'b','2021-10-10')
insert into t1 values(0,'1ࠏ','b','2020-10-09')'
```
2. execute in tispark
select count(*) from t1
**What do you expect**
<!-- A clear and concise description of what you expected to happen. -->
8
**What happens instead**
<!-- If an error occurs, please provide complete error stack. -->
<!--
**Screenshots**
If applicable, add screenshots to help explain your problem.
-->
5
**Spark and TiSpark version info**
<!-- What version of Spark and TiSpark are you using? (Provide Spark version and run `spark.sql(“select ti_version()”).show(false)` in spark-shell) -->
<!--
**Additional context**
Add any other context about the problem here.
You may also provide TiDB version here if it is related to the issue.
-->
Git Commit Hash: 8ed90eddf872734950321728a966e5bf7a9d5ad3
Git Branch: release-2.3
UTC Build Time: 2020-11-06 06:28:01
Supported Spark Version: 2.3 2.4
Current Spark Version: 2.4.3
Current Spark Major Version: 2.4
TimeZone: Asia/Shanghai
tidb: release-4.0 | 1.0 | [BUG] count(*) doesn't return number of retrieved rows containing null - **Describe the bug**
<!-- A clear and concise description of what the bug is. -->
count(*) doesn't return number of retrieved rows containing null
**What did you do**
<!--
If possible, please provide a code receipt to produce this issue.
e.g.,
1. run `spark-shell --jars xxx.jar`
2. in spark-shell, run
```
val df = spark.sql(“select sum(b) from t where a = 1”)
df.show(20)
```
3. update some data through TiDB
4. in spark-shell, run
```
val df = spark.sql(“select sum(b) from t where a = 1”)
df.show(20)
```
-->
1. execute in tidb
```sql
create table t1(a int,b char(2),c enum('a','b','c'),d datetime)
insert into t1 values(10,'1','c','2020-10-10')
insert into t1 values(9,'1ࠀ','b','2020-10-10')
insert into t1 values(9,'15','b','2020-10-10')
insert into t1 values(9,'1🧑','b','2020-10-10')
insert into t1 values(null,'0','b','2020-10-10')
insert into t1 values(null,'-','b','2020-10-10')
insert into t1 values(null,null,'b','2021-10-10')
insert into t1 values(0,'1ࠏ','b','2020-10-09')'
```
2. execute in tispark
select count(*) from t1
**What do you expect**
<!-- A clear and concise description of what you expected to happen. -->
8
**What happens instead**
<!-- If an error occurs, please provide complete error stack. -->
<!--
**Screenshots**
If applicable, add screenshots to help explain your problem.
-->
5
**Spark and TiSpark version info**
<!-- What version of Spark and TiSpark are you using? (Provide Spark version and run `spark.sql(“select ti_version()”).show(false)` in spark-shell) -->
<!--
**Additional context**
Add any other context about the problem here.
You may also provide TiDB version here if it is related to the issue.
-->
Git Commit Hash: 8ed90eddf872734950321728a966e5bf7a9d5ad3
Git Branch: release-2.3
UTC Build Time: 2020-11-06 06:28:01
Supported Spark Version: 2.3 2.4
Current Spark Version: 2.4.3
Current Spark Major Version: 2.4
TimeZone: Asia/Shanghai
tidb: release-4.0 | priority | count doesn t return number of retrieved rows containing null describe the bug count doesn t return number of retrieved rows containing null what did you do if possible please provide a code receipt to produce this issue e g run spark shell jars xxx jar in spark shell run val df spark sql “select sum b from t where a ” df show update some data through tidb in spark shell run val df spark sql “select sum b from t where a ” df show execute in tidb sql create table a int b char c enum a b c d datetime insert into values c insert into values b insert into values b insert into values 🧑 b insert into values null b insert into values null b insert into values null null b insert into values b execute in tispark select count from what do you expect what happens instead screenshots if applicable add screenshots to help explain your problem spark and tispark version info additional context add any other context about the problem here you may also provide tidb version here if it is related to the issue git commit hash git branch release utc build time supported spark version current spark version current spark major version timezone asia shanghai tidb release | 1 |
98,870 | 20,816,036,156 | IssuesEvent | 2022-03-18 10:22:49 | DD2480-Group-19/CI-LabMakeUp | https://api.github.com/repos/DD2480-Group-19/CI-LabMakeUp | closed | Branch assessment # Code | documentation Code Writing | - [x] Property (core CI feature #1 - compilation): the CI server supports compiling the group project, a static syntax check is to be performed for languages without compiler. Compilation is triggered as webhook, the CI server compiles the branch where the change has been made, as specified in the HTTP payload.
- [x] the students prepare a specific branch called "assessment" (not "master"). The students document in the README how compilation has been implemented and unit-tested. | 1.0 | Branch assessment # Code - - [x] Property (core CI feature #1 - compilation): the CI server supports compiling the group project, a static syntax check is to be performed for languages without compiler. Compilation is triggered as webhook, the CI server compiles the branch where the change has been made, as specified in the HTTP payload.
- [x] the students prepare a specific branch called "assessment" (not "master"). The students document in the README how compilation has been implemented and unit-tested. | non_priority | branch assessment code property core ci feature compilation the ci server supports compiling the group project a static syntax check is to be performed for languages without compiler compilation is triggered as webhook the ci server compiles the branch where the change has been made as specified in the http payload the students prepare a specific branch called assessment not master the students document in the readme how compilation has been implemented and unit tested | 0 |
328,879 | 10,001,033,205 | IssuesEvent | 2019-07-12 14:43:35 | wazuh/wazuh-kibana-app | https://api.github.com/repos/wazuh/wazuh-kibana-app | closed | Wazuh app doesn't open under custom spaces | bug community delayed priority/medium | As you know, 6.x introduced spaces as a way to manage collections of visualization, dashboards, etc. Selecting a custom space, and trying to open the wazuh app yields a blank screen. See screenshot below.
Wazuh 3.7.2 + Kibana 6.5.4
| 1.0 | Wazuh app doesn't open under custom spaces - As you know, 6.x introduced spaces as a way to manage collections of visualization, dashboards, etc. Selecting a custom space, and trying to open the wazuh app yields a blank screen. See screenshot below.
Wazuh 3.7.2 + Kibana 6.5.4
| priority | wazuh app doesn t open under custom spaces as you know x introduced spaces as a way to manage collections of visualization dashboards etc selecting a custom space and trying to open the wazuh app yields a blank screen see screenshot below wazuh kibana | 1 |
713,597 | 24,532,669,788 | IssuesEvent | 2022-10-11 17:49:23 | googleapis/java-logging-logback | https://api.github.com/repos/googleapis/java-logging-logback | closed | Size of the dependencies - all really required ? | priority: p2 type: question api: logging | We want to implement the GLogging appender for `java.util.logging handler` in a legacy j2ee app - read, no code change.
However, due to the additional dependencies, our `war` web container has doubled in size !
Looking at the below, there are 2 libraries related to `grpc` which have excessive sizes compared to the feature we want to implement, namely:
1. compress log
2. send it through `http`
None require additional dependencies.
Can these libs be safely removed - without trial and error ?
If not, do stripped versions exist to only support the appender ?
Thanks ! | 1.0 | Size of the dependencies - all really required ? - We want to implement the GLogging appender for `java.util.logging handler` in a legacy j2ee app - read, no code change.
However, due to the additional dependencies, our `war` web container has doubled in size !
Looking at the below, there are 2 libraries related to `grpc` which have excessive sizes compared to the feature we want to implement, namely:
1. compress log
2. send it through `http`
None require additional dependencies.
Can these libs be safely removed - without trial and error ?
If not, do stripped versions exist to only support the appender ?
Thanks ! | priority | size of the dependencies all really required we want to implement the glogging appender for java util logging handler in a legacy app read no code change however due to the additional dependencies our war web container has doubled in size looking at the below there are libraries related to grpc which have excessive sizes compared to the feature we want to implement namely compress log send it through http none require additional dependencies can these libs be safely removed without trial and error if not do stripped versions exist to only support the appender thanks | 1 |
126,185 | 17,869,386,174 | IssuesEvent | 2021-09-06 13:34:37 | fasttrack-solutions/terraform-provider-kubernetes | https://api.github.com/repos/fasttrack-solutions/terraform-provider-kubernetes | opened | CVE-2021-3121 (High) detected in github.com/gogo/protobuf-v1.2.0 | security vulnerability | ## CVE-2021-3121 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>github.com/gogo/protobuf-v1.2.0</b></p></summary>
<p>Protocol Buffers for Go with Gadgets</p>
<p>
Dependency Hierarchy:
- github.com/kubernetes/client-go-v10.0.0 (Root Library)
- :x: **github.com/gogo/protobuf-v1.2.0** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/fasttrack-solutions/terraform-provider-kubernetes/commit/07e1540f8f53e83e2cde9ba285dcc711789744ca">07e1540f8f53e83e2cde9ba285dcc711789744ca</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>
An issue was discovered in GoGo Protobuf before 1.3.2. plugin/unmarshal/unmarshal.go lacks certain index validation, aka the "skippy peanut butter" issue.
<p>Publish Date: 2021-01-11
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-3121>CVE-2021-3121</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.6</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: 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-3121">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3121</a></p>
<p>Release Date: 2021-01-11</p>
<p>Fix Resolution: v1.3.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-2021-3121 (High) detected in github.com/gogo/protobuf-v1.2.0 - ## CVE-2021-3121 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>github.com/gogo/protobuf-v1.2.0</b></p></summary>
<p>Protocol Buffers for Go with Gadgets</p>
<p>
Dependency Hierarchy:
- github.com/kubernetes/client-go-v10.0.0 (Root Library)
- :x: **github.com/gogo/protobuf-v1.2.0** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/fasttrack-solutions/terraform-provider-kubernetes/commit/07e1540f8f53e83e2cde9ba285dcc711789744ca">07e1540f8f53e83e2cde9ba285dcc711789744ca</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>
An issue was discovered in GoGo Protobuf before 1.3.2. plugin/unmarshal/unmarshal.go lacks certain index validation, aka the "skippy peanut butter" issue.
<p>Publish Date: 2021-01-11
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-3121>CVE-2021-3121</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.6</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: 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-3121">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-3121</a></p>
<p>Release Date: 2021-01-11</p>
<p>Fix Resolution: v1.3.2</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in github com gogo protobuf cve high severity vulnerability vulnerable library github com gogo protobuf protocol buffers for go with gadgets dependency hierarchy github com kubernetes client go root library x github com gogo protobuf vulnerable library found in head commit a href found in base branch master vulnerability details an issue was discovered in gogo protobuf before plugin unmarshal unmarshal go lacks certain index validation aka the skippy peanut butter issue 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 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 |
397,708 | 27,174,511,965 | IssuesEvent | 2023-02-17 23:11:51 | MFlowCode/MFC | https://api.github.com/repos/MFlowCode/MFC | closed | Document undocumented patches | documentation good first issue | Currently, patch types 14 to 19 are undocumented and they perhaps should be.
While on the topic, wouldn't it be clearer if each patch type had its own derived type within `patch_icpp(i)`? For example, an STL patch (#83) could be defined as:
```
patch_icpp(2)%geometry: 20,
patch_icpp(2)%stl%filepath: 'path/to/stl/file`,
patch_icpp(2)%stl%scale(2): 1.0,
patch_icpp(2)%stl%offset(3): 0.25,
```
This, in a sense, self-documents what properties each patch type can have. Every attribute that is common to all patches would be in the base `patch_icpp(i)%` scope. | 1.0 | Document undocumented patches - Currently, patch types 14 to 19 are undocumented and they perhaps should be.
While on the topic, wouldn't it be clearer if each patch type had its own derived type within `patch_icpp(i)`? For example, an STL patch (#83) could be defined as:
```
patch_icpp(2)%geometry: 20,
patch_icpp(2)%stl%filepath: 'path/to/stl/file`,
patch_icpp(2)%stl%scale(2): 1.0,
patch_icpp(2)%stl%offset(3): 0.25,
```
This, in a sense, self-documents what properties each patch type can have. Every attribute that is common to all patches would be in the base `patch_icpp(i)%` scope. | non_priority | document undocumented patches currently patch types to are undocumented and they perhaps should be while on the topic wouldn t it be clearer if each patch type had its own derived type within patch icpp i for example an stl patch could be defined as patch icpp geometry patch icpp stl filepath path to stl file patch icpp stl scale patch icpp stl offset this in a sense self documents what properties each patch type can have every attribute that is common to all patches would be in the base patch icpp i scope | 0 |
42,119 | 17,037,140,142 | IssuesEvent | 2021-07-05 08:40:11 | Azure/azure-powershell | https://api.github.com/repos/Azure/azure-powershell | reopened | Random Failure in Test-UpdateExchangeIPv6OnResourceId | Engineering Peering Service Attention | ## Description
The random failure happens to the following line in the function of Test-UpdateExchangeIPv6OnResourceId
`$newipv6 = getPeeringVariable "newIpv6" (newIpV6Address $true $false 0 (getRandomNumber))`
```
function Test-UpdateExchangeIPv6OnResourceId {
# Hard coded name because the resource has to exist and cant be created ad-hoc.
$randNum = getRandomNumber
Write-Debug "Random Number $randNum";
$peerAsn = makePeerAsn $randNum
$resourceGroups = TestSetup-CreateResourceGroup
$resourceGroup = $resourceGroups.ResourceGroupName
$peering = CreateExchangePeering $resourceGroup $peerAsn.Name
Assert-NotNull $peering
$newipv6 = getPeeringVariable "newIpv6" (newIpV6Address $true $false 0 (getRandomNumber))
$oldpeering = $peering
$peering.Connections[0] = $peering.Connections[0] | Set-AzPeeringExchangeConnectionObject -PeerSessionIPv6Address $newipv6
Write-Debug $peering.Name
Assert-ThrowsContains { $update = Update-AzPeering -ResourceId $peering.Id $peering.Connections } "BadArgument"
}
```
Error log of the test case
```
2021-07-05T06:09:53.5146016Z [xUnit.net 00:00:12.12] Microsoft.Azure.Commands.Peering.Test.ScenarioTests.ScenarioExchangePeeringTests.TestUpdateExchangeIPv6OnResourceId [FAIL]
2021-07-05T06:09:55.5249232Z X Microsoft.Azure.Commands.Peering.Test.ScenarioTests.ScenarioExchangePeeringTests.TestUpdateExchangeIPv6OnResourceId [664ms]
2021-07-05T06:09:55.5250417Z EXEC : error Message: [/home/vsts/work/1/s/build.proj]
2021-07-05T06:09:55.5252358Z System.Management.Automation.MethodInvocationException : Exception calling "OffSet" with "4" argument(s): "An invalid IP address was specified.
2021-07-05T06:09:55.5253634Z Parameter name: address"
2021-07-05T06:09:55.5255295Z ---- System.ArgumentException : An invalid IP address was specified.
2021-07-05T06:09:55.5256365Z Parameter name: address
2021-07-05T06:09:55.5256924Z Stack Trace:
2021-07-05T06:09:55.5257521Z at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)
2021-07-05T06:09:55.5258145Z at System.Management.Automation.Runspaces.Pipeline.Invoke()
2021-07-05T06:09:55.5258832Z at System.Management.Automation.PowerShell.Worker.ConstructPipelineAndDoWork(Runspace rs, Boolean performSyncInvoke)
2021-07-05T06:09:55.5259599Z at System.Management.Automation.PowerShell.Worker.CreateRunspaceIfNeededAndDoWork(Runspace rsToUse, Boolean isSync)
2021-07-05T06:09:55.5260401Z at System.Management.Automation.PowerShell.CoreInvokeHelper[TInput,TOutput](PSDataCollection`1 input, PSDataCollection`1 output, PSInvocationSettings settings)
2021-07-05T06:09:55.5261768Z at System.Management.Automation.PowerShell.CoreInvoke[TInput,TOutput](PSDataCollection`1 input, PSDataCollection`1 output, PSInvocationSettings settings)
2021-07-05T06:09:55.5263472Z at System.Management.Automation.PowerShell.CoreInvoke[TOutput](IEnumerable input, PSDataCollection`1 output, PSInvocationSettings settings)
2021-07-05T06:09:55.5282051Z at System.Management.Automation.PowerShell.Invoke(IEnumerable input, PSInvocationSettings settings)
2021-07-05T06:09:55.5283658Z at System.Management.Automation.PowerShell.Invoke()
2021-07-05T06:09:55.5285554Z at Microsoft.WindowsAzure.Commands.ScenarioTest.EnvironmentSetupHelper.RunPowerShellTest(String[] scripts) in /home/vsts/work/1/s/tools/ScenarioTest.ResourceManager/EnvironmentSetupHelper.cs:line 573
2021-07-05T06:09:55.5287538Z at Microsoft.Azure.Commands.Peering.Test.ScenarioTests.TestController.RunPsTestWorkflow(Func`1 scriptBuilder, Action cleanup, String callingClassType, String mockName) in /home/vsts/work/1/s/src/Peering/Peering.Test/ScenarioTests/TestController.cs:line 120
2021-07-05T06:09:55.5296662Z at Microsoft.Azure.Commands.Peering.Test.ScenarioTests.TestController.RunPowerShellTest(XunitTracingInterceptor logger, String[] scripts) in /home/vsts/work/1/s/src/Peering/Peering.Test/ScenarioTests/TestController.cs:line 70
2021-07-05T06:09:55.5299074Z at Microsoft.Azure.Commands.Peering.Test.ScenarioTests.ScenarioExchangePeeringTests.TestUpdateExchangeIPv6OnResourceId() in /home/vsts/work/1/s/src/Peering/Peering.Test/ScenarioTests/ScenarioExchangePeeringTests.cs:line 67
2021-07-05T06:09:55.5301897Z ----- Inner Stack Trace -----
2021-07-05T06:09:55.5303883Z at System.Net.IPAddress..ctor(ReadOnlySpan`1 address)
2021-07-05T06:09:55.5305966Z at System.Net.IPAddress..ctor(Byte[] address)
2021-07-05T06:09:55.5307651Z at Microsoft.Azure.PowerShell.Cmdlets.Peering.Common.HelperExtensionMethods.ToIpAddress(BigInteger self, AddressFamily addressFamily) in /home/vsts/work/1/s/src/Peering/Peering/Common/HelperExtensionMethods.cs:line 91
2021-07-05T06:09:55.5309312Z at Microsoft.Azure.Commands.Peering.Test.ScenarioTests.IPGenerator.OffSet(String ipAddress, Boolean v6, Int32 offset, Boolean hasPrefix) in /home/vsts/work/1/s/src/Peering/Peering.Test/ScenarioTests/IPGenerator.cs:line 65
2021-07-05T06:09:55.5317364Z at CallSite.Target(Closure , CallSite , Object , Object , Boolean , Object , Object )
2021-07-05T06:09:55.5317856Z Standard Output Messages:
2021-07-05T06:09:55.5318401Z Test-UpdateExchangeIPv6OnResourceId
2021-07-05T06:09:55.5318937Z Caught Exception: System.Management.Automation.MethodInvocationException: Exception calling "OffSet" with "4" argument(s): "An invalid IP address was specified.
2021-07-05T06:09:55.5319716Z Parameter name: address" ---> System.ArgumentException: An invalid IP address was specified.
2021-07-05T06:09:55.5320102Z Parameter name: address
2021-07-05T06:09:55.5320408Z at System.Net.IPAddress..ctor(ReadOnlySpan`1 address)
2021-07-05T06:09:55.5320886Z at System.Net.IPAddress..ctor(Byte[] address)
2021-07-05T06:09:55.5321611Z at Microsoft.Azure.PowerShell.Cmdlets.Peering.Common.HelperExtensionMethods.ToIpAddress(BigInteger self, AddressFamily addressFamily) in /home/vsts/work/1/s/src/Peering/Peering/Common/HelperExtensionMethods.cs:line 91
2021-07-05T06:09:55.5322394Z at Microsoft.Azure.Commands.Peering.Test.ScenarioTests.IPGenerator.OffSet(String ipAddress, Boolean v6, Int32 offset, Boolean hasPrefix) in /home/vsts/work/1/s/src/Peering/Peering.Test/ScenarioTests/IPGenerator.cs:line 65
2021-07-05T06:09:55.5323089Z at CallSite.Target(Closure , CallSite , Object , Object , Boolean , Object , Object )
2021-07-05T06:09:55.5323741Z --- End of inner exception stack trace ---
2021-07-05T06:09:55.5324242Z at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)
2021-07-05T06:09:55.5325008Z at System.Management.Automation.Runspaces.Pipeline.Invoke()
2021-07-05T06:09:55.5325463Z at System.Management.Automation.PowerShell.Worker.ConstructPipelineAndDoWork(Runspace rs, Boolean performSyncInvoke)
2021-07-05T06:09:55.5325953Z at System.Management.Automation.PowerShell.Worker.CreateRunspaceIfNeededAndDoWork(Runspace rsToUse, Boolean isSync)
2021-07-05T06:09:55.5326637Z at System.Management.Automation.PowerShell.CoreInvokeHelper[TInput,TOutput](PSDataCollection`1 input, PSDataCollection`1 output, PSInvocationSettings settings)
2021-07-05T06:09:55.5327289Z at System.Management.Automation.PowerShell.CoreInvoke[TInput,TOutput](PSDataCollection`1 input, PSDataCollection`1 output, PSInvocationSettings settings)
2021-07-05T06:09:55.5327863Z at System.Management.Automation.PowerShell.CoreInvoke[TOutput](IEnumerable input, PSDataCollection`1 output, PSInvocationSettings settings)
2021-07-05T06:09:55.5328391Z at System.Management.Automation.PowerShell.Invoke(IEnumerable input, PSInvocationSettings settings)
2021-07-05T06:09:55.5328821Z at System.Management.Automation.PowerShell.Invoke()
2021-07-05T06:09:55.5329345Z at Microsoft.WindowsAzure.Commands.ScenarioTest.EnvironmentSetupHelper.RunPowerShellTest(String[] scripts) in /home/vsts/work/1/s/tools/ScenarioTest.ResourceManager/EnvironmentSetupHelper.cs:line 573
2021-07-05T06:09:55.5329962Z Message: Exception calling "OffSet" with "4" argument(s): "An invalid IP address was specified.
2021-07-05T06:09:55.5330531Z Parameter name: address"
2021-07-05T06:09:55.5331588Z EXEC : PowerShell error Record: Exception calling "OffSet" with "4" argument(s): "An invalid IP address was specified. [/home/vsts/work/1/s/build.proj]
2021-07-05T06:09:55.5332347Z Parameter name: address"
2021-07-05T06:09:55.5333043Z Exception:System.Management.Automation.ParentContainsErrorRecordException: Exception calling "OffSet" with "4" argument(s): "An invalid IP address was specified.
2021-07-05T06:09:55.5333669Z Parameter name: address"
2021-07-05T06:09:55.5334022Z Details:
2021-07-05T06:09:55.5334539Z Script Stack Trace: at newIpV6Address, /home/vsts/work/1/s/src/Peering/Peering.Test/bin/Debug/netcoreapp2.1/ScenarioTests/PeeringCommon.ps1: line 52
2021-07-05T06:09:55.5336204Z at Test-UpdateExchangeIPv6OnResourceId, /home/vsts/work/1/s/src/Peering/Peering.Test/bin/Debug/netcoreapp2.1/ScenarioTests/ScenarioExchangePeeringTests.ps1: line 50
2021-07-05T06:09:55.5336776Z at <ScriptBlock>, <No file>: line 1
2021-07-05T06:09:55.5337089Z : Target:
2021-07-05T06:09:55.5337354Z
2021-07-05T06:09:55.5337687Z Caught Exception: System.ArgumentException: An invalid IP address was specified.
2021-07-05T06:09:55.5338073Z Parameter name: address
2021-07-05T06:09:55.5338403Z at System.Net.IPAddress..ctor(ReadOnlySpan`1 address)
2021-07-05T06:09:55.5338771Z at System.Net.IPAddress..ctor(Byte[] address)
2021-07-05T06:09:55.5339305Z at Microsoft.Azure.PowerShell.Cmdlets.Peering.Common.HelperExtensionMethods.ToIpAddress(BigInteger self, AddressFamily addressFamily) in /home/vsts/work/1/s/src/Peering/Peering/Common/HelperExtensionMethods.cs:line 91
2021-07-05T06:09:55.5340529Z at Microsoft.Azure.Commands.Peering.Test.ScenarioTests.IPGenerator.OffSet(String ipAddress, Boolean v6, Int32 offset, Boolean hasPrefix) in /home/vsts/work/1/s/src/Peering/Peering.Test/ScenarioTests/IPGenerator.cs:line 65
2021-07-05T06:09:55.5431677Z at CallSite.Target(Closure , CallSite , Object , Object , Boolean , Object , Object )
2021-07-05T06:09:55.5432485Z Message: An invalid IP address was specified.
2021-07-05T06:09:55.5433058Z Parameter name: address
```
https://dev.azure.com/azure-sdk/public/_build/results?buildId=983143&view=logs&j=ad07b744-5a1a-5d54-7693-fcb02e666633&t=b0841cae-a6b1-5a5c-4ebd-3cc6b3d3163d
## Cost
| 1.0 | Random Failure in Test-UpdateExchangeIPv6OnResourceId - ## Description
The random failure happens to the following line in the function of Test-UpdateExchangeIPv6OnResourceId
`$newipv6 = getPeeringVariable "newIpv6" (newIpV6Address $true $false 0 (getRandomNumber))`
```
function Test-UpdateExchangeIPv6OnResourceId {
# Hard coded name because the resource has to exist and cant be created ad-hoc.
$randNum = getRandomNumber
Write-Debug "Random Number $randNum";
$peerAsn = makePeerAsn $randNum
$resourceGroups = TestSetup-CreateResourceGroup
$resourceGroup = $resourceGroups.ResourceGroupName
$peering = CreateExchangePeering $resourceGroup $peerAsn.Name
Assert-NotNull $peering
$newipv6 = getPeeringVariable "newIpv6" (newIpV6Address $true $false 0 (getRandomNumber))
$oldpeering = $peering
$peering.Connections[0] = $peering.Connections[0] | Set-AzPeeringExchangeConnectionObject -PeerSessionIPv6Address $newipv6
Write-Debug $peering.Name
Assert-ThrowsContains { $update = Update-AzPeering -ResourceId $peering.Id $peering.Connections } "BadArgument"
}
```
Error log of the test case
```
2021-07-05T06:09:53.5146016Z [xUnit.net 00:00:12.12] Microsoft.Azure.Commands.Peering.Test.ScenarioTests.ScenarioExchangePeeringTests.TestUpdateExchangeIPv6OnResourceId [FAIL]
2021-07-05T06:09:55.5249232Z X Microsoft.Azure.Commands.Peering.Test.ScenarioTests.ScenarioExchangePeeringTests.TestUpdateExchangeIPv6OnResourceId [664ms]
2021-07-05T06:09:55.5250417Z EXEC : error Message: [/home/vsts/work/1/s/build.proj]
2021-07-05T06:09:55.5252358Z System.Management.Automation.MethodInvocationException : Exception calling "OffSet" with "4" argument(s): "An invalid IP address was specified.
2021-07-05T06:09:55.5253634Z Parameter name: address"
2021-07-05T06:09:55.5255295Z ---- System.ArgumentException : An invalid IP address was specified.
2021-07-05T06:09:55.5256365Z Parameter name: address
2021-07-05T06:09:55.5256924Z Stack Trace:
2021-07-05T06:09:55.5257521Z at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)
2021-07-05T06:09:55.5258145Z at System.Management.Automation.Runspaces.Pipeline.Invoke()
2021-07-05T06:09:55.5258832Z at System.Management.Automation.PowerShell.Worker.ConstructPipelineAndDoWork(Runspace rs, Boolean performSyncInvoke)
2021-07-05T06:09:55.5259599Z at System.Management.Automation.PowerShell.Worker.CreateRunspaceIfNeededAndDoWork(Runspace rsToUse, Boolean isSync)
2021-07-05T06:09:55.5260401Z at System.Management.Automation.PowerShell.CoreInvokeHelper[TInput,TOutput](PSDataCollection`1 input, PSDataCollection`1 output, PSInvocationSettings settings)
2021-07-05T06:09:55.5261768Z at System.Management.Automation.PowerShell.CoreInvoke[TInput,TOutput](PSDataCollection`1 input, PSDataCollection`1 output, PSInvocationSettings settings)
2021-07-05T06:09:55.5263472Z at System.Management.Automation.PowerShell.CoreInvoke[TOutput](IEnumerable input, PSDataCollection`1 output, PSInvocationSettings settings)
2021-07-05T06:09:55.5282051Z at System.Management.Automation.PowerShell.Invoke(IEnumerable input, PSInvocationSettings settings)
2021-07-05T06:09:55.5283658Z at System.Management.Automation.PowerShell.Invoke()
2021-07-05T06:09:55.5285554Z at Microsoft.WindowsAzure.Commands.ScenarioTest.EnvironmentSetupHelper.RunPowerShellTest(String[] scripts) in /home/vsts/work/1/s/tools/ScenarioTest.ResourceManager/EnvironmentSetupHelper.cs:line 573
2021-07-05T06:09:55.5287538Z at Microsoft.Azure.Commands.Peering.Test.ScenarioTests.TestController.RunPsTestWorkflow(Func`1 scriptBuilder, Action cleanup, String callingClassType, String mockName) in /home/vsts/work/1/s/src/Peering/Peering.Test/ScenarioTests/TestController.cs:line 120
2021-07-05T06:09:55.5296662Z at Microsoft.Azure.Commands.Peering.Test.ScenarioTests.TestController.RunPowerShellTest(XunitTracingInterceptor logger, String[] scripts) in /home/vsts/work/1/s/src/Peering/Peering.Test/ScenarioTests/TestController.cs:line 70
2021-07-05T06:09:55.5299074Z at Microsoft.Azure.Commands.Peering.Test.ScenarioTests.ScenarioExchangePeeringTests.TestUpdateExchangeIPv6OnResourceId() in /home/vsts/work/1/s/src/Peering/Peering.Test/ScenarioTests/ScenarioExchangePeeringTests.cs:line 67
2021-07-05T06:09:55.5301897Z ----- Inner Stack Trace -----
2021-07-05T06:09:55.5303883Z at System.Net.IPAddress..ctor(ReadOnlySpan`1 address)
2021-07-05T06:09:55.5305966Z at System.Net.IPAddress..ctor(Byte[] address)
2021-07-05T06:09:55.5307651Z at Microsoft.Azure.PowerShell.Cmdlets.Peering.Common.HelperExtensionMethods.ToIpAddress(BigInteger self, AddressFamily addressFamily) in /home/vsts/work/1/s/src/Peering/Peering/Common/HelperExtensionMethods.cs:line 91
2021-07-05T06:09:55.5309312Z at Microsoft.Azure.Commands.Peering.Test.ScenarioTests.IPGenerator.OffSet(String ipAddress, Boolean v6, Int32 offset, Boolean hasPrefix) in /home/vsts/work/1/s/src/Peering/Peering.Test/ScenarioTests/IPGenerator.cs:line 65
2021-07-05T06:09:55.5317364Z at CallSite.Target(Closure , CallSite , Object , Object , Boolean , Object , Object )
2021-07-05T06:09:55.5317856Z Standard Output Messages:
2021-07-05T06:09:55.5318401Z Test-UpdateExchangeIPv6OnResourceId
2021-07-05T06:09:55.5318937Z Caught Exception: System.Management.Automation.MethodInvocationException: Exception calling "OffSet" with "4" argument(s): "An invalid IP address was specified.
2021-07-05T06:09:55.5319716Z Parameter name: address" ---> System.ArgumentException: An invalid IP address was specified.
2021-07-05T06:09:55.5320102Z Parameter name: address
2021-07-05T06:09:55.5320408Z at System.Net.IPAddress..ctor(ReadOnlySpan`1 address)
2021-07-05T06:09:55.5320886Z at System.Net.IPAddress..ctor(Byte[] address)
2021-07-05T06:09:55.5321611Z at Microsoft.Azure.PowerShell.Cmdlets.Peering.Common.HelperExtensionMethods.ToIpAddress(BigInteger self, AddressFamily addressFamily) in /home/vsts/work/1/s/src/Peering/Peering/Common/HelperExtensionMethods.cs:line 91
2021-07-05T06:09:55.5322394Z at Microsoft.Azure.Commands.Peering.Test.ScenarioTests.IPGenerator.OffSet(String ipAddress, Boolean v6, Int32 offset, Boolean hasPrefix) in /home/vsts/work/1/s/src/Peering/Peering.Test/ScenarioTests/IPGenerator.cs:line 65
2021-07-05T06:09:55.5323089Z at CallSite.Target(Closure , CallSite , Object , Object , Boolean , Object , Object )
2021-07-05T06:09:55.5323741Z --- End of inner exception stack trace ---
2021-07-05T06:09:55.5324242Z at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)
2021-07-05T06:09:55.5325008Z at System.Management.Automation.Runspaces.Pipeline.Invoke()
2021-07-05T06:09:55.5325463Z at System.Management.Automation.PowerShell.Worker.ConstructPipelineAndDoWork(Runspace rs, Boolean performSyncInvoke)
2021-07-05T06:09:55.5325953Z at System.Management.Automation.PowerShell.Worker.CreateRunspaceIfNeededAndDoWork(Runspace rsToUse, Boolean isSync)
2021-07-05T06:09:55.5326637Z at System.Management.Automation.PowerShell.CoreInvokeHelper[TInput,TOutput](PSDataCollection`1 input, PSDataCollection`1 output, PSInvocationSettings settings)
2021-07-05T06:09:55.5327289Z at System.Management.Automation.PowerShell.CoreInvoke[TInput,TOutput](PSDataCollection`1 input, PSDataCollection`1 output, PSInvocationSettings settings)
2021-07-05T06:09:55.5327863Z at System.Management.Automation.PowerShell.CoreInvoke[TOutput](IEnumerable input, PSDataCollection`1 output, PSInvocationSettings settings)
2021-07-05T06:09:55.5328391Z at System.Management.Automation.PowerShell.Invoke(IEnumerable input, PSInvocationSettings settings)
2021-07-05T06:09:55.5328821Z at System.Management.Automation.PowerShell.Invoke()
2021-07-05T06:09:55.5329345Z at Microsoft.WindowsAzure.Commands.ScenarioTest.EnvironmentSetupHelper.RunPowerShellTest(String[] scripts) in /home/vsts/work/1/s/tools/ScenarioTest.ResourceManager/EnvironmentSetupHelper.cs:line 573
2021-07-05T06:09:55.5329962Z Message: Exception calling "OffSet" with "4" argument(s): "An invalid IP address was specified.
2021-07-05T06:09:55.5330531Z Parameter name: address"
2021-07-05T06:09:55.5331588Z EXEC : PowerShell error Record: Exception calling "OffSet" with "4" argument(s): "An invalid IP address was specified. [/home/vsts/work/1/s/build.proj]
2021-07-05T06:09:55.5332347Z Parameter name: address"
2021-07-05T06:09:55.5333043Z Exception:System.Management.Automation.ParentContainsErrorRecordException: Exception calling "OffSet" with "4" argument(s): "An invalid IP address was specified.
2021-07-05T06:09:55.5333669Z Parameter name: address"
2021-07-05T06:09:55.5334022Z Details:
2021-07-05T06:09:55.5334539Z Script Stack Trace: at newIpV6Address, /home/vsts/work/1/s/src/Peering/Peering.Test/bin/Debug/netcoreapp2.1/ScenarioTests/PeeringCommon.ps1: line 52
2021-07-05T06:09:55.5336204Z at Test-UpdateExchangeIPv6OnResourceId, /home/vsts/work/1/s/src/Peering/Peering.Test/bin/Debug/netcoreapp2.1/ScenarioTests/ScenarioExchangePeeringTests.ps1: line 50
2021-07-05T06:09:55.5336776Z at <ScriptBlock>, <No file>: line 1
2021-07-05T06:09:55.5337089Z : Target:
2021-07-05T06:09:55.5337354Z
2021-07-05T06:09:55.5337687Z Caught Exception: System.ArgumentException: An invalid IP address was specified.
2021-07-05T06:09:55.5338073Z Parameter name: address
2021-07-05T06:09:55.5338403Z at System.Net.IPAddress..ctor(ReadOnlySpan`1 address)
2021-07-05T06:09:55.5338771Z at System.Net.IPAddress..ctor(Byte[] address)
2021-07-05T06:09:55.5339305Z at Microsoft.Azure.PowerShell.Cmdlets.Peering.Common.HelperExtensionMethods.ToIpAddress(BigInteger self, AddressFamily addressFamily) in /home/vsts/work/1/s/src/Peering/Peering/Common/HelperExtensionMethods.cs:line 91
2021-07-05T06:09:55.5340529Z at Microsoft.Azure.Commands.Peering.Test.ScenarioTests.IPGenerator.OffSet(String ipAddress, Boolean v6, Int32 offset, Boolean hasPrefix) in /home/vsts/work/1/s/src/Peering/Peering.Test/ScenarioTests/IPGenerator.cs:line 65
2021-07-05T06:09:55.5431677Z at CallSite.Target(Closure , CallSite , Object , Object , Boolean , Object , Object )
2021-07-05T06:09:55.5432485Z Message: An invalid IP address was specified.
2021-07-05T06:09:55.5433058Z Parameter name: address
```
https://dev.azure.com/azure-sdk/public/_build/results?buildId=983143&view=logs&j=ad07b744-5a1a-5d54-7693-fcb02e666633&t=b0841cae-a6b1-5a5c-4ebd-3cc6b3d3163d
## Cost
| non_priority | random failure in test description the random failure happens to the following line in the function of test getpeeringvariable true false getrandomnumber function test hard coded name because the resource has to exist and cant be created ad hoc randnum getrandomnumber write debug random number randnum peerasn makepeerasn randnum resourcegroups testsetup createresourcegroup resourcegroup resourcegroups resourcegroupname peering createexchangepeering resourcegroup peerasn name assert notnull peering getpeeringvariable true false getrandomnumber oldpeering peering peering connections peering connections set azpeeringexchangeconnectionobject write debug peering name assert throwscontains update update azpeering resourceid peering id peering connections badargument error log of the test case microsoft azure commands peering test scenariotests scenarioexchangepeeringtests x microsoft azure commands peering test scenariotests scenarioexchangepeeringtests exec error message system management automation methodinvocationexception exception calling offset with argument s an invalid ip address was specified parameter name address system argumentexception an invalid ip address was specified parameter name address stack trace at system management automation runspaces pipelinebase invoke ienumerable input at system management automation runspaces pipeline invoke at system management automation powershell worker constructpipelineanddowork runspace rs boolean performsyncinvoke at system management automation powershell worker createrunspaceifneededanddowork runspace rstouse boolean issync at system management automation powershell coreinvokehelper psdatacollection input psdatacollection output psinvocationsettings settings at system management automation powershell coreinvoke psdatacollection input psdatacollection output psinvocationsettings settings at system management automation powershell coreinvoke ienumerable input psdatacollection output psinvocationsettings settings at system management automation powershell invoke ienumerable input psinvocationsettings settings at system management automation powershell invoke at microsoft windowsazure commands scenariotest environmentsetuphelper runpowershelltest string scripts in home vsts work s tools scenariotest resourcemanager environmentsetuphelper cs line at microsoft azure commands peering test scenariotests testcontroller runpstestworkflow func scriptbuilder action cleanup string callingclasstype string mockname in home vsts work s src peering peering test scenariotests testcontroller cs line at microsoft azure commands peering test scenariotests testcontroller runpowershelltest xunittracinginterceptor logger string scripts in home vsts work s src peering peering test scenariotests testcontroller cs line at microsoft azure commands peering test scenariotests scenarioexchangepeeringtests in home vsts work s src peering peering test scenariotests scenarioexchangepeeringtests cs line inner stack trace at system net ipaddress ctor readonlyspan address at system net ipaddress ctor byte address at microsoft azure powershell cmdlets peering common helperextensionmethods toipaddress biginteger self addressfamily addressfamily in home vsts work s src peering peering common helperextensionmethods cs line at microsoft azure commands peering test scenariotests ipgenerator offset string ipaddress boolean offset boolean hasprefix in home vsts work s src peering peering test scenariotests ipgenerator cs line at callsite target closure callsite object object boolean object object standard output messages test caught exception system management automation methodinvocationexception exception calling offset with argument s an invalid ip address was specified parameter name address system argumentexception an invalid ip address was specified parameter name address at system net ipaddress ctor readonlyspan address at system net ipaddress ctor byte address at microsoft azure powershell cmdlets peering common helperextensionmethods toipaddress biginteger self addressfamily addressfamily in home vsts work s src peering peering common helperextensionmethods cs line at microsoft azure commands peering test scenariotests ipgenerator offset string ipaddress boolean offset boolean hasprefix in home vsts work s src peering peering test scenariotests ipgenerator cs line at callsite target closure callsite object object boolean object object end of inner exception stack trace at system management automation runspaces pipelinebase invoke ienumerable input at system management automation runspaces pipeline invoke at system management automation powershell worker constructpipelineanddowork runspace rs boolean performsyncinvoke at system management automation powershell worker createrunspaceifneededanddowork runspace rstouse boolean issync at system management automation powershell coreinvokehelper psdatacollection input psdatacollection output psinvocationsettings settings at system management automation powershell coreinvoke psdatacollection input psdatacollection output psinvocationsettings settings at system management automation powershell coreinvoke ienumerable input psdatacollection output psinvocationsettings settings at system management automation powershell invoke ienumerable input psinvocationsettings settings at system management automation powershell invoke at microsoft windowsazure commands scenariotest environmentsetuphelper runpowershelltest string scripts in home vsts work s tools scenariotest resourcemanager environmentsetuphelper cs line message exception calling offset with argument s an invalid ip address was specified parameter name address exec powershell error record exception calling offset with argument s an invalid ip address was specified parameter name address exception system management automation parentcontainserrorrecordexception exception calling offset with argument s an invalid ip address was specified parameter name address details script stack trace at home vsts work s src peering peering test bin debug scenariotests peeringcommon line at test home vsts work s src peering peering test bin debug scenariotests scenarioexchangepeeringtests line at line target caught exception system argumentexception an invalid ip address was specified parameter name address at system net ipaddress ctor readonlyspan address at system net ipaddress ctor byte address at microsoft azure powershell cmdlets peering common helperextensionmethods toipaddress biginteger self addressfamily addressfamily in home vsts work s src peering peering common helperextensionmethods cs line at microsoft azure commands peering test scenariotests ipgenerator offset string ipaddress boolean offset boolean hasprefix in home vsts work s src peering peering test scenariotests ipgenerator cs line at callsite target closure callsite object object boolean object object message an invalid ip address was specified parameter name address cost | 0 |
707,288 | 24,301,336,238 | IssuesEvent | 2022-09-29 14:04:44 | feast-dev/feast | https://api.github.com/repos/feast-dev/feast | closed | Feast cannot be installed in Python 3.10 | kind/bug priority/p0 priority/p2 | ## Expected Behavior
A user should be able to install Feast in a Python 3.10 environment. In setup.py it shows that `REQUIRES_PYTHON = ">=3.7.0"` which means it should work for Python 3.10
## Current Behavior
Pip install fails when it hits the `mmh3` package since it does not support Python 3.10. This package hasn't been updated in over a year so it doesn't look like they will support Python 3.10 any time soon.
## Steps to reproduce
Create a virtual environment with Python 3.10 and run `pip install feast`
### Specifications
- Version:
- Platform:
- Subsystem:
## Possible Solution
Use a different hashing library than `mmh3` | 2.0 | Feast cannot be installed in Python 3.10 - ## Expected Behavior
A user should be able to install Feast in a Python 3.10 environment. In setup.py it shows that `REQUIRES_PYTHON = ">=3.7.0"` which means it should work for Python 3.10
## Current Behavior
Pip install fails when it hits the `mmh3` package since it does not support Python 3.10. This package hasn't been updated in over a year so it doesn't look like they will support Python 3.10 any time soon.
## Steps to reproduce
Create a virtual environment with Python 3.10 and run `pip install feast`
### Specifications
- Version:
- Platform:
- Subsystem:
## Possible Solution
Use a different hashing library than `mmh3` | priority | feast cannot be installed in python expected behavior a user should be able to install feast in a python environment in setup py it shows that requires python which means it should work for python current behavior pip install fails when it hits the package since it does not support python this package hasn t been updated in over a year so it doesn t look like they will support python any time soon steps to reproduce create a virtual environment with python and run pip install feast specifications version platform subsystem possible solution use a different hashing library than | 1 |
452,274 | 13,047,799,188 | IssuesEvent | 2020-07-29 11:22:51 | OpenApoc/OpenApoc | https://api.github.com/repos/OpenApoc/OpenApoc | closed | (With multiple craft selected) Craft do not follow assigned order to "Attack UFO" or "Go to building" | !BUG! low priority | Observed under 0.1-214
If multiple vehicles are selected to attack a craft or go to a building, they do not always execute the order and leave their current location for the assigned mission...
| 1.0 | (With multiple craft selected) Craft do not follow assigned order to "Attack UFO" or "Go to building" - Observed under 0.1-214
If multiple vehicles are selected to attack a craft or go to a building, they do not always execute the order and leave their current location for the assigned mission...
| priority | with multiple craft selected craft do not follow assigned order to attack ufo or go to building observed under if multiple vehicles are selected to attack a craft or go to a building they do not always execute the order and leave their current location for the assigned mission | 1 |
23,724 | 3,851,866,014 | IssuesEvent | 2016-04-06 05:28:07 | GPF/imame4all | https://api.github.com/repos/GPF/imame4all | closed | Heavy Barrel(US) L/R buttons do not function | auto-migrated Priority-Medium Type-Defect | ```
What steps will reproduce the problem?
1. Load Heavy Barrel(US)
2. Attempt to turn with L/R
3. Only sadness results, no turning
What is the expected output? What do you see instead?
In the standard Mame4Droid (non-reloaded version) the L/R buttons will turn the
direction the player is facing, so that the player can move and fire in
different directions.
What version of the product are you using? On what operating system?
MAME4droid Reloaded (0.139)
Nexus 7
Jelly Bean 4.1.1
Please provide any additional information below.
```
Original issue reported on code.google.com by `deepdark...@gmail.com` on 19 Jul 2012 at 12:54 | 1.0 | Heavy Barrel(US) L/R buttons do not function - ```
What steps will reproduce the problem?
1. Load Heavy Barrel(US)
2. Attempt to turn with L/R
3. Only sadness results, no turning
What is the expected output? What do you see instead?
In the standard Mame4Droid (non-reloaded version) the L/R buttons will turn the
direction the player is facing, so that the player can move and fire in
different directions.
What version of the product are you using? On what operating system?
MAME4droid Reloaded (0.139)
Nexus 7
Jelly Bean 4.1.1
Please provide any additional information below.
```
Original issue reported on code.google.com by `deepdark...@gmail.com` on 19 Jul 2012 at 12:54 | non_priority | heavy barrel us l r buttons do not function what steps will reproduce the problem load heavy barrel us attempt to turn with l r only sadness results no turning what is the expected output what do you see instead in the standard non reloaded version the l r buttons will turn the direction the player is facing so that the player can move and fire in different directions what version of the product are you using on what operating system reloaded nexus jelly bean please provide any additional information below original issue reported on code google com by deepdark gmail com on jul at | 0 |
265,819 | 23,200,828,125 | IssuesEvent | 2022-08-01 21:16:19 | MEGA65/mega65-tools | https://api.github.com/repos/MEGA65/mega65-tools | closed | (WINDOWS) mega65_ftp adds invalid root directory changes to the current directory path | bug fix test | ## When you try to change to an invalid directory by prepending / it actually changes you to an invalid directory.
### Examples below:
**MEGA65 SD-Card:/>** cd /hello
ERROR: Could not find directory segment 'hello'
ERROR: Could not open directory '/hello'
**MEGA65 SD-Card:/hello>** dir
ERROR: Could not find directory segment 'hello'
0 Dir(s), 0 File(s)
**MEGA65 SD-Card:/hello>** cd /should/not/change/path/if/the/path/doesnt/exist
ERROR: Could not find directory segment 'should'
ERROR: Could not open directory '/should/not/change/path/if/the/path/doesnt/exist'
**MEGA65 SD-Card:/should/not/change/path/if/the/path/doesnt/exist>** dir
ERROR: Could not find directory segment 'should'
0 Dir(s), 0 File(s)
**MEGA65 SD-Card:/should/not/change/path/if/the/path/doesnt/exist>** cd /
**MEGA65 SD-Card:/>** dir *.ROM
131072 | 2022-05-12 02:07:40 | MEGA65.ROM |
131072 | 2022-05-06 20:39:56 | MEGA651.ROM |
131072 | 2022-05-06 20:39:56 | MEGA652.ROM |
131072 | 2022-05-12 02:06:40 | MEGA653.ROM |
0 Dir(s), 4 File(s)
**MEGA65 SD-Card:/>**
## Behavior should mirror what happens if you normally try to change to an invalid directory:
MEGA65 SD-Card:/> cd poo
ERROR: Could not find directory segment 'poo'
ERROR: Could not open directory '/poo'
MEGA65 SD-Card:/>
| 1.0 | (WINDOWS) mega65_ftp adds invalid root directory changes to the current directory path - ## When you try to change to an invalid directory by prepending / it actually changes you to an invalid directory.
### Examples below:
**MEGA65 SD-Card:/>** cd /hello
ERROR: Could not find directory segment 'hello'
ERROR: Could not open directory '/hello'
**MEGA65 SD-Card:/hello>** dir
ERROR: Could not find directory segment 'hello'
0 Dir(s), 0 File(s)
**MEGA65 SD-Card:/hello>** cd /should/not/change/path/if/the/path/doesnt/exist
ERROR: Could not find directory segment 'should'
ERROR: Could not open directory '/should/not/change/path/if/the/path/doesnt/exist'
**MEGA65 SD-Card:/should/not/change/path/if/the/path/doesnt/exist>** dir
ERROR: Could not find directory segment 'should'
0 Dir(s), 0 File(s)
**MEGA65 SD-Card:/should/not/change/path/if/the/path/doesnt/exist>** cd /
**MEGA65 SD-Card:/>** dir *.ROM
131072 | 2022-05-12 02:07:40 | MEGA65.ROM |
131072 | 2022-05-06 20:39:56 | MEGA651.ROM |
131072 | 2022-05-06 20:39:56 | MEGA652.ROM |
131072 | 2022-05-12 02:06:40 | MEGA653.ROM |
0 Dir(s), 4 File(s)
**MEGA65 SD-Card:/>**
## Behavior should mirror what happens if you normally try to change to an invalid directory:
MEGA65 SD-Card:/> cd poo
ERROR: Could not find directory segment 'poo'
ERROR: Could not open directory '/poo'
MEGA65 SD-Card:/>
| non_priority | windows ftp adds invalid root directory changes to the current directory path when you try to change to an invalid directory by prepending it actually changes you to an invalid directory examples below sd card cd hello error could not find directory segment hello error could not open directory hello sd card hello dir error could not find directory segment hello dir s file s sd card hello cd should not change path if the path doesnt exist error could not find directory segment should error could not open directory should not change path if the path doesnt exist sd card should not change path if the path doesnt exist dir error could not find directory segment should dir s file s sd card should not change path if the path doesnt exist cd sd card dir rom rom rom rom rom dir s file s sd card behavior should mirror what happens if you normally try to change to an invalid directory sd card cd poo error could not find directory segment poo error could not open directory poo sd card | 0 |
485,426 | 13,965,312,868 | IssuesEvent | 2020-10-25 21:53:45 | rathena/rathena | https://api.github.com/repos/rathena/rathena | closed | Server received Crash Signal | component:core mode:prerenewal mode:renewal priority:high status:confirmed type:bug | <!-- NOTE: Anything within these brackets will be hidden on the preview of the Issue. -->
* **rAthena Hash**: f28019a7986321fd8fa537af6864d48d9e4c092e
<!-- Please specify the rAthena [GitHub hash](https://help.github.com/articles/autolinked-references-and-urls/#commit-shas) on which you encountered this issue.
How to get your GitHub Hash:
1. cd your/rAthena/directory/
2. git rev-parse --short HEAD
3. Copy the resulting hash.
-->
* **Client Date**: 20200304
<!-- Please specify the client date you used. -->
* **Server Mode**: re
<!-- Which mode does your server use: Pre-Renewal or Renewal? -->
* **Description of Issue**:
Logging in on this "player" character causes this. This started happening after I updated to the latest version of rAthena. Cant explain it. The server then crashes after logging in one more time with the message "Server Recieved Crash Signal" **This only happens when logging in 1 character -> the Char: "Player"**
this is script.cpp
* **Modifications that may affect results**:
Lapine UI
Refine UI cydh
another modification was
https://github.com/rathena/rathena/issues/5466#issuecomment-713081757
I used it, but removed it after I received this error but the error kept showing up even after removing all related to this. | 1.0 | Server received Crash Signal - <!-- NOTE: Anything within these brackets will be hidden on the preview of the Issue. -->
* **rAthena Hash**: f28019a7986321fd8fa537af6864d48d9e4c092e
<!-- Please specify the rAthena [GitHub hash](https://help.github.com/articles/autolinked-references-and-urls/#commit-shas) on which you encountered this issue.
How to get your GitHub Hash:
1. cd your/rAthena/directory/
2. git rev-parse --short HEAD
3. Copy the resulting hash.
-->
* **Client Date**: 20200304
<!-- Please specify the client date you used. -->
* **Server Mode**: re
<!-- Which mode does your server use: Pre-Renewal or Renewal? -->
* **Description of Issue**:
Logging in on this "player" character causes this. This started happening after I updated to the latest version of rAthena. Cant explain it. The server then crashes after logging in one more time with the message "Server Recieved Crash Signal" **This only happens when logging in 1 character -> the Char: "Player"**
this is script.cpp
* **Modifications that may affect results**:
Lapine UI
Refine UI cydh
another modification was
https://github.com/rathena/rathena/issues/5466#issuecomment-713081757
I used it, but removed it after I received this error but the error kept showing up even after removing all related to this. | priority | server received crash signal rathena hash please specify the rathena on which you encountered this issue how to get your github hash cd your rathena directory git rev parse short head copy the resulting hash client date server mode re description of issue logging in on this player character causes this this started happening after i updated to the latest version of rathena cant explain it the server then crashes after logging in one more time with the message server recieved crash signal this only happens when logging in character the char player this is script cpp modifications that may affect results lapine ui refine ui cydh another modification was i used it but removed it after i received this error but the error kept showing up even after removing all related to this | 1 |
101,359 | 12,677,498,578 | IssuesEvent | 2020-06-19 07:53:38 | scionproto/scion | https://api.github.com/repos/scionproto/scion | closed | Infra: Design automatic key rollover | design | The infra should handle key rollover automatically.
Currently the CS and other elements needs to be restarted to reload the keys.
| 1.0 | Infra: Design automatic key rollover - The infra should handle key rollover automatically.
Currently the CS and other elements needs to be restarted to reload the keys.
| non_priority | infra design automatic key rollover the infra should handle key rollover automatically currently the cs and other elements needs to be restarted to reload the keys | 0 |
676,024 | 23,113,918,724 | IssuesEvent | 2022-07-27 15:05:12 | NIAEFEUP/tts-revamp-fe | https://api.github.com/repos/NIAEFEUP/tts-revamp-fe | closed | Permanent state | high priority high effort | When changing the page to about or selecting new subjects, the state mustn't be deleted.
| 1.0 | Permanent state - When changing the page to about or selecting new subjects, the state mustn't be deleted.
| priority | permanent state when changing the page to about or selecting new subjects the state mustn t be deleted | 1 |
408,356 | 11,945,662,934 | IssuesEvent | 2020-04-03 06:25:16 | webcompat/web-bugs | https://api.github.com/repos/webcompat/web-bugs | closed | www.instagram.com - video or audio doesn't play | browser-fenix engine-gecko priority-critical | <!-- @browser: Firefox Mobile 76.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 5.1.1; Mobile; rv:76.0) Gecko/76.0 Firefox/76.0 -->
<!-- @reported_with: -->
<!-- @extra_labels: browser-fenix -->
**URL**: https://www.instagram.com/
**Browser / Version**: Firefox Mobile 76.0
**Operating System**: Android 5.1.1
**Tested Another Browser**: Yes Chrome
**Problem type**: Video or audio doesn't play
**Description**: The video or audio does not play
**Steps to Reproduce**:
Trying to use the Instagram inside de Firefox Nightly. Because it's a PWA app and that smartphone hardware and storage is limited. All working except the okay of videos and the slow speed. thanks. And I can create a site app icon in the Microsoft laucher.
<details><summary>View the screenshot</summary><img alt='Screenshot' src='https://webcompat.com/uploads/2020/4/96b35b78-d0f1-4253-92b9-8ddd0f4843a9.jpg'></details>
<details>
<summary>Browser Configuration</summary>
<ul>
<li>None</li>
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_ | 1.0 | www.instagram.com - video or audio doesn't play - <!-- @browser: Firefox Mobile 76.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 5.1.1; Mobile; rv:76.0) Gecko/76.0 Firefox/76.0 -->
<!-- @reported_with: -->
<!-- @extra_labels: browser-fenix -->
**URL**: https://www.instagram.com/
**Browser / Version**: Firefox Mobile 76.0
**Operating System**: Android 5.1.1
**Tested Another Browser**: Yes Chrome
**Problem type**: Video or audio doesn't play
**Description**: The video or audio does not play
**Steps to Reproduce**:
Trying to use the Instagram inside de Firefox Nightly. Because it's a PWA app and that smartphone hardware and storage is limited. All working except the okay of videos and the slow speed. thanks. And I can create a site app icon in the Microsoft laucher.
<details><summary>View the screenshot</summary><img alt='Screenshot' src='https://webcompat.com/uploads/2020/4/96b35b78-d0f1-4253-92b9-8ddd0f4843a9.jpg'></details>
<details>
<summary>Browser Configuration</summary>
<ul>
<li>None</li>
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_ | priority | video or audio doesn t play url browser version firefox mobile operating system android tested another browser yes chrome problem type video or audio doesn t play description the video or audio does not play steps to reproduce trying to use the instagram inside de firefox nightly because it s a pwa app and that smartphone hardware and storage is limited all working except the okay of videos and the slow speed thanks and i can create a site app icon in the microsoft laucher view the screenshot img alt screenshot src browser configuration none from with ❤️ | 1 |
151,729 | 13,431,555,897 | IssuesEvent | 2020-09-07 07:11:20 | chubaofs/chubaofs | https://api.github.com/repos/chubaofs/chubaofs | closed | Apply review suggestions to the release notes of version v2.0.0 . | documentation enhancement priority/normal | Following review suggestions need to be applied to the release note of version `v2.2.0` to improve content readability.
- Project function and code test related information does not need to be reflected in Release Notes, because these contents have nothing to do with functionality.
_Originally posted by @mervinkid in https://github.com/chubaofs/chubaofs/pull/868#r483499727_
- Can't understand the meaning of this sentence.
_Originally posted by @mervinkid in https://github.com/chubaofs/chubaofs/pull/868#r483501481_
- It is recommended to adjust to "`Introducing **nearRead** optation that allow client read data priority from the nearest DataNode to improve reading performance`".
_Originally posted by @mervinkid in https://github.com/chubaofs/chubaofs/pull/868#r483515658_
- It is recommended to adjust to "`Improve compatibility for ListObjects and ListObjectsV2 interfaces`".
_Originally posted by @mervinkid in https://github.com/chubaofs/chubaofs/pull/868#r483512276_
- It is recommended to adjuest to "`Introducing **autoRepair** optation for limit data repair speed on **DataNode**`".
_Originally posted by @mervinkid in https://github.com/chubaofs/chubaofs/pull/868#r483513540_
- It is recommended to modify to "`The data repair task will skip extent which has been already deleted`".
_Originally posted by @mervinkid in https://github.com/chubaofs/chubaofs/pull/868#r483524593_
- Documentation related works does not need to be add into the release notes.
_Originally posted by @mervinkid in https://github.com/chubaofs/chubaofs/pull/868#r483523824_
- It it recommended to modify to "`Fix deadlock problem while **MetaNode** deleting **dentry**`".
_Originally posted by @mervinkid in https://github.com/chubaofs/chubaofs/pull/868#r483517910_
- It is recommended to modify to "`Fix the problem that sometimes some deleted file data cannot be successfully released`".
_Originally posted by @mervinkid in https://github.com/chubaofs/chubaofs/pull/868#r483516907_
- It it recommended to modify to "`Fix problem that opening file with outdated extents information`".
_Originally posted by @mervinkid in https://github.com/chubaofs/chubaofs/pull/868#r483519338_
- It is recommended to modify to "`Fix the problem that authorized user mount failure`".
_Originally posted by @mervinkid in https://github.com/chubaofs/chubaofs/pull/868#r483523254_
- It it recommended to modify to "`Fix serval issue in automatic repair process for tiny extent`".
_Originally posted by @mervinkid in https://github.com/chubaofs/chubaofs/pull/868#r483522345_
- It is recommended to modify to "`Fix the problem that the client still applies to create a new extent to a data partition that has no space`".
_Originally posted by @mervinkid in https://github.com/chubaofs/chubaofs/pull/868#r483521542_ | 1.0 | Apply review suggestions to the release notes of version v2.0.0 . - Following review suggestions need to be applied to the release note of version `v2.2.0` to improve content readability.
- Project function and code test related information does not need to be reflected in Release Notes, because these contents have nothing to do with functionality.
_Originally posted by @mervinkid in https://github.com/chubaofs/chubaofs/pull/868#r483499727_
- Can't understand the meaning of this sentence.
_Originally posted by @mervinkid in https://github.com/chubaofs/chubaofs/pull/868#r483501481_
- It is recommended to adjust to "`Introducing **nearRead** optation that allow client read data priority from the nearest DataNode to improve reading performance`".
_Originally posted by @mervinkid in https://github.com/chubaofs/chubaofs/pull/868#r483515658_
- It is recommended to adjust to "`Improve compatibility for ListObjects and ListObjectsV2 interfaces`".
_Originally posted by @mervinkid in https://github.com/chubaofs/chubaofs/pull/868#r483512276_
- It is recommended to adjuest to "`Introducing **autoRepair** optation for limit data repair speed on **DataNode**`".
_Originally posted by @mervinkid in https://github.com/chubaofs/chubaofs/pull/868#r483513540_
- It is recommended to modify to "`The data repair task will skip extent which has been already deleted`".
_Originally posted by @mervinkid in https://github.com/chubaofs/chubaofs/pull/868#r483524593_
- Documentation related works does not need to be add into the release notes.
_Originally posted by @mervinkid in https://github.com/chubaofs/chubaofs/pull/868#r483523824_
- It it recommended to modify to "`Fix deadlock problem while **MetaNode** deleting **dentry**`".
_Originally posted by @mervinkid in https://github.com/chubaofs/chubaofs/pull/868#r483517910_
- It is recommended to modify to "`Fix the problem that sometimes some deleted file data cannot be successfully released`".
_Originally posted by @mervinkid in https://github.com/chubaofs/chubaofs/pull/868#r483516907_
- It it recommended to modify to "`Fix problem that opening file with outdated extents information`".
_Originally posted by @mervinkid in https://github.com/chubaofs/chubaofs/pull/868#r483519338_
- It is recommended to modify to "`Fix the problem that authorized user mount failure`".
_Originally posted by @mervinkid in https://github.com/chubaofs/chubaofs/pull/868#r483523254_
- It it recommended to modify to "`Fix serval issue in automatic repair process for tiny extent`".
_Originally posted by @mervinkid in https://github.com/chubaofs/chubaofs/pull/868#r483522345_
- It is recommended to modify to "`Fix the problem that the client still applies to create a new extent to a data partition that has no space`".
_Originally posted by @mervinkid in https://github.com/chubaofs/chubaofs/pull/868#r483521542_ | non_priority | apply review suggestions to the release notes of version following review suggestions need to be applied to the release note of version to improve content readability project function and code test related information does not need to be reflected in release notes because these contents have nothing to do with functionality originally posted by mervinkid in can t understand the meaning of this sentence originally posted by mervinkid in it is recommended to adjust to introducing nearread optation that allow client read data priority from the nearest datanode to improve reading performance originally posted by mervinkid in it is recommended to adjust to improve compatibility for listobjects and interfaces originally posted by mervinkid in it is recommended to adjuest to introducing autorepair optation for limit data repair speed on datanode originally posted by mervinkid in it is recommended to modify to the data repair task will skip extent which has been already deleted originally posted by mervinkid in documentation related works does not need to be add into the release notes originally posted by mervinkid in it it recommended to modify to fix deadlock problem while metanode deleting dentry originally posted by mervinkid in it is recommended to modify to fix the problem that sometimes some deleted file data cannot be successfully released originally posted by mervinkid in it it recommended to modify to fix problem that opening file with outdated extents information originally posted by mervinkid in it is recommended to modify to fix the problem that authorized user mount failure originally posted by mervinkid in it it recommended to modify to fix serval issue in automatic repair process for tiny extent originally posted by mervinkid in it is recommended to modify to fix the problem that the client still applies to create a new extent to a data partition that has no space originally posted by mervinkid in | 0 |
22,574 | 3,790,833,342 | IssuesEvent | 2016-03-21 23:06:50 | diablodale/dp.kinect2 | https://api.github.com/repos/diablodale/dp.kinect2 | closed | registration problem | by design not-a-bug | Win 10
Max 7 32 bits 7.2.1 registered
Runtime 2.0
dp.kinect2 v1.1.20160225.0
I can't register properly the dp.kinect2 external.
I followed the instructions and it worked but only with the max 64 bit version. After registering the external in Max 64 bits it works for a while also in Max 32 bit version, but after closing max the registration disappears and I have to repeate the whole process again.
Thanks! | 1.0 | registration problem - Win 10
Max 7 32 bits 7.2.1 registered
Runtime 2.0
dp.kinect2 v1.1.20160225.0
I can't register properly the dp.kinect2 external.
I followed the instructions and it worked but only with the max 64 bit version. After registering the external in Max 64 bits it works for a while also in Max 32 bit version, but after closing max the registration disappears and I have to repeate the whole process again.
Thanks! | non_priority | registration problem win max bits registered runtime dp i can t register properly the dp external i followed the instructions and it worked but only with the max bit version after registering the external in max bits it works for a while also in max bit version but after closing max the registration disappears and i have to repeate the whole process again thanks | 0 |
277,298 | 8,628,563,752 | IssuesEvent | 2018-11-21 17:45:25 | googleapis/google-cloud-php | https://api.github.com/repos/googleapis/google-cloud-php | closed | Synthesis failed for speech | autosynth failure priority: p1 type: bug | Hello! Autosynth couldn't regenerate speech. :broken_heart:
Here's the output from running `synth.py`:
```
Cloning into 'working_repo'...
Switched to branch 'autosynth-speech'
[35msynthtool > [31m[43mYou are running the synthesis script directly, this will be disabled in a future release of Synthtool. Please use python3 -m synthtool instead.[0m
[35msynthtool > [36mEnsuring dependencies.[0m
[35msynthtool > [36mPulling artman image.[0m
latest: Pulling from googleapis/artman
Digest: sha256:2f6b261ee7fe1aedf238991c93a20b3820de37a343d0cacf3e3e9555c2aaf2ea
Status: Image is up to date for googleapis/artman:latest
[35msynthtool > [36mCloning googleapis.[0m
[35msynthtool > [36mRunning generator for google/cloud/speech/artman_speech_v1.yaml.[0m
[35msynthtool > [32mGenerated code into /home/kbuilder/.cache/synthtool/googleapis/artman-genfiles/php/google-cloud-speech-v1.[0m
[35msynthtool > [36mRunning generator for google/cloud/speech/artman_speech_v1p1beta1.yaml.[0m
[35msynthtool > [32mGenerated code into /home/kbuilder/.cache/synthtool/googleapis/artman-genfiles/php/google-cloud-speech-v1p1beta1.[0m
[35msynthtool > [34mReplaced 'Copyright \\d{4}' in src/V1p1beta1/Gapic/SpeechGapicClient.php.[0m
[35msynthtool > [34mReplaced 'Copyright \\d{4}' in src/V1/Gapic/SpeechGapicClient.php.[0m
[35msynthtool > [34mReplaced 'Copyright \\d{4}' in src/V1p1beta1/Gapic/SpeechGapicClient.php.[0m
[35msynthtool > [34mReplaced 'Copyright \\d{4}' in tests/Snippet/V1/SpeechClientTest.php.[0m
[35msynthtool > [34mReplaced 'Copyright \\d{4}' in tests/Unit/V1p1beta1/SpeechClientTest.php.[0m
[35msynthtool > [34mReplaced 'Copyright \\d{4}' in tests/Unit/V1/SpeechClientTest.php.[0m
[35msynthtool > [34mReplaced 'Copyright \\d{4}' in tests/Unit/V1/SpeechClientExtensionTest.php.[0m
[35msynthtool > [34mReplaced 'Copyright \\d{4}' in tests/System/V1p1beta1/SpeechSmokeTest.php.[0m
[35msynthtool > [34mReplaced 'Copyright \\d{4}' in tests/System/V1/SpeechSmokeTest.php.[0m
[35msynthtool > [34mReplaced 'RecognitionConfig_AudioEncoding' in src/V1p1beta1/Gapic/SpeechGapicClient.php.[0m
[35msynthtool > [34mReplaced 'RecognitionConfig_AudioEncoding' in src/V1/Gapic/SpeechGapicClient.php.[0m
[35msynthtool > [34mReplaced 'will be removed in the next major release' in src/V1p1beta1/RecognitionMetadata_InteractionType.php.[0m
[35msynthtool > [34mReplaced 'will be removed in the next major release' in src/V1p1beta1/RecognitionConfig_AudioEncoding.php.[0m
[35msynthtool > [34mReplaced 'will be removed in the next major release' in src/V1p1beta1/StreamingRecognizeResponse_SpeechEventType.php.[0m
[35msynthtool > [34mReplaced 'will be removed in the next major release' in src/V1p1beta1/RecognitionMetadata_MicrophoneDistance.php.[0m
[35msynthtool > [34mReplaced 'will be removed in the next major release' in src/V1p1beta1/RecognitionMetadata_RecordingDeviceType.php.[0m
[35msynthtool > [34mReplaced 'will be removed in the next major release' in src/V1p1beta1/RecognitionMetadata_OriginalMediaType.php.[0m
[35msynthtool > [34mReplaced 'will be removed in the next major release' in src/V1/RecognitionConfig_AudioEncoding.php.[0m
[35msynthtool > [34mReplaced 'will be removed in the next major release' in src/V1/StreamingRecognizeResponse_SpeechEventType.php.[0m
[35msynthtool > [36mCleaned up 1 temporary directories.[0m
Changed files:
On branch autosynth-speech
nothing to commit, working tree clean
Traceback (most recent call last):
File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/runpy.py", line 193, in _run_module_as_main
"__main__", mod_spec)
File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 166, in <module>
main()
File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 151, in main
commit_changes(pr_title)
File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 95, in commit_changes
subprocess.check_call(["git", "commit", "-m", message])
File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/subprocess.py", line 291, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['git', 'commit', '-m', '[CHANGE ME] Re-generated Speech to pick up changes in the API or client library generator.']' returned non-zero exit status 1.
```
Google internal developers can see the full log [here](https://sponge/72b66427-a48f-4376-80dc-810b01105202).
| 1.0 | Synthesis failed for speech - Hello! Autosynth couldn't regenerate speech. :broken_heart:
Here's the output from running `synth.py`:
```
Cloning into 'working_repo'...
Switched to branch 'autosynth-speech'
[35msynthtool > [31m[43mYou are running the synthesis script directly, this will be disabled in a future release of Synthtool. Please use python3 -m synthtool instead.[0m
[35msynthtool > [36mEnsuring dependencies.[0m
[35msynthtool > [36mPulling artman image.[0m
latest: Pulling from googleapis/artman
Digest: sha256:2f6b261ee7fe1aedf238991c93a20b3820de37a343d0cacf3e3e9555c2aaf2ea
Status: Image is up to date for googleapis/artman:latest
[35msynthtool > [36mCloning googleapis.[0m
[35msynthtool > [36mRunning generator for google/cloud/speech/artman_speech_v1.yaml.[0m
[35msynthtool > [32mGenerated code into /home/kbuilder/.cache/synthtool/googleapis/artman-genfiles/php/google-cloud-speech-v1.[0m
[35msynthtool > [36mRunning generator for google/cloud/speech/artman_speech_v1p1beta1.yaml.[0m
[35msynthtool > [32mGenerated code into /home/kbuilder/.cache/synthtool/googleapis/artman-genfiles/php/google-cloud-speech-v1p1beta1.[0m
[35msynthtool > [34mReplaced 'Copyright \\d{4}' in src/V1p1beta1/Gapic/SpeechGapicClient.php.[0m
[35msynthtool > [34mReplaced 'Copyright \\d{4}' in src/V1/Gapic/SpeechGapicClient.php.[0m
[35msynthtool > [34mReplaced 'Copyright \\d{4}' in src/V1p1beta1/Gapic/SpeechGapicClient.php.[0m
[35msynthtool > [34mReplaced 'Copyright \\d{4}' in tests/Snippet/V1/SpeechClientTest.php.[0m
[35msynthtool > [34mReplaced 'Copyright \\d{4}' in tests/Unit/V1p1beta1/SpeechClientTest.php.[0m
[35msynthtool > [34mReplaced 'Copyright \\d{4}' in tests/Unit/V1/SpeechClientTest.php.[0m
[35msynthtool > [34mReplaced 'Copyright \\d{4}' in tests/Unit/V1/SpeechClientExtensionTest.php.[0m
[35msynthtool > [34mReplaced 'Copyright \\d{4}' in tests/System/V1p1beta1/SpeechSmokeTest.php.[0m
[35msynthtool > [34mReplaced 'Copyright \\d{4}' in tests/System/V1/SpeechSmokeTest.php.[0m
[35msynthtool > [34mReplaced 'RecognitionConfig_AudioEncoding' in src/V1p1beta1/Gapic/SpeechGapicClient.php.[0m
[35msynthtool > [34mReplaced 'RecognitionConfig_AudioEncoding' in src/V1/Gapic/SpeechGapicClient.php.[0m
[35msynthtool > [34mReplaced 'will be removed in the next major release' in src/V1p1beta1/RecognitionMetadata_InteractionType.php.[0m
[35msynthtool > [34mReplaced 'will be removed in the next major release' in src/V1p1beta1/RecognitionConfig_AudioEncoding.php.[0m
[35msynthtool > [34mReplaced 'will be removed in the next major release' in src/V1p1beta1/StreamingRecognizeResponse_SpeechEventType.php.[0m
[35msynthtool > [34mReplaced 'will be removed in the next major release' in src/V1p1beta1/RecognitionMetadata_MicrophoneDistance.php.[0m
[35msynthtool > [34mReplaced 'will be removed in the next major release' in src/V1p1beta1/RecognitionMetadata_RecordingDeviceType.php.[0m
[35msynthtool > [34mReplaced 'will be removed in the next major release' in src/V1p1beta1/RecognitionMetadata_OriginalMediaType.php.[0m
[35msynthtool > [34mReplaced 'will be removed in the next major release' in src/V1/RecognitionConfig_AudioEncoding.php.[0m
[35msynthtool > [34mReplaced 'will be removed in the next major release' in src/V1/StreamingRecognizeResponse_SpeechEventType.php.[0m
[35msynthtool > [36mCleaned up 1 temporary directories.[0m
Changed files:
On branch autosynth-speech
nothing to commit, working tree clean
Traceback (most recent call last):
File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/runpy.py", line 193, in _run_module_as_main
"__main__", mod_spec)
File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 166, in <module>
main()
File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 151, in main
commit_changes(pr_title)
File "/tmpfs/src/git/autosynth/autosynth/synth.py", line 95, in commit_changes
subprocess.check_call(["git", "commit", "-m", message])
File "/home/kbuilder/.pyenv/versions/3.6.1/lib/python3.6/subprocess.py", line 291, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['git', 'commit', '-m', '[CHANGE ME] Re-generated Speech to pick up changes in the API or client library generator.']' returned non-zero exit status 1.
```
Google internal developers can see the full log [here](https://sponge/72b66427-a48f-4376-80dc-810b01105202).
| priority | synthesis failed for speech hello autosynth couldn t regenerate speech broken heart here s the output from running synth py cloning into working repo switched to branch autosynth speech are running the synthesis script directly this will be disabled in a future release of synthtool please use m synthtool instead dependencies artman image latest pulling from googleapis artman digest status image is up to date for googleapis artman latest googleapis generator for google cloud speech artman speech yaml code into home kbuilder cache synthtool googleapis artman genfiles php google cloud speech generator for google cloud speech artman speech yaml code into home kbuilder cache synthtool googleapis artman genfiles php google cloud speech copyright d in src gapic speechgapicclient php copyright d in src gapic speechgapicclient php copyright d in src gapic speechgapicclient php copyright d in tests snippet speechclienttest php copyright d in tests unit speechclienttest php copyright d in tests unit speechclienttest php copyright d in tests unit speechclientextensiontest php copyright d in tests system speechsmoketest php copyright d in tests system speechsmoketest php recognitionconfig audioencoding in src gapic speechgapicclient php recognitionconfig audioencoding in src gapic speechgapicclient php will be removed in the next major release in src recognitionmetadata interactiontype php will be removed in the next major release in src recognitionconfig audioencoding php will be removed in the next major release in src streamingrecognizeresponse speecheventtype php will be removed in the next major release in src recognitionmetadata microphonedistance php will be removed in the next major release in src recognitionmetadata recordingdevicetype php will be removed in the next major release in src recognitionmetadata originalmediatype php will be removed in the next major release in src recognitionconfig audioencoding php will be removed in the next major release in src streamingrecognizeresponse speecheventtype php up temporary directories changed files on branch autosynth speech nothing to commit working tree clean traceback most recent call last file home kbuilder pyenv versions lib runpy py line in run module as main main mod spec file home kbuilder pyenv versions lib runpy py line in run code exec code run globals file tmpfs src git autosynth autosynth synth py line in main file tmpfs src git autosynth autosynth synth py line in main commit changes pr title file tmpfs src git autosynth autosynth synth py line in commit changes subprocess check call file home kbuilder pyenv versions lib subprocess py line in check call raise calledprocesserror retcode cmd subprocess calledprocesserror command re generated speech to pick up changes in the api or client library generator returned non zero exit status google internal developers can see the full log | 1 |
292,677 | 25,228,763,025 | IssuesEvent | 2022-11-14 17:58:50 | ImagingDataCommons/IDC-WebApp | https://api.github.com/repos/ImagingDataCommons/IDC-WebApp | closed | Analysis type collections do not contain the description and links to match the original collections in Prod Tier UI | enhancement merged:dev testing needed testing passed | 
| 2.0 | Analysis type collections do not contain the description and links to match the original collections in Prod Tier UI - 
| non_priority | analysis type collections do not contain the description and links to match the original collections in prod tier ui | 0 |
157,959 | 6,019,265,645 | IssuesEvent | 2017-06-07 14:11:36 | openshift/origin | https://api.github.com/repos/openshift/origin | closed | Unable to parse docker version "1.26": illegal version string "1.26" | component/kubernetes kind/bug priority/P1 | I see the `Unable to parse docker version "1.26": illegal version string "1.26"` error in OpenShift logs.
##### Version
```console
$ openshift version
openshift v3.6.0-alpha.1+a666b7c-745-dirty
kubernetes v1.6.1+5115d708d7
etcd 3.1.0
$ oc version
oc v3.6.0-alpha.1+a666b7c-745-dirty
kubernetes v1.6.1+5115d708d7
features: Basic-Auth
Unable to connect to the server: x509: certificate signed by unknown authority
```
##### Steps To Reproduce
1. `cd examples/sample-app`
2. `sudo `which openshift` start --public-master=127.0.0.1 --volume-dir=$PWD/volumes &>logs/openshift.log`
##### Current Result
```
E0522 17:37:54.975306 12527 container_manager_linux.go:90] Unable to parse docker version "1.26": illegal version string "1.26"
W0522 17:37:55.066851 12527 container_manager_linux.go:750] CPUAccounting not enabled for pid: 12131
W0522 17:37:55.066868 12527 container_manager_linux.go:753] MemoryAccounting not enabled for pid: 12131
W0522 17:37:55.066960 12527 container_manager_linux.go:750] CPUAccounting not enabled for pid: 12527
W0522 17:37:55.066965 12527 container_manager_linux.go:753] MemoryAccounting not enabled for pid: 12527
```
##### Expected Result
There is no such error.
##### Additional Information
```console
$ docker version
Client:
Version: 1.13.1
API version: 1.26
Package version: docker-1.13.1-9.git14cc629.fc27.x86_64
Go version: go1.8.1
Git commit: 14cc629/1.13.1
Built: Thu Apr 13 18:28:00 2017
OS/Arch: linux/amd64
Server:
Version: 1.13.1
API version: 1.26 (minimum version 1.12)
Package version: docker-1.13.1-9.git14cc629.fc27.x86_64
Go version: go1.8.1
Git commit: 14cc629/1.13.1
Built: Thu Apr 13 18:28:00 2017
OS/Arch: linux/amd64
Experimental: false
$ rpm -qa | grep docker
docker-common-1.13.1-9.git14cc629.fc27.x86_64
docker-rhel-push-plugin-1.13.1-9.git14cc629.fc27.x86_64
docker-1.13.1-9.git14cc629.fc27.x86_64
$ cat /etc/redhat-release
Fedora release 25 (Twenty Five)
```
| 1.0 | Unable to parse docker version "1.26": illegal version string "1.26" - I see the `Unable to parse docker version "1.26": illegal version string "1.26"` error in OpenShift logs.
##### Version
```console
$ openshift version
openshift v3.6.0-alpha.1+a666b7c-745-dirty
kubernetes v1.6.1+5115d708d7
etcd 3.1.0
$ oc version
oc v3.6.0-alpha.1+a666b7c-745-dirty
kubernetes v1.6.1+5115d708d7
features: Basic-Auth
Unable to connect to the server: x509: certificate signed by unknown authority
```
##### Steps To Reproduce
1. `cd examples/sample-app`
2. `sudo `which openshift` start --public-master=127.0.0.1 --volume-dir=$PWD/volumes &>logs/openshift.log`
##### Current Result
```
E0522 17:37:54.975306 12527 container_manager_linux.go:90] Unable to parse docker version "1.26": illegal version string "1.26"
W0522 17:37:55.066851 12527 container_manager_linux.go:750] CPUAccounting not enabled for pid: 12131
W0522 17:37:55.066868 12527 container_manager_linux.go:753] MemoryAccounting not enabled for pid: 12131
W0522 17:37:55.066960 12527 container_manager_linux.go:750] CPUAccounting not enabled for pid: 12527
W0522 17:37:55.066965 12527 container_manager_linux.go:753] MemoryAccounting not enabled for pid: 12527
```
##### Expected Result
There is no such error.
##### Additional Information
```console
$ docker version
Client:
Version: 1.13.1
API version: 1.26
Package version: docker-1.13.1-9.git14cc629.fc27.x86_64
Go version: go1.8.1
Git commit: 14cc629/1.13.1
Built: Thu Apr 13 18:28:00 2017
OS/Arch: linux/amd64
Server:
Version: 1.13.1
API version: 1.26 (minimum version 1.12)
Package version: docker-1.13.1-9.git14cc629.fc27.x86_64
Go version: go1.8.1
Git commit: 14cc629/1.13.1
Built: Thu Apr 13 18:28:00 2017
OS/Arch: linux/amd64
Experimental: false
$ rpm -qa | grep docker
docker-common-1.13.1-9.git14cc629.fc27.x86_64
docker-rhel-push-plugin-1.13.1-9.git14cc629.fc27.x86_64
docker-1.13.1-9.git14cc629.fc27.x86_64
$ cat /etc/redhat-release
Fedora release 25 (Twenty Five)
```
| priority | unable to parse docker version illegal version string i see the unable to parse docker version illegal version string error in openshift logs version console openshift version openshift alpha dirty kubernetes etcd oc version oc alpha dirty kubernetes features basic auth unable to connect to the server certificate signed by unknown authority steps to reproduce cd examples sample app sudo which openshift start public master volume dir pwd volumes logs openshift log current result container manager linux go unable to parse docker version illegal version string container manager linux go cpuaccounting not enabled for pid container manager linux go memoryaccounting not enabled for pid container manager linux go cpuaccounting not enabled for pid container manager linux go memoryaccounting not enabled for pid expected result there is no such error additional information console docker version client version api version package version docker go version git commit built thu apr os arch linux server version api version minimum version package version docker go version git commit built thu apr os arch linux experimental false rpm qa grep docker docker common docker rhel push plugin docker cat etc redhat release fedora release twenty five | 1 |
13,870 | 3,203,778,964 | IssuesEvent | 2015-10-02 20:50:44 | SEED-platform/seed | https://api.github.com/repos/SEED-platform/seed | opened | Reports -- order of building classification | Design Issue Reporting | Looks like building classification is in reverse alpha order when looking at the labels on the Y axis from top to bottom
Seems like it should be alpha order with the top being the beginning of the alphabet? Not sure, but to me seems more intuitive ? Probably in the long run, we may want to give the user control over this, so maybe for now we will just leave it as is and see what users say.
| 1.0 | Reports -- order of building classification - Looks like building classification is in reverse alpha order when looking at the labels on the Y axis from top to bottom
Seems like it should be alpha order with the top being the beginning of the alphabet? Not sure, but to me seems more intuitive ? Probably in the long run, we may want to give the user control over this, so maybe for now we will just leave it as is and see what users say.
| non_priority | reports order of building classification looks like building classification is in reverse alpha order when looking at the labels on the y axis from top to bottom seems like it should be alpha order with the top being the beginning of the alphabet not sure but to me seems more intuitive probably in the long run we may want to give the user control over this so maybe for now we will just leave it as is and see what users say | 0 |
346,768 | 24,887,226,594 | IssuesEvent | 2022-10-28 08:49:44 | dr-arrgghh/ped | https://api.github.com/repos/dr-arrgghh/ped | opened | No table of contents | severity.Low type.DocumentationBug | There is no table of contents to help user navigate efficiently through the user guide.
<!--session: 1666944385276-2efd3564-4078-4a9a-80e8-1f545f8edbfa-->
<!--Version: Web v3.4.4--> | 1.0 | No table of contents - There is no table of contents to help user navigate efficiently through the user guide.
<!--session: 1666944385276-2efd3564-4078-4a9a-80e8-1f545f8edbfa-->
<!--Version: Web v3.4.4--> | non_priority | no table of contents there is no table of contents to help user navigate efficiently through the user guide | 0 |
729,124 | 25,110,034,397 | IssuesEvent | 2022-11-08 19:42:36 | osulp/Scholars-Archive | https://api.github.com/repos/osulp/Scholars-Archive | closed | Pre-populate license field for datasets | Enhancement Priority: Medium | ### Descriptive summary
It would be useful to have the license field to be pre-populated with a CC BY license as default, instead of appearing blank. During dataset reviews we often encounter that researchers are not familiar with licenses, and chose them according to what sounds best, which is usually not the best license. Having a default may help streamline the process. Since the description in the field recommends CC BY, it makes sense to have this default license to be CC BY.
I suspect that this would only be appropriate for datasets, not for other SA content. @simholt ?
### Expected behavior
When submitting a dataset, the user sees the field License pre-populated with the default option CC BY. User can change the option if desired.
### Actual behavior
When submitting a dataset, the user sees the field License blank.
### Steps to reproduce the behavior
What we are looking for is exactly the behavior of the Rights Statement, that is pre-populated with the "In Copyright" option.
### Related work
| 1.0 | Pre-populate license field for datasets - ### Descriptive summary
It would be useful to have the license field to be pre-populated with a CC BY license as default, instead of appearing blank. During dataset reviews we often encounter that researchers are not familiar with licenses, and chose them according to what sounds best, which is usually not the best license. Having a default may help streamline the process. Since the description in the field recommends CC BY, it makes sense to have this default license to be CC BY.
I suspect that this would only be appropriate for datasets, not for other SA content. @simholt ?
### Expected behavior
When submitting a dataset, the user sees the field License pre-populated with the default option CC BY. User can change the option if desired.
### Actual behavior
When submitting a dataset, the user sees the field License blank.
### Steps to reproduce the behavior
What we are looking for is exactly the behavior of the Rights Statement, that is pre-populated with the "In Copyright" option.
### Related work
| priority | pre populate license field for datasets descriptive summary it would be useful to have the license field to be pre populated with a cc by license as default instead of appearing blank during dataset reviews we often encounter that researchers are not familiar with licenses and chose them according to what sounds best which is usually not the best license having a default may help streamline the process since the description in the field recommends cc by it makes sense to have this default license to be cc by i suspect that this would only be appropriate for datasets not for other sa content simholt expected behavior when submitting a dataset the user sees the field license pre populated with the default option cc by user can change the option if desired actual behavior when submitting a dataset the user sees the field license blank steps to reproduce the behavior what we are looking for is exactly the behavior of the rights statement that is pre populated with the in copyright option related work | 1 |
382,052 | 11,300,102,061 | IssuesEvent | 2020-01-17 12:52:11 | AutoPas/AutoPas | https://api.github.com/repos/AutoPas/AutoPas | closed | AlignedAllocator is incompatible with c++20 | c++20 low priority | **Is your feature request related to a problem? Please describe.**
AlignedAllocator is incompatible with c++20 and uses deprecated functionality (c++17), see:
https://en.cppreference.com/w/cpp/memory/allocator
**Describe the solution you'd like**
Adapt to c++20
**Describe alternatives you've considered**
**Additional context**
| 1.0 | AlignedAllocator is incompatible with c++20 - **Is your feature request related to a problem? Please describe.**
AlignedAllocator is incompatible with c++20 and uses deprecated functionality (c++17), see:
https://en.cppreference.com/w/cpp/memory/allocator
**Describe the solution you'd like**
Adapt to c++20
**Describe alternatives you've considered**
**Additional context**
| priority | alignedallocator is incompatible with c is your feature request related to a problem please describe alignedallocator is incompatible with c and uses deprecated functionality c see describe the solution you d like adapt to c describe alternatives you ve considered additional context | 1 |
702,065 | 24,120,576,409 | IssuesEvent | 2022-09-20 18:19:27 | googleapis/nodejs-dlp | https://api.github.com/repos/googleapis/nodejs-dlp | closed | deid: should ignore insensitive data when masking a string failed | type: bug priority: p1 api: dlp flakybot: issue | 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: 7c53b9fb61d90cbc3e592070fcf577289d54ba21
buildURL: [Build Status](https://source.cloud.google.com/results/invocations/146260ea-01e2-4622-a770-b7111df00aa4), [Sponge](http://sponge2/146260ea-01e2-4622-a770-b7111df00aa4)
status: failed
<details><summary>Test output</summary><br><pre>Command failed: node deidentifyWithMask.js long-door-651 "My favorite color is blue"
16 UNAUTHENTICATED: Request had invalid authentication credentials. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project.
Error: Command failed: node deidentifyWithMask.js long-door-651 "My favorite color is blue"
16 UNAUTHENTICATED: Request had invalid authentication credentials. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project.
at checkExecSyncError (child_process.js:635:11)
at Object.execSync (child_process.js:671:15)
at execSync (system-test/deid.test.js:24:28)
at Context.<anonymous> (system-test/deid.test.js:50:20)
at processImmediate (internal/timers.js:461:21)</pre></details> | 1.0 | deid: should ignore insensitive data when masking a string 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: 7c53b9fb61d90cbc3e592070fcf577289d54ba21
buildURL: [Build Status](https://source.cloud.google.com/results/invocations/146260ea-01e2-4622-a770-b7111df00aa4), [Sponge](http://sponge2/146260ea-01e2-4622-a770-b7111df00aa4)
status: failed
<details><summary>Test output</summary><br><pre>Command failed: node deidentifyWithMask.js long-door-651 "My favorite color is blue"
16 UNAUTHENTICATED: Request had invalid authentication credentials. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project.
Error: Command failed: node deidentifyWithMask.js long-door-651 "My favorite color is blue"
16 UNAUTHENTICATED: Request had invalid authentication credentials. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project.
at checkExecSyncError (child_process.js:635:11)
at Object.execSync (child_process.js:671:15)
at execSync (system-test/deid.test.js:24:28)
at Context.<anonymous> (system-test/deid.test.js:50:20)
at processImmediate (internal/timers.js:461:21)</pre></details> | priority | deid should ignore insensitive data when masking a string 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 command failed node deidentifywithmask js long door my favorite color is blue unauthenticated request had invalid authentication credentials expected oauth access token login cookie or other valid authentication credential see error command failed node deidentifywithmask js long door my favorite color is blue unauthenticated request had invalid authentication credentials expected oauth access token login cookie or other valid authentication credential see at checkexecsyncerror child process js at object execsync child process js at execsync system test deid test js at context system test deid test js at processimmediate internal timers js | 1 |
80,469 | 3,561,948,046 | IssuesEvent | 2016-01-24 04:49:45 | derekparker/delve | https://api.github.com/repos/derekparker/delve | opened | Remaining Windows work | kind/discussion kind/enhancement os/windows priority/P0 | - [ ] **TestDebugLinePrologueParser**
Only on some machines and Go versions. Appears to be because of buffers in the debugline data which are larger than they should be in Windows binaries? I suspect there is a bug in the Go compiler on Windows that we'll need to work around.
- [ ] **TestNextConcurrent flakiness**
Occasional occurrences of the following errors:
`proc_test.go:355: Program did not continue to correct next location expected 11 was parallel_next.go:10`
`proc_test.go:355: Program did not continue to correct next location expected 11 was parallel_next.go:8`
`proc_test.go:355: Program did not continue to correct next location expected 10 was parallel_next.go:8`
`proc_test.go:410: Program did not continue to correct next location expected 11 was parallel_next.go:10`
`proc_test.go:403: Initial breakpoint triggered twice for the same goroutine`
- [ ] **Attach is not supported**
Should also add test coverage for attach on all platforms.
- [ ] **TestNextNetHTTP is disabled on Windows**
Temporarily disabled this test, need to investigate the failure.
- [ ] **Should we load symbols on Windows?**
Thread information is not displayed nicely for most non-active threads because the PC on those threads is in ntdll or other dynamically loaded code. To address this, we would need to load symbols on Windows and merge that information with the DWARF symbols. This should be possible, but worth discussing before implementing.
- [ ] **thread.halt() may need to actually halt threads in some cases**
See comment in implementation.
- [ ] **Can we remove canContinue?**
dbp.Step currently relies on checking this, but would be nice to factor it to not need this concept in addition to blocked and stopped.
- [ ] **Infrequent failures in TestBreakPointCount**
Pretty infrequent occurence, and seemingly always with 101 + 99. So it appears that one of the breakpoint hits is getting recorded as being on the wrong thread.
Once merged, we will also want to do:
- [ ] **Add Appveyor project tracking derekparker/delve and badge in README**
- [ ] **Update docs with info on building/running on Windows**
Mostly just MinGW requirement which is likely not present for many Windows Go users. | 1.0 | Remaining Windows work - - [ ] **TestDebugLinePrologueParser**
Only on some machines and Go versions. Appears to be because of buffers in the debugline data which are larger than they should be in Windows binaries? I suspect there is a bug in the Go compiler on Windows that we'll need to work around.
- [ ] **TestNextConcurrent flakiness**
Occasional occurrences of the following errors:
`proc_test.go:355: Program did not continue to correct next location expected 11 was parallel_next.go:10`
`proc_test.go:355: Program did not continue to correct next location expected 11 was parallel_next.go:8`
`proc_test.go:355: Program did not continue to correct next location expected 10 was parallel_next.go:8`
`proc_test.go:410: Program did not continue to correct next location expected 11 was parallel_next.go:10`
`proc_test.go:403: Initial breakpoint triggered twice for the same goroutine`
- [ ] **Attach is not supported**
Should also add test coverage for attach on all platforms.
- [ ] **TestNextNetHTTP is disabled on Windows**
Temporarily disabled this test, need to investigate the failure.
- [ ] **Should we load symbols on Windows?**
Thread information is not displayed nicely for most non-active threads because the PC on those threads is in ntdll or other dynamically loaded code. To address this, we would need to load symbols on Windows and merge that information with the DWARF symbols. This should be possible, but worth discussing before implementing.
- [ ] **thread.halt() may need to actually halt threads in some cases**
See comment in implementation.
- [ ] **Can we remove canContinue?**
dbp.Step currently relies on checking this, but would be nice to factor it to not need this concept in addition to blocked and stopped.
- [ ] **Infrequent failures in TestBreakPointCount**
Pretty infrequent occurence, and seemingly always with 101 + 99. So it appears that one of the breakpoint hits is getting recorded as being on the wrong thread.
Once merged, we will also want to do:
- [ ] **Add Appveyor project tracking derekparker/delve and badge in README**
- [ ] **Update docs with info on building/running on Windows**
Mostly just MinGW requirement which is likely not present for many Windows Go users. | priority | remaining windows work testdebuglineprologueparser only on some machines and go versions appears to be because of buffers in the debugline data which are larger than they should be in windows binaries i suspect there is a bug in the go compiler on windows that we ll need to work around testnextconcurrent flakiness occasional occurrences of the following errors proc test go program did not continue to correct next location expected was parallel next go proc test go program did not continue to correct next location expected was parallel next go proc test go program did not continue to correct next location expected was parallel next go proc test go program did not continue to correct next location expected was parallel next go proc test go initial breakpoint triggered twice for the same goroutine attach is not supported should also add test coverage for attach on all platforms testnextnethttp is disabled on windows temporarily disabled this test need to investigate the failure should we load symbols on windows thread information is not displayed nicely for most non active threads because the pc on those threads is in ntdll or other dynamically loaded code to address this we would need to load symbols on windows and merge that information with the dwarf symbols this should be possible but worth discussing before implementing thread halt may need to actually halt threads in some cases see comment in implementation can we remove cancontinue dbp step currently relies on checking this but would be nice to factor it to not need this concept in addition to blocked and stopped infrequent failures in testbreakpointcount pretty infrequent occurence and seemingly always with so it appears that one of the breakpoint hits is getting recorded as being on the wrong thread once merged we will also want to do add appveyor project tracking derekparker delve and badge in readme update docs with info on building running on windows mostly just mingw requirement which is likely not present for many windows go users | 1 |
21,889 | 14,918,487,813 | IssuesEvent | 2021-01-22 21:47:32 | PavlidisLab/Gemma | https://api.github.com/repos/PavlidisLab/Gemma | opened | Use Tomcat Manager App to deploy/redeploy Gemma | enhancement infrastructure | This is less disruptive than restarting Tomcat and safer than auto-reloading the app when then WAR changes.
- [ ] disable auto-reload
- [ ] add jenkins to the list of authorized users in Tomcat configuration
More details here: https://tomcat.apache.org/tomcat-8.5-doc/manager-howto.html#Supported_Manager_Commands
It should be first tested on the development instance. | 1.0 | Use Tomcat Manager App to deploy/redeploy Gemma - This is less disruptive than restarting Tomcat and safer than auto-reloading the app when then WAR changes.
- [ ] disable auto-reload
- [ ] add jenkins to the list of authorized users in Tomcat configuration
More details here: https://tomcat.apache.org/tomcat-8.5-doc/manager-howto.html#Supported_Manager_Commands
It should be first tested on the development instance. | non_priority | use tomcat manager app to deploy redeploy gemma this is less disruptive than restarting tomcat and safer than auto reloading the app when then war changes disable auto reload add jenkins to the list of authorized users in tomcat configuration more details here it should be first tested on the development instance | 0 |
723,917 | 24,912,421,020 | IssuesEvent | 2022-10-30 01:53:37 | milvus-io/milvus | https://api.github.com/repos/milvus-io/milvus | closed | [Bug]: Create index for varchar field timeout after Milvus reinstallation in master branch | kind/bug priority/critical-urgent severity/critical triage/accepted | ### Is there an existing issue for this?
- [X] I have searched the existing issues
### Environment
```markdown
- Milvus version:master-20220926-804c18df
- Deployment mode(standalone or cluster): standalone
- SDK version(e.g. pymilvus v2.0.0rc2): pymilvus==2.2.0.dev30
- OS(Ubuntu or CentOS):
- CPU/Memory:
- GPU:
- Others:
```
### Current Behavior
```
[2022-09-26T09:14:55.762Z] [2022-09-26 09:10:57 - INFO - ci_test]: inserted 3000 data into collection deploy_test_index_type_BIN_IVF_FLAT_is_compacted_not_compacted_segment_status_all_is_vector_indexed_is_vector_indexed_is_string_indexed_is_string_indexed_replica_number_0_is_deleted_is_deleted_data_size_3000 (common_func.py:684)
[2022-09-26T09:14:55.762Z] [2022-09-26 09:10:57 - DEBUG - ci_test]: (api_request) : [Collection.insert] args: [ int64 float varchar binary_vector
[2022-09-26T09:14:55.762Z] 0 0 0.0 0 b'\xdb\xdf\x18\x9a\xf6\x0e&\xb1\x9c}\xfc\x16\x...
[2022-09-26T09:14:55.762Z] 1 1 1.0 1 b'\xc6\x1aP\xd0\xe2\xb4}\x83\xf7\x06X \x9c\x9a6U'
[2022-09-26T09:14:55.762Z] 2 2 2.0 2 b'\x86D\xf5\x8f\x0e\xd34\xe6\xa1]......, kwargs: {'timeout': 20} (api_request.py:56)
[2022-09-26T09:14:55.762Z] [2022-09-26 09:10:57 - DEBUG - ci_test]: (api_response) : (insert count: 3000, delete count: 0, upsert count: 0, timestamp: 436255708385640449, success count: 3000, err count: 0) (api_request.py:31)
[2022-09-26T09:14:55.762Z] [2022-09-26 09:10:57 - DEBUG - ci_test]: (api_request) : [Collection.flush] args: [], kwargs: {'timeout': 20} (api_request.py:56)
[2022-09-26T09:14:55.762Z] [2022-09-26 09:11:00 - DEBUG - ci_test]: (api_response) : None (api_request.py:31)
[2022-09-26T09:14:55.762Z] [2022-09-26 09:11:00 - DEBUG - ci_test]: (api_request) : [Collection.delete] args: ['int64 in [10, 11, 12, 13, 14, 15, 16, 17, 18, 19]', None, 20], kwargs: {} (api_request.py:56)
[2022-09-26T09:14:55.762Z] [2022-09-26 09:11:00 - DEBUG - ci_test]: (api_response) : (insert count: 0, delete count: 10, upsert count: 0, timestamp: 436255709171810306, success count: 0, err count: 0) (api_request.py:31)
[2022-09-26T09:14:55.762Z] [2022-09-26 09:11:00 - DEBUG - ci_test]: (api_request) : [Collection.create_index] args: ['binary_vector', {'index_type': 'BIN_IVF_FLAT', 'params': {'nlist': 128}, 'metric_type': 'HAMMING'}], kwargs: {'timeout': 40, 'index_name': '_default_idx'} (api_request.py:56)
[2022-09-26T09:14:55.762Z] [2022-09-26 09:11:11 - DEBUG - ci_test]: (api_response) : Status(code=0, message='') (api_request.py:31)
[2022-09-26T09:14:55.762Z] [2022-09-26 09:11:11 - DEBUG - ci_test]: (api_request) : [Collection.create_index] args: ['varchar', {}], kwargs: {'timeout': 40, 'index_name': '_default_string_idx'} (api_request.py:56)
[2022-09-26T09:14:55.762Z] [2022-09-26 09:11:51 - ERROR - pymilvus.decorators]: RPC error: [wait_for_creating_index], <MilvusException: (code=1, message=CreateIndex Timeout)>, <Time:{'RPC start': '2022-09-26 09:11:11.524852', 'RPC error': '2022-09-26 09:11:51.587205'}> (decorators.py:100)
[2022-09-26T09:14:55.762Z] [2022-09-26 09:11:51 - ERROR - pymilvus.decorators]: RPC error: [create_index], <MilvusException: (code=1, message=CreateIndex Timeout)>, <Time:{'RPC start': '2022-09-26 09:11:11.507777', 'RPC error': '2022-09-26 09:11:51.587436'}> (decorators.py:100)
[2022-09-26T09:14:55.762Z] [2022-09-26 09:11:51 - ERROR - ci_test]: Traceback (most recent call last):
[2022-09-26T09:14:55.762Z] File "/home/jenkins/agent/workspace/tests/python_client/utils/api_request.py", line 26, in inner_wrapper
[2022-09-26T09:14:55.762Z] res = func(*args, **_kwargs)
[2022-09-26T09:14:55.762Z] File "/home/jenkins/agent/workspace/tests/python_client/utils/api_request.py", line 57, in api_request
[2022-09-26T09:14:55.762Z] return func(*arg, **kwargs)
[2022-09-26T09:14:55.762Z] File "/usr/local/lib/python3.7/dist-packages/pymilvus/orm/collection.py", line 1087, in create_index
[2022-09-26T09:14:55.762Z] timeout=timeout, **kwargs)
[2022-09-26T09:14:55.762Z] File "/usr/local/lib/python3.7/dist-packages/pymilvus/decorators.py", line 101, in handler
[2022-09-26T09:14:55.762Z] raise e
[2022-09-26T09:14:55.762Z] File "/usr/local/lib/python3.7/dist-packages/pymilvus/decorators.py", line 97, in handler
[2022-09-26T09:14:55.762Z] return func(*args, **kwargs)
[2022-09-26T09:14:55.762Z] File "/usr/local/lib/python3.7/dist-packages/pymilvus/decorators.py", line 127, in handler
[2022-09-26T09:14:55.762Z] ret = func(self, *args, **kwargs)
[2022-09-26T09:14:55.762Z] File "/usr/local/lib/python3.7/dist-packages/pymilvus/decorators.py", line 79, in handler
[2022-09-26T09:14:55.762Z] raise e
[2022-09-26T09:14:55.762Z] File "/usr/local/lib/python3.7/dist-packages/pymilvus/decorators.py", line 50, in handler
[2022-09-26T09:14:55.762Z] return func(self, *args, **kwargs)
[2022-09-26T09:14:55.762Z] File "/usr/local/lib/python3.7/dist-packages/pymilvus/client/grpc_handler.py", line 581, in create_index
[2022-09-26T09:14:55.762Z] timeout=timeout)
[2022-09-26T09:14:55.762Z] File "/usr/local/lib/python3.7/dist-packages/pymilvus/decorators.py", line 101, in handler
[2022-09-26T09:14:55.762Z] raise e
[2022-09-26T09:14:55.762Z] File "/usr/local/lib/python3.7/dist-packages/pymilvus/decorators.py", line 97, in handler
[2022-09-26T09:14:55.762Z] return func(*args, **kwargs)
[2022-09-26T09:14:55.762Z] File "/usr/local/lib/python3.7/dist-packages/pymilvus/decorators.py", line 127, in handler
[2022-09-26T09:14:55.762Z] ret = func(self, *args, **kwargs)
[2022-09-26T09:14:55.762Z] File "/usr/local/lib/python3.7/dist-packages/pymilvus/decorators.py", line 79, in handler
[2022-09-26T09:14:55.762Z] raise e
[2022-09-26T09:14:55.762Z] File "/usr/local/lib/python3.7/dist-packages/pymilvus/decorators.py", line 50, in handler
[2022-09-26T09:14:55.762Z] return func(self, *args, **kwargs)
[2022-09-26T09:14:55.762Z] File "/usr/local/lib/python3.7/dist-packages/pymilvus/client/grpc_handler.py", line 652, in wait_for_creating_index
[2022-09-26T09:14:55.762Z] raise MilvusException(1, "CreateIndex Timeout")
[2022-09-26T09:14:55.762Z] pymilvus.exceptions.MilvusException: <MilvusException: (code=1, message=CreateIndex Timeout)>
[2022-09-26T09:14:55.762Z] (api_request.py:39)
```
### Expected Behavior
all test cases passed
### Steps To Reproduce
_No response_
### Milvus Log
failed job: https://qa-jenkins.milvus.io/blue/organizations/jenkins/deploy_test/detail/deploy_test/301/pipeline
log:
[artifacts-standalone-reinstall-301-server-logs.tar.gz](https://github.com/milvus-io/milvus/files/9645232/artifacts-standalone-reinstall-301-server-logs.tar.gz)
[artifacts-standalone-reinstall-301-pytest-logs.tar.gz](https://github.com/milvus-io/milvus/files/9645235/artifacts-standalone-reinstall-301-pytest-logs.tar.gz)
### Anything else?
_No response_ | 1.0 | [Bug]: Create index for varchar field timeout after Milvus reinstallation in master branch - ### Is there an existing issue for this?
- [X] I have searched the existing issues
### Environment
```markdown
- Milvus version:master-20220926-804c18df
- Deployment mode(standalone or cluster): standalone
- SDK version(e.g. pymilvus v2.0.0rc2): pymilvus==2.2.0.dev30
- OS(Ubuntu or CentOS):
- CPU/Memory:
- GPU:
- Others:
```
### Current Behavior
```
[2022-09-26T09:14:55.762Z] [2022-09-26 09:10:57 - INFO - ci_test]: inserted 3000 data into collection deploy_test_index_type_BIN_IVF_FLAT_is_compacted_not_compacted_segment_status_all_is_vector_indexed_is_vector_indexed_is_string_indexed_is_string_indexed_replica_number_0_is_deleted_is_deleted_data_size_3000 (common_func.py:684)
[2022-09-26T09:14:55.762Z] [2022-09-26 09:10:57 - DEBUG - ci_test]: (api_request) : [Collection.insert] args: [ int64 float varchar binary_vector
[2022-09-26T09:14:55.762Z] 0 0 0.0 0 b'\xdb\xdf\x18\x9a\xf6\x0e&\xb1\x9c}\xfc\x16\x...
[2022-09-26T09:14:55.762Z] 1 1 1.0 1 b'\xc6\x1aP\xd0\xe2\xb4}\x83\xf7\x06X \x9c\x9a6U'
[2022-09-26T09:14:55.762Z] 2 2 2.0 2 b'\x86D\xf5\x8f\x0e\xd34\xe6\xa1]......, kwargs: {'timeout': 20} (api_request.py:56)
[2022-09-26T09:14:55.762Z] [2022-09-26 09:10:57 - DEBUG - ci_test]: (api_response) : (insert count: 3000, delete count: 0, upsert count: 0, timestamp: 436255708385640449, success count: 3000, err count: 0) (api_request.py:31)
[2022-09-26T09:14:55.762Z] [2022-09-26 09:10:57 - DEBUG - ci_test]: (api_request) : [Collection.flush] args: [], kwargs: {'timeout': 20} (api_request.py:56)
[2022-09-26T09:14:55.762Z] [2022-09-26 09:11:00 - DEBUG - ci_test]: (api_response) : None (api_request.py:31)
[2022-09-26T09:14:55.762Z] [2022-09-26 09:11:00 - DEBUG - ci_test]: (api_request) : [Collection.delete] args: ['int64 in [10, 11, 12, 13, 14, 15, 16, 17, 18, 19]', None, 20], kwargs: {} (api_request.py:56)
[2022-09-26T09:14:55.762Z] [2022-09-26 09:11:00 - DEBUG - ci_test]: (api_response) : (insert count: 0, delete count: 10, upsert count: 0, timestamp: 436255709171810306, success count: 0, err count: 0) (api_request.py:31)
[2022-09-26T09:14:55.762Z] [2022-09-26 09:11:00 - DEBUG - ci_test]: (api_request) : [Collection.create_index] args: ['binary_vector', {'index_type': 'BIN_IVF_FLAT', 'params': {'nlist': 128}, 'metric_type': 'HAMMING'}], kwargs: {'timeout': 40, 'index_name': '_default_idx'} (api_request.py:56)
[2022-09-26T09:14:55.762Z] [2022-09-26 09:11:11 - DEBUG - ci_test]: (api_response) : Status(code=0, message='') (api_request.py:31)
[2022-09-26T09:14:55.762Z] [2022-09-26 09:11:11 - DEBUG - ci_test]: (api_request) : [Collection.create_index] args: ['varchar', {}], kwargs: {'timeout': 40, 'index_name': '_default_string_idx'} (api_request.py:56)
[2022-09-26T09:14:55.762Z] [2022-09-26 09:11:51 - ERROR - pymilvus.decorators]: RPC error: [wait_for_creating_index], <MilvusException: (code=1, message=CreateIndex Timeout)>, <Time:{'RPC start': '2022-09-26 09:11:11.524852', 'RPC error': '2022-09-26 09:11:51.587205'}> (decorators.py:100)
[2022-09-26T09:14:55.762Z] [2022-09-26 09:11:51 - ERROR - pymilvus.decorators]: RPC error: [create_index], <MilvusException: (code=1, message=CreateIndex Timeout)>, <Time:{'RPC start': '2022-09-26 09:11:11.507777', 'RPC error': '2022-09-26 09:11:51.587436'}> (decorators.py:100)
[2022-09-26T09:14:55.762Z] [2022-09-26 09:11:51 - ERROR - ci_test]: Traceback (most recent call last):
[2022-09-26T09:14:55.762Z] File "/home/jenkins/agent/workspace/tests/python_client/utils/api_request.py", line 26, in inner_wrapper
[2022-09-26T09:14:55.762Z] res = func(*args, **_kwargs)
[2022-09-26T09:14:55.762Z] File "/home/jenkins/agent/workspace/tests/python_client/utils/api_request.py", line 57, in api_request
[2022-09-26T09:14:55.762Z] return func(*arg, **kwargs)
[2022-09-26T09:14:55.762Z] File "/usr/local/lib/python3.7/dist-packages/pymilvus/orm/collection.py", line 1087, in create_index
[2022-09-26T09:14:55.762Z] timeout=timeout, **kwargs)
[2022-09-26T09:14:55.762Z] File "/usr/local/lib/python3.7/dist-packages/pymilvus/decorators.py", line 101, in handler
[2022-09-26T09:14:55.762Z] raise e
[2022-09-26T09:14:55.762Z] File "/usr/local/lib/python3.7/dist-packages/pymilvus/decorators.py", line 97, in handler
[2022-09-26T09:14:55.762Z] return func(*args, **kwargs)
[2022-09-26T09:14:55.762Z] File "/usr/local/lib/python3.7/dist-packages/pymilvus/decorators.py", line 127, in handler
[2022-09-26T09:14:55.762Z] ret = func(self, *args, **kwargs)
[2022-09-26T09:14:55.762Z] File "/usr/local/lib/python3.7/dist-packages/pymilvus/decorators.py", line 79, in handler
[2022-09-26T09:14:55.762Z] raise e
[2022-09-26T09:14:55.762Z] File "/usr/local/lib/python3.7/dist-packages/pymilvus/decorators.py", line 50, in handler
[2022-09-26T09:14:55.762Z] return func(self, *args, **kwargs)
[2022-09-26T09:14:55.762Z] File "/usr/local/lib/python3.7/dist-packages/pymilvus/client/grpc_handler.py", line 581, in create_index
[2022-09-26T09:14:55.762Z] timeout=timeout)
[2022-09-26T09:14:55.762Z] File "/usr/local/lib/python3.7/dist-packages/pymilvus/decorators.py", line 101, in handler
[2022-09-26T09:14:55.762Z] raise e
[2022-09-26T09:14:55.762Z] File "/usr/local/lib/python3.7/dist-packages/pymilvus/decorators.py", line 97, in handler
[2022-09-26T09:14:55.762Z] return func(*args, **kwargs)
[2022-09-26T09:14:55.762Z] File "/usr/local/lib/python3.7/dist-packages/pymilvus/decorators.py", line 127, in handler
[2022-09-26T09:14:55.762Z] ret = func(self, *args, **kwargs)
[2022-09-26T09:14:55.762Z] File "/usr/local/lib/python3.7/dist-packages/pymilvus/decorators.py", line 79, in handler
[2022-09-26T09:14:55.762Z] raise e
[2022-09-26T09:14:55.762Z] File "/usr/local/lib/python3.7/dist-packages/pymilvus/decorators.py", line 50, in handler
[2022-09-26T09:14:55.762Z] return func(self, *args, **kwargs)
[2022-09-26T09:14:55.762Z] File "/usr/local/lib/python3.7/dist-packages/pymilvus/client/grpc_handler.py", line 652, in wait_for_creating_index
[2022-09-26T09:14:55.762Z] raise MilvusException(1, "CreateIndex Timeout")
[2022-09-26T09:14:55.762Z] pymilvus.exceptions.MilvusException: <MilvusException: (code=1, message=CreateIndex Timeout)>
[2022-09-26T09:14:55.762Z] (api_request.py:39)
```
### Expected Behavior
all test cases passed
### Steps To Reproduce
_No response_
### Milvus Log
failed job: https://qa-jenkins.milvus.io/blue/organizations/jenkins/deploy_test/detail/deploy_test/301/pipeline
log:
[artifacts-standalone-reinstall-301-server-logs.tar.gz](https://github.com/milvus-io/milvus/files/9645232/artifacts-standalone-reinstall-301-server-logs.tar.gz)
[artifacts-standalone-reinstall-301-pytest-logs.tar.gz](https://github.com/milvus-io/milvus/files/9645235/artifacts-standalone-reinstall-301-pytest-logs.tar.gz)
### Anything else?
_No response_ | priority | create index for varchar field timeout after milvus reinstallation in master branch is there an existing issue for this i have searched the existing issues environment markdown milvus version master deployment mode standalone or cluster standalone sdk version e g pymilvus pymilvus os ubuntu or centos cpu memory gpu others current behavior inserted data into collection deploy test index type bin ivf flat is compacted not compacted segment status all is vector indexed is vector indexed is string indexed is string indexed replica number is deleted is deleted data size common func py api request args float varchar binary vector b xdb xdf xfc x b b kwargs timeout api request py api response insert count delete count upsert count timestamp success count err count api request py api request args kwargs timeout api request py api response none api request py api request args none kwargs api request py api response insert count delete count upsert count timestamp success count err count api request py api request args kwargs timeout index name default idx api request py api response status code message api request py api request args kwargs timeout index name default string idx api request py rpc error decorators py rpc error decorators py traceback most recent call last file home jenkins agent workspace tests python client utils api request py line in inner wrapper res func args kwargs file home jenkins agent workspace tests python client utils api request py line in api request return func arg kwargs file usr local lib dist packages pymilvus orm collection py line in create index timeout timeout kwargs file usr local lib dist packages pymilvus decorators py line in handler raise e file usr local lib dist packages pymilvus decorators py line in handler return func args kwargs file usr local lib dist packages pymilvus decorators py line in handler ret func self args kwargs file usr local lib dist packages pymilvus decorators py line in handler raise e file usr local lib dist packages pymilvus decorators py line in handler return func self args kwargs file usr local lib dist packages pymilvus client grpc handler py line in create index timeout timeout file usr local lib dist packages pymilvus decorators py line in handler raise e file usr local lib dist packages pymilvus decorators py line in handler return func args kwargs file usr local lib dist packages pymilvus decorators py line in handler ret func self args kwargs file usr local lib dist packages pymilvus decorators py line in handler raise e file usr local lib dist packages pymilvus decorators py line in handler return func self args kwargs file usr local lib dist packages pymilvus client grpc handler py line in wait for creating index raise milvusexception createindex timeout pymilvus exceptions milvusexception api request py expected behavior all test cases passed steps to reproduce no response milvus log failed job log anything else no response | 1 |
793,910 | 28,015,628,269 | IssuesEvent | 2023-03-27 22:22:25 | rtulip/haystack | https://api.github.com/repos/rtulip/haystack | closed | Unary operator accessor fails with tuples | bug good first issue effort_low priority_low | ```
fn foo([u64 u64]: mut pair) -> [[u64 u64]] {
pair::0 dup * *pair::0 !
pair
}
```
gives the following error:
```
Error: Cannot access into non-record type `[u64 u64]`
``` | 1.0 | Unary operator accessor fails with tuples - ```
fn foo([u64 u64]: mut pair) -> [[u64 u64]] {
pair::0 dup * *pair::0 !
pair
}
```
gives the following error:
```
Error: Cannot access into non-record type `[u64 u64]`
``` | priority | unary operator accessor fails with tuples fn foo mut pair pair dup pair pair gives the following error error cannot access into non record type | 1 |
145,606 | 11,700,554,729 | IssuesEvent | 2020-03-06 17:44:41 | elastic/elasticsearch | https://api.github.com/repos/elastic/elasticsearch | opened | testSingleNumericFeatureAndMixedTrainingAndNonTrainingRows test failures | :ml >test-failure v8.0.0 | Test failure can be seen here: https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+matrix-java-periodic/ES_RUNTIME_JAVA=openjdk15,nodes=general-purpose/553/console
Not able to reliably reproduce locally.
The server logs show an interesting story.
```
[2020-03-06T16:59:01,906][INFO ][o.e.x.m.d.DataFrameAnalyticsManager] [integTest-2] [classification_single_numeric_feature_and_mixed_data_set] Started reindexing
[2020-03-06T16:59:02,613][INFO ][o.e.x.m.d.p.AnalyticsProcessManager] [integTest-2] [classification_single_numeric_feature_and_mixed_data_set] Started loading data
[2020-03-06T16:59:02,623][INFO ][o.e.x.m.d.p.AnalyticsProcessManager] [integTest-2] [classification_single_numeric_feature_and_mixed_data_set] Started analyzing
[2020-03-06T16:59:02,623][INFO ][o.e.x.m.d.p.AnalyticsProcessManager] [integTest-2] [classification_single_numeric_feature_and_mixed_data_set] Waiting for result processor to complete
[2020-03-06T16:59:04,067][INFO ][o.e.x.m.p.l.CppLogMessageHandler] [integTest-2] [classification_single_numeric_feature_and_mixed_data_set] [data_frame_analyzer/399059] [CBoostedTreeImpl.cc@1155] loss* = 0.00841236, regularization* = (depth penalty multiplier = 3.767144, soft depth limit = 5.683778, soft depth tolerance = 0.050000, tree size penalty multiplier = 1.033723, leaf weight penalty multiplier = 0.469302), downsample factor* = 1, eta* = 0.223607, eta growth rate per tree* = 1.33541, maximum number trees* = 7, feature bag fraction* = 0.2
[2020-03-06T16:59:04,067][INFO ][o.e.x.m.d.p.AnalyticsProcessManager] [integTest-2] [classification_single_numeric_feature_and_mixed_data_set] Result processor has completed
[2020-03-06T16:59:04,067][INFO ][o.e.x.m.d.p.AnalyticsProcessManager] [integTest-2] [classification_single_numeric_feature_and_mixed_data_set] Closing process
[2020-03-06T16:59:04,071][INFO ][o.e.x.m.p.l.CppLogMessageHandler] [integTest-2] [classification_single_numeric_feature_and_mixed_data_set] [data_frame_analyzer/399059] [CBoostedTreeImpl.cc@240] Training finished after 18 iterations. Time per iteration in ms mean: 106.211 std. dev: 224.044
[2020-03-06T16:59:04,176][ERROR][o.e.x.m.p.l.CppLogMessageHandler] [integTest-2] [controller/387903] [CDetachedProcessSpawner.cc@184] Child process with PID 399059 was terminated by signal 6
[2020-03-06T16:59:04,472][INFO ][o.e.x.m.p.AbstractNativeProcess] [integTest-2] [classification_single_numeric_feature_and_mixed_data_set] State output finished
[2020-03-06T16:59:04,473][ERROR][o.e.x.m.d.p.AnalyticsProcessManager] [integTest-2] [classification_single_numeric_feature_and_mixed_data_set] Error closing data frame analyzer process
org.elasticsearch.ElasticsearchException: Fatal error: '7fb1ce761000-7fb1ce762000 rw-p 00000000 00:00 0 ', version: 8.0.0-SNAPSHOT (build 5102588ca22c4b)
Fatal error: '7ffd33405000-7ffd33426000 rw-p 00000000 00:00 0 [stack]', version: 8.0.0-SNAPSHOT (build 5102588ca22c4b)
Fatal error: '7ffd3344c000-7ffd3344e000 r-xp 00000000 00:00 0 [vdso]', version: 8.0.0-SNAPSHOT (build 5102588ca22c4b)
Fatal error: 'ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall]', version: 8.0.0-SNAPSHOT (build 5102588ca22c4b)
Fatal error: 'si_signo 6, si_code: -6, si_errno: 0, address: 0x7fb1cc5ca337, library: /lib64/libc.so.6, base: 0x7fb1cc594000, normalized address: 0x36337', version: 8.0.0-SNAPSHOT (build 5102588ca22c4b)
at org.elasticsearch.xpack.core.ml.utils.ExceptionsHelper.serverError(ExceptionsHelper.java:51) ~[x-pack-core-8.0.0-SNAPSHOT.jar:8.0.0-SNAPSHOT]
at org.elasticsearch.xpack.ml.process.AbstractNativeProcess.close(AbstractNativeProcess.java:184) ~[x-pack-ml-8.0.0-SNAPSHOT.jar:8.0.0-SNAPSHOT]
at org.elasticsearch.xpack.ml.dataframe.process.AnalyticsProcessManager.closeProcess(AnalyticsProcessManager.java:320) [x-pack-ml-8.0.0-SNAPSHOT.jar:8.0.0-SNAPSHOT]
at org.elasticsearch.xpack.ml.dataframe.process.AnalyticsProcessManager.processData(AnalyticsProcessManager.java:189) [x-pack-ml-8.0.0-SNAPSHOT.jar:8.0.0-SNAPSHOT]
at org.elasticsearch.xpack.ml.dataframe.process.AnalyticsProcessManager.lambda$runJob$1(AnalyticsProcessManager.java:124) [x-pack-ml-8.0.0-SNAPSHOT.jar:8.0.0-SNAPSHOT]
at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:688) [elasticsearch-8.0.0-SNAPSHOT.jar:8.0.0-SNAPSHOT]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:630) [?:?]
at java.lang.Thread.run(Thread.java:832) [?:?]
```
Observe the line:
```
[2020-03-06T16:59:04,473][ERROR][o.e.x.m.d.p.AnalyticsProcessManager] [integTest-2] [classification_single_numeric_feature_and_mixed_data_set] Error closing data frame analyzer process
org.elasticsearch.ElasticsearchException: Fatal error: '7fb1ce761000-7fb1ce762000 rw-p 00000000 00:00 0 ', version: 8.0.0-SNAPSHOT (build 5102588ca22c4b)
Fatal error: '7ffd33405000-7ffd33426000 rw-p 00000000 00:00 0 [stack]', version: 8.0.0-SNAPSHOT (build 5102588ca22c4b)
Fatal error: '7ffd3344c000-7ffd3344e000 r-xp 00000000 00:00 0 [vdso]', version: 8.0.0-SNAPSHOT (build 5102588ca22c4b)
Fatal error: 'ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall]', version: 8.0.0-SNAPSHOT (build 5102588ca22c4b)
Fatal error: 'si_signo 6, si_code: -6, si_errno: 0, address: 0x7fb1cc5ca337, library: /lib64/libc.so.6, base: 0x7fb1cc594000, normalized address: 0x36337', version: 8.0.0-SNAPSHOT (build 5102588ca22c4b)
```
This indicates the native process called `abort()`.
***MIGHT*** be related to https://github.com/elastic/ml-cpp/issues/1040 | 1.0 | testSingleNumericFeatureAndMixedTrainingAndNonTrainingRows test failures - Test failure can be seen here: https://elasticsearch-ci.elastic.co/job/elastic+elasticsearch+master+matrix-java-periodic/ES_RUNTIME_JAVA=openjdk15,nodes=general-purpose/553/console
Not able to reliably reproduce locally.
The server logs show an interesting story.
```
[2020-03-06T16:59:01,906][INFO ][o.e.x.m.d.DataFrameAnalyticsManager] [integTest-2] [classification_single_numeric_feature_and_mixed_data_set] Started reindexing
[2020-03-06T16:59:02,613][INFO ][o.e.x.m.d.p.AnalyticsProcessManager] [integTest-2] [classification_single_numeric_feature_and_mixed_data_set] Started loading data
[2020-03-06T16:59:02,623][INFO ][o.e.x.m.d.p.AnalyticsProcessManager] [integTest-2] [classification_single_numeric_feature_and_mixed_data_set] Started analyzing
[2020-03-06T16:59:02,623][INFO ][o.e.x.m.d.p.AnalyticsProcessManager] [integTest-2] [classification_single_numeric_feature_and_mixed_data_set] Waiting for result processor to complete
[2020-03-06T16:59:04,067][INFO ][o.e.x.m.p.l.CppLogMessageHandler] [integTest-2] [classification_single_numeric_feature_and_mixed_data_set] [data_frame_analyzer/399059] [CBoostedTreeImpl.cc@1155] loss* = 0.00841236, regularization* = (depth penalty multiplier = 3.767144, soft depth limit = 5.683778, soft depth tolerance = 0.050000, tree size penalty multiplier = 1.033723, leaf weight penalty multiplier = 0.469302), downsample factor* = 1, eta* = 0.223607, eta growth rate per tree* = 1.33541, maximum number trees* = 7, feature bag fraction* = 0.2
[2020-03-06T16:59:04,067][INFO ][o.e.x.m.d.p.AnalyticsProcessManager] [integTest-2] [classification_single_numeric_feature_and_mixed_data_set] Result processor has completed
[2020-03-06T16:59:04,067][INFO ][o.e.x.m.d.p.AnalyticsProcessManager] [integTest-2] [classification_single_numeric_feature_and_mixed_data_set] Closing process
[2020-03-06T16:59:04,071][INFO ][o.e.x.m.p.l.CppLogMessageHandler] [integTest-2] [classification_single_numeric_feature_and_mixed_data_set] [data_frame_analyzer/399059] [CBoostedTreeImpl.cc@240] Training finished after 18 iterations. Time per iteration in ms mean: 106.211 std. dev: 224.044
[2020-03-06T16:59:04,176][ERROR][o.e.x.m.p.l.CppLogMessageHandler] [integTest-2] [controller/387903] [CDetachedProcessSpawner.cc@184] Child process with PID 399059 was terminated by signal 6
[2020-03-06T16:59:04,472][INFO ][o.e.x.m.p.AbstractNativeProcess] [integTest-2] [classification_single_numeric_feature_and_mixed_data_set] State output finished
[2020-03-06T16:59:04,473][ERROR][o.e.x.m.d.p.AnalyticsProcessManager] [integTest-2] [classification_single_numeric_feature_and_mixed_data_set] Error closing data frame analyzer process
org.elasticsearch.ElasticsearchException: Fatal error: '7fb1ce761000-7fb1ce762000 rw-p 00000000 00:00 0 ', version: 8.0.0-SNAPSHOT (build 5102588ca22c4b)
Fatal error: '7ffd33405000-7ffd33426000 rw-p 00000000 00:00 0 [stack]', version: 8.0.0-SNAPSHOT (build 5102588ca22c4b)
Fatal error: '7ffd3344c000-7ffd3344e000 r-xp 00000000 00:00 0 [vdso]', version: 8.0.0-SNAPSHOT (build 5102588ca22c4b)
Fatal error: 'ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall]', version: 8.0.0-SNAPSHOT (build 5102588ca22c4b)
Fatal error: 'si_signo 6, si_code: -6, si_errno: 0, address: 0x7fb1cc5ca337, library: /lib64/libc.so.6, base: 0x7fb1cc594000, normalized address: 0x36337', version: 8.0.0-SNAPSHOT (build 5102588ca22c4b)
at org.elasticsearch.xpack.core.ml.utils.ExceptionsHelper.serverError(ExceptionsHelper.java:51) ~[x-pack-core-8.0.0-SNAPSHOT.jar:8.0.0-SNAPSHOT]
at org.elasticsearch.xpack.ml.process.AbstractNativeProcess.close(AbstractNativeProcess.java:184) ~[x-pack-ml-8.0.0-SNAPSHOT.jar:8.0.0-SNAPSHOT]
at org.elasticsearch.xpack.ml.dataframe.process.AnalyticsProcessManager.closeProcess(AnalyticsProcessManager.java:320) [x-pack-ml-8.0.0-SNAPSHOT.jar:8.0.0-SNAPSHOT]
at org.elasticsearch.xpack.ml.dataframe.process.AnalyticsProcessManager.processData(AnalyticsProcessManager.java:189) [x-pack-ml-8.0.0-SNAPSHOT.jar:8.0.0-SNAPSHOT]
at org.elasticsearch.xpack.ml.dataframe.process.AnalyticsProcessManager.lambda$runJob$1(AnalyticsProcessManager.java:124) [x-pack-ml-8.0.0-SNAPSHOT.jar:8.0.0-SNAPSHOT]
at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:688) [elasticsearch-8.0.0-SNAPSHOT.jar:8.0.0-SNAPSHOT]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1130) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:630) [?:?]
at java.lang.Thread.run(Thread.java:832) [?:?]
```
Observe the line:
```
[2020-03-06T16:59:04,473][ERROR][o.e.x.m.d.p.AnalyticsProcessManager] [integTest-2] [classification_single_numeric_feature_and_mixed_data_set] Error closing data frame analyzer process
org.elasticsearch.ElasticsearchException: Fatal error: '7fb1ce761000-7fb1ce762000 rw-p 00000000 00:00 0 ', version: 8.0.0-SNAPSHOT (build 5102588ca22c4b)
Fatal error: '7ffd33405000-7ffd33426000 rw-p 00000000 00:00 0 [stack]', version: 8.0.0-SNAPSHOT (build 5102588ca22c4b)
Fatal error: '7ffd3344c000-7ffd3344e000 r-xp 00000000 00:00 0 [vdso]', version: 8.0.0-SNAPSHOT (build 5102588ca22c4b)
Fatal error: 'ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall]', version: 8.0.0-SNAPSHOT (build 5102588ca22c4b)
Fatal error: 'si_signo 6, si_code: -6, si_errno: 0, address: 0x7fb1cc5ca337, library: /lib64/libc.so.6, base: 0x7fb1cc594000, normalized address: 0x36337', version: 8.0.0-SNAPSHOT (build 5102588ca22c4b)
```
This indicates the native process called `abort()`.
***MIGHT*** be related to https://github.com/elastic/ml-cpp/issues/1040 | non_priority | testsinglenumericfeatureandmixedtrainingandnontrainingrows test failures test failure can be seen here not able to reliably reproduce locally the server logs show an interesting story started reindexing started loading data started analyzing waiting for result processor to complete loss regularization depth penalty multiplier soft depth limit soft depth tolerance tree size penalty multiplier leaf weight penalty multiplier downsample factor eta eta growth rate per tree maximum number trees feature bag fraction result processor has completed closing process training finished after iterations time per iteration in ms mean std dev child process with pid was terminated by signal state output finished error closing data frame analyzer process org elasticsearch elasticsearchexception fatal error rw p version snapshot build fatal error rw p version snapshot build fatal error r xp version snapshot build fatal error r xp version snapshot build fatal error si signo si code si errno address library libc so base normalized address version snapshot build at org elasticsearch xpack core ml utils exceptionshelper servererror exceptionshelper java at org elasticsearch xpack ml process abstractnativeprocess close abstractnativeprocess java at org elasticsearch xpack ml dataframe process analyticsprocessmanager closeprocess analyticsprocessmanager java at org elasticsearch xpack ml dataframe process analyticsprocessmanager processdata analyticsprocessmanager java at org elasticsearch xpack ml dataframe process analyticsprocessmanager lambda runjob analyticsprocessmanager java at org elasticsearch common util concurrent threadcontext contextpreservingrunnable run threadcontext java at java util concurrent threadpoolexecutor runworker threadpoolexecutor java at java util concurrent threadpoolexecutor worker run threadpoolexecutor java at java lang thread run thread java observe the line error closing data frame analyzer process org elasticsearch elasticsearchexception fatal error rw p version snapshot build fatal error rw p version snapshot build fatal error r xp version snapshot build fatal error r xp version snapshot build fatal error si signo si code si errno address library libc so base normalized address version snapshot build this indicates the native process called abort might be related to | 0 |
231,603 | 25,524,978,228 | IssuesEvent | 2022-11-29 00:56:23 | opensearch-project/dashboards-reports | https://api.github.com/repos/opensearch-project/dashboards-reports | closed | CVE-2022-24999 (Medium) detected in qs-6.5.2.tgz | security vulnerability | ## CVE-2022-24999 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>qs-6.5.2.tgz</b></p></summary>
<p>A querystring parser that supports nesting and arrays, with a depth limit</p>
<p>Library home page: <a href="https://registry.npmjs.org/qs/-/qs-6.5.2.tgz">https://registry.npmjs.org/qs/-/qs-6.5.2.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/qs/package.json</p>
<p>
Dependency Hierarchy:
- jsdom-16.5.0.tgz (Root Library)
- request-2.88.2.tgz
- :x: **qs-6.5.2.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>
qs before 6.10.3, as used in Express before 4.17.3 and other products, allows attackers to cause a Node process hang for an Express application because an __ proto__ key can be used. In many typical Express use cases, an unauthenticated remote attacker can place the attack payload in the query string of the URL that is used to visit the application, such as a[__proto__]=b&a[__proto__]&a[length]=100000000. The fix was backported to qs 6.9.7, 6.8.3, 6.7.3, 6.6.1, 6.5.3, 6.4.1, 6.3.3, and 6.2.4 (and therefore Express 4.17.3, which has "deps: qs@6.9.7" in its release description, is not vulnerable).
<p>Publish Date: 2022-11-26
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-24999>CVE-2022-24999</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: 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://www.cve.org/CVERecord?id=CVE-2022-24999">https://www.cve.org/CVERecord?id=CVE-2022-24999</a></p>
<p>Release Date: 2022-11-26</p>
<p>Fix Resolution: qs - 6.2.4,6.3.3,6.4.1,6.5.3,6.6.1,6.7.3,6.8.3,6.9.7,6.10.3</p>
</p>
</details>
<p></p>
| True | CVE-2022-24999 (Medium) detected in qs-6.5.2.tgz - ## CVE-2022-24999 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>qs-6.5.2.tgz</b></p></summary>
<p>A querystring parser that supports nesting and arrays, with a depth limit</p>
<p>Library home page: <a href="https://registry.npmjs.org/qs/-/qs-6.5.2.tgz">https://registry.npmjs.org/qs/-/qs-6.5.2.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/qs/package.json</p>
<p>
Dependency Hierarchy:
- jsdom-16.5.0.tgz (Root Library)
- request-2.88.2.tgz
- :x: **qs-6.5.2.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>
qs before 6.10.3, as used in Express before 4.17.3 and other products, allows attackers to cause a Node process hang for an Express application because an __ proto__ key can be used. In many typical Express use cases, an unauthenticated remote attacker can place the attack payload in the query string of the URL that is used to visit the application, such as a[__proto__]=b&a[__proto__]&a[length]=100000000. The fix was backported to qs 6.9.7, 6.8.3, 6.7.3, 6.6.1, 6.5.3, 6.4.1, 6.3.3, and 6.2.4 (and therefore Express 4.17.3, which has "deps: qs@6.9.7" in its release description, is not vulnerable).
<p>Publish Date: 2022-11-26
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-24999>CVE-2022-24999</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: 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://www.cve.org/CVERecord?id=CVE-2022-24999">https://www.cve.org/CVERecord?id=CVE-2022-24999</a></p>
<p>Release Date: 2022-11-26</p>
<p>Fix Resolution: qs - 6.2.4,6.3.3,6.4.1,6.5.3,6.6.1,6.7.3,6.8.3,6.9.7,6.10.3</p>
</p>
</details>
<p></p>
| non_priority | cve medium detected in qs tgz cve medium severity vulnerability vulnerable library qs tgz a querystring parser that supports nesting and arrays with a depth limit library home page a href path to dependency file package json path to vulnerable library node modules qs package json dependency hierarchy jsdom tgz root library request tgz x qs tgz vulnerable library found in base branch main vulnerability details qs before as used in express before and other products allows attackers to cause a node process hang for an express application because an proto key can be used in many typical express use cases an unauthenticated remote attacker can place the attack payload in the query string of the url that is used to visit the application such as a b a a the fix was backported to qs and and therefore express which has deps qs in its release description is not vulnerable 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 qs | 0 |
123,184 | 10,256,603,088 | IssuesEvent | 2019-08-21 18:04:23 | kcigeospatial/Fred_Co_Land-Management | https://api.github.com/repos/kcigeospatial/Fred_Co_Land-Management | closed | ProjectDox- Planning Workflow - Resubmittal | Ready for Test Env. Retest | System is in an awaiting applicant revisions milestone, Project Dox not receiving the communication of the condition from IPS. Applicant shouldn't go into R4C during stage
Reviews should not be added with a null result code
Ensure notifications are in place to prevent citizen from being notified via IPS.
| 2.0 | ProjectDox- Planning Workflow - Resubmittal - System is in an awaiting applicant revisions milestone, Project Dox not receiving the communication of the condition from IPS. Applicant shouldn't go into R4C during stage
Reviews should not be added with a null result code
Ensure notifications are in place to prevent citizen from being notified via IPS.
| non_priority | projectdox planning workflow resubmittal system is in an awaiting applicant revisions milestone project dox not receiving the communication of the condition from ips applicant shouldn t go into during stage reviews should not be added with a null result code ensure notifications are in place to prevent citizen from being notified via ips | 0 |
578,610 | 17,148,958,588 | IssuesEvent | 2021-07-13 17:50:37 | Couchers-org/couchers | https://api.github.com/repos/Couchers-org/couchers | closed | gRPC interceptors don't work with gRPC-Web Devtools | bug frontend priority: low | This means that the unathenticated error handler doesn't run correctly, so for example you won't be kicked out if the backend suddenly jails your or logs you out (e.g. due to ToS version updating).
This works correctly in the prod build though because we disable the dev tools there.
See also https://github.com/grpc/grpc-web/issues/1012 and https://github.com/SafetyCulture/grpc-web-devtools/issues/80 | 1.0 | gRPC interceptors don't work with gRPC-Web Devtools - This means that the unathenticated error handler doesn't run correctly, so for example you won't be kicked out if the backend suddenly jails your or logs you out (e.g. due to ToS version updating).
This works correctly in the prod build though because we disable the dev tools there.
See also https://github.com/grpc/grpc-web/issues/1012 and https://github.com/SafetyCulture/grpc-web-devtools/issues/80 | priority | grpc interceptors don t work with grpc web devtools this means that the unathenticated error handler doesn t run correctly so for example you won t be kicked out if the backend suddenly jails your or logs you out e g due to tos version updating this works correctly in the prod build though because we disable the dev tools there see also and | 1 |
11,399 | 8,380,598,652 | IssuesEvent | 2018-10-07 16:18:28 | kevinpapst/kimai2 | https://api.github.com/repos/kevinpapst/kimai2 | closed | invalid CSRF-Token | bug security | **Describe the bug**
having recieved a passwort-reset-URI , follwing it results in a CSRF-Error
**To Reproduce**
Steps to reproduce the behavior:
1. Go to 'forgot password'
2. recieve mail and click on the confirmation-URI
3. kimai-installation complains about invalid CSRF-Token
**Expected behavior**
beeing able to set new password
**Desktop (please complete the following information):**
- OS: Linux
- Browser Firefox
- Version 62.0.3
| True | invalid CSRF-Token - **Describe the bug**
having recieved a passwort-reset-URI , follwing it results in a CSRF-Error
**To Reproduce**
Steps to reproduce the behavior:
1. Go to 'forgot password'
2. recieve mail and click on the confirmation-URI
3. kimai-installation complains about invalid CSRF-Token
**Expected behavior**
beeing able to set new password
**Desktop (please complete the following information):**
- OS: Linux
- Browser Firefox
- Version 62.0.3
| non_priority | invalid csrf token describe the bug having recieved a passwort reset uri follwing it results in a csrf error to reproduce steps to reproduce the behavior go to forgot password recieve mail and click on the confirmation uri kimai installation complains about invalid csrf token expected behavior beeing able to set new password desktop please complete the following information os linux browser firefox version | 0 |
334,019 | 29,820,334,730 | IssuesEvent | 2023-06-17 01:29:42 | unifyai/ivy | https://api.github.com/repos/unifyai/ivy | closed | Fix elementwise.test_bitwise_and | Sub Task Failing Test | | | |
|---|---|
|numpy|<a href="null"><img src=https://img.shields.io/badge/-success-success></a>
|torch|<a href="null"><img src=https://img.shields.io/badge/-success-success></a>
|jax|<a href="null"><img src=https://img.shields.io/badge/-success-success></a>
|tensorflow|<a href="null"><img src=https://img.shields.io/badge/-success-success></a>
|paddle|<a href="null"><img src=https://img.shields.io/badge/-success-success></a>
| 1.0 | Fix elementwise.test_bitwise_and - | | |
|---|---|
|numpy|<a href="null"><img src=https://img.shields.io/badge/-success-success></a>
|torch|<a href="null"><img src=https://img.shields.io/badge/-success-success></a>
|jax|<a href="null"><img src=https://img.shields.io/badge/-success-success></a>
|tensorflow|<a href="null"><img src=https://img.shields.io/badge/-success-success></a>
|paddle|<a href="null"><img src=https://img.shields.io/badge/-success-success></a>
| non_priority | fix elementwise test bitwise and numpy img src torch img src jax img src tensorflow img src paddle img src | 0 |
355,376 | 10,579,955,346 | IssuesEvent | 2019-10-08 04:53:59 | CalNourish/ucbfpa-webapp | https://api.github.com/repos/CalNourish/ucbfpa-webapp | opened | New Checkout Flow | feature 🚀 high priority 🔥 | To address issue where volunteers may be scanning items too quickly.
- Add items to cart and hit checkout, which will then commit to DB (rather than have a transaction on each scan)
- And move checkout button under the grocery list
| 1.0 | New Checkout Flow - To address issue where volunteers may be scanning items too quickly.
- Add items to cart and hit checkout, which will then commit to DB (rather than have a transaction on each scan)
- And move checkout button under the grocery list
| priority | new checkout flow to address issue where volunteers may be scanning items too quickly add items to cart and hit checkout which will then commit to db rather than have a transaction on each scan and move checkout button under the grocery list | 1 |
589,040 | 17,688,522,674 | IssuesEvent | 2021-08-24 06:57:13 | threefoldfoundation/www_threefold_io | https://api.github.com/repos/threefoldfoundation/www_threefold_io | closed | Fix scaling of header image on Careers page on mobile view | priority_minor | On Careers page bottom component (Join our Community / Join our Team) scales nicely on mobile,
on the other hand, header image is shrinking small.
Please see and apply solution so header image scales as nicely as a bottom component on mobile view. Maybe we can use the same component that on the bottom of page just not link the text to anything.
Bottom component:
Header image:
| 1.0 | Fix scaling of header image on Careers page on mobile view - On Careers page bottom component (Join our Community / Join our Team) scales nicely on mobile,
on the other hand, header image is shrinking small.
Please see and apply solution so header image scales as nicely as a bottom component on mobile view. Maybe we can use the same component that on the bottom of page just not link the text to anything.
Bottom component:
Header image:
| priority | fix scaling of header image on careers page on mobile view on careers page bottom component join our community join our team scales nicely on mobile on the other hand header image is shrinking small please see and apply solution so header image scales as nicely as a bottom component on mobile view maybe we can use the same component that on the bottom of page just not link the text to anything bottom component header image | 1 |
24,906 | 17,874,759,598 | IssuesEvent | 2021-09-07 00:34:54 | leanjunio/scheduler | https://api.github.com/repos/leanjunio/scheduler | opened | Merging PRs to main does not trigger a deploy to Netlify | bug infrastructure | Problem: Even though netlify has been set to supposedly listen to merges to the main branch, it still does not trigger a build and deploy
Possible Solution: Check into using Github Actions to trigger deployments to netlify instead | 1.0 | Merging PRs to main does not trigger a deploy to Netlify - Problem: Even though netlify has been set to supposedly listen to merges to the main branch, it still does not trigger a build and deploy
Possible Solution: Check into using Github Actions to trigger deployments to netlify instead | non_priority | merging prs to main does not trigger a deploy to netlify problem even though netlify has been set to supposedly listen to merges to the main branch it still does not trigger a build and deploy possible solution check into using github actions to trigger deployments to netlify instead | 0 |
34,450 | 2,781,001,478 | IssuesEvent | 2015-05-06 09:58:41 | kromkrom/wordcontrol | https://api.github.com/repos/kromkrom/wordcontrol | opened | Display matched spelling in lexeme list | issue:change_request priority:-1 | Lexeme in the list must be accompanied by a wordform, whose spelling it was filtered by. | 1.0 | Display matched spelling in lexeme list - Lexeme in the list must be accompanied by a wordform, whose spelling it was filtered by. | priority | display matched spelling in lexeme list lexeme in the list must be accompanied by a wordform whose spelling it was filtered by | 1 |
109,439 | 4,387,416,435 | IssuesEvent | 2016-08-08 15:43:57 | RobotLocomotion/drake | https://api.github.com/repos/RobotLocomotion/drake | closed | Mysterious CI Failure - Marking the build as aborted. | priority: backlog team: software core type: bug type: continuous integration | # The Error
```
[drake:make] -- Installing: /home/ubuntu/workspace/linux-gcc-exBuild timed out (after 240 minutes). Marking the build as aborted.
20:06:49 Build was aborted
```
# Example Logs
* https://drake-jenkins.csail.mit.edu/job/linux-gcc-experimental-ros/75/console | 1.0 | Mysterious CI Failure - Marking the build as aborted. - # The Error
```
[drake:make] -- Installing: /home/ubuntu/workspace/linux-gcc-exBuild timed out (after 240 minutes). Marking the build as aborted.
20:06:49 Build was aborted
```
# Example Logs
* https://drake-jenkins.csail.mit.edu/job/linux-gcc-experimental-ros/75/console | priority | mysterious ci failure marking the build as aborted the error installing home ubuntu workspace linux gcc exbuild timed out after minutes marking the build as aborted build was aborted example logs | 1 |
2,124 | 3,295,405,967 | IssuesEvent | 2015-10-31 22:32:41 | OpenRA/OpenRA | https://api.github.com/repos/OpenRA/OpenRA | opened | Performance on latest playtest seems significantly worse than release 20150614 | Performance | I downloaded and installed the Windows packages of release 20150614 and playtest 20151031 and ran one instance each. On my system (Win7x64, i5-2500 @ 3.5 GHz, Turbo disabled), `Tick` on the RA shellmap on older release hovered in the 2.5-3.3 ms range, while the playtest varied from 3.2-5.2ms.
`Render` was ~1.7-2.2ms for both.
Their respective `perf.log` (I used local `support` dir) didn't turn up anything out of the ordinary, in fact going by `perf.log` alone, the playtest should have been a bit faster. | True | Performance on latest playtest seems significantly worse than release 20150614 - I downloaded and installed the Windows packages of release 20150614 and playtest 20151031 and ran one instance each. On my system (Win7x64, i5-2500 @ 3.5 GHz, Turbo disabled), `Tick` on the RA shellmap on older release hovered in the 2.5-3.3 ms range, while the playtest varied from 3.2-5.2ms.
`Render` was ~1.7-2.2ms for both.
Their respective `perf.log` (I used local `support` dir) didn't turn up anything out of the ordinary, in fact going by `perf.log` alone, the playtest should have been a bit faster. | non_priority | performance on latest playtest seems significantly worse than release i downloaded and installed the windows packages of release and playtest and ran one instance each on my system ghz turbo disabled tick on the ra shellmap on older release hovered in the ms range while the playtest varied from render was for both their respective perf log i used local support dir didn t turn up anything out of the ordinary in fact going by perf log alone the playtest should have been a bit faster | 0 |
297,876 | 22,407,402,569 | IssuesEvent | 2022-06-18 07:00:21 | phukiendienthoaigiare/Qua-Tang-Doanh-Nghiep-4-trong-1 | https://api.github.com/repos/phukiendienthoaigiare/Qua-Tang-Doanh-Nghiep-4-trong-1 | opened | Cùng “Đập Hộp” Quà Tặng Doanh Nghiệp 3 Trong 1 GS304 Để Xem Bên Trong Có Gì “Ngon” | documentation help wanted good first issue question | <p><strong>Bài viết này không phải là bài review, lại càng không phải là bài PR sản phẩm. Mình viết bài này chủ yếu để “đập hộp” xem thử bên trong món quà tặng doanh nghiệp 3 trong 1 GS304 này có gì để những ai có nhu cầu có thể tham khảo thôi nhé!</strong></p>
<p>Những ai làm chủ doanh nghiệp (hoặc giữ một chức vụ quan trọng trong công ty) mỗi năm, vào những dịp quan trọng sẽ có một vài món quà nho nhỏ gửi tặng đến đối tác, khách hàng thay cho lời tri ân và cảm ơn họ đã đồng hành cùng công ty. Đây cũng là cách khá phổ biến để giữ mối quan hệ cả hai thêm bền vững, có thể hợp tác lâu dài và cùng nhau hướng đến thành công trong từng dự án. Vì vậy, những món quà tặng bao giờ cũng cần phải hợp thời đại, hữu ích và được thiết kế sang trọng nhất có thể.</p>
<p>Vì thế, Quà tặng doanh nghiệp 3 trong 1 GS304 đã được ra đời với sứ mệnh vô cùng cao cả: trở thành món quà kết nối giữa các đối tác, công ty – khách hàng lại với nhau. Và lẽ dĩ nhiên, những gì thuộc gói quà tặng này đều vô cùng hữu ích đối với hầu hết các đối tượng trong xã hội.</p>
<p>Cùng xem bên trong món quà tặng này có gì nhé!</p>
<h2 id="h-dập-hộp-qua-tặng-doanh-nghiệp-3-trong-1-gs304">“Đập hộp” Quà tặng doanh nghiệp 3 trong 1 GS304</h2>
<p>Khi đập hộp xong thì mình nhận thấy, bên trong Quà tặng doanh nghiệp GS304 bao gồm:</p>
<ul><li>Pin sạc dự phòng.</li><li>Củ sạc nhanh.</li><li>Móc dán điện thoại.</li><li>Cáp sạc USB.</li><li>Hướng dẫn sử dụng.</li></ul>
<p>Cả 3 món quà trên đều là những quà tặng công nghệ vô cùng hữu dụng và hợp với thời đại công nghệ 4.0 hiện nay, lại đặc biệt phù hợp với hầu hết đối tượng trong xã hội (trừ các bé thiếu nhi). Vì vậy, xét trên phương diện hợp thời đại thì đây là hộp quà tặng vô cùng rất đáng để cho các doanh nghiệp lưu tâm.</p>
<p>Bây giờ, hãy xem xét chi tiết các món quà như thế nào nhé!</p>
<div class="wp-block-image"><figure class="aligncenter size-full"><img width="1000" height="1000" src="https://phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-11.jpg" alt="Quà Tặng Doanh Nghiệp 3 Trong 1 GS304" class="wp-image-16080" srcset="//phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-11.jpg 1000w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-11-300x300.jpg 300w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-11-150x150.jpg 150w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-11-768x768.jpg 768w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-11-990x990.jpg 990w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-11-441x441.jpg 441w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-11-600x600.jpg 600w" sizes="(max-width: 1000px) 100vw, 1000px" /><figcaption><em>Bên trong chiếc hộp Quà tặng doanh nghiệp 3 trong 1 GS304 bao gồm: pin sạc dự phòng, củ sạc nhanh và móc dán điện thoạ</em>i</figcaption></figure></div>
<h3 id="h-1-về-pin-sạc-dự-phong">1. Về pin sạc dự phòng</h3>
<p>Pin sạc dự phòng trong hộp quà có dung lượng khoảng 3000mAh – tức phụ kiện có thể cung cấp dòng điện 1000mAh trong 3 giờ đồng hồ. Như vậy, những ai sử dụng điện thoại có dung lượng pin khoảng 2000 – 3000mAh thì có thể sử dụng phụ kiện này và sạc được 50% pin, thích hợp dùng trong những lúc smartphone cạn kiệt năng lượng và cần nạp thêm pin để tiếp tục công việc.</p>
<div class="wp-block-image"><figure class="aligncenter size-full"><img width="800" height="800" src="https://phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-8.jpg" alt="Quà Tặng Doanh Nghiệp 3 Trong 1 GS304" class="wp-image-16083" srcset="//phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-8.jpg 800w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-8-300x300.jpg 300w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-8-150x150.jpg 150w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-8-768x768.jpg 768w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-8-441x441.jpg 441w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-8-600x600.jpg 600w" sizes="(max-width: 800px) 100vw, 800px" /><figcaption>Pin sạc dự phòng với đầy đủ các chức năng </figcaption></figure></div>
<p><strong><em>Đánh giá ưu nhược điểm:</em></strong></p>
<p><em><u>Ưu điểm</u></em>:</p>
<ul><li>Hỗ trợ nạp pin trong trường hợp khẩn cấp.</li><li>Tương thích với hầu hết thiết bị điện tử trên thị trường.</li><li>Có tính năng bảo vệ quá nhiệt, quá tải và tự động ngắt nguồn điện khi sạc đầy.</li><li>Thiết kế nhỏ gọn, sang trọng, dễ dàng mang theo mọi lúc, mọi nơi.</li><li>Chất liệu nhựa ABS an toàn, bền bỉ, không thấm nước.</li><li>Có đèn LED thông báo tình trạng sạc pin.</li></ul>
<p><em><u>Nhược điểm</u></em>:</p>
<ul><li>Chỉ sạc được hơn 50% pin.</li><li>Thời gian chờ sạc đầy pin lâu hơn so với các dòng phụ kiện có dung lượng pin lớn.</li></ul>
<h3 id="h-2-củ-sạc-nhanh">2. Củ sạc nhanh</h3>
<p>Đây là phụ kiện khá phổ biến trên thị trường phụ kiện điện thoại hiện nay. Sản phẩm có thể sạc nhanh hơn 40% so với các củ sạc thông thường, cụ thể là sạc điện thoại trong vòng 0,5 – 1 giờ đồng hồ. Với tính năng sạc nhanh này, củ sạc vô cùng thích hợp đối với những ai thường xuyên bận rộn với công việc.</p>
<div class="wp-block-image"><figure class="aligncenter size-large"><img width="1024" height="1024" src="https://phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-1-1024x1024.jpg" alt="Quà Tặng Doanh Nghiệp 3 Trong 1 GS304" class="wp-image-16084" srcset="//phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-1-1024x1024.jpg 1024w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-1-300x300.jpg 300w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-1-150x150.jpg 150w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-1-768x767.jpg 768w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-1-990x989.jpg 990w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-1-441x441.jpg 441w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-1-600x599.jpg 600w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-1.jpg 1134w" sizes="(max-width: 1024px) 100vw, 1024px" /><figcaption>Củ sạc nhanh tiêu chuẩn 2A</figcaption></figure></div>
<p><strong><em>Đánh giá củ sạc nhanh 2A:</em></strong></p>
<ul><li>Tương thích với hầu hết thiết bị điện tử trên thị trường.</li><li>Cho thời gian sạc nhanh, phù hợp với đối tác, khách hàng của doanh nghiệp trong các dự án.</li><li>Dễ dàng mang theo và sử dụng mọi lúc, mọi nơi.</li></ul>
<h3 id="h-3-moc-dan-diện-thoại">3. Móc dán điện thoại</h3>
<p>Dù không phải là món quà tặng hợp với thời đại công nghệ số như hai món quà trên trong bộ Quà tặng doanh nghiệp GS304 nhưng chiếc móc dán điện thoại lại có thể được dùng để in Logo doanh nghiệp, tạo hiệu ứng và quảng bá thương hiệu đến với người khác. Với cách làm này, doanh nghiệp sẽ có thể tìm kiếm khách hàng mục tiêu, đồng thời tăng khả năng nhận diện thương hiệu mà không mất quá nhiều chi phí cho công cuộc marketing.</p>
<p>Ngoài ra, đi kèm cùng 3 món quà tặng trên là một cáp sạc đa năng với 3 cổng kết nối: Lightning, cổng USB và cổng MicroUSB, thích hợp sử dụng cho nhiều thiết bị điện tử khác nhau.</p>
<div class="wp-block-image"><figure class="aligncenter size-full"><img width="1000" height="1000" src="https://phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-14.jpg" alt="Quà Tặng Doanh Nghiệp 3 Trong 1 GS304" class="wp-image-16081" srcset="//phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-14.jpg 1000w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-14-300x300.jpg 300w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-14-150x150.jpg 150w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-14-768x768.jpg 768w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-14-990x990.jpg 990w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-14-441x441.jpg 441w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-14-600x600.jpg 600w" sizes="(max-width: 1000px) 100vw, 1000px" /><figcaption><em>Cáp sạc đa năng 3 trong 1 phù hợp để sạc với hầu hết thiết bị điện tử hiện nay</em></figcaption></figure></div>
<h2 id="h-co-nen-chọn-qua-tặng-doanh-nghiệp-3-trong-1-gs304">Có nên chọn Quà tặng doanh nghiệp 3 trong 1 GS304?</h2>
<p>Trước khi đưa ra quyết định, các doanh nghiệp có thể xem xét đến các yếu tố sau:</p>
<h3 id="h-1-về-xu-hướng">1. Về xu hướng</h3>
<p>Cả 3 món quà tặng đều có liên quan đến công nghệ, hợp với xu hướng thị trường và thời đại công nghệ 4.0, lại phù hợp với hầu hết các đối tượng và dễ dàng mang theo bên mình.</p>
<h3 id="h-2-về-mặt-tiền">2. Về “mặt tiền”</h3>
<p>3 món Quà tặng doanh nghiệp GS304 đều được đặt trong một chiếc hộp vô cùng sang trọng. Bên trong hộp được lót một tấm mica lót vải nhung tạo sự trang trọng cho hộp quà và phù hợp với tính chất của doanh nghiệp.</p>
<h3 id="h-3-về-sự-hữu-dụng">3. Về sự hữu dụng</h3>
<p>Khác với các dòng sản phẩm đơn lẻ mà mình thường review trước đó, bộ Quà tặng doanh nghiệp 3 trong 1 GS304 là sự kết hợp của 3 thiết bị công nghệ vô cùng cần thiết với người dùng, tạo nên sự đa dạng và phong phủ của món quà.</p>
<h3 id="h-4-về-chất-lượng">4. Về chất lượng</h3>
<p>Cả 3 món quà trong hộp Quà tặng doanh nghiệp GS304 đều đạt được các chứng nhận sau:</p>
<ul><li>CE: Chứng nhận về chất lượng của sản phẩm.</li><li>FCC: Chứng nhận đảm bảo về mặt chất lượng của các thiết bị điện tử mà không bị nhiễu động quá mức, được cấp bởi Ủy bang Truyền thông Liên bang Hoa Kỳ.</li><li>RoHS: Chứng nhận về hạn chế các chất cháy nổ trong các thiết bị điện tử.</li><li>CO: Chứng nhận xuất xứ, nguồn gốc hàng hóa của một quốc gia/lãnh thổ và được cấp bởi cơ quan có thẩm quyền.</li></ul>
<h3 id="h-5-về-gia-trị-kinh-tế">5. Về giá trị kinh tế</h3>
<p>Hộp Quà tặng doanh nghiệp 3 trong 1 GS304 có giá thành không quá cao so với các bộ Quà tặng doanh nghiệp khác, giúp các cá nhân/doanh nghiệp tiết kiệm chi phí mà vẫn có thể quảng bá thương hiệu đến với mọi người.</p>
<div class="wp-block-image"><figure class="aligncenter size-full"><img width="1000" height="1000" src="https://phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-4.jpg" alt="Quà Tặng Doanh Nghiệp 3 Trong 1 GS304" class="wp-image-16085" srcset="//phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-4.jpg 1000w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-4-300x300.jpg 300w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-4-150x150.jpg 150w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-4-768x768.jpg 768w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-4-990x990.jpg 990w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-4-441x441.jpg 441w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-4-600x600.jpg 600w" sizes="(max-width: 1000px) 100vw, 1000px" /><figcaption> Quà tặng doanh nghiệp 3 trong 1 GS304 chính là món quà tặng công nghệ hợp thời và cực kỳ tiện ích</figcaption></figure></div>
<h2 id="h-kết">Kết</h2>
<p>Nhìn chung, theo mình thì hộp Quà tặng doanh nghiệp 3 trong 1 GS304 là một món quà mang cả ý nghĩa về vật chất lẫn tinh thần của doanh nghiệp với đối tác, khách hàng. Bên cạnh đó, đây còn là một phương pháp marketing ít tốn kém nhất mà mang lại hiệu quả cao cho doanh nghiệp.</p>
<p>Nếu đứng trên cương vị là người tặng, mình sẽ lựa chọn ngay Hộp quà này bởi giá trị mang lại khá nhiều mà không mất nhiều chi phí. Còn nếu đứng trên cương vị khách hàng, mình sẽ rất vui khi nhận được món quà hợp thời đại và hữu ích, thậm chí còn đánh giá cao khả năng bắt kịp xu hướng và “đọc” tâm lý người khác.</p>
<p>Ngoài món Quà tặng doanh nghiệp 3 trong 1 GS304 này ra, doanh nghiệp cũng có thể lựa chọn những món quà tặng riêng lẻ như pin sạc dự phòng kiêm sạc không dây, đèn bàn tích hợp sạc thông minh và đồng hồ thông minh, đồng hồ kiêm sạc không dây,… để làm quà cho đối tác, khách hàng. Tuy nhiên, việc lựa chọn những sản phẩm mình vừa kể trên sẽ khá tốn chi phí so với tặng quà theo Gift set như thế này đấy!</p>
<div style="height:100px" aria-hidden="true" class="wp-block-spacer"></div>
<div data-block-name="woocommerce/handpicked-products" data-columns="4" data-edit-mode="false" data-content-visibility="{"title":true,"price":true,"rating":true,"button":false}" data-products="[15001,14876,15037,15079,14981,15467,15550,15061,15531,14942,15570,8502,8435,14959,14915,15446]" data-align-buttons="true" class="wc-block-grid wp-block-handpicked-products wc-block-handpicked-products has-4-columns has-multiple-rows has-aligned-buttons"><ul class="wc-block-grid__products"><li class="wc-block-grid__product">
<a href="https://phukiendienthoaigiare.com/product/qua-tang-khuyen-mai-in-logo-thuong-hieu-so-luong-it-gs306/" class="wc-block-grid__product-link">
<div class="wc-block-grid__product-image"><img width="300" height="300" src="https://phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-mien-phi-in-logo-thuong-hieu-qua-tang-hoi-nghi-1-300x300.jpg" class="attachment-woocommerce_thumbnail size-woocommerce_thumbnail" alt="quà tặng công nghệ cao cấp 3 trong 1 in logo doanh nghiệp số lượng ít tphcm quà tặng khuyến mãi" srcset="//phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-mien-phi-in-logo-thuong-hieu-qua-tang-hoi-nghi-1-300x300.jpg 300w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-mien-phi-in-logo-thuong-hieu-qua-tang-hoi-nghi-1-150x150.jpg 150w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-mien-phi-in-logo-thuong-hieu-qua-tang-hoi-nghi-1-768x768.jpg 768w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-mien-phi-in-logo-thuong-hieu-qua-tang-hoi-nghi-1-441x441.jpg 441w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-mien-phi-in-logo-thuong-hieu-qua-tang-hoi-nghi-1-600x600.jpg 600w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-mien-phi-in-logo-thuong-hieu-qua-tang-hoi-nghi-1.jpg 800w" sizes="(max-width: 360px) 147px, (max-width: 300px) 100vw, 300px" /></div>
<div class="wc-block-grid__product-title">Quà Tặng Khuyến Mãi in Logo Thương Hiệu Số Lượng Ít GS306</div>
</a>
<div class="wc-block-grid__product-price price"><span class="woocommerce-Price-amount amount">385.000 <span class="woocommerce-Price-currencySymbol">₫</span></span></div>
<div class="wc-block-grid__product-rating"><div class="star-rating" role="img" aria-label="Được xếp hạng 5.00 5 sao"><span style="width:100%"><strong class="rating">5.00</strong> trên 5 dựa trên <span class="rating">82</span> đánh giá</span></div></div>
</li><li class="wc-block-grid__product">
<a href="https://phukiendienthoaigiare.com/product/qua-tang-doanh-nghiep-3in1-gs305-in-logo-thuong-hieu/" class="wc-block-grid__product-link">
<div class="wc-block-grid__product-image"><img width="300" height="300" src="https://phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-khach-moi-hoi-nghi-in-logo-thuong-hieu-tphcm-1-300x300.jpg" class="attachment-woocommerce_thumbnail size-woocommerce_thumbnail" alt="quà tặng công nghệ cao cấp 3 trong 1 miễn phí in logo doanh nghiệp, logo led phát sáng khi sử dụng quà tặng doanh nghiệp" srcset="//phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-khach-moi-hoi-nghi-in-logo-thuong-hieu-tphcm-1-300x300.jpg 300w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-khach-moi-hoi-nghi-in-logo-thuong-hieu-tphcm-1-150x150.jpg 150w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-khach-moi-hoi-nghi-in-logo-thuong-hieu-tphcm-1-768x768.jpg 768w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-khach-moi-hoi-nghi-in-logo-thuong-hieu-tphcm-1-990x990.jpg 990w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-khach-moi-hoi-nghi-in-logo-thuong-hieu-tphcm-1-441x441.jpg 441w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-khach-moi-hoi-nghi-in-logo-thuong-hieu-tphcm-1-600x600.jpg 600w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-khach-moi-hoi-nghi-in-logo-thuong-hieu-tphcm-1.jpg 1000w" sizes="(max-width: 360px) 147px, (max-width: 300px) 100vw, 300px" /></div>
<div class="wc-block-grid__product-title">Quà Tặng Doanh Nghiệp 3in1 GS305 In Logo Thương Hiệu</div>
</a>
<div class="wc-block-grid__product-price price"><span class="woocommerce-Price-amount amount">745.000 <span class="woocommerce-Price-currencySymbol">₫</span></span></div>
<div class="wc-block-grid__product-rating"><div class="star-rating" role="img" aria-label="Được xếp hạng 5.00 5 sao"><span style="width:100%"><strong class="rating">5.00</strong> trên 5 dựa trên <span class="rating">83</span> đánh giá</span></div></div>
</li><li class="wc-block-grid__product">
<a href="https://phukiendienthoaigiare.com/product/qua-tang-doanh-nghiep-4in1-gs402-in-logo-doanh-thuong-hieu-so-luong-it/" class="wc-block-grid__product-link">
<div class="wc-block-grid__product-image"><img width="300" height="300" src="https://phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-4-trong-1-in-logo-thuong-hieu-300x300.jpg" class="attachment-woocommerce_thumbnail size-woocommerce_thumbnail" alt="quà tặng công nghệ cao cấp 4 trong 1 miễn phí in logo doanh nghiệp quà tặng doanh nghiệp quà tặng khách hàng hội nghị" srcset="//phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-4-trong-1-in-logo-thuong-hieu-300x300.jpg 300w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-4-trong-1-in-logo-thuong-hieu-150x150.jpg 150w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-4-trong-1-in-logo-thuong-hieu-768x768.jpg 768w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-4-trong-1-in-logo-thuong-hieu-990x990.jpg 990w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-4-trong-1-in-logo-thuong-hieu-441x441.jpg 441w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-4-trong-1-in-logo-thuong-hieu-600x600.jpg 600w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-4-trong-1-in-logo-thuong-hieu.jpg 1000w" sizes="(max-width: 360px) 147px, (max-width: 300px) 100vw, 300px" /></div>
<div class="wc-block-grid__product-title">Quà Tặng Doanh Nghiệp 4in1 GS402 – In Logo Doanh Thương Hiệu Số Lượng Ít</div>
</a>
<div class="wc-block-grid__product-price price"><span class="woocommerce-Price-amount amount">1.365.000 <span class="woocommerce-Price-currencySymbol">₫</span></span></div>
<div class="wc-block-grid__product-rating"><div class="star-rating" role="img" aria-label="Được xếp hạng 5.00 5 sao"><span style="width:100%"><strong class="rating">5.00</strong> trên 5 dựa trên <span class="rating">81</span> đánh giá</span></div></div>
</li><li class="wc-block-grid__product">
<a href="https://phukiendienthoaigiare.com/product/qua-tang-doanh-nghiep-3-trong-1-gs304-in-logo-doanh-nghiep-so-luong-it/" class="wc-block-grid__product-link">
<div class="wc-block-grid__product-image"><img width="300" height="300" src="https://phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-in-logo-thuong-hieu-300x300.jpg" class="attachment-woocommerce_thumbnail size-woocommerce_thumbnail" alt="Quà Tặng Doanh Nghiệp 3 Trong 1 GS304 - In Logo Doanh Nghiệp Số Lượng Ít" srcset="//phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-in-logo-thuong-hieu-300x300.jpg 300w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-in-logo-thuong-hieu-150x150.jpg 150w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-in-logo-thuong-hieu-768x768.jpg 768w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-in-logo-thuong-hieu-990x990.jpg 990w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-in-logo-thuong-hieu-441x441.jpg 441w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-in-logo-thuong-hieu-600x600.jpg 600w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-in-logo-thuong-hieu.jpg 1000w" sizes="(max-width: 360px) 147px, (max-width: 300px) 100vw, 300px" /></div>
<div class="wc-block-grid__product-title">Quà Tặng Doanh Nghiệp 3 Trong 1 GS304 – In Logo Doanh Nghiệp Số Lượng Ít</div>
</a>
<div class="wc-block-grid__product-price price"><span class="woocommerce-Price-amount amount">385.000 <span class="woocommerce-Price-currencySymbol">₫</span></span></div>
<div class="wc-block-grid__product-rating"><div class="star-rating" role="img" aria-label="Được xếp hạng 5.00 5 sao"><span style="width:100%"><strong class="rating">5.00</strong> trên 5 dựa trên <span class="rating">85</span> đánh giá</span></div></div>
</li><li class="wc-block-grid__product">
<a href="https://phukiendienthoaigiare.com/product/combo-qua-tang-phu-kien-cao-cap-cho-iphone-13-series/" class="wc-block-grid__product-link">
<div class="wc-block-grid__product-image"><img width="300" height="300" src="https://phukiendienthoaigiare.com/wp-content/uploads/2021/12/combo-qua-tang-phu-kien-cao-cap-cho-iphone-13-in-logo-doanh-nghiep-300x300.jpg" class="attachment-woocommerce_thumbnail size-woocommerce_thumbnail" alt="combo quà tặng phụ kiện cao cấp iphone 13 series 5 trong 1" srcset="//phukiendienthoaigiare.com/wp-content/uploads/2021/12/combo-qua-tang-phu-kien-cao-cap-cho-iphone-13-in-logo-doanh-nghiep-300x300.jpg 300w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/combo-qua-tang-phu-kien-cao-cap-cho-iphone-13-in-logo-doanh-nghiep-150x150.jpg 150w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/combo-qua-tang-phu-kien-cao-cap-cho-iphone-13-in-logo-doanh-nghiep-768x768.jpg 768w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/combo-qua-tang-phu-kien-cao-cap-cho-iphone-13-in-logo-doanh-nghiep-441x441.jpg 441w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/combo-qua-tang-phu-kien-cao-cap-cho-iphone-13-in-logo-doanh-nghiep-600x600.jpg 600w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/combo-qua-tang-phu-kien-cao-cap-cho-iphone-13-in-logo-doanh-nghiep.jpg 790w" sizes="(max-width: 360px) 147px, (max-width: 300px) 100vw, 300px" /></div>
<div class="wc-block-grid__product-title">Combo Quà Tặng Phụ Kiện Cao Cấp Cho Iphone 13 Series</div>
</a>
<div class="wc-block-grid__product-price price"><span class="woocommerce-Price-amount amount">1.365.000 <span class="woocommerce-Price-currencySymbol">₫</span></span></div>
<div class="wc-block-grid__product-rating"><div class="star-rating" role="img" aria-label="Được xếp hạng 5.00 5 sao"><span style="width:100%"><strong class="rating">5.00</strong> trên 5 dựa trên <span class="rating">84</span> đánh giá</span></div></div>
</li><li class="wc-block-grid__product">
<a href="https://phukiendienthoaigiare.com/product/qua-tang-cong-nghe-5-trong-1-cao-cap-gs504/" class="wc-block-grid__product-link">
<div class="wc-block-grid__product-image"><img width="300" height="300" src="https://phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-in-logo-doanh-nghiep-cao-cap-qua-tang-doi-tac-tphcm-300x300.png" class="attachment-woocommerce_thumbnail size-woocommerce_thumbnail" alt="Bộ quà tặng Doanh Nghiệp 5 trong 1 Pin Sạc dự phòng 10000mAh, sạc nhanh PD+QC3.0 18W Củ sạc nhanh QC3.0 PD 18W Cáp sạc nhanh PD 18W" srcset="//phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-in-logo-doanh-nghiep-cao-cap-qua-tang-doi-tac-tphcm-300x300.png 300w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-in-logo-doanh-nghiep-cao-cap-qua-tang-doi-tac-tphcm-150x150.png 150w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-in-logo-doanh-nghiep-cao-cap-qua-tang-doi-tac-tphcm-768x768.png 768w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-in-logo-doanh-nghiep-cao-cap-qua-tang-doi-tac-tphcm-441x441.png 441w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-in-logo-doanh-nghiep-cao-cap-qua-tang-doi-tac-tphcm-600x600.png 600w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-in-logo-doanh-nghiep-cao-cap-qua-tang-doi-tac-tphcm.png 800w" sizes="(max-width: 360px) 147px, (max-width: 300px) 100vw, 300px" /></div>
<div class="wc-block-grid__product-title">Quà Tặng Công Nghệ 5 Trong 1 Cao Cấp GS504</div>
</a>
<div class="wc-block-grid__product-price price"><span class="woocommerce-Price-amount amount">1.350.000 <span class="woocommerce-Price-currencySymbol">₫</span></span></div>
<div class="wc-block-grid__product-rating"><div class="star-rating" role="img" aria-label="Được xếp hạng 5.00 5 sao"><span style="width:100%"><strong class="rating">5.00</strong> trên 5 dựa trên <span class="rating">90</span> đánh giá</span></div></div>
</li><li class="wc-block-grid__product">
<a href="https://phukiendienthoaigiare.com/product/qua-tang-doanh-nghiep-4-in-1-hop-qua-tet-2022-gs401/" class="wc-block-grid__product-link">
<div class="wc-block-grid__product-image"><img width="300" height="300" src="https://phukiendienthoaigiare.com/wp-content/uploads/2021/12/set-qua-tet-2022-qua-tang-doanh-nghiep-tai-nghe-bluetooth-pin-sac-du-phong-10000mah-300x300.jpg" class="attachment-woocommerce_thumbnail size-woocommerce_thumbnail" alt="Bộ quà tặng Doanh Nghiệp 4 trong 1 Pin Sạc dự phòng , Củ sạc nhanh QC3.0 PD 18W Cáp sạc nhanh PD 18W tai nghe bluetooth" srcset="//phukiendienthoaigiare.com/wp-content/uploads/2021/12/set-qua-tet-2022-qua-tang-doanh-nghiep-tai-nghe-bluetooth-pin-sac-du-phong-10000mah-300x300.jpg 300w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/set-qua-tet-2022-qua-tang-doanh-nghiep-tai-nghe-bluetooth-pin-sac-du-phong-10000mah-150x150.jpg 150w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/set-qua-tet-2022-qua-tang-doanh-nghiep-tai-nghe-bluetooth-pin-sac-du-phong-10000mah-441x442.jpg 441w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/set-qua-tet-2022-qua-tang-doanh-nghiep-tai-nghe-bluetooth-pin-sac-du-phong-10000mah.jpg 459w" sizes="(max-width: 360px) 147px, (max-width: 300px) 100vw, 300px" /></div>
<div class="wc-block-grid__product-title">Quà Tặng Doanh Nghiệp 4 in 1 Hộp Quà Tết 2022 GS401</div>
</a>
<div class="wc-block-grid__product-price price"><span class="woocommerce-Price-amount amount">650.000 <span class="woocommerce-Price-currencySymbol">₫</span></span></div>
<div class="wc-block-grid__product-rating"><div class="star-rating" role="img" aria-label="Được xếp hạng 5.00 5 sao"><span style="width:100%"><strong class="rating">5.00</strong> trên 5 dựa trên <span class="rating">89</span> đánh giá</span></div></div>
</li><li class="wc-block-grid__product">
<a href="https://phukiendienthoaigiare.com/product/qua-tang-cong-nghe-5in1-hop-qua-tet-2022-gs503/" class="wc-block-grid__product-link">
<div class="wc-block-grid__product-image"><img width="300" height="300" src="https://phukiendienthoaigiare.com/wp-content/uploads/2021/12/hop-qua-tet-2022-qua-tang-cong-nghe-cao-cap-300x300.jpg" class="attachment-woocommerce_thumbnail size-woocommerce_thumbnail" alt="hộp quà tết 2022 quà tặng công nghệ cao cấp in logo thương hiệu" srcset="//phukiendienthoaigiare.com/wp-content/uploads/2021/12/hop-qua-tet-2022-qua-tang-cong-nghe-cao-cap-300x300.jpg 300w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/hop-qua-tet-2022-qua-tang-cong-nghe-cao-cap-150x150.jpg 150w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/hop-qua-tet-2022-qua-tang-cong-nghe-cao-cap.jpg 439w" sizes="(max-width: 360px) 147px, (max-width: 300px) 100vw, 300px" /></div>
<div class="wc-block-grid__product-title">Quà Tặng Công Nghệ 5 in 1 Hộp Quà Tết 2022 GS503</div>
</a>
<div class="wc-block-grid__product-price price"><span class="woocommerce-Price-amount amount">950.000 <span class="woocommerce-Price-currencySymbol">₫</span></span></div>
<div class="wc-block-grid__product-rating"><div class="star-rating" role="img" aria-label="Được xếp hạng 5.00 5 sao"><span style="width:100%"><strong class="rating">5.00</strong> trên 5 dựa trên <span class="rating">91</span> đánh giá</span></div></div>
</li><li class="wc-block-grid__product">
<a href="https://phukiendienthoaigiare.com/product/hop-qua-tang-cong-nghe-6-trong-1-gs601/" class="wc-block-grid__product-link">
<div class="wc-block-grid__product-image"><img width="300" height="300" src="https://phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-doi-tac-hop-qua-tang-cong-nghe-cao-cap-6-trong-1-tai-nghe-bluetooth-sac-khong-day-pin-sac-du-phong-cap-sac-nhanh-gia-do-dien-thoai-tai-nghe-buletooth-in-logo-doanh-nghiep-300x300.jpg" class="attachment-woocommerce_thumbnail size-woocommerce_thumbnail" alt="Bộ quà tặng Doanh Nghiệp 6 trong 1 Pin Sạc dự phòng 10000mAh, sạc nhanh PD+QC3.0 18W Củ sạc nhanh QC3.0 PD 18W Cáp sạc nhanh PD 18W" srcset="//phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-doi-tac-hop-qua-tang-cong-nghe-cao-cap-6-trong-1-tai-nghe-bluetooth-sac-khong-day-pin-sac-du-phong-cap-sac-nhanh-gia-do-dien-thoai-tai-nghe-buletooth-in-logo-doanh-nghiep-300x300.jpg 300w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-doi-tac-hop-qua-tang-cong-nghe-cao-cap-6-trong-1-tai-nghe-bluetooth-sac-khong-day-pin-sac-du-phong-cap-sac-nhanh-gia-do-dien-thoai-tai-nghe-buletooth-in-logo-doanh-nghiep-150x150.jpg 150w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-doi-tac-hop-qua-tang-cong-nghe-cao-cap-6-trong-1-tai-nghe-bluetooth-sac-khong-day-pin-sac-du-phong-cap-sac-nhanh-gia-do-dien-thoai-tai-nghe-buletooth-in-logo-doanh-nghiep-768x768.jpg 768w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-doi-tac-hop-qua-tang-cong-nghe-cao-cap-6-trong-1-tai-nghe-bluetooth-sac-khong-day-pin-sac-du-phong-cap-sac-nhanh-gia-do-dien-thoai-tai-nghe-buletooth-in-logo-doanh-nghiep-441x441.jpg 441w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-doi-tac-hop-qua-tang-cong-nghe-cao-cap-6-trong-1-tai-nghe-bluetooth-sac-khong-day-pin-sac-du-phong-cap-sac-nhanh-gia-do-dien-thoai-tai-nghe-buletooth-in-logo-doanh-nghiep-600x600.jpg 600w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-doi-tac-hop-qua-tang-cong-nghe-cao-cap-6-trong-1-tai-nghe-bluetooth-sac-khong-day-pin-sac-du-phong-cap-sac-nhanh-gia-do-dien-thoai-tai-nghe-buletooth-in-logo-doanh-nghiep.jpg 800w" sizes="(max-width: 360px) 147px, (max-width: 300px) 100vw, 300px" /></div>
<div class="wc-block-grid__product-title">Hộp Quà Tặng Công Nghệ 6 Trong 1 GS601</div>
</a>
<div class="wc-block-grid__product-price price"><span class="woocommerce-Price-amount amount">1.350.000 <span class="woocommerce-Price-currencySymbol">₫</span></span></div>
<div class="wc-block-grid__product-rating"><div class="star-rating" role="img" aria-label="Được xếp hạng 5.00 5 sao"><span style="width:100%"><strong class="rating">5.00</strong> trên 5 dựa trên <span class="rating">92</span> đánh giá</span></div></div>
</li><li class="wc-block-grid__product">
<a href="https://phukiendienthoaigiare.com/product/qua-tang-cong-nghe-cao-cap-gift-box-5in1-gs502/" class="wc-block-grid__product-link">
<div class="wc-block-grid__product-image"><img width="300" height="300" src="https://phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-5-trong-1-mien-phi-in-logo-thuong-hieu-logo-led-phat-sang-khi-su-dung-300x300.jpg" class="attachment-woocommerce_thumbnail size-woocommerce_thumbnail" alt="quà tặng công nghệ cao cấp 5 trong 1 miễn phí in logo doanh nghiệp quà tặng đối tác quà tặng khách hàng hội nghị tai nghe không dây sạc không dây cáp sạc 3 trong 1 củ sạc nhanh qc3.0 pin sạc dự phòng 10000mah" srcset="//phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-5-trong-1-mien-phi-in-logo-thuong-hieu-logo-led-phat-sang-khi-su-dung-300x300.jpg 300w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-5-trong-1-mien-phi-in-logo-thuong-hieu-logo-led-phat-sang-khi-su-dung-150x150.jpg 150w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-5-trong-1-mien-phi-in-logo-thuong-hieu-logo-led-phat-sang-khi-su-dung-768x768.jpg 768w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-5-trong-1-mien-phi-in-logo-thuong-hieu-logo-led-phat-sang-khi-su-dung-441x441.jpg 441w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-5-trong-1-mien-phi-in-logo-thuong-hieu-logo-led-phat-sang-khi-su-dung-600x600.jpg 600w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-5-trong-1-mien-phi-in-logo-thuong-hieu-logo-led-phat-sang-khi-su-dung.jpg 800w" sizes="(max-width: 360px) 147px, (max-width: 300px) 100vw, 300px" /></div>
<div class="wc-block-grid__product-title">Quà Tặng Công Nghệ Cao Cấp Gift Box 5in1 GS502</div>
</a>
<div class="wc-block-grid__product-price price"><span class="woocommerce-Price-amount amount">1.950.000 <span class="woocommerce-Price-currencySymbol">₫</span></span></div>
<div class="wc-block-grid__product-rating"><div class="star-rating" role="img" aria-label="Được xếp hạng 5.00 5 sao"><span style="width:100%"><strong class="rating">5.00</strong> trên 5 dựa trên <span class="rating">93</span> đánh giá</span></div></div>
</li><li class="wc-block-grid__product">
<a href="https://phukiendienthoaigiare.com/product/set-qua-tang-5in1-phu-kien-cong-nghe-cho-xe-o-to-gs501/" class="wc-block-grid__product-link">
<div class="wc-block-grid__product-image"><img width="300" height="300" src="https://phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-5-trong-1-mien-phi-in-logo-thuong-hieu-set-qua-tang-phu-kien-xa-hoi-300x300.jpg" class="attachment-woocommerce_thumbnail size-woocommerce_thumbnail" alt="quà tặng công nghệ cao cấp 5 trong 1 miễn phí in logo doanh nghiệp quà tặng đối tác quà tặng khách hàng hội nghị" srcset="//phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-5-trong-1-mien-phi-in-logo-thuong-hieu-set-qua-tang-phu-kien-xa-hoi-300x300.jpg 300w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-5-trong-1-mien-phi-in-logo-thuong-hieu-set-qua-tang-phu-kien-xa-hoi-150x150.jpg 150w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-5-trong-1-mien-phi-in-logo-thuong-hieu-set-qua-tang-phu-kien-xa-hoi-768x768.jpg 768w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-5-trong-1-mien-phi-in-logo-thuong-hieu-set-qua-tang-phu-kien-xa-hoi-441x441.jpg 441w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-5-trong-1-mien-phi-in-logo-thuong-hieu-set-qua-tang-phu-kien-xa-hoi-600x600.jpg 600w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-5-trong-1-mien-phi-in-logo-thuong-hieu-set-qua-tang-phu-kien-xa-hoi.jpg 800w" sizes="(max-width: 360px) 147px, (max-width: 300px) 100vw, 300px" /></div>
<div class="wc-block-grid__product-title">Set Quà Tặng 5in1 Phụ Kiện Công Nghệ Cho Xe Ô Tô GS501</div>
</a>
<div class="wc-block-grid__product-price price"><span class="woocommerce-Price-amount amount">1.350.000 <span class="woocommerce-Price-currencySymbol">₫</span></span></div>
<div class="wc-block-grid__product-rating"><div class="star-rating" role="img" aria-label="Được xếp hạng 5.00 5 sao"><span style="width:100%"><strong class="rating">5.00</strong> trên 5 dựa trên <span class="rating">92</span> đánh giá</span></div></div>
</li><li class="wc-block-grid__product">
<a href="https://phukiendienthoaigiare.com/product/qua-tang-doanh-nghiep-cao-cap-hop-qua-tang-3in1-gs303/" class="wc-block-grid__product-link">
<div class="wc-block-grid__product-image"><img width="300" height="300" src="https://phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-in-logo-thuong-hieu-logo-led-phat-sang-khi-su-dung-1-300x300.jpg" class="attachment-woocommerce_thumbnail size-woocommerce_thumbnail" alt="quà tặng công nghệ cao cấp 3 trong 1 miễn phí in logo doanh nghiệp, logo led phát sáng khi sử dụng quà tặng đối tác quà tặng khách hàng hội nghị" srcset="//phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-in-logo-thuong-hieu-logo-led-phat-sang-khi-su-dung-1-300x300.jpg 300w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-in-logo-thuong-hieu-logo-led-phat-sang-khi-su-dung-1-150x150.jpg 150w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-in-logo-thuong-hieu-logo-led-phat-sang-khi-su-dung-1-441x442.jpg 441w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-in-logo-thuong-hieu-logo-led-phat-sang-khi-su-dung-1-600x601.jpg 600w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-in-logo-thuong-hieu-logo-led-phat-sang-khi-su-dung-1.jpg 634w" sizes="(max-width: 360px) 147px, (max-width: 300px) 100vw, 300px" /></div>
<div class="wc-block-grid__product-title">Quà Tặng Doanh Nghiệp Cao Cấp Hộp Quà Tặng 3in1 GS303</div>
</a>
<div class="wc-block-grid__product-price price"><span class="woocommerce-Price-amount amount">850.000 <span class="woocommerce-Price-currencySymbol">₫</span></span></div>
<div class="wc-block-grid__product-rating"><div class="star-rating" role="img" aria-label="Được xếp hạng 5.00 5 sao"><span style="width:100%"><strong class="rating">5.00</strong> trên 5 dựa trên <span class="rating">92</span> đánh giá</span></div></div>
</li><li class="wc-block-grid__product">
<a href="https://phukiendienthoaigiare.com/product/set-qua-tang-cong-nghe-cao-cap-3-in-1-gs302/" class="wc-block-grid__product-link">
<div class="wc-block-grid__product-image"><img width="300" height="300" src="https://phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-in-logo-thuong-hieu-logo-led-phat-sang-khi-su-dung-300x300.jpg" class="attachment-woocommerce_thumbnail size-woocommerce_thumbnail" alt="quà tặng công nghệ cao cấp 3 trong 1 miễn phí in logo doanh nghiệp, logo led phát sáng khi sử dụng quà tặng đối tác quà tặng khách hàng hội nghị" srcset="//phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-in-logo-thuong-hieu-logo-led-phat-sang-khi-su-dung-300x300.jpg 300w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-in-logo-thuong-hieu-logo-led-phat-sang-khi-su-dung-150x150.jpg 150w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-in-logo-thuong-hieu-logo-led-phat-sang-khi-su-dung-441x441.jpg 441w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-in-logo-thuong-hieu-logo-led-phat-sang-khi-su-dung-600x600.jpg 600w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-in-logo-thuong-hieu-logo-led-phat-sang-khi-su-dung.jpg 640w" sizes="(max-width: 360px) 147px, (max-width: 300px) 100vw, 300px" /></div>
<div class="wc-block-grid__product-title">Set Quà Tặng Công Nghệ Cao Cấp 3in1 GS302</div>
</a>
<div class="wc-block-grid__product-price price"><span class="woocommerce-Price-amount amount">1.350.000 <span class="woocommerce-Price-currencySymbol">₫</span></span></div>
<div class="wc-block-grid__product-rating"><div class="star-rating" role="img" aria-label="Được xếp hạng 5.00 5 sao"><span style="width:100%"><strong class="rating">5.00</strong> trên 5 dựa trên <span class="rating">92</span> đánh giá</span></div></div>
</li><li class="wc-block-grid__product">
<a href="https://phukiendienthoaigiare.com/product/hop-qua-tang-cong-nghe-cao-cap-3-trong-1-gs301/" class="wc-block-grid__product-link">
<div class="wc-block-grid__product-image"><img width="300" height="300" src="https://phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-in-logo-thuong-hieu-logo-led-phat-sang-khi-su-dung-300x300.png" class="attachment-woocommerce_thumbnail size-woocommerce_thumbnail" alt="quà tặng công nghệ cao cấp 3 trong 1 miễn phí in logo doanh nghiệp, logo led phát sáng khi sử dụng quà tặng đối tác quà tặng khách hàng hội nghị" srcset="//phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-in-logo-thuong-hieu-logo-led-phat-sang-khi-su-dung-300x300.png 300w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-in-logo-thuong-hieu-logo-led-phat-sang-khi-su-dung-150x150.png 150w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-in-logo-thuong-hieu-logo-led-phat-sang-khi-su-dung-441x442.png 441w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-in-logo-thuong-hieu-logo-led-phat-sang-khi-su-dung-600x601.png 600w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-in-logo-thuong-hieu-logo-led-phat-sang-khi-su-dung.png 724w" sizes="(max-width: 360px) 147px, (max-width: 300px) 100vw, 300px" /></div>
<div class="wc-block-grid__product-title">Hộp Quà Tăng Công Nghệ Cao Cấp 3 Trong 1 GS301</div>
</a>
<div class="wc-block-grid__product-price price"><span class="woocommerce-Price-amount amount">1.250.000 <span class="woocommerce-Price-currencySymbol">₫</span></span></div>
<div class="wc-block-grid__product-rating"><div class="star-rating" role="img" aria-label="Được xếp hạng 5.00 5 sao"><span style="width:100%"><strong class="rating">5.00</strong> trên 5 dựa trên <span class="rating">92</span> đánh giá</span></div></div>
</li><li class="wc-block-grid__product">
<a href="https://phukiendienthoaigiare.com/product/sac-khong-day-magsafe-battery-pack-bb01t/" class="wc-block-grid__product-link">
<div class="wc-block-grid__product-image"><img width="300" height="300" src="https://phukiendienthoaigiare.com/wp-content/uploads/2021/11/BB-19-300x300.jpg" class="attachment-woocommerce_thumbnail size-woocommerce_thumbnail" alt="Sạc Không Dây Magsafe Battery Pack BB01T" srcset="//phukiendienthoaigiare.com/wp-content/uploads/2021/11/BB-19-300x300.jpg 300w, //phukiendienthoaigiare.com/wp-content/uploads/2021/11/BB-19-150x150.jpg 150w, //phukiendienthoaigiare.com/wp-content/uploads/2021/11/BB-19-600x600.jpg 600w, //phukiendienthoaigiare.com/wp-content/uploads/2021/11/BB-19-441x441.jpg 441w, //phukiendienthoaigiare.com/wp-content/uploads/2021/11/BB-19.jpg 736w" sizes="(max-width: 360px) 147px, (max-width: 300px) 100vw, 300px" /></div>
<div class="wc-block-grid__product-title">Sạc Không Dây Magsafe Battery Pack BB01T</div>
</a>
<div class="wc-block-grid__product-price price"><span class="woocommerce-Price-amount amount">750.000 <span class="woocommerce-Price-currencySymbol">₫</span></span></div>
<div class="wc-block-grid__product-rating"><div class="star-rating" role="img" aria-label="Được xếp hạng 5.00 5 sao"><span style="width:100%"><strong class="rating">5.00</strong> trên 5 dựa trên <span class="rating">90</span> đánh giá</span></div></div>
</li><li class="wc-block-grid__product">
<a href="https://phukiendienthoaigiare.com/product/sac-khong-day-magsafe-charger-wctx2-15w-chuan-qi-cho-iphone-12-13/" class="wc-block-grid__product-link">
<div class="wc-block-grid__product-image"><img width="300" height="300" src="https://phukiendienthoaigiare.com/wp-content/uploads/2021/11/X2-11-300x300.jpg" class="attachment-woocommerce_thumbnail size-woocommerce_thumbnail" alt="Sạc Không Dây Magsafe Charger WCTX2 15W Chuẩn Qi Cho iPhone 12, 13" srcset="//phukiendienthoaigiare.com/wp-content/uploads/2021/11/X2-11-300x300.jpg 300w, //phukiendienthoaigiare.com/wp-content/uploads/2021/11/X2-11-150x150.jpg 150w, //phukiendienthoaigiare.com/wp-content/uploads/2021/11/X2-11-600x600.jpg 600w, //phukiendienthoaigiare.com/wp-content/uploads/2021/11/X2-11-1024x1024.jpg 1024w, //phukiendienthoaigiare.com/wp-content/uploads/2021/11/X2-11-768x768.jpg 768w, //phukiendienthoaigiare.com/wp-content/uploads/2021/11/X2-11-990x990.jpg 990w, //phukiendienthoaigiare.com/wp-content/uploads/2021/11/X2-11-441x441.jpg 441w, //phukiendienthoaigiare.com/wp-content/uploads/2021/11/X2-11.jpg 1200w" sizes="(max-width: 360px) 147px, (max-width: 300px) 100vw, 300px" /></div>
<div class="wc-block-grid__product-title">Sạc Không Dây Magsafe Charger WCTX2 15W Chuẩn Qi Cho iPhone 12, 13</div>
</a>
<div class="wc-block-grid__product-price price"><span class="woocommerce-Price-amount amount">450.000 <span class="woocommerce-Price-currencySymbol">₫</span></span></div>
<div class="wc-block-grid__product-rating"><div class="star-rating" role="img" aria-label="Được xếp hạng 5.00 5 sao"><span style="width:100%"><strong class="rating">5.00</strong> trên 5 dựa trên <span class="rating">97</span> đánh giá</span></div></div>
</li></ul></div>
<div style="height:100px" aria-hidden="true" class="wp-block-spacer"></div>
<section class="sc_fs_event sc_card">
<h2>Tìm đại lý phân phối – Quà Tặng Doanh Nghiệp 3 Trong 1 GS304 – In Logo Doanh Nghiệp Số Lượng Ít</h2> <figure>
<a href="https://phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-11.jpg" title="">
<img src="https://phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-11-150x150.jpg" alt=""/>
</a>
<meta content="https://phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-11.jpg">
<meta content="1000">
<meta content="1000">
</figure>
<p>
Bộ quà tặng Doanh Nghiệp 3 trong 1 GS304<br>Pin Sạc dự phòng 3000mAh<br>Củ sạc nhanh 2A<br>Móc dán điện thoại in logo Doanh Nghiệp<br>Nhập Khẩu Bảo hành chính hãng<br>Chứng nhận an toàn : CE/FCC/RoHS<br>Chứng nhận xuất xứ hàng hóa: CO<br>Phù hợp làm quà tặng Doanh Nghiệp, Quà tặng nhân viên, Quà khuyến mãi…<br>Customized Branding Logo (MOQ=10pcs)<br> </p>
<div class="sc_row w-100">
<div class="sc_grey-box">
<div class="sc_box-label">
Event Meta </div>
<div class="sc_company">
<div class="sc_company-infos">
<div class="sc_input-group">
<div class="sc_input-label">
Name </div>
<div class="wp-block-structured-content-event__location">
Tìm đại lý phân phối – Quà Tặng Doanh Nghiệp 3 Trong 1 GS304 – In Logo Doanh Nghiệp Số Lượng Ít </div>
</div>
<div class="sc_input-group">
<div class="sc_input-label">
Event Status </div>
<div class="wp-block-structured-content-event__status">
Scheduled </div>
</div>
<div class="sc_input-group">
<div class="sc_input-label">
Start Date </div>
<div class="wp-block-structured-content-event__start_date">
01/12/2021 11:05 Chiều </div>
</div>
<div class="sc_input-group">
<div class="sc_input-label">
End Date </div>
<div class="wp-block-structured-content-event__end_date">
01/12/2050 11:05 Chiều </div>
</div>
</div>
</div>
</div>
<div class="sc_grey-box">
<div class="sc_box-label">
Event Location </div>
<div class="sc_input-group">
<div class="sc_input-label">
Attendance Mode </div>
<div class="wp-block-structured-content-event__event_attendance_mode">
Online </div>
</div>
<div class="sc_input-group">
<div class="sc_input-label">
URL </div>
<div class="wp-block-structured-content-event__online_url">
<a target="_blank" href="https://phukiendienthoaigiare.com/product/qua-tang-doanh-nghiep-3-trong-1-gs304-in-logo-doanh-nghiep-so-luong-it/">https://phukiendienthoaigiare.com/product/qua-tang-doanh-nghiep-3-trong-1-gs304-in-logo-doanh-nghiep-so-luong-it/</a>
</div>
</div>
</div>
</div>
<div class="sc_row w-100">
<div class="sc_grey-box">
<div class="sc_box-label">
Performer </div>
<div class="sc_input-group">
<div class="sc_input-label">
Type </div>
<div class="wp-block-structured-content-event__offer_availability">
Performing Group </div>
</div>
<div class="sc_input-group">
<div class="sc_input-label">
Name </div>
<div class="wp-block-structured-content-event__offer_url">
Phụ kiện điện thoại giá rẻ – PMCS TECH </div>
</div>
</div>
<div class="sc_grey-box">
<div class="sc_box-label">
Offer </div>
<div class="sc_row">
<div class="sc_input-group">
<div class="sc_input-label">
Availability </div>
<div class="wp-block-structured-content-event__offer_availability">
In Stock </div>
</div>
<div class="sc_input-group">
<div class="sc_input-label">
Ticket Website </div>
<div class="wp-block-structured-content-event__offer_url">
<a href="https://phukiendienthoaigiare.com/product/qua-tang-doanh-nghiep-3-trong-1-gs304-in-logo-doanh-nghiep-so-luong-it/">https://phukiendienthoaigiare.com/product/qua-tang-doanh-nghiep-3-trong-1-gs304-in-logo-doanh-nghiep-so-luong-it/</a>
</div>
</div>
</div>
<div class="sc_row">
<div class="sc_input-group">
<div class="sc_input-label">
Currency ISO Code </div>
<div class="wp-block-structured-content-event__currency">
VND </div>
</div>
<div class="sc_input-group">
<div class="sc_input-label">
Price </div>
<div class="wp-block-structured-content-event__price">
385.000,00 </div>
</div>
</div>
<div class="sc_input-group">
<div class="sc_input-label">
Valid From </div>
<div class="wp-block-structured-content-event__valid_from">
01/12/2021 11:04 Chiều </div>
</div>
</div>
</div>
</section>
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Event",
"organizer": { "@type": "Organization", "name": "PHỤ KIỆN ĐIỆN THOẠI GIÁ RẺ", "url": "https://phukiendienthoaigiare.com" },
"eventStatus": "https://schema.org/EventScheduled",
"eventAttendanceMode": "https://schema.org/OnlineEventAttendanceMode",
"name": "Tìm đại lý phân phối - Quà Tặng Doanh Nghiệp 3 Trong 1 GS304 – In Logo Doanh Nghiệp Số Lượng Ít",
"startDate": "2021-12-01T23:05:00+07:00",
"endDate": "2050-12-01T23:05:00+07:00",
"location":
{
"@type": "VirtualLocation",
"url": "https://phukiendienthoaigiare.com/product/qua-tang-doanh-nghiep-3-trong-1-gs304-in-logo-doanh-nghiep-so-luong-it/"
}
,
"image" : ["https://phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-11.jpg"],
"offers": {
"@type": "Offer",
"url": "https://phukiendienthoaigiare.com/product/qua-tang-doanh-nghiep-3-trong-1-gs304-in-logo-doanh-nghiep-so-luong-it/",
"price": "385000.00",
"priceCurrency": "VND",
"availability": "https://schema.org/InStock",
"validFrom": "2021-12-01T23:04:00+07:00"
},
"performer": {
"@type": "PerformingGroup",
"name": "Phụ kiện điện thoại giá rẻ - PMCS TECH"
},
"description": "Bộ quà tặng Doanh Nghiệp 3 trong 1 GS304<br>Pin Sạc dự phòng 3000mAh<br>Củ sạc nhanh 2A<br>Móc dán điện thoại in logo Doanh Nghiệp<br>Nhập Khẩu Bảo hành chính hãng<br>Chứng nhận an toàn : CE/FCC/RoHS<br>Chứng nhận xuất xứ hàng hóa: CO<br>Phù hợp làm quà tặng Doanh Nghiệp, Quà tặng nhân viên, Quà khuyến mãi…<br>Customized Branding Logo (MOQ=10pcs)<br>"
}
</script>
<div style="height:100px" aria-hidden="true" class="wp-block-spacer"></div>
<h2 id="h-xem-them-1">Xem thêm:</h2>
<ul class="wp-block-yoast-seo-related-links"><li><a href="https://phukiendienthoaigiare.com/loa-bluetooth-qua-tang-doanh-nghiep-sp001/">Loa Bluetooth Quà Tặng Doanh Nghiệp SP001</a></li><li><a href="https://phukiendienthoaigiare.com/product/loa-bluetooth-qua-tang-doanh-nghiep-sp001-logo-led-phat-sang/">Loa Bluetooth Quà Tặng Doanh Nghiệp SP001 Logo LED Phát Sáng</a></li><li><a href="https://phukiendienthoaigiare.com/product/qua-tang-doanh-nghiep-loa-bluetooth-mini-sp004-logo-led-phat-sang/">Quà Tặng Doanh Nghiệp Loa Bluetooth Mini SP004 – Logo LED Phát Sáng</a></li><li><a href="https://phukiendienthoaigiare.com/product/qua-tang-doanh-nghiep-cao-cap-hop-qua-tang-3in1-gs303/">Quà Tặng Doanh Nghiệp Cao Cấp Hộp Quà Tặng 3in1 GS303</a></li><li><a href="https://phukiendienthoaigiare.com/product/top-sale-pin-sac-du-phong-5000mah-pb0503-logo-cty-phat-sang/">Sạc Dự Phòng 5000mAh PB0503 – Logo Phát Sáng Khi Sử Dụng</a></li></ul>
<div style="height:100px" aria-hidden="true" class="wp-block-spacer"></div>
<h2 id="h-bai-viết-mới-1">Bài viết mới</h2>
<ul class="is-grid columns-2 wp-block-rss"><li class='wp-block-rss__item'><div class='wp-block-rss__item-title'><a href='https://phukiendienthoaigiare.com/pin-sac-du-phong-10000mah-pb1002-co-tot-khong/'>Pin Sạc Dự Phòng 10000mAh PB1002 Có Tốt Không?</a></div><div class="wp-block-rss__item-excerpt">Pin sạc dự phòng PB1002 với dung lượng 10000mAh cho thời gian sạc vô cùng nhanh chóng với QC4.0 PD20W. Với củ sạc này, phụ kiện có thể cung cấp thêm 5 – 6 giờ sử dụng khi chỉ cần sạc được 5 phút và 50% thời gian dùng nếu […]</div></li><li class='wp-block-rss__item'><div class='wp-block-rss__item-title'><a href='https://phukiendienthoaigiare.com/review-dong-ho-bao-thuc-kiem-sac-khong-day-15w-wct001-tinh-nang-uu-nhuoc-diem/'>[Review] Đồng Hồ Báo Thức Kiêm Sạc Không Dây 15W WCT001: Tính Năng, Ưu Nhược Điểm</a></div><div class="wp-block-rss__item-excerpt">Đồng hồ báo thức kiêm sạc không dây 15W mã WCT001 có thể dùng như một vật trang trí trên kệ sách, bàn làm việc hoặc làm quà tặng cho bạn bè, người thân. Với kiểu dáng sang trọng cùng tính đa nhiệm, thiết bị còn thích hợp để phát […]</div></li><li class='wp-block-rss__item'><div class='wp-block-rss__item-title'><a href='https://phukiendienthoaigiare.com/review-pin-sac-du-phong-10000mah-sac-nhanh-qc3-0-pb1006-uu-nhuoc-diem-va-gia-ca/'>Review Pin Sạc Dự Phòng 10000mAh Sạc Nhanh QC3.0 PB1006: Ưu – Nhược Điểm Và Giá Cả</a></div><div class="wp-block-rss__item-excerpt">Với kiểu dáng thanh lịch, sang trọng và trang nhã cùng thiết kế nhỏ gọn, lại là sản phẩm hợp với thời đại công nghệ nên Pin sạc dự phòng PB1006 rất thích hợp dùng làm quà tặng cho các đối tác, khách hàng thân thiết của các chủ doanh […]</div></li><li class='wp-block-rss__item'><div class='wp-block-rss__item-title'><a href='https://phukiendienthoaigiare.com/review-pin-sac-du-phong-10000mah-tich-hop-sac-khong-day-pb1007-logo-phat-sang-khi-su-dung/'>Review Pin Sạc Dự Phòng 10000mAh Tích Hợp Sạc Không Dây Pb1007 – Logo Phát Sáng Khi Sử Dụng</a></div><div class="wp-block-rss__item-excerpt">Khoảng ¾ diện tích pin sạc PB1007 được phủ chất liệu vải linen – loại vải có khả năng thấm hút mồ hôi, chịu nhiệt tốt và có độ bóng mượt rất đẹp. Chính vì vậy, dù được bao phủ bởi chất liệu là vải nhưng pin sạc dự phòng […]</div></li></ul>
<h2 id="h-sản-phẩm-mới-1">Sản phẩm mới</h2>
<ul class="is-grid columns-2 wp-block-rss"><li class='wp-block-rss__item'><div class='wp-block-rss__item-title'><a href='https://phukiendienthoaigiare.com/product/haofa-skeleton-automatic-tourbillon-1901-1-double-spring-watch/'>HAOFA SKELETON AUTOMATIC TOURBILLON 1901-1 DOUBLE SPRING WATCH</a></div><div class="wp-block-rss__item-excerpt">THÔNG SỐ CHUNG： Case diameter: 51.5mmx44mm Case thickness: 16.5mm Movement: E.3H41Automatic Movement Vibration frequency: 28800 (times/hour) Drive: double spring drive Winding method: automatic winding Gem Bearings: 26 Bezel material: carbon fiber Case Material : Titanium-magnesium alloy Strap material: rubber Waterproof depth: 30m life waterproof Mirror back cover: artificial sapphire CÁC […]</div></li><li class='wp-block-rss__item'><div class='wp-block-rss__item-title'><a href='https://phukiendienthoaigiare.com/product/pin-sac-du-phong-10000mah-recci-rpb-p09-sac-nhanh-22-5w-chuan-pd-qc3-0/'>Pin Sạc Dự Phòng 10000mAh Recci RPB-P09 Sạc Nhanh 22.5W Chuẩn PD , QC3.0</a></div><div class="wp-block-rss__item-excerpt">Pin sạc dự phòng 10000mAh Recci RPB_P09 Sạc Nhanh 22.5W Chuẩn PD , QC3.0 Cho Điện Thoại Và Máy Tính Bảng Thiết kế sang trọng, nhỏ gọn và mạnh mẽ với 2 màu đen, trắng thời trang Đèn LED hiển thị dung lượng pin, mỗi vạch tương ứng 25% dung […]</div></li><li class='wp-block-rss__item'><div class='wp-block-rss__item-title'><a href='https://phukiendienthoaigiare.com/product/pin-sac-du-phong-khong-day-10000-mah-pd-qc3-0-recci-ten-series/'>Pin Sạc Dự Phòng Không Dây 10000 mAh PD QC3.0 Recci Ten Series</a></div><div class="wp-block-rss__item-excerpt">Pin Sạc Dự Phòng Không Dây Recci Ten Series 10000 mAh Sạc Nhanh PD QC3.0 Tích hợp Sạc Không Dây Qi 10W Tương thích nhiều thiết bị Thiết kế sang trọng, nhỏ gọn và mạnh mẽ với 2 màu đen, trắng thời trang Đèn LED hiển thị dung lượng pin, […]</div></li><li class='wp-block-rss__item'><div class='wp-block-rss__item-title'><a href='https://phukiendienthoaigiare.com/product/pin-sac-du-phong-polymer-10000mah-type-c-18w-pd-qc3-0-recci-p01/'>Pin Sạc Dự Phòng Polymer 10000mAh Type C 18W PD QC3.0 Recci P01</a></div><div class="wp-block-rss__item-excerpt">Pin Sạc Dự Phòng Polymer 10.000 mAh Recci P01 SẠC NHANH TRONG NHÁY MẮT Thiết kế sang trọng, nhỏ gọn , vỏ nhôm cứng cáp với 2 màu đen, xanh thời trang Tích hợp công nghệ sạc thông minh Power Delivery sạc nhanh 2 chiều 18 W. Hỗ trợ 2 […]</div></li></ul><p>The post <a rel="nofollow" href="https://phukiendienthoaigiare.com/cung-dap-hop-qua-tang-doanh-nghiep-3-trong-1-gs304-de-xem-ben-trong-co-gi-ngon/">Cùng “Đập Hộp” Quà Tặng Doanh Nghiệp 3 Trong 1 GS304 Để Xem Bên Trong Có Gì “Ngon”</a> appeared first on <a rel="nofollow" href="https://phukiendienthoaigiare.com">Phụ kiện điện thoại</a>.</p> | 1.0 | Cùng “Đập Hộp” Quà Tặng Doanh Nghiệp 3 Trong 1 GS304 Để Xem Bên Trong Có Gì “Ngon” - <p><strong>Bài viết này không phải là bài review, lại càng không phải là bài PR sản phẩm. Mình viết bài này chủ yếu để “đập hộp” xem thử bên trong món quà tặng doanh nghiệp 3 trong 1 GS304 này có gì để những ai có nhu cầu có thể tham khảo thôi nhé!</strong></p>
<p>Những ai làm chủ doanh nghiệp (hoặc giữ một chức vụ quan trọng trong công ty) mỗi năm, vào những dịp quan trọng sẽ có một vài món quà nho nhỏ gửi tặng đến đối tác, khách hàng thay cho lời tri ân và cảm ơn họ đã đồng hành cùng công ty. Đây cũng là cách khá phổ biến để giữ mối quan hệ cả hai thêm bền vững, có thể hợp tác lâu dài và cùng nhau hướng đến thành công trong từng dự án. Vì vậy, những món quà tặng bao giờ cũng cần phải hợp thời đại, hữu ích và được thiết kế sang trọng nhất có thể.</p>
<p>Vì thế, Quà tặng doanh nghiệp 3 trong 1 GS304 đã được ra đời với sứ mệnh vô cùng cao cả: trở thành món quà kết nối giữa các đối tác, công ty – khách hàng lại với nhau. Và lẽ dĩ nhiên, những gì thuộc gói quà tặng này đều vô cùng hữu ích đối với hầu hết các đối tượng trong xã hội.</p>
<p>Cùng xem bên trong món quà tặng này có gì nhé!</p>
<h2 id="h-dập-hộp-qua-tặng-doanh-nghiệp-3-trong-1-gs304">“Đập hộp” Quà tặng doanh nghiệp 3 trong 1 GS304</h2>
<p>Khi đập hộp xong thì mình nhận thấy, bên trong Quà tặng doanh nghiệp GS304 bao gồm:</p>
<ul><li>Pin sạc dự phòng.</li><li>Củ sạc nhanh.</li><li>Móc dán điện thoại.</li><li>Cáp sạc USB.</li><li>Hướng dẫn sử dụng.</li></ul>
<p>Cả 3 món quà trên đều là những quà tặng công nghệ vô cùng hữu dụng và hợp với thời đại công nghệ 4.0 hiện nay, lại đặc biệt phù hợp với hầu hết đối tượng trong xã hội (trừ các bé thiếu nhi). Vì vậy, xét trên phương diện hợp thời đại thì đây là hộp quà tặng vô cùng rất đáng để cho các doanh nghiệp lưu tâm.</p>
<p>Bây giờ, hãy xem xét chi tiết các món quà như thế nào nhé!</p>
<div class="wp-block-image"><figure class="aligncenter size-full"><img width="1000" height="1000" src="https://phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-11.jpg" alt="Quà Tặng Doanh Nghiệp 3 Trong 1 GS304" class="wp-image-16080" srcset="//phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-11.jpg 1000w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-11-300x300.jpg 300w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-11-150x150.jpg 150w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-11-768x768.jpg 768w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-11-990x990.jpg 990w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-11-441x441.jpg 441w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-11-600x600.jpg 600w" sizes="(max-width: 1000px) 100vw, 1000px" /><figcaption><em>Bên trong chiếc hộp Quà tặng doanh nghiệp 3 trong 1 GS304 bao gồm: pin sạc dự phòng, củ sạc nhanh và móc dán điện thoạ</em>i</figcaption></figure></div>
<h3 id="h-1-về-pin-sạc-dự-phong">1. Về pin sạc dự phòng</h3>
<p>Pin sạc dự phòng trong hộp quà có dung lượng khoảng 3000mAh – tức phụ kiện có thể cung cấp dòng điện 1000mAh trong 3 giờ đồng hồ. Như vậy, những ai sử dụng điện thoại có dung lượng pin khoảng 2000 – 3000mAh thì có thể sử dụng phụ kiện này và sạc được 50% pin, thích hợp dùng trong những lúc smartphone cạn kiệt năng lượng và cần nạp thêm pin để tiếp tục công việc.</p>
<div class="wp-block-image"><figure class="aligncenter size-full"><img width="800" height="800" src="https://phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-8.jpg" alt="Quà Tặng Doanh Nghiệp 3 Trong 1 GS304" class="wp-image-16083" srcset="//phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-8.jpg 800w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-8-300x300.jpg 300w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-8-150x150.jpg 150w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-8-768x768.jpg 768w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-8-441x441.jpg 441w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-8-600x600.jpg 600w" sizes="(max-width: 800px) 100vw, 800px" /><figcaption>Pin sạc dự phòng với đầy đủ các chức năng </figcaption></figure></div>
<p><strong><em>Đánh giá ưu nhược điểm:</em></strong></p>
<p><em><u>Ưu điểm</u></em>:</p>
<ul><li>Hỗ trợ nạp pin trong trường hợp khẩn cấp.</li><li>Tương thích với hầu hết thiết bị điện tử trên thị trường.</li><li>Có tính năng bảo vệ quá nhiệt, quá tải và tự động ngắt nguồn điện khi sạc đầy.</li><li>Thiết kế nhỏ gọn, sang trọng, dễ dàng mang theo mọi lúc, mọi nơi.</li><li>Chất liệu nhựa ABS an toàn, bền bỉ, không thấm nước.</li><li>Có đèn LED thông báo tình trạng sạc pin.</li></ul>
<p><em><u>Nhược điểm</u></em>:</p>
<ul><li>Chỉ sạc được hơn 50% pin.</li><li>Thời gian chờ sạc đầy pin lâu hơn so với các dòng phụ kiện có dung lượng pin lớn.</li></ul>
<h3 id="h-2-củ-sạc-nhanh">2. Củ sạc nhanh</h3>
<p>Đây là phụ kiện khá phổ biến trên thị trường phụ kiện điện thoại hiện nay. Sản phẩm có thể sạc nhanh hơn 40% so với các củ sạc thông thường, cụ thể là sạc điện thoại trong vòng 0,5 – 1 giờ đồng hồ. Với tính năng sạc nhanh này, củ sạc vô cùng thích hợp đối với những ai thường xuyên bận rộn với công việc.</p>
<div class="wp-block-image"><figure class="aligncenter size-large"><img width="1024" height="1024" src="https://phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-1-1024x1024.jpg" alt="Quà Tặng Doanh Nghiệp 3 Trong 1 GS304" class="wp-image-16084" srcset="//phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-1-1024x1024.jpg 1024w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-1-300x300.jpg 300w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-1-150x150.jpg 150w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-1-768x767.jpg 768w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-1-990x989.jpg 990w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-1-441x441.jpg 441w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-1-600x599.jpg 600w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-1.jpg 1134w" sizes="(max-width: 1024px) 100vw, 1024px" /><figcaption>Củ sạc nhanh tiêu chuẩn 2A</figcaption></figure></div>
<p><strong><em>Đánh giá củ sạc nhanh 2A:</em></strong></p>
<ul><li>Tương thích với hầu hết thiết bị điện tử trên thị trường.</li><li>Cho thời gian sạc nhanh, phù hợp với đối tác, khách hàng của doanh nghiệp trong các dự án.</li><li>Dễ dàng mang theo và sử dụng mọi lúc, mọi nơi.</li></ul>
<h3 id="h-3-moc-dan-diện-thoại">3. Móc dán điện thoại</h3>
<p>Dù không phải là món quà tặng hợp với thời đại công nghệ số như hai món quà trên trong bộ Quà tặng doanh nghiệp GS304 nhưng chiếc móc dán điện thoại lại có thể được dùng để in Logo doanh nghiệp, tạo hiệu ứng và quảng bá thương hiệu đến với người khác. Với cách làm này, doanh nghiệp sẽ có thể tìm kiếm khách hàng mục tiêu, đồng thời tăng khả năng nhận diện thương hiệu mà không mất quá nhiều chi phí cho công cuộc marketing.</p>
<p>Ngoài ra, đi kèm cùng 3 món quà tặng trên là một cáp sạc đa năng với 3 cổng kết nối: Lightning, cổng USB và cổng MicroUSB, thích hợp sử dụng cho nhiều thiết bị điện tử khác nhau.</p>
<div class="wp-block-image"><figure class="aligncenter size-full"><img width="1000" height="1000" src="https://phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-14.jpg" alt="Quà Tặng Doanh Nghiệp 3 Trong 1 GS304" class="wp-image-16081" srcset="//phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-14.jpg 1000w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-14-300x300.jpg 300w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-14-150x150.jpg 150w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-14-768x768.jpg 768w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-14-990x990.jpg 990w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-14-441x441.jpg 441w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-14-600x600.jpg 600w" sizes="(max-width: 1000px) 100vw, 1000px" /><figcaption><em>Cáp sạc đa năng 3 trong 1 phù hợp để sạc với hầu hết thiết bị điện tử hiện nay</em></figcaption></figure></div>
<h2 id="h-co-nen-chọn-qua-tặng-doanh-nghiệp-3-trong-1-gs304">Có nên chọn Quà tặng doanh nghiệp 3 trong 1 GS304?</h2>
<p>Trước khi đưa ra quyết định, các doanh nghiệp có thể xem xét đến các yếu tố sau:</p>
<h3 id="h-1-về-xu-hướng">1. Về xu hướng</h3>
<p>Cả 3 món quà tặng đều có liên quan đến công nghệ, hợp với xu hướng thị trường và thời đại công nghệ 4.0, lại phù hợp với hầu hết các đối tượng và dễ dàng mang theo bên mình.</p>
<h3 id="h-2-về-mặt-tiền">2. Về “mặt tiền”</h3>
<p>3 món Quà tặng doanh nghiệp GS304 đều được đặt trong một chiếc hộp vô cùng sang trọng. Bên trong hộp được lót một tấm mica lót vải nhung tạo sự trang trọng cho hộp quà và phù hợp với tính chất của doanh nghiệp.</p>
<h3 id="h-3-về-sự-hữu-dụng">3. Về sự hữu dụng</h3>
<p>Khác với các dòng sản phẩm đơn lẻ mà mình thường review trước đó, bộ Quà tặng doanh nghiệp 3 trong 1 GS304 là sự kết hợp của 3 thiết bị công nghệ vô cùng cần thiết với người dùng, tạo nên sự đa dạng và phong phủ của món quà.</p>
<h3 id="h-4-về-chất-lượng">4. Về chất lượng</h3>
<p>Cả 3 món quà trong hộp Quà tặng doanh nghiệp GS304 đều đạt được các chứng nhận sau:</p>
<ul><li>CE: Chứng nhận về chất lượng của sản phẩm.</li><li>FCC: Chứng nhận đảm bảo về mặt chất lượng của các thiết bị điện tử mà không bị nhiễu động quá mức, được cấp bởi Ủy bang Truyền thông Liên bang Hoa Kỳ.</li><li>RoHS: Chứng nhận về hạn chế các chất cháy nổ trong các thiết bị điện tử.</li><li>CO: Chứng nhận xuất xứ, nguồn gốc hàng hóa của một quốc gia/lãnh thổ và được cấp bởi cơ quan có thẩm quyền.</li></ul>
<h3 id="h-5-về-gia-trị-kinh-tế">5. Về giá trị kinh tế</h3>
<p>Hộp Quà tặng doanh nghiệp 3 trong 1 GS304 có giá thành không quá cao so với các bộ Quà tặng doanh nghiệp khác, giúp các cá nhân/doanh nghiệp tiết kiệm chi phí mà vẫn có thể quảng bá thương hiệu đến với mọi người.</p>
<div class="wp-block-image"><figure class="aligncenter size-full"><img width="1000" height="1000" src="https://phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-4.jpg" alt="Quà Tặng Doanh Nghiệp 3 Trong 1 GS304" class="wp-image-16085" srcset="//phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-4.jpg 1000w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-4-300x300.jpg 300w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-4-150x150.jpg 150w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-4-768x768.jpg 768w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-4-990x990.jpg 990w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-4-441x441.jpg 441w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-4-600x600.jpg 600w" sizes="(max-width: 1000px) 100vw, 1000px" /><figcaption> Quà tặng doanh nghiệp 3 trong 1 GS304 chính là món quà tặng công nghệ hợp thời và cực kỳ tiện ích</figcaption></figure></div>
<h2 id="h-kết">Kết</h2>
<p>Nhìn chung, theo mình thì hộp Quà tặng doanh nghiệp 3 trong 1 GS304 là một món quà mang cả ý nghĩa về vật chất lẫn tinh thần của doanh nghiệp với đối tác, khách hàng. Bên cạnh đó, đây còn là một phương pháp marketing ít tốn kém nhất mà mang lại hiệu quả cao cho doanh nghiệp.</p>
<p>Nếu đứng trên cương vị là người tặng, mình sẽ lựa chọn ngay Hộp quà này bởi giá trị mang lại khá nhiều mà không mất nhiều chi phí. Còn nếu đứng trên cương vị khách hàng, mình sẽ rất vui khi nhận được món quà hợp thời đại và hữu ích, thậm chí còn đánh giá cao khả năng bắt kịp xu hướng và “đọc” tâm lý người khác.</p>
<p>Ngoài món Quà tặng doanh nghiệp 3 trong 1 GS304 này ra, doanh nghiệp cũng có thể lựa chọn những món quà tặng riêng lẻ như pin sạc dự phòng kiêm sạc không dây, đèn bàn tích hợp sạc thông minh và đồng hồ thông minh, đồng hồ kiêm sạc không dây,… để làm quà cho đối tác, khách hàng. Tuy nhiên, việc lựa chọn những sản phẩm mình vừa kể trên sẽ khá tốn chi phí so với tặng quà theo Gift set như thế này đấy!</p>
<div style="height:100px" aria-hidden="true" class="wp-block-spacer"></div>
<div data-block-name="woocommerce/handpicked-products" data-columns="4" data-edit-mode="false" data-content-visibility="{"title":true,"price":true,"rating":true,"button":false}" data-products="[15001,14876,15037,15079,14981,15467,15550,15061,15531,14942,15570,8502,8435,14959,14915,15446]" data-align-buttons="true" class="wc-block-grid wp-block-handpicked-products wc-block-handpicked-products has-4-columns has-multiple-rows has-aligned-buttons"><ul class="wc-block-grid__products"><li class="wc-block-grid__product">
<a href="https://phukiendienthoaigiare.com/product/qua-tang-khuyen-mai-in-logo-thuong-hieu-so-luong-it-gs306/" class="wc-block-grid__product-link">
<div class="wc-block-grid__product-image"><img width="300" height="300" src="https://phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-mien-phi-in-logo-thuong-hieu-qua-tang-hoi-nghi-1-300x300.jpg" class="attachment-woocommerce_thumbnail size-woocommerce_thumbnail" alt="quà tặng công nghệ cao cấp 3 trong 1 in logo doanh nghiệp số lượng ít tphcm quà tặng khuyến mãi" srcset="//phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-mien-phi-in-logo-thuong-hieu-qua-tang-hoi-nghi-1-300x300.jpg 300w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-mien-phi-in-logo-thuong-hieu-qua-tang-hoi-nghi-1-150x150.jpg 150w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-mien-phi-in-logo-thuong-hieu-qua-tang-hoi-nghi-1-768x768.jpg 768w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-mien-phi-in-logo-thuong-hieu-qua-tang-hoi-nghi-1-441x441.jpg 441w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-mien-phi-in-logo-thuong-hieu-qua-tang-hoi-nghi-1-600x600.jpg 600w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-mien-phi-in-logo-thuong-hieu-qua-tang-hoi-nghi-1.jpg 800w" sizes="(max-width: 360px) 147px, (max-width: 300px) 100vw, 300px" /></div>
<div class="wc-block-grid__product-title">Quà Tặng Khuyến Mãi in Logo Thương Hiệu Số Lượng Ít GS306</div>
</a>
<div class="wc-block-grid__product-price price"><span class="woocommerce-Price-amount amount">385.000 <span class="woocommerce-Price-currencySymbol">₫</span></span></div>
<div class="wc-block-grid__product-rating"><div class="star-rating" role="img" aria-label="Được xếp hạng 5.00 5 sao"><span style="width:100%"><strong class="rating">5.00</strong> trên 5 dựa trên <span class="rating">82</span> đánh giá</span></div></div>
</li><li class="wc-block-grid__product">
<a href="https://phukiendienthoaigiare.com/product/qua-tang-doanh-nghiep-3in1-gs305-in-logo-thuong-hieu/" class="wc-block-grid__product-link">
<div class="wc-block-grid__product-image"><img width="300" height="300" src="https://phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-khach-moi-hoi-nghi-in-logo-thuong-hieu-tphcm-1-300x300.jpg" class="attachment-woocommerce_thumbnail size-woocommerce_thumbnail" alt="quà tặng công nghệ cao cấp 3 trong 1 miễn phí in logo doanh nghiệp, logo led phát sáng khi sử dụng quà tặng doanh nghiệp" srcset="//phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-khach-moi-hoi-nghi-in-logo-thuong-hieu-tphcm-1-300x300.jpg 300w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-khach-moi-hoi-nghi-in-logo-thuong-hieu-tphcm-1-150x150.jpg 150w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-khach-moi-hoi-nghi-in-logo-thuong-hieu-tphcm-1-768x768.jpg 768w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-khach-moi-hoi-nghi-in-logo-thuong-hieu-tphcm-1-990x990.jpg 990w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-khach-moi-hoi-nghi-in-logo-thuong-hieu-tphcm-1-441x441.jpg 441w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-khach-moi-hoi-nghi-in-logo-thuong-hieu-tphcm-1-600x600.jpg 600w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-khach-moi-hoi-nghi-in-logo-thuong-hieu-tphcm-1.jpg 1000w" sizes="(max-width: 360px) 147px, (max-width: 300px) 100vw, 300px" /></div>
<div class="wc-block-grid__product-title">Quà Tặng Doanh Nghiệp 3in1 GS305 In Logo Thương Hiệu</div>
</a>
<div class="wc-block-grid__product-price price"><span class="woocommerce-Price-amount amount">745.000 <span class="woocommerce-Price-currencySymbol">₫</span></span></div>
<div class="wc-block-grid__product-rating"><div class="star-rating" role="img" aria-label="Được xếp hạng 5.00 5 sao"><span style="width:100%"><strong class="rating">5.00</strong> trên 5 dựa trên <span class="rating">83</span> đánh giá</span></div></div>
</li><li class="wc-block-grid__product">
<a href="https://phukiendienthoaigiare.com/product/qua-tang-doanh-nghiep-4in1-gs402-in-logo-doanh-thuong-hieu-so-luong-it/" class="wc-block-grid__product-link">
<div class="wc-block-grid__product-image"><img width="300" height="300" src="https://phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-4-trong-1-in-logo-thuong-hieu-300x300.jpg" class="attachment-woocommerce_thumbnail size-woocommerce_thumbnail" alt="quà tặng công nghệ cao cấp 4 trong 1 miễn phí in logo doanh nghiệp quà tặng doanh nghiệp quà tặng khách hàng hội nghị" srcset="//phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-4-trong-1-in-logo-thuong-hieu-300x300.jpg 300w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-4-trong-1-in-logo-thuong-hieu-150x150.jpg 150w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-4-trong-1-in-logo-thuong-hieu-768x768.jpg 768w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-4-trong-1-in-logo-thuong-hieu-990x990.jpg 990w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-4-trong-1-in-logo-thuong-hieu-441x441.jpg 441w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-4-trong-1-in-logo-thuong-hieu-600x600.jpg 600w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-4-trong-1-in-logo-thuong-hieu.jpg 1000w" sizes="(max-width: 360px) 147px, (max-width: 300px) 100vw, 300px" /></div>
<div class="wc-block-grid__product-title">Quà Tặng Doanh Nghiệp 4in1 GS402 – In Logo Doanh Thương Hiệu Số Lượng Ít</div>
</a>
<div class="wc-block-grid__product-price price"><span class="woocommerce-Price-amount amount">1.365.000 <span class="woocommerce-Price-currencySymbol">₫</span></span></div>
<div class="wc-block-grid__product-rating"><div class="star-rating" role="img" aria-label="Được xếp hạng 5.00 5 sao"><span style="width:100%"><strong class="rating">5.00</strong> trên 5 dựa trên <span class="rating">81</span> đánh giá</span></div></div>
</li><li class="wc-block-grid__product">
<a href="https://phukiendienthoaigiare.com/product/qua-tang-doanh-nghiep-3-trong-1-gs304-in-logo-doanh-nghiep-so-luong-it/" class="wc-block-grid__product-link">
<div class="wc-block-grid__product-image"><img width="300" height="300" src="https://phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-in-logo-thuong-hieu-300x300.jpg" class="attachment-woocommerce_thumbnail size-woocommerce_thumbnail" alt="Quà Tặng Doanh Nghiệp 3 Trong 1 GS304 - In Logo Doanh Nghiệp Số Lượng Ít" srcset="//phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-in-logo-thuong-hieu-300x300.jpg 300w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-in-logo-thuong-hieu-150x150.jpg 150w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-in-logo-thuong-hieu-768x768.jpg 768w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-in-logo-thuong-hieu-990x990.jpg 990w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-in-logo-thuong-hieu-441x441.jpg 441w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-in-logo-thuong-hieu-600x600.jpg 600w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-in-logo-thuong-hieu.jpg 1000w" sizes="(max-width: 360px) 147px, (max-width: 300px) 100vw, 300px" /></div>
<div class="wc-block-grid__product-title">Quà Tặng Doanh Nghiệp 3 Trong 1 GS304 – In Logo Doanh Nghiệp Số Lượng Ít</div>
</a>
<div class="wc-block-grid__product-price price"><span class="woocommerce-Price-amount amount">385.000 <span class="woocommerce-Price-currencySymbol">₫</span></span></div>
<div class="wc-block-grid__product-rating"><div class="star-rating" role="img" aria-label="Được xếp hạng 5.00 5 sao"><span style="width:100%"><strong class="rating">5.00</strong> trên 5 dựa trên <span class="rating">85</span> đánh giá</span></div></div>
</li><li class="wc-block-grid__product">
<a href="https://phukiendienthoaigiare.com/product/combo-qua-tang-phu-kien-cao-cap-cho-iphone-13-series/" class="wc-block-grid__product-link">
<div class="wc-block-grid__product-image"><img width="300" height="300" src="https://phukiendienthoaigiare.com/wp-content/uploads/2021/12/combo-qua-tang-phu-kien-cao-cap-cho-iphone-13-in-logo-doanh-nghiep-300x300.jpg" class="attachment-woocommerce_thumbnail size-woocommerce_thumbnail" alt="combo quà tặng phụ kiện cao cấp iphone 13 series 5 trong 1" srcset="//phukiendienthoaigiare.com/wp-content/uploads/2021/12/combo-qua-tang-phu-kien-cao-cap-cho-iphone-13-in-logo-doanh-nghiep-300x300.jpg 300w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/combo-qua-tang-phu-kien-cao-cap-cho-iphone-13-in-logo-doanh-nghiep-150x150.jpg 150w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/combo-qua-tang-phu-kien-cao-cap-cho-iphone-13-in-logo-doanh-nghiep-768x768.jpg 768w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/combo-qua-tang-phu-kien-cao-cap-cho-iphone-13-in-logo-doanh-nghiep-441x441.jpg 441w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/combo-qua-tang-phu-kien-cao-cap-cho-iphone-13-in-logo-doanh-nghiep-600x600.jpg 600w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/combo-qua-tang-phu-kien-cao-cap-cho-iphone-13-in-logo-doanh-nghiep.jpg 790w" sizes="(max-width: 360px) 147px, (max-width: 300px) 100vw, 300px" /></div>
<div class="wc-block-grid__product-title">Combo Quà Tặng Phụ Kiện Cao Cấp Cho Iphone 13 Series</div>
</a>
<div class="wc-block-grid__product-price price"><span class="woocommerce-Price-amount amount">1.365.000 <span class="woocommerce-Price-currencySymbol">₫</span></span></div>
<div class="wc-block-grid__product-rating"><div class="star-rating" role="img" aria-label="Được xếp hạng 5.00 5 sao"><span style="width:100%"><strong class="rating">5.00</strong> trên 5 dựa trên <span class="rating">84</span> đánh giá</span></div></div>
</li><li class="wc-block-grid__product">
<a href="https://phukiendienthoaigiare.com/product/qua-tang-cong-nghe-5-trong-1-cao-cap-gs504/" class="wc-block-grid__product-link">
<div class="wc-block-grid__product-image"><img width="300" height="300" src="https://phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-in-logo-doanh-nghiep-cao-cap-qua-tang-doi-tac-tphcm-300x300.png" class="attachment-woocommerce_thumbnail size-woocommerce_thumbnail" alt="Bộ quà tặng Doanh Nghiệp 5 trong 1 Pin Sạc dự phòng 10000mAh, sạc nhanh PD+QC3.0 18W Củ sạc nhanh QC3.0 PD 18W Cáp sạc nhanh PD 18W" srcset="//phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-in-logo-doanh-nghiep-cao-cap-qua-tang-doi-tac-tphcm-300x300.png 300w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-in-logo-doanh-nghiep-cao-cap-qua-tang-doi-tac-tphcm-150x150.png 150w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-in-logo-doanh-nghiep-cao-cap-qua-tang-doi-tac-tphcm-768x768.png 768w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-in-logo-doanh-nghiep-cao-cap-qua-tang-doi-tac-tphcm-441x441.png 441w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-in-logo-doanh-nghiep-cao-cap-qua-tang-doi-tac-tphcm-600x600.png 600w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-in-logo-doanh-nghiep-cao-cap-qua-tang-doi-tac-tphcm.png 800w" sizes="(max-width: 360px) 147px, (max-width: 300px) 100vw, 300px" /></div>
<div class="wc-block-grid__product-title">Quà Tặng Công Nghệ 5 Trong 1 Cao Cấp GS504</div>
</a>
<div class="wc-block-grid__product-price price"><span class="woocommerce-Price-amount amount">1.350.000 <span class="woocommerce-Price-currencySymbol">₫</span></span></div>
<div class="wc-block-grid__product-rating"><div class="star-rating" role="img" aria-label="Được xếp hạng 5.00 5 sao"><span style="width:100%"><strong class="rating">5.00</strong> trên 5 dựa trên <span class="rating">90</span> đánh giá</span></div></div>
</li><li class="wc-block-grid__product">
<a href="https://phukiendienthoaigiare.com/product/qua-tang-doanh-nghiep-4-in-1-hop-qua-tet-2022-gs401/" class="wc-block-grid__product-link">
<div class="wc-block-grid__product-image"><img width="300" height="300" src="https://phukiendienthoaigiare.com/wp-content/uploads/2021/12/set-qua-tet-2022-qua-tang-doanh-nghiep-tai-nghe-bluetooth-pin-sac-du-phong-10000mah-300x300.jpg" class="attachment-woocommerce_thumbnail size-woocommerce_thumbnail" alt="Bộ quà tặng Doanh Nghiệp 4 trong 1 Pin Sạc dự phòng , Củ sạc nhanh QC3.0 PD 18W Cáp sạc nhanh PD 18W tai nghe bluetooth" srcset="//phukiendienthoaigiare.com/wp-content/uploads/2021/12/set-qua-tet-2022-qua-tang-doanh-nghiep-tai-nghe-bluetooth-pin-sac-du-phong-10000mah-300x300.jpg 300w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/set-qua-tet-2022-qua-tang-doanh-nghiep-tai-nghe-bluetooth-pin-sac-du-phong-10000mah-150x150.jpg 150w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/set-qua-tet-2022-qua-tang-doanh-nghiep-tai-nghe-bluetooth-pin-sac-du-phong-10000mah-441x442.jpg 441w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/set-qua-tet-2022-qua-tang-doanh-nghiep-tai-nghe-bluetooth-pin-sac-du-phong-10000mah.jpg 459w" sizes="(max-width: 360px) 147px, (max-width: 300px) 100vw, 300px" /></div>
<div class="wc-block-grid__product-title">Quà Tặng Doanh Nghiệp 4 in 1 Hộp Quà Tết 2022 GS401</div>
</a>
<div class="wc-block-grid__product-price price"><span class="woocommerce-Price-amount amount">650.000 <span class="woocommerce-Price-currencySymbol">₫</span></span></div>
<div class="wc-block-grid__product-rating"><div class="star-rating" role="img" aria-label="Được xếp hạng 5.00 5 sao"><span style="width:100%"><strong class="rating">5.00</strong> trên 5 dựa trên <span class="rating">89</span> đánh giá</span></div></div>
</li><li class="wc-block-grid__product">
<a href="https://phukiendienthoaigiare.com/product/qua-tang-cong-nghe-5in1-hop-qua-tet-2022-gs503/" class="wc-block-grid__product-link">
<div class="wc-block-grid__product-image"><img width="300" height="300" src="https://phukiendienthoaigiare.com/wp-content/uploads/2021/12/hop-qua-tet-2022-qua-tang-cong-nghe-cao-cap-300x300.jpg" class="attachment-woocommerce_thumbnail size-woocommerce_thumbnail" alt="hộp quà tết 2022 quà tặng công nghệ cao cấp in logo thương hiệu" srcset="//phukiendienthoaigiare.com/wp-content/uploads/2021/12/hop-qua-tet-2022-qua-tang-cong-nghe-cao-cap-300x300.jpg 300w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/hop-qua-tet-2022-qua-tang-cong-nghe-cao-cap-150x150.jpg 150w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/hop-qua-tet-2022-qua-tang-cong-nghe-cao-cap.jpg 439w" sizes="(max-width: 360px) 147px, (max-width: 300px) 100vw, 300px" /></div>
<div class="wc-block-grid__product-title">Quà Tặng Công Nghệ 5 in 1 Hộp Quà Tết 2022 GS503</div>
</a>
<div class="wc-block-grid__product-price price"><span class="woocommerce-Price-amount amount">950.000 <span class="woocommerce-Price-currencySymbol">₫</span></span></div>
<div class="wc-block-grid__product-rating"><div class="star-rating" role="img" aria-label="Được xếp hạng 5.00 5 sao"><span style="width:100%"><strong class="rating">5.00</strong> trên 5 dựa trên <span class="rating">91</span> đánh giá</span></div></div>
</li><li class="wc-block-grid__product">
<a href="https://phukiendienthoaigiare.com/product/hop-qua-tang-cong-nghe-6-trong-1-gs601/" class="wc-block-grid__product-link">
<div class="wc-block-grid__product-image"><img width="300" height="300" src="https://phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-doi-tac-hop-qua-tang-cong-nghe-cao-cap-6-trong-1-tai-nghe-bluetooth-sac-khong-day-pin-sac-du-phong-cap-sac-nhanh-gia-do-dien-thoai-tai-nghe-buletooth-in-logo-doanh-nghiep-300x300.jpg" class="attachment-woocommerce_thumbnail size-woocommerce_thumbnail" alt="Bộ quà tặng Doanh Nghiệp 6 trong 1 Pin Sạc dự phòng 10000mAh, sạc nhanh PD+QC3.0 18W Củ sạc nhanh QC3.0 PD 18W Cáp sạc nhanh PD 18W" srcset="//phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-doi-tac-hop-qua-tang-cong-nghe-cao-cap-6-trong-1-tai-nghe-bluetooth-sac-khong-day-pin-sac-du-phong-cap-sac-nhanh-gia-do-dien-thoai-tai-nghe-buletooth-in-logo-doanh-nghiep-300x300.jpg 300w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-doi-tac-hop-qua-tang-cong-nghe-cao-cap-6-trong-1-tai-nghe-bluetooth-sac-khong-day-pin-sac-du-phong-cap-sac-nhanh-gia-do-dien-thoai-tai-nghe-buletooth-in-logo-doanh-nghiep-150x150.jpg 150w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-doi-tac-hop-qua-tang-cong-nghe-cao-cap-6-trong-1-tai-nghe-bluetooth-sac-khong-day-pin-sac-du-phong-cap-sac-nhanh-gia-do-dien-thoai-tai-nghe-buletooth-in-logo-doanh-nghiep-768x768.jpg 768w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-doi-tac-hop-qua-tang-cong-nghe-cao-cap-6-trong-1-tai-nghe-bluetooth-sac-khong-day-pin-sac-du-phong-cap-sac-nhanh-gia-do-dien-thoai-tai-nghe-buletooth-in-logo-doanh-nghiep-441x441.jpg 441w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-doi-tac-hop-qua-tang-cong-nghe-cao-cap-6-trong-1-tai-nghe-bluetooth-sac-khong-day-pin-sac-du-phong-cap-sac-nhanh-gia-do-dien-thoai-tai-nghe-buletooth-in-logo-doanh-nghiep-600x600.jpg 600w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-doi-tac-hop-qua-tang-cong-nghe-cao-cap-6-trong-1-tai-nghe-bluetooth-sac-khong-day-pin-sac-du-phong-cap-sac-nhanh-gia-do-dien-thoai-tai-nghe-buletooth-in-logo-doanh-nghiep.jpg 800w" sizes="(max-width: 360px) 147px, (max-width: 300px) 100vw, 300px" /></div>
<div class="wc-block-grid__product-title">Hộp Quà Tặng Công Nghệ 6 Trong 1 GS601</div>
</a>
<div class="wc-block-grid__product-price price"><span class="woocommerce-Price-amount amount">1.350.000 <span class="woocommerce-Price-currencySymbol">₫</span></span></div>
<div class="wc-block-grid__product-rating"><div class="star-rating" role="img" aria-label="Được xếp hạng 5.00 5 sao"><span style="width:100%"><strong class="rating">5.00</strong> trên 5 dựa trên <span class="rating">92</span> đánh giá</span></div></div>
</li><li class="wc-block-grid__product">
<a href="https://phukiendienthoaigiare.com/product/qua-tang-cong-nghe-cao-cap-gift-box-5in1-gs502/" class="wc-block-grid__product-link">
<div class="wc-block-grid__product-image"><img width="300" height="300" src="https://phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-5-trong-1-mien-phi-in-logo-thuong-hieu-logo-led-phat-sang-khi-su-dung-300x300.jpg" class="attachment-woocommerce_thumbnail size-woocommerce_thumbnail" alt="quà tặng công nghệ cao cấp 5 trong 1 miễn phí in logo doanh nghiệp quà tặng đối tác quà tặng khách hàng hội nghị tai nghe không dây sạc không dây cáp sạc 3 trong 1 củ sạc nhanh qc3.0 pin sạc dự phòng 10000mah" srcset="//phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-5-trong-1-mien-phi-in-logo-thuong-hieu-logo-led-phat-sang-khi-su-dung-300x300.jpg 300w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-5-trong-1-mien-phi-in-logo-thuong-hieu-logo-led-phat-sang-khi-su-dung-150x150.jpg 150w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-5-trong-1-mien-phi-in-logo-thuong-hieu-logo-led-phat-sang-khi-su-dung-768x768.jpg 768w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-5-trong-1-mien-phi-in-logo-thuong-hieu-logo-led-phat-sang-khi-su-dung-441x441.jpg 441w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-5-trong-1-mien-phi-in-logo-thuong-hieu-logo-led-phat-sang-khi-su-dung-600x600.jpg 600w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-5-trong-1-mien-phi-in-logo-thuong-hieu-logo-led-phat-sang-khi-su-dung.jpg 800w" sizes="(max-width: 360px) 147px, (max-width: 300px) 100vw, 300px" /></div>
<div class="wc-block-grid__product-title">Quà Tặng Công Nghệ Cao Cấp Gift Box 5in1 GS502</div>
</a>
<div class="wc-block-grid__product-price price"><span class="woocommerce-Price-amount amount">1.950.000 <span class="woocommerce-Price-currencySymbol">₫</span></span></div>
<div class="wc-block-grid__product-rating"><div class="star-rating" role="img" aria-label="Được xếp hạng 5.00 5 sao"><span style="width:100%"><strong class="rating">5.00</strong> trên 5 dựa trên <span class="rating">93</span> đánh giá</span></div></div>
</li><li class="wc-block-grid__product">
<a href="https://phukiendienthoaigiare.com/product/set-qua-tang-5in1-phu-kien-cong-nghe-cho-xe-o-to-gs501/" class="wc-block-grid__product-link">
<div class="wc-block-grid__product-image"><img width="300" height="300" src="https://phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-5-trong-1-mien-phi-in-logo-thuong-hieu-set-qua-tang-phu-kien-xa-hoi-300x300.jpg" class="attachment-woocommerce_thumbnail size-woocommerce_thumbnail" alt="quà tặng công nghệ cao cấp 5 trong 1 miễn phí in logo doanh nghiệp quà tặng đối tác quà tặng khách hàng hội nghị" srcset="//phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-5-trong-1-mien-phi-in-logo-thuong-hieu-set-qua-tang-phu-kien-xa-hoi-300x300.jpg 300w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-5-trong-1-mien-phi-in-logo-thuong-hieu-set-qua-tang-phu-kien-xa-hoi-150x150.jpg 150w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-5-trong-1-mien-phi-in-logo-thuong-hieu-set-qua-tang-phu-kien-xa-hoi-768x768.jpg 768w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-5-trong-1-mien-phi-in-logo-thuong-hieu-set-qua-tang-phu-kien-xa-hoi-441x441.jpg 441w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-5-trong-1-mien-phi-in-logo-thuong-hieu-set-qua-tang-phu-kien-xa-hoi-600x600.jpg 600w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-5-trong-1-mien-phi-in-logo-thuong-hieu-set-qua-tang-phu-kien-xa-hoi.jpg 800w" sizes="(max-width: 360px) 147px, (max-width: 300px) 100vw, 300px" /></div>
<div class="wc-block-grid__product-title">Set Quà Tặng 5in1 Phụ Kiện Công Nghệ Cho Xe Ô Tô GS501</div>
</a>
<div class="wc-block-grid__product-price price"><span class="woocommerce-Price-amount amount">1.350.000 <span class="woocommerce-Price-currencySymbol">₫</span></span></div>
<div class="wc-block-grid__product-rating"><div class="star-rating" role="img" aria-label="Được xếp hạng 5.00 5 sao"><span style="width:100%"><strong class="rating">5.00</strong> trên 5 dựa trên <span class="rating">92</span> đánh giá</span></div></div>
</li><li class="wc-block-grid__product">
<a href="https://phukiendienthoaigiare.com/product/qua-tang-doanh-nghiep-cao-cap-hop-qua-tang-3in1-gs303/" class="wc-block-grid__product-link">
<div class="wc-block-grid__product-image"><img width="300" height="300" src="https://phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-in-logo-thuong-hieu-logo-led-phat-sang-khi-su-dung-1-300x300.jpg" class="attachment-woocommerce_thumbnail size-woocommerce_thumbnail" alt="quà tặng công nghệ cao cấp 3 trong 1 miễn phí in logo doanh nghiệp, logo led phát sáng khi sử dụng quà tặng đối tác quà tặng khách hàng hội nghị" srcset="//phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-in-logo-thuong-hieu-logo-led-phat-sang-khi-su-dung-1-300x300.jpg 300w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-in-logo-thuong-hieu-logo-led-phat-sang-khi-su-dung-1-150x150.jpg 150w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-in-logo-thuong-hieu-logo-led-phat-sang-khi-su-dung-1-441x442.jpg 441w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-in-logo-thuong-hieu-logo-led-phat-sang-khi-su-dung-1-600x601.jpg 600w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-in-logo-thuong-hieu-logo-led-phat-sang-khi-su-dung-1.jpg 634w" sizes="(max-width: 360px) 147px, (max-width: 300px) 100vw, 300px" /></div>
<div class="wc-block-grid__product-title">Quà Tặng Doanh Nghiệp Cao Cấp Hộp Quà Tặng 3in1 GS303</div>
</a>
<div class="wc-block-grid__product-price price"><span class="woocommerce-Price-amount amount">850.000 <span class="woocommerce-Price-currencySymbol">₫</span></span></div>
<div class="wc-block-grid__product-rating"><div class="star-rating" role="img" aria-label="Được xếp hạng 5.00 5 sao"><span style="width:100%"><strong class="rating">5.00</strong> trên 5 dựa trên <span class="rating">92</span> đánh giá</span></div></div>
</li><li class="wc-block-grid__product">
<a href="https://phukiendienthoaigiare.com/product/set-qua-tang-cong-nghe-cao-cap-3-in-1-gs302/" class="wc-block-grid__product-link">
<div class="wc-block-grid__product-image"><img width="300" height="300" src="https://phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-in-logo-thuong-hieu-logo-led-phat-sang-khi-su-dung-300x300.jpg" class="attachment-woocommerce_thumbnail size-woocommerce_thumbnail" alt="quà tặng công nghệ cao cấp 3 trong 1 miễn phí in logo doanh nghiệp, logo led phát sáng khi sử dụng quà tặng đối tác quà tặng khách hàng hội nghị" srcset="//phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-in-logo-thuong-hieu-logo-led-phat-sang-khi-su-dung-300x300.jpg 300w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-in-logo-thuong-hieu-logo-led-phat-sang-khi-su-dung-150x150.jpg 150w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-in-logo-thuong-hieu-logo-led-phat-sang-khi-su-dung-441x441.jpg 441w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-in-logo-thuong-hieu-logo-led-phat-sang-khi-su-dung-600x600.jpg 600w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-in-logo-thuong-hieu-logo-led-phat-sang-khi-su-dung.jpg 640w" sizes="(max-width: 360px) 147px, (max-width: 300px) 100vw, 300px" /></div>
<div class="wc-block-grid__product-title">Set Quà Tặng Công Nghệ Cao Cấp 3in1 GS302</div>
</a>
<div class="wc-block-grid__product-price price"><span class="woocommerce-Price-amount amount">1.350.000 <span class="woocommerce-Price-currencySymbol">₫</span></span></div>
<div class="wc-block-grid__product-rating"><div class="star-rating" role="img" aria-label="Được xếp hạng 5.00 5 sao"><span style="width:100%"><strong class="rating">5.00</strong> trên 5 dựa trên <span class="rating">92</span> đánh giá</span></div></div>
</li><li class="wc-block-grid__product">
<a href="https://phukiendienthoaigiare.com/product/hop-qua-tang-cong-nghe-cao-cap-3-trong-1-gs301/" class="wc-block-grid__product-link">
<div class="wc-block-grid__product-image"><img width="300" height="300" src="https://phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-in-logo-thuong-hieu-logo-led-phat-sang-khi-su-dung-300x300.png" class="attachment-woocommerce_thumbnail size-woocommerce_thumbnail" alt="quà tặng công nghệ cao cấp 3 trong 1 miễn phí in logo doanh nghiệp, logo led phát sáng khi sử dụng quà tặng đối tác quà tặng khách hàng hội nghị" srcset="//phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-in-logo-thuong-hieu-logo-led-phat-sang-khi-su-dung-300x300.png 300w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-in-logo-thuong-hieu-logo-led-phat-sang-khi-su-dung-150x150.png 150w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-in-logo-thuong-hieu-logo-led-phat-sang-khi-su-dung-441x442.png 441w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-in-logo-thuong-hieu-logo-led-phat-sang-khi-su-dung-600x601.png 600w, //phukiendienthoaigiare.com/wp-content/uploads/2021/12/qua-tang-cong-nghe-cao-cap-3-trong-1-in-logo-thuong-hieu-logo-led-phat-sang-khi-su-dung.png 724w" sizes="(max-width: 360px) 147px, (max-width: 300px) 100vw, 300px" /></div>
<div class="wc-block-grid__product-title">Hộp Quà Tăng Công Nghệ Cao Cấp 3 Trong 1 GS301</div>
</a>
<div class="wc-block-grid__product-price price"><span class="woocommerce-Price-amount amount">1.250.000 <span class="woocommerce-Price-currencySymbol">₫</span></span></div>
<div class="wc-block-grid__product-rating"><div class="star-rating" role="img" aria-label="Được xếp hạng 5.00 5 sao"><span style="width:100%"><strong class="rating">5.00</strong> trên 5 dựa trên <span class="rating">92</span> đánh giá</span></div></div>
</li><li class="wc-block-grid__product">
<a href="https://phukiendienthoaigiare.com/product/sac-khong-day-magsafe-battery-pack-bb01t/" class="wc-block-grid__product-link">
<div class="wc-block-grid__product-image"><img width="300" height="300" src="https://phukiendienthoaigiare.com/wp-content/uploads/2021/11/BB-19-300x300.jpg" class="attachment-woocommerce_thumbnail size-woocommerce_thumbnail" alt="Sạc Không Dây Magsafe Battery Pack BB01T" srcset="//phukiendienthoaigiare.com/wp-content/uploads/2021/11/BB-19-300x300.jpg 300w, //phukiendienthoaigiare.com/wp-content/uploads/2021/11/BB-19-150x150.jpg 150w, //phukiendienthoaigiare.com/wp-content/uploads/2021/11/BB-19-600x600.jpg 600w, //phukiendienthoaigiare.com/wp-content/uploads/2021/11/BB-19-441x441.jpg 441w, //phukiendienthoaigiare.com/wp-content/uploads/2021/11/BB-19.jpg 736w" sizes="(max-width: 360px) 147px, (max-width: 300px) 100vw, 300px" /></div>
<div class="wc-block-grid__product-title">Sạc Không Dây Magsafe Battery Pack BB01T</div>
</a>
<div class="wc-block-grid__product-price price"><span class="woocommerce-Price-amount amount">750.000 <span class="woocommerce-Price-currencySymbol">₫</span></span></div>
<div class="wc-block-grid__product-rating"><div class="star-rating" role="img" aria-label="Được xếp hạng 5.00 5 sao"><span style="width:100%"><strong class="rating">5.00</strong> trên 5 dựa trên <span class="rating">90</span> đánh giá</span></div></div>
</li><li class="wc-block-grid__product">
<a href="https://phukiendienthoaigiare.com/product/sac-khong-day-magsafe-charger-wctx2-15w-chuan-qi-cho-iphone-12-13/" class="wc-block-grid__product-link">
<div class="wc-block-grid__product-image"><img width="300" height="300" src="https://phukiendienthoaigiare.com/wp-content/uploads/2021/11/X2-11-300x300.jpg" class="attachment-woocommerce_thumbnail size-woocommerce_thumbnail" alt="Sạc Không Dây Magsafe Charger WCTX2 15W Chuẩn Qi Cho iPhone 12, 13" srcset="//phukiendienthoaigiare.com/wp-content/uploads/2021/11/X2-11-300x300.jpg 300w, //phukiendienthoaigiare.com/wp-content/uploads/2021/11/X2-11-150x150.jpg 150w, //phukiendienthoaigiare.com/wp-content/uploads/2021/11/X2-11-600x600.jpg 600w, //phukiendienthoaigiare.com/wp-content/uploads/2021/11/X2-11-1024x1024.jpg 1024w, //phukiendienthoaigiare.com/wp-content/uploads/2021/11/X2-11-768x768.jpg 768w, //phukiendienthoaigiare.com/wp-content/uploads/2021/11/X2-11-990x990.jpg 990w, //phukiendienthoaigiare.com/wp-content/uploads/2021/11/X2-11-441x441.jpg 441w, //phukiendienthoaigiare.com/wp-content/uploads/2021/11/X2-11.jpg 1200w" sizes="(max-width: 360px) 147px, (max-width: 300px) 100vw, 300px" /></div>
<div class="wc-block-grid__product-title">Sạc Không Dây Magsafe Charger WCTX2 15W Chuẩn Qi Cho iPhone 12, 13</div>
</a>
<div class="wc-block-grid__product-price price"><span class="woocommerce-Price-amount amount">450.000 <span class="woocommerce-Price-currencySymbol">₫</span></span></div>
<div class="wc-block-grid__product-rating"><div class="star-rating" role="img" aria-label="Được xếp hạng 5.00 5 sao"><span style="width:100%"><strong class="rating">5.00</strong> trên 5 dựa trên <span class="rating">97</span> đánh giá</span></div></div>
</li></ul></div>
<div style="height:100px" aria-hidden="true" class="wp-block-spacer"></div>
<section class="sc_fs_event sc_card">
<h2>Tìm đại lý phân phối – Quà Tặng Doanh Nghiệp 3 Trong 1 GS304 – In Logo Doanh Nghiệp Số Lượng Ít</h2> <figure>
<a href="https://phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-11.jpg" title="">
<img src="https://phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-11-150x150.jpg" alt=""/>
</a>
<meta content="https://phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-11.jpg">
<meta content="1000">
<meta content="1000">
</figure>
<p>
Bộ quà tặng Doanh Nghiệp 3 trong 1 GS304<br>Pin Sạc dự phòng 3000mAh<br>Củ sạc nhanh 2A<br>Móc dán điện thoại in logo Doanh Nghiệp<br>Nhập Khẩu Bảo hành chính hãng<br>Chứng nhận an toàn : CE/FCC/RoHS<br>Chứng nhận xuất xứ hàng hóa: CO<br>Phù hợp làm quà tặng Doanh Nghiệp, Quà tặng nhân viên, Quà khuyến mãi…<br>Customized Branding Logo (MOQ=10pcs)<br> </p>
<div class="sc_row w-100">
<div class="sc_grey-box">
<div class="sc_box-label">
Event Meta </div>
<div class="sc_company">
<div class="sc_company-infos">
<div class="sc_input-group">
<div class="sc_input-label">
Name </div>
<div class="wp-block-structured-content-event__location">
Tìm đại lý phân phối – Quà Tặng Doanh Nghiệp 3 Trong 1 GS304 – In Logo Doanh Nghiệp Số Lượng Ít </div>
</div>
<div class="sc_input-group">
<div class="sc_input-label">
Event Status </div>
<div class="wp-block-structured-content-event__status">
Scheduled </div>
</div>
<div class="sc_input-group">
<div class="sc_input-label">
Start Date </div>
<div class="wp-block-structured-content-event__start_date">
01/12/2021 11:05 Chiều </div>
</div>
<div class="sc_input-group">
<div class="sc_input-label">
End Date </div>
<div class="wp-block-structured-content-event__end_date">
01/12/2050 11:05 Chiều </div>
</div>
</div>
</div>
</div>
<div class="sc_grey-box">
<div class="sc_box-label">
Event Location </div>
<div class="sc_input-group">
<div class="sc_input-label">
Attendance Mode </div>
<div class="wp-block-structured-content-event__event_attendance_mode">
Online </div>
</div>
<div class="sc_input-group">
<div class="sc_input-label">
URL </div>
<div class="wp-block-structured-content-event__online_url">
<a target="_blank" href="https://phukiendienthoaigiare.com/product/qua-tang-doanh-nghiep-3-trong-1-gs304-in-logo-doanh-nghiep-so-luong-it/">https://phukiendienthoaigiare.com/product/qua-tang-doanh-nghiep-3-trong-1-gs304-in-logo-doanh-nghiep-so-luong-it/</a>
</div>
</div>
</div>
</div>
<div class="sc_row w-100">
<div class="sc_grey-box">
<div class="sc_box-label">
Performer </div>
<div class="sc_input-group">
<div class="sc_input-label">
Type </div>
<div class="wp-block-structured-content-event__offer_availability">
Performing Group </div>
</div>
<div class="sc_input-group">
<div class="sc_input-label">
Name </div>
<div class="wp-block-structured-content-event__offer_url">
Phụ kiện điện thoại giá rẻ – PMCS TECH </div>
</div>
</div>
<div class="sc_grey-box">
<div class="sc_box-label">
Offer </div>
<div class="sc_row">
<div class="sc_input-group">
<div class="sc_input-label">
Availability </div>
<div class="wp-block-structured-content-event__offer_availability">
In Stock </div>
</div>
<div class="sc_input-group">
<div class="sc_input-label">
Ticket Website </div>
<div class="wp-block-structured-content-event__offer_url">
<a href="https://phukiendienthoaigiare.com/product/qua-tang-doanh-nghiep-3-trong-1-gs304-in-logo-doanh-nghiep-so-luong-it/">https://phukiendienthoaigiare.com/product/qua-tang-doanh-nghiep-3-trong-1-gs304-in-logo-doanh-nghiep-so-luong-it/</a>
</div>
</div>
</div>
<div class="sc_row">
<div class="sc_input-group">
<div class="sc_input-label">
Currency ISO Code </div>
<div class="wp-block-structured-content-event__currency">
VND </div>
</div>
<div class="sc_input-group">
<div class="sc_input-label">
Price </div>
<div class="wp-block-structured-content-event__price">
385.000,00 </div>
</div>
</div>
<div class="sc_input-group">
<div class="sc_input-label">
Valid From </div>
<div class="wp-block-structured-content-event__valid_from">
01/12/2021 11:04 Chiều </div>
</div>
</div>
</div>
</section>
<script type="application/ld+json">
{
"@context": "https://schema.org",
"@type": "Event",
"organizer": { "@type": "Organization", "name": "PHỤ KIỆN ĐIỆN THOẠI GIÁ RẺ", "url": "https://phukiendienthoaigiare.com" },
"eventStatus": "https://schema.org/EventScheduled",
"eventAttendanceMode": "https://schema.org/OnlineEventAttendanceMode",
"name": "Tìm đại lý phân phối - Quà Tặng Doanh Nghiệp 3 Trong 1 GS304 – In Logo Doanh Nghiệp Số Lượng Ít",
"startDate": "2021-12-01T23:05:00+07:00",
"endDate": "2050-12-01T23:05:00+07:00",
"location":
{
"@type": "VirtualLocation",
"url": "https://phukiendienthoaigiare.com/product/qua-tang-doanh-nghiep-3-trong-1-gs304-in-logo-doanh-nghiep-so-luong-it/"
}
,
"image" : ["https://phukiendienthoaigiare.com/wp-content/uploads/2021/12/Cung-Dap-Hop-Qua-Tang-Doanh-Nghiep-3-Trong-1-GS304-De-Xem-Ben-Trong-Co-Gi-Ngon-11.jpg"],
"offers": {
"@type": "Offer",
"url": "https://phukiendienthoaigiare.com/product/qua-tang-doanh-nghiep-3-trong-1-gs304-in-logo-doanh-nghiep-so-luong-it/",
"price": "385000.00",
"priceCurrency": "VND",
"availability": "https://schema.org/InStock",
"validFrom": "2021-12-01T23:04:00+07:00"
},
"performer": {
"@type": "PerformingGroup",
"name": "Phụ kiện điện thoại giá rẻ - PMCS TECH"
},
"description": "Bộ quà tặng Doanh Nghiệp 3 trong 1 GS304<br>Pin Sạc dự phòng 3000mAh<br>Củ sạc nhanh 2A<br>Móc dán điện thoại in logo Doanh Nghiệp<br>Nhập Khẩu Bảo hành chính hãng<br>Chứng nhận an toàn : CE/FCC/RoHS<br>Chứng nhận xuất xứ hàng hóa: CO<br>Phù hợp làm quà tặng Doanh Nghiệp, Quà tặng nhân viên, Quà khuyến mãi…<br>Customized Branding Logo (MOQ=10pcs)<br>"
}
</script>
<div style="height:100px" aria-hidden="true" class="wp-block-spacer"></div>
<h2 id="h-xem-them-1">Xem thêm:</h2>
<ul class="wp-block-yoast-seo-related-links"><li><a href="https://phukiendienthoaigiare.com/loa-bluetooth-qua-tang-doanh-nghiep-sp001/">Loa Bluetooth Quà Tặng Doanh Nghiệp SP001</a></li><li><a href="https://phukiendienthoaigiare.com/product/loa-bluetooth-qua-tang-doanh-nghiep-sp001-logo-led-phat-sang/">Loa Bluetooth Quà Tặng Doanh Nghiệp SP001 Logo LED Phát Sáng</a></li><li><a href="https://phukiendienthoaigiare.com/product/qua-tang-doanh-nghiep-loa-bluetooth-mini-sp004-logo-led-phat-sang/">Quà Tặng Doanh Nghiệp Loa Bluetooth Mini SP004 – Logo LED Phát Sáng</a></li><li><a href="https://phukiendienthoaigiare.com/product/qua-tang-doanh-nghiep-cao-cap-hop-qua-tang-3in1-gs303/">Quà Tặng Doanh Nghiệp Cao Cấp Hộp Quà Tặng 3in1 GS303</a></li><li><a href="https://phukiendienthoaigiare.com/product/top-sale-pin-sac-du-phong-5000mah-pb0503-logo-cty-phat-sang/">Sạc Dự Phòng 5000mAh PB0503 – Logo Phát Sáng Khi Sử Dụng</a></li></ul>
<div style="height:100px" aria-hidden="true" class="wp-block-spacer"></div>
<h2 id="h-bai-viết-mới-1">Bài viết mới</h2>
<ul class="is-grid columns-2 wp-block-rss"><li class='wp-block-rss__item'><div class='wp-block-rss__item-title'><a href='https://phukiendienthoaigiare.com/pin-sac-du-phong-10000mah-pb1002-co-tot-khong/'>Pin Sạc Dự Phòng 10000mAh PB1002 Có Tốt Không?</a></div><div class="wp-block-rss__item-excerpt">Pin sạc dự phòng PB1002 với dung lượng 10000mAh cho thời gian sạc vô cùng nhanh chóng với QC4.0 PD20W. Với củ sạc này, phụ kiện có thể cung cấp thêm 5 – 6 giờ sử dụng khi chỉ cần sạc được 5 phút và 50% thời gian dùng nếu […]</div></li><li class='wp-block-rss__item'><div class='wp-block-rss__item-title'><a href='https://phukiendienthoaigiare.com/review-dong-ho-bao-thuc-kiem-sac-khong-day-15w-wct001-tinh-nang-uu-nhuoc-diem/'>[Review] Đồng Hồ Báo Thức Kiêm Sạc Không Dây 15W WCT001: Tính Năng, Ưu Nhược Điểm</a></div><div class="wp-block-rss__item-excerpt">Đồng hồ báo thức kiêm sạc không dây 15W mã WCT001 có thể dùng như một vật trang trí trên kệ sách, bàn làm việc hoặc làm quà tặng cho bạn bè, người thân. Với kiểu dáng sang trọng cùng tính đa nhiệm, thiết bị còn thích hợp để phát […]</div></li><li class='wp-block-rss__item'><div class='wp-block-rss__item-title'><a href='https://phukiendienthoaigiare.com/review-pin-sac-du-phong-10000mah-sac-nhanh-qc3-0-pb1006-uu-nhuoc-diem-va-gia-ca/'>Review Pin Sạc Dự Phòng 10000mAh Sạc Nhanh QC3.0 PB1006: Ưu – Nhược Điểm Và Giá Cả</a></div><div class="wp-block-rss__item-excerpt">Với kiểu dáng thanh lịch, sang trọng và trang nhã cùng thiết kế nhỏ gọn, lại là sản phẩm hợp với thời đại công nghệ nên Pin sạc dự phòng PB1006 rất thích hợp dùng làm quà tặng cho các đối tác, khách hàng thân thiết của các chủ doanh […]</div></li><li class='wp-block-rss__item'><div class='wp-block-rss__item-title'><a href='https://phukiendienthoaigiare.com/review-pin-sac-du-phong-10000mah-tich-hop-sac-khong-day-pb1007-logo-phat-sang-khi-su-dung/'>Review Pin Sạc Dự Phòng 10000mAh Tích Hợp Sạc Không Dây Pb1007 – Logo Phát Sáng Khi Sử Dụng</a></div><div class="wp-block-rss__item-excerpt">Khoảng ¾ diện tích pin sạc PB1007 được phủ chất liệu vải linen – loại vải có khả năng thấm hút mồ hôi, chịu nhiệt tốt và có độ bóng mượt rất đẹp. Chính vì vậy, dù được bao phủ bởi chất liệu là vải nhưng pin sạc dự phòng […]</div></li></ul>
<h2 id="h-sản-phẩm-mới-1">Sản phẩm mới</h2>
<ul class="is-grid columns-2 wp-block-rss"><li class='wp-block-rss__item'><div class='wp-block-rss__item-title'><a href='https://phukiendienthoaigiare.com/product/haofa-skeleton-automatic-tourbillon-1901-1-double-spring-watch/'>HAOFA SKELETON AUTOMATIC TOURBILLON 1901-1 DOUBLE SPRING WATCH</a></div><div class="wp-block-rss__item-excerpt">THÔNG SỐ CHUNG： Case diameter: 51.5mmx44mm Case thickness: 16.5mm Movement: E.3H41Automatic Movement Vibration frequency: 28800 (times/hour) Drive: double spring drive Winding method: automatic winding Gem Bearings: 26 Bezel material: carbon fiber Case Material : Titanium-magnesium alloy Strap material: rubber Waterproof depth: 30m life waterproof Mirror back cover: artificial sapphire CÁC […]</div></li><li class='wp-block-rss__item'><div class='wp-block-rss__item-title'><a href='https://phukiendienthoaigiare.com/product/pin-sac-du-phong-10000mah-recci-rpb-p09-sac-nhanh-22-5w-chuan-pd-qc3-0/'>Pin Sạc Dự Phòng 10000mAh Recci RPB-P09 Sạc Nhanh 22.5W Chuẩn PD , QC3.0</a></div><div class="wp-block-rss__item-excerpt">Pin sạc dự phòng 10000mAh Recci RPB_P09 Sạc Nhanh 22.5W Chuẩn PD , QC3.0 Cho Điện Thoại Và Máy Tính Bảng Thiết kế sang trọng, nhỏ gọn và mạnh mẽ với 2 màu đen, trắng thời trang Đèn LED hiển thị dung lượng pin, mỗi vạch tương ứng 25% dung […]</div></li><li class='wp-block-rss__item'><div class='wp-block-rss__item-title'><a href='https://phukiendienthoaigiare.com/product/pin-sac-du-phong-khong-day-10000-mah-pd-qc3-0-recci-ten-series/'>Pin Sạc Dự Phòng Không Dây 10000 mAh PD QC3.0 Recci Ten Series</a></div><div class="wp-block-rss__item-excerpt">Pin Sạc Dự Phòng Không Dây Recci Ten Series 10000 mAh Sạc Nhanh PD QC3.0 Tích hợp Sạc Không Dây Qi 10W Tương thích nhiều thiết bị Thiết kế sang trọng, nhỏ gọn và mạnh mẽ với 2 màu đen, trắng thời trang Đèn LED hiển thị dung lượng pin, […]</div></li><li class='wp-block-rss__item'><div class='wp-block-rss__item-title'><a href='https://phukiendienthoaigiare.com/product/pin-sac-du-phong-polymer-10000mah-type-c-18w-pd-qc3-0-recci-p01/'>Pin Sạc Dự Phòng Polymer 10000mAh Type C 18W PD QC3.0 Recci P01</a></div><div class="wp-block-rss__item-excerpt">Pin Sạc Dự Phòng Polymer 10.000 mAh Recci P01 SẠC NHANH TRONG NHÁY MẮT Thiết kế sang trọng, nhỏ gọn , vỏ nhôm cứng cáp với 2 màu đen, xanh thời trang Tích hợp công nghệ sạc thông minh Power Delivery sạc nhanh 2 chiều 18 W. Hỗ trợ 2 […]</div></li></ul><p>The post <a rel="nofollow" href="https://phukiendienthoaigiare.com/cung-dap-hop-qua-tang-doanh-nghiep-3-trong-1-gs304-de-xem-ben-trong-co-gi-ngon/">Cùng “Đập Hộp” Quà Tặng Doanh Nghiệp 3 Trong 1 GS304 Để Xem Bên Trong Có Gì “Ngon”</a> appeared first on <a rel="nofollow" href="https://phukiendienthoaigiare.com">Phụ kiện điện thoại</a>.</p> | non_priority | cùng “đập hộp” quà tặng doanh nghiệp trong để xem bên trong có gì “ngon” bài viết này không phải là bài review lại càng không phải là bài pr sản phẩm mình viết bài này chủ yếu để “đập hộp” xem thử bên trong món quà tặng doanh nghiệp trong này có gì để những ai có nhu cầu có thể tham khảo thôi nhé những ai làm chủ doanh nghiệp hoặc giữ một chức vụ quan trọng trong công ty mỗi năm vào những dịp quan trọng sẽ có một vài món quà nho nhỏ gửi tặng đến đối tác khách hàng thay cho lời tri ân và cảm ơn họ đã đồng hành cùng công ty đây cũng là cách khá phổ biến để giữ mối quan hệ cả hai thêm bền vững có thể hợp tác lâu dài và cùng nhau hướng đến thành công trong từng dự án vì vậy những món quà tặng bao giờ cũng cần phải hợp thời đại hữu ích và được thiết kế sang trọng nhất có thể vì thế quà tặng doanh nghiệp trong đã được ra đời với sứ mệnh vô cùng cao cả trở thành món quà kết nối giữa các đối tác công ty – khách hàng lại với nhau và lẽ dĩ nhiên những gì thuộc gói quà tặng này đều vô cùng hữu ích đối với hầu hết các đối tượng trong xã hội cùng xem bên trong món quà tặng này có gì nhé “đập hộp” quà tặng doanh nghiệp trong khi đập hộp xong thì mình nhận thấy bên trong quà tặng doanh nghiệp bao gồm pin sạc dự phòng củ sạc nhanh móc dán điện thoại cáp sạc usb hướng dẫn sử dụng cả món quà trên đều là những quà tặng công nghệ vô cùng hữu dụng và hợp với thời đại công nghệ hiện nay lại đặc biệt phù hợp với hầu hết đối tượng trong xã hội trừ các bé thiếu nhi vì vậy xét trên phương diện hợp thời đại thì đây là hộp quà tặng vô cùng rất đáng để cho các doanh nghiệp lưu tâm bây giờ hãy xem xét chi tiết các món quà như thế nào nhé bên trong chiếc hộp quà tặng doanh nghiệp trong bao gồm pin sạc dự phòng củ sạc nhanh và móc dán điện thoạ i về pin sạc dự phòng pin sạc dự phòng trong hộp quà có dung lượng khoảng – tức phụ kiện có thể cung cấp dòng điện trong giờ đồng hồ như vậy những ai sử dụng điện thoại có dung lượng pin khoảng – thì có thể sử dụng phụ kiện này và sạc được pin thích hợp dùng trong những lúc smartphone cạn kiệt năng lượng và cần nạp thêm pin để tiếp tục công việc pin sạc dự phòng với đầy đủ các chức năng đánh giá ưu nhược điểm ưu điểm hỗ trợ nạp pin trong trường hợp khẩn cấp tương thích với hầu hết thiết bị điện tử trên thị trường có tính năng bảo vệ quá nhiệt quá tải và tự động ngắt nguồn điện khi sạc đầy thiết kế nhỏ gọn sang trọng dễ dàng mang theo mọi lúc mọi nơi chất liệu nhựa abs an toàn bền bỉ không thấm nước có đèn led thông báo tình trạng sạc pin nhược điểm chỉ sạc được hơn pin thời gian chờ sạc đầy pin lâu hơn so với các dòng phụ kiện có dung lượng pin lớn củ sạc nhanh đây là phụ kiện khá phổ biến trên thị trường phụ kiện điện thoại hiện nay sản phẩm có thể sạc nhanh hơn so với các củ sạc thông thường cụ thể là sạc điện thoại trong vòng – giờ đồng hồ với tính năng sạc nhanh này củ sạc vô cùng thích hợp đối với những ai thường xuyên bận rộn với công việc củ sạc nhanh tiêu chuẩn đánh giá củ sạc nhanh tương thích với hầu hết thiết bị điện tử trên thị trường cho thời gian sạc nhanh phù hợp với đối tác khách hàng của doanh nghiệp trong các dự án dễ dàng mang theo và sử dụng mọi lúc mọi nơi móc dán điện thoại dù không phải là món quà tặng hợp với thời đại công nghệ số như hai món quà trên trong bộ quà tặng doanh nghiệp nhưng chiếc móc dán điện thoại lại có thể được dùng để in logo doanh nghiệp tạo hiệu ứng và quảng bá thương hiệu đến với người khác với cách làm này doanh nghiệp sẽ có thể tìm kiếm khách hàng mục tiêu đồng thời tăng khả năng nhận diện thương hiệu mà không mất quá nhiều chi phí cho công cuộc marketing ngoài ra đi kèm cùng món quà tặng trên là một cáp sạc đa năng với cổng kết nối lightning cổng usb và cổng microusb thích hợp sử dụng cho nhiều thiết bị điện tử khác nhau cáp sạc đa năng trong phù hợp để sạc với hầu hết thiết bị điện tử hiện nay có nên chọn quà tặng doanh nghiệp trong trước khi đưa ra quyết định các doanh nghiệp có thể xem xét đến các yếu tố sau về xu hướng cả món quà tặng đều có liên quan đến công nghệ hợp với xu hướng thị trường và thời đại công nghệ lại phù hợp với hầu hết các đối tượng và dễ dàng mang theo bên mình về “mặt tiền” món quà tặng doanh nghiệp đều được đặt trong một chiếc hộp vô cùng sang trọng bên trong hộp được lót một tấm mica lót vải nhung tạo sự trang trọng cho hộp quà và phù hợp với tính chất của doanh nghiệp về sự hữu dụng khác với các dòng sản phẩm đơn lẻ mà mình thường review trước đó bộ quà tặng doanh nghiệp trong là sự kết hợp của thiết bị công nghệ vô cùng cần thiết với người dùng tạo nên sự đa dạng và phong phủ của món quà về chất lượng cả món quà trong hộp quà tặng doanh nghiệp đều đạt được các chứng nhận sau ce chứng nhận về chất lượng của sản phẩm fcc chứng nhận đảm bảo về mặt chất lượng của các thiết bị điện tử mà không bị nhiễu động quá mức được cấp bởi ủy bang truyền thông liên bang hoa kỳ rohs chứng nhận về hạn chế các chất cháy nổ trong các thiết bị điện tử co chứng nhận xuất xứ nguồn gốc hàng hóa của một quốc gia lãnh thổ và được cấp bởi cơ quan có thẩm quyền về giá trị kinh tế hộp quà tặng doanh nghiệp trong có giá thành không quá cao so với các bộ quà tặng doanh nghiệp khác giúp các cá nhân doanh nghiệp tiết kiệm chi phí mà vẫn có thể quảng bá thương hiệu đến với mọi người quà tặng doanh nghiệp trong chính là món quà tặng công nghệ hợp thời và cực kỳ tiện ích kết nhìn chung theo mình thì hộp quà tặng doanh nghiệp trong là một món quà mang cả ý nghĩa về vật chất lẫn tinh thần của doanh nghiệp với đối tác khách hàng bên cạnh đó đây còn là một phương pháp marketing ít tốn kém nhất mà mang lại hiệu quả cao cho doanh nghiệp nếu đứng trên cương vị là người tặng mình sẽ lựa chọn ngay hộp quà này bởi giá trị mang lại khá nhiều mà không mất nhiều chi phí còn nếu đứng trên cương vị khách hàng mình sẽ rất vui khi nhận được món quà hợp thời đại và hữu ích thậm chí còn đánh giá cao khả năng bắt kịp xu hướng và “đọc” tâm lý người khác ngoài món quà tặng doanh nghiệp trong này ra doanh nghiệp cũng có thể lựa chọn những món quà tặng riêng lẻ như pin sạc dự phòng kiêm sạc không dây đèn bàn tích hợp sạc thông minh và đồng hồ thông minh đồng hồ kiêm sạc không dây … để làm quà cho đối tác khách hàng tuy nhiên việc lựa chọn những sản phẩm mình vừa kể trên sẽ khá tốn chi phí so với tặng quà theo gift set như thế này đấy quà tặng khuyến mãi in logo thương hiệu số lượng ít nbsp ₫ trên dựa trên đánh giá quà tặng doanh nghiệp in logo thương hiệu nbsp ₫ trên dựa trên đánh giá quà tặng doanh nghiệp – in logo doanh thương hiệu số lượng ít nbsp ₫ trên dựa trên đánh giá quà tặng doanh nghiệp trong – in logo doanh nghiệp số lượng ít nbsp ₫ trên dựa trên đánh giá combo quà tặng phụ kiện cao cấp cho iphone series nbsp ₫ trên dựa trên đánh giá quà tặng công nghệ trong cao cấp nbsp ₫ trên dựa trên đánh giá quà tặng doanh nghiệp in hộp quà tết nbsp ₫ trên dựa trên đánh giá quà tặng công nghệ in hộp quà tết nbsp ₫ trên dựa trên đánh giá hộp quà tặng công nghệ trong nbsp ₫ trên dựa trên đánh giá quà tặng công nghệ cao cấp gift box nbsp ₫ trên dựa trên đánh giá set quà tặng phụ kiện công nghệ cho xe ô tô nbsp ₫ trên dựa trên đánh giá quà tặng doanh nghiệp cao cấp hộp quà tặng nbsp ₫ trên dựa trên đánh giá set quà tặng công nghệ cao cấp nbsp ₫ trên dựa trên đánh giá hộp quà tăng công nghệ cao cấp trong nbsp ₫ trên dựa trên đánh giá sạc không dây magsafe battery pack nbsp ₫ trên dựa trên đánh giá sạc không dây magsafe charger chuẩn qi cho iphone nbsp ₫ trên dựa trên đánh giá tìm đại lý phân phối – quà tặng doanh nghiệp trong – in logo doanh nghiệp số lượng ít meta content bộ quà tặng doanh nghiệp trong pin sạc dự phòng củ sạc nhanh móc dán điện thoại in logo doanh nghiệp nhập khẩu bảo hành chính hãng chứng nhận an toàn ce fcc rohs chứng nhận xuất xứ hàng hóa co phù hợp làm quà tặng doanh nghiệp quà tặng nhân viên quà khuyến mãi… customized branding logo moq event meta name tìm đại lý phân phối – quà tặng doanh nghiệp trong – in logo doanh nghiệp số lượng ít event status scheduled start date chiều end date chiều event location attendance mode online url a target blank href performer type performing group name phụ kiện điện thoại giá rẻ – pmcs tech offer availability in stock ticket website a href currency iso code vnd price valid from chiều context type event organizer type organization name phụ kiện điện thoại giá rẻ url eventstatus eventattendancemode name tìm đại lý phân phối quà tặng doanh nghiệp trong – in logo doanh nghiệp số lượng ít startdate enddate location type virtuallocation url image offers type offer url price pricecurrency vnd availability validfrom performer type performinggroup name phụ kiện điện thoại giá rẻ pmcs tech description bộ quà tặng doanh nghiệp trong pin sạc dự phòng củ sạc nhanh móc dán điện thoại in logo doanh nghiệp nhập khẩu bảo hành chính hãng chứng nhận an toàn ce fcc rohs chứng nhận xuất xứ hàng hóa co phù hợp làm quà tặng doanh nghiệp quà tặng nhân viên quà khuyến mãi… customized branding logo moq xem thêm bài viết mới pin sạc dự phòng với dung lượng cho thời gian sạc vô cùng nhanh chóng với với củ sạc này phụ kiện có thể cung cấp thêm – giờ sử dụng khi chỉ cần sạc được phút và thời gian dùng nếu đồng hồ báo thức kiêm sạc không dây mã có thể dùng như một vật trang trí trên kệ sách bàn làm việc hoặc làm quà tặng cho bạn bè người thân với kiểu dáng sang trọng cùng tính đa nhiệm thiết bị còn thích hợp để phát với kiểu dáng thanh lịch sang trọng và trang nhã cùng thiết kế nhỏ gọn lại là sản phẩm hợp với thời đại công nghệ nên pin sạc dự phòng rất thích hợp dùng làm quà tặng cho các đối tác khách hàng thân thiết của các chủ doanh khoảng ¾ diện tích pin sạc được phủ chất liệu vải linen – loại vải có khả năng thấm hút mồ hôi chịu nhiệt tốt và có độ bóng mượt rất đẹp chính vì vậy dù được bao phủ bởi chất liệu là vải nhưng pin sạc dự phòng sản phẩm mới thông số chung： case diameter case thickness movement e movement vibration frequency times hour drive double spring drive winding method automatic winding gem bearings bezel material carbon fiber case material titanium magnesium alloy strap material rubber waterproof depth life waterproof mirror back cover artificial sapphire các pin sạc dự phòng recci rpb sạc nhanh chuẩn pd cho điện thoại và máy tính bảng thiết kế sang trọng nhỏ gọn và mạnh mẽ với màu đen trắng thời trang đèn led hiển thị dung lượng pin mỗi vạch tương ứng dung pin sạc dự phòng không dây recci ten series mah sạc nhanh pd tích hợp sạc không dây qi tương thích nhiều thiết bị thiết kế sang trọng nhỏ gọn và mạnh mẽ với màu đen trắng thời trang đèn led hiển thị dung lượng pin pin sạc dự phòng polymer mah recci sạc nhanh trong nháy mắt thiết kế sang trọng nhỏ gọn vỏ nhôm cứng cáp với màu đen xanh thời trang tích hợp công nghệ sạc thông minh power delivery sạc nhanh chiều w hỗ trợ the post appeared first on | 0 |
398,662 | 11,742,138,812 | IssuesEvent | 2020-03-11 23:44:25 | thaliawww/concrexit | https://api.github.com/repos/thaliawww/concrexit | closed | Event dates are missing from plaintext newsletter | bug newsletter priority: medium | In GitLab by @se-bastiaan on May 22, 2017, 16:18
### One-sentence description
Event dates are missing from plaintext newsletter
### Current behaviour
All places where a date should be in the text there is nothing.
### Expected behaviour
There should be dates
### Steps to reproduce
1. Send and receive a newsletter
2. Look at the plaintext version | 1.0 | Event dates are missing from plaintext newsletter - In GitLab by @se-bastiaan on May 22, 2017, 16:18
### One-sentence description
Event dates are missing from plaintext newsletter
### Current behaviour
All places where a date should be in the text there is nothing.
### Expected behaviour
There should be dates
### Steps to reproduce
1. Send and receive a newsletter
2. Look at the plaintext version | priority | event dates are missing from plaintext newsletter in gitlab by se bastiaan on may one sentence description event dates are missing from plaintext newsletter current behaviour all places where a date should be in the text there is nothing expected behaviour there should be dates steps to reproduce send and receive a newsletter look at the plaintext version | 1 |
11,633 | 2,660,009,988 | IssuesEvent | 2015-03-19 01:32:34 | perfsonar/mesh-config | https://api.github.com/repos/perfsonar/mesh-config | opened | mesh config "http get" doesn't retry with all resolved addresses | Milestone-Release3.5 Priority-Medium Type-Defect | _From @arlake228 on March 14, 2015 12:41_
Original [issue 1013](https://code.google.com/p/perfsonar-ps/issues/detail?id=1013) created by arlake228 on 2014-11-04T13:31:00.000Z:
If a DNS name resolves to v4 and v6 addresses but v6 is either disabled on the client or unavailable on the server, the mesh config https_get routine, using IO::Socket::INET6 under the hood, will try the v6 address and fail, even though the v4 address is accessible. There is a MultiHomed flag that you can add to the IO::Socket::* modules, but when we did that, it went into an unhelpful infinite loop with the module version available in RedHat 6. There are a few options to fix this:
1) Find a better Perl module, that's available in RedHat 6 or EPEL6, and rewrite the https_get routine using it
2) Have the https_get routine do the address resolving, and iterate through the addresses itself
3) Package a newer version of the IO::Socket::INET6 module
I'm partial to # 1 if there's something we can use, but barring that, # 2 seems the way to go. I'd imagine # 3 would just lead to all sorts of pain.
_Copied from original issue: perfsonar/project#1011_ | 1.0 | mesh config "http get" doesn't retry with all resolved addresses - _From @arlake228 on March 14, 2015 12:41_
Original [issue 1013](https://code.google.com/p/perfsonar-ps/issues/detail?id=1013) created by arlake228 on 2014-11-04T13:31:00.000Z:
If a DNS name resolves to v4 and v6 addresses but v6 is either disabled on the client or unavailable on the server, the mesh config https_get routine, using IO::Socket::INET6 under the hood, will try the v6 address and fail, even though the v4 address is accessible. There is a MultiHomed flag that you can add to the IO::Socket::* modules, but when we did that, it went into an unhelpful infinite loop with the module version available in RedHat 6. There are a few options to fix this:
1) Find a better Perl module, that's available in RedHat 6 or EPEL6, and rewrite the https_get routine using it
2) Have the https_get routine do the address resolving, and iterate through the addresses itself
3) Package a newer version of the IO::Socket::INET6 module
I'm partial to # 1 if there's something we can use, but barring that, # 2 seems the way to go. I'd imagine # 3 would just lead to all sorts of pain.
_Copied from original issue: perfsonar/project#1011_ | non_priority | mesh config http get doesn t retry with all resolved addresses from on march original created by on if a dns name resolves to and addresses but is either disabled on the client or unavailable on the server the mesh config https get routine using io socket under the hood will try the address and fail even though the address is accessible there is a multihomed flag that you can add to the io socket modules but when we did that it went into an unhelpful infinite loop with the module version available in redhat there are a few options to fix this find a better perl module that s available in redhat or and rewrite the https get routine using it have the https get routine do the address resolving and iterate through the addresses itself package a newer version of the io socket module i m partial to nbsp if there s something we can use but barring that nbsp seems the way to go i d imagine nbsp would just lead to all sorts of pain copied from original issue perfsonar project | 0 |
75,540 | 3,466,209,898 | IssuesEvent | 2015-12-22 01:27:36 | Itseez/opencv | https://api.github.com/repos/Itseez/opencv | closed | Release openCV 3 with bitcode enabled for iOS9 | affected: 2.4 affected: master bug category: ios priority: normal | OpenCV 3.0 wasn't build with enabled bitcode flag. Please make a build with this flag enabled. | 1.0 | Release openCV 3 with bitcode enabled for iOS9 - OpenCV 3.0 wasn't build with enabled bitcode flag. Please make a build with this flag enabled. | priority | release opencv with bitcode enabled for opencv wasn t build with enabled bitcode flag please make a build with this flag enabled | 1 |
87,507 | 15,779,916,193 | IssuesEvent | 2021-04-01 09:17:51 | AlexRogalskiy/gradle-java-sample | https://api.github.com/repos/AlexRogalskiy/gradle-java-sample | opened | CVE-2021-21343 (High) detected in xstream-1.4.10.jar | security vulnerability | ## CVE-2021-21343 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>xstream-1.4.10.jar</b></p></summary>
<p>XStream is a serialization library from Java objects to XML and back.</p>
<p>Library home page: <a href="http://x-stream.github.io">http://x-stream.github.io</a></p>
<p>Path to dependency file: gradle-java-sample/buildSrc/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.thoughtworks.xstream/xstream/1.4.10/dfecae23647abc9d9fd0416629a4213a3882b101/xstream-1.4.10.jar</p>
<p>
Dependency Hierarchy:
- gradle-versions-plugin-0.28.0.jar (Root Library)
- :x: **xstream-1.4.10.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/AlexRogalskiy/gradle-java-sample/commit/faab29c6da2c042014b345fb42b18ed6d5648688">faab29c6da2c042014b345fb42b18ed6d5648688</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 Java library to serialize objects to XML and back again. In XStream before version 1.4.16, there is a vulnerability where the processed stream at unmarshalling time contains type information to recreate the formerly written objects. XStream creates therefore new instances based on these type information. An attacker can manipulate the processed input stream and replace or inject objects, that result in the deletion of a file on the local host. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types. If you rely on XStream's default blacklist of the Security Framework, you will have to use at least version 1.4.16.
<p>Publish Date: 2021-03-23
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-21343>CVE-2021-21343</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/x-stream/xstream/security/advisories/GHSA-74cv-f58x-f9wf">https://github.com/x-stream/xstream/security/advisories/GHSA-74cv-f58x-f9wf</a></p>
<p>Release Date: 2021-03-23</p>
<p>Fix Resolution: com.thoughtworks.xstream:xstream:1.4.16</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2021-21343 (High) detected in xstream-1.4.10.jar - ## CVE-2021-21343 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>xstream-1.4.10.jar</b></p></summary>
<p>XStream is a serialization library from Java objects to XML and back.</p>
<p>Library home page: <a href="http://x-stream.github.io">http://x-stream.github.io</a></p>
<p>Path to dependency file: gradle-java-sample/buildSrc/build.gradle</p>
<p>Path to vulnerable library: /home/wss-scanner/.gradle/caches/modules-2/files-2.1/com.thoughtworks.xstream/xstream/1.4.10/dfecae23647abc9d9fd0416629a4213a3882b101/xstream-1.4.10.jar</p>
<p>
Dependency Hierarchy:
- gradle-versions-plugin-0.28.0.jar (Root Library)
- :x: **xstream-1.4.10.jar** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/AlexRogalskiy/gradle-java-sample/commit/faab29c6da2c042014b345fb42b18ed6d5648688">faab29c6da2c042014b345fb42b18ed6d5648688</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 Java library to serialize objects to XML and back again. In XStream before version 1.4.16, there is a vulnerability where the processed stream at unmarshalling time contains type information to recreate the formerly written objects. XStream creates therefore new instances based on these type information. An attacker can manipulate the processed input stream and replace or inject objects, that result in the deletion of a file on the local host. No user is affected, who followed the recommendation to setup XStream's security framework with a whitelist limited to the minimal required types. If you rely on XStream's default blacklist of the Security Framework, you will have to use at least version 1.4.16.
<p>Publish Date: 2021-03-23
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2021-21343>CVE-2021-21343</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/x-stream/xstream/security/advisories/GHSA-74cv-f58x-f9wf">https://github.com/x-stream/xstream/security/advisories/GHSA-74cv-f58x-f9wf</a></p>
<p>Release Date: 2021-03-23</p>
<p>Fix Resolution: com.thoughtworks.xstream:xstream:1.4.16</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in xstream jar cve high severity vulnerability vulnerable library xstream jar xstream is a serialization library from java objects to xml and back library home page a href path to dependency file gradle java sample buildsrc build gradle path to vulnerable library home wss scanner gradle caches modules files com thoughtworks xstream xstream xstream jar dependency hierarchy gradle versions plugin jar root library x xstream jar vulnerable library found in head commit a href vulnerability details xstream is a java library to serialize objects to xml and back again in xstream before version there is a vulnerability where the processed stream at unmarshalling time contains type information to recreate the formerly written objects xstream creates therefore new instances based on these type information an attacker can manipulate the processed input stream and replace or inject objects that result in the deletion of a file on the local host no user is affected who followed the recommendation to setup xstream s security framework with a whitelist limited to the minimal required types if you rely on xstream s default blacklist of the security framework you will have to use at least version 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 com thoughtworks xstream xstream step up your open source security game with whitesource | 0 |
15,723 | 10,340,593,563 | IssuesEvent | 2019-09-03 22:30:18 | microsoft/BotFramework-Services | https://api.github.com/repos/microsoft/BotFramework-Services | closed | MSTeams: Carousel Card not displaying recently. | Bot Services bug customer-replied-to customer-reported | Version: SDK V3 Bot Framework
Deployment : Azure
Language : C#
Adpative card Verison : 1.0
Bot Builder Version : 3.15.3
Bot Connector Version : 3.15.3 or tried even 3.20.*
Channel: MSTeams
we developed a bot which takes some input, according to it displays 9 adaptive cards in carousel format.
this was working till day before yesterday. the bot was showing carousel cards in teams channel without any errors but suddenly from today i am facing an error just when bot reply in attachment the carousel card.
The main exception which it gives is :
Exception: Microsoft.Bot.Connector.ErrorResponseException: Operation returned an invalid status code 'BadRequest
Traced in local with ngrok
`Exception: Microsoft.Bot.Connector.ErrorResponseException: Operation returned an invalid status code 'BadRequest'
at Microsoft.Bot.Connector.Conversations.d__10.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Bot.Connector.ConversationsExtensions.d__11.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Bot.Builder.Dialogs.Internals.AlwaysSendDirect_BotToUser.d__4.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Bot.Builder.Dialogs.Internals.InputHintQueue.d__4.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Bot.Builder.Dialogs.Internals.AutoInputHint_BotToUser.d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Bot.Builder.Dialogs.Internals.MapToChannelData_BotToUser.d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Bot.Builder.Dialogs.Internals.LogBotToUser.d__4.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Bot.Builder.Dialogs.Internals.DialogContext.d__12.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.GetResult()`
| 1.0 | MSTeams: Carousel Card not displaying recently. - Version: SDK V3 Bot Framework
Deployment : Azure
Language : C#
Adpative card Verison : 1.0
Bot Builder Version : 3.15.3
Bot Connector Version : 3.15.3 or tried even 3.20.*
Channel: MSTeams
we developed a bot which takes some input, according to it displays 9 adaptive cards in carousel format.
this was working till day before yesterday. the bot was showing carousel cards in teams channel without any errors but suddenly from today i am facing an error just when bot reply in attachment the carousel card.
The main exception which it gives is :
Exception: Microsoft.Bot.Connector.ErrorResponseException: Operation returned an invalid status code 'BadRequest
Traced in local with ngrok
`Exception: Microsoft.Bot.Connector.ErrorResponseException: Operation returned an invalid status code 'BadRequest'
at Microsoft.Bot.Connector.Conversations.d__10.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Bot.Connector.ConversationsExtensions.d__11.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Bot.Builder.Dialogs.Internals.AlwaysSendDirect_BotToUser.d__4.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Bot.Builder.Dialogs.Internals.InputHintQueue.d__4.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Bot.Builder.Dialogs.Internals.AutoInputHint_BotToUser.d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Bot.Builder.Dialogs.Internals.MapToChannelData_BotToUser.d__3.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Bot.Builder.Dialogs.Internals.LogBotToUser.d__4.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.Bot.Builder.Dialogs.Internals.DialogContext.d__12.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.GetResult()`
| non_priority | msteams carousel card not displaying recently version sdk bot framework deployment azure language c adpative card verison bot builder version bot connector version or tried even channel msteams we developed a bot which takes some input according to it displays adaptive cards in carousel format this was working till day before yesterday the bot was showing carousel cards in teams channel without any errors but suddenly from today i am facing an error just when bot reply in attachment the carousel card the main exception which it gives is exception microsoft bot connector errorresponseexception operation returned an invalid status code badrequest traced in local with ngrok exception microsoft bot connector errorresponseexception operation returned an invalid status code badrequest at microsoft bot connector conversations d movenext end of stack trace from previous location where exception was thrown at system runtime compilerservices taskawaiter throwfornonsuccess task task at system runtime compilerservices taskawaiter handlenonsuccessanddebuggernotification task task at microsoft bot connector conversationsextensions d movenext end of stack trace from previous location where exception was thrown at system runtime compilerservices taskawaiter throwfornonsuccess task task at system runtime compilerservices taskawaiter handlenonsuccessanddebuggernotification task task at microsoft bot builder dialogs internals alwayssenddirect bottouser d movenext end of stack trace from previous location where exception was thrown at system runtime compilerservices taskawaiter throwfornonsuccess task task at system runtime compilerservices taskawaiter handlenonsuccessanddebuggernotification task task at microsoft bot builder dialogs internals inputhintqueue d movenext end of stack trace from previous location where exception was thrown at system runtime compilerservices taskawaiter throwfornonsuccess task task at system runtime compilerservices taskawaiter handlenonsuccessanddebuggernotification task task at microsoft bot builder dialogs internals autoinputhint bottouser d movenext end of stack trace from previous location where exception was thrown at system runtime compilerservices taskawaiter throwfornonsuccess task task at system runtime compilerservices taskawaiter handlenonsuccessanddebuggernotification task task at microsoft bot builder dialogs internals maptochanneldata bottouser d movenext end of stack trace from previous location where exception was thrown at system runtime compilerservices taskawaiter throwfornonsuccess task task at system runtime compilerservices taskawaiter handlenonsuccessanddebuggernotification task task at microsoft bot builder dialogs internals logbottouser d movenext end of stack trace from previous location where exception was thrown at system runtime compilerservices taskawaiter throwfornonsuccess task task at system runtime compilerservices taskawaiter handlenonsuccessanddebuggernotification task task at microsoft bot builder dialogs internals dialogcontext d movenext end of stack trace from previous location where exception was thrown at system runtime compilerservices taskawaiter throwfornonsuccess task task at system runtime compilerservices taskawaiter handlenonsuccessanddebuggernotification task task at system runtime compilerservices taskawaiter getresult | 0 |
359,936 | 10,682,610,761 | IssuesEvent | 2019-10-22 06:06:20 | data2health/website | https://api.github.com/repos/data2health/website | closed | Add additional tools to Tools for CTSAs page | high priority (easy fix) tools for CTSAs page | https://ctsa.ncats.nih.gov/cd2h/tools-for-ctsas/
comment from [google doc](https://docs.google.com/document/d/1rQ1_hzY4HilH2D9tPRFJvz8n--VZrxOU9gn2EjnsPDk/edit):
Was this list crowdsourced? It seems like there are some missing tools. This would be a great opportunity for the CD2H team/our hubs to weigh in.
MH- yes this was my suggestion too. I think when we advertise the new site and on the site itself, it should say “your tool here” or somesuch.
SB: Yes, this was the plan. “Add your tool here” button will be added to site soon. Initial list was generated at the IT Infrastructure strategy meeting in late October.
| 1.0 | Add additional tools to Tools for CTSAs page - https://ctsa.ncats.nih.gov/cd2h/tools-for-ctsas/
comment from [google doc](https://docs.google.com/document/d/1rQ1_hzY4HilH2D9tPRFJvz8n--VZrxOU9gn2EjnsPDk/edit):
Was this list crowdsourced? It seems like there are some missing tools. This would be a great opportunity for the CD2H team/our hubs to weigh in.
MH- yes this was my suggestion too. I think when we advertise the new site and on the site itself, it should say “your tool here” or somesuch.
SB: Yes, this was the plan. “Add your tool here” button will be added to site soon. Initial list was generated at the IT Infrastructure strategy meeting in late October.
| priority | add additional tools to tools for ctsas page comment from was this list crowdsourced it seems like there are some missing tools this would be a great opportunity for the team our hubs to weigh in mh yes this was my suggestion too i think when we advertise the new site and on the site itself it should say “your tool here” or somesuch sb yes this was the plan “add your tool here” button will be added to site soon initial list was generated at the it infrastructure strategy meeting in late october | 1 |
235,976 | 19,476,923,207 | IssuesEvent | 2021-12-24 14:29:52 | tarantool/cartridge | https://api.github.com/repos/tarantool/cartridge | closed | flaky test: unit.tar.test_errors | bug teamS flaky test | From time to time the `unit.tar.test_errors` test fails. See the test run log below.
```
$ .rocks/bin/luatest -v -b
compatibility.cartridge_upgrade.test_upgrade ... (0.000s) skip
.../tarantool/test/compatibility/cartridge_upgrade_test.lua:61: No older version provided. Skipping
compatibility.config.test_failover_2_0_1_78 ... (0.470s) Ok
compatibility.config.test_failover_2_0_1_95 ... (0.318s) Ok
hotreload.forbidden.test_errors ... (0.000s) Ok
hotreload.myrole.test_events ... (0.020s) Ok
hotreload.myrole.test_errors ... (0.034s) Ok
hotreload.myrole.test_roledeps ... (0.031s) Ok
hotreload.myrole.test_rpc ... (0.033s) Ok
hotreload.myrole.test_netbox ... (0.035s) Ok
hotreload.myrole.test_routes ... (0.170s) Ok
hotreload.myrole.test_globals ... (0.035s) Ok
hotreload.myrole.test_fibers ... (0.035s) Ok
hotreload.myrole.test_console ... (0.016s) Ok
hotreload.vshard.test_router ... (0.236s) Ok
hotreload.vshard.test_storage ... (0.347s) Ok
hotreload.vshard.test_rebalancer ... (0.609s) Ok
integration.admin.test_api ... (0.010s) Ok
integration.admin.test_login ... (0.010s) Ok
integration.advertise_change.test_issues ... (0.026s) Ok
integration.advertise_change.test_topology_query ... (0.003s) Ok
integration.advertise_change.test_suggestion ... (0.003s) Ok
integration.advertise_change.test_2pc ... (0.263s) Ok
integration.advertise_change.test_failover ... (0.033s) Ok
integration.api_edit.test_edit_server ... (0.249s) Ok
integration.api_edit.test_edit_replicaset ... (0.090s) Ok
integration.api_edit.test_all_rw_false ... (0.035s) Ok
integration.api_edit.test_all_rw_true ... (0.108s) Ok
integration.api_join.test_join_server ... (0.379s) Ok
integration.api_query.test_self ... (0.726s) Ok
integration.api_query.test_suggestions ... (0.003s) Ok
integration.api_query.test_custom_http_endpoint ... (0.003s) Ok
integration.api_query.test_server_stat_schema ... (0.006s) Ok
integration.api_query.test_server_info_schema ... (0.008s) Ok
integration.api_query.test_replication_info_schema ... (0.006s) Ok
integration.api_query.test_servers ... (0.006s) Ok
integration.api_query.test_replicasets ... (0.003s) Ok
integration.api_query.test_probe_server ... (0.270s) Ok
integration.api_query.test_clock_delta ... (0.002s) Ok
integration.api_query.test_topology_caching ... (0.004s) Ok
integration.api_query.test_operation_error ... (0.345s) Ok
integration.api_query.test_webui_blacklist ... (0.004s) Ok
integration.api_query.test_app_name ... (0.315s) Ok
integration.api_query.test_membership_leave ... (0.002s) Ok
integration.api_query.test_issues ... (0.007s) Ok
integration.api_query.test_stop_roles_on_shutdown ... (0.001s) Ok
integration.api_uninitialized.test_uninitialized ... (0.216s) Ok
integration.api_uninitialized.test_membership_options ... (0.000s) Ok
integration.api_uninitialized.test_rpc ... (0.001s) Ok
integration.api_uninitialized.test_issues ... (0.001s) Ok
integration.auth.test_login_master_auth_enabled ... (0.083s) Ok
integration.auth.test_login_master_auth_disabled ... (0.056s) Ok
integration.auth.test_login_replica_auth_enabled ... (0.077s) Ok
integration.auth.test_login_replica_auth_disabled ... (0.049s) Ok
integration.auth.test_empty_list ... (0.016s) Ok
integration.auth.test_auth_disabled ... (0.083s) Ok
integration.auth.test_auth_enabled ... (0.024s) Ok
integration.auth.test_uninitialized ... (0.011s) Ok
integration.auth.test_keepalive ... (0.025s) Ok
integration.auth.test_basic_auth ... (0.029s) Ok
integration.auth.test_set_params_graphql ... (0.089s) Ok
integration.auth.test_cookie_renew ... (0.027s) Ok
integration.auth.test_cookie_expiry ... (0.043s) Ok
integration.auth.test_invalidate_cookie_on_password_change ... (0.042s) Ok
integration.auth.test_admin_disabled ... (0.324s) Ok
integration.bootstrap.test_cookie_change ... (4.208s) Ok
integration.bootstrap.test_workdir_collision ... (0.798s) Ok
integration.clock_delta.test_clock_delta ... (0.015s) Ok
integration.config.test_upload_good ... (0.056s) Ok
integration.config.test_upload_fail ... (0.019s) Ok
integration.config.test_validate ... (0.033s) Ok
integration.config.test_rollback ... (0.011s) Ok
integration.config.test_formatting ... (0.018s) Ok
integration.config.test_on_patch_trigger ... (0.014s) Ok
integration.config.test_patch_clusterwide ... (0.064s) Ok
integration.console_sock.test_console_sock ... (0.001s) Ok
integration.cookie_change.test_cluster_restart ... (2.906s) Ok
integration.cookie_change.test_server_restart ... (2.106s) Ok
integration.ddl.test_luaapi ... (0.034s) Ok
integration.ddl.test_formatting_preserved ... (0.014s) Ok
integration.ddl.test_replicas ... (0.009s) Ok
integration.ddl.test_graphql_errors ... (0.043s) Ok
integration.ddl.test_space_removal ... (0.025s) Ok
integration.ddl.test_example_schema ... (0.025s) Ok
integration.ddl.test_no_instances_to_check_schema ... (0.004s) Ok
integration.disable.test_api_disable ... (0.997s) Ok
integration.disable.test_suggestion ... (1.001s) Ok
integration.etcd2_client.test_locks ... (1.070s) Ok
integration.etcd2_client.test_appointments ... (1.056s) Ok
integration.etcd2_client.test_longpolling ... (1.258s) Ok
integration.etcd2_client.test_event_cleared ... (3.768s) Ok
integration.etcd2_client.test_client_drop_session ... (1.057s) Ok
integration.etcd2_client.test_outage ... (1.271s) Ok
integration.etcd2_client.test_client_session ... (1.056s) Ok
integration.etcd2_client.test_authentication ... (1.830s) Ok
integration.etcd2_client.test_vclockkeeper ... (1.066s) Ok
integration.etcd2_client.test_quorum ... (5.059s) Ok
integration.expel.test_api ... (0.003s) Ok
integration.failover_eventual.test_api_master ... (0.078s) Ok
integration.failover_eventual.test_api_failover ... (2.277s) Ok
integration.failover_eventual.test_switchover ... (0.081s) Ok
integration.failover_eventual.test_sigkill ... (0.675s) Ok
integration.failover_eventual.test_all_rw_failover ... (0.846s) Ok
integration.failover_eventual.test_sigstop ... (10.153s) Ok
integration.failover_stateful.etcd2.test_state_provider_restart ... (2.187s) Ok
integration.failover_stateful.etcd2.test_coordinator_restart ... (0.108s) Ok
integration.failover_stateful.etcd2.test_leader_restart ... (1.488s) Ok
integration.failover_stateful.etcd2.test_leader_promote ... (3.163s) Ok
integration.failover_stateful.etcd2.test_leaderless ... (2.675s) Ok
integration.failover_stateful.etcd2.test_issues ... (1.064s) Ok
integration.failover_stateful.etcd2.test_force_promote_timeout ... (2.025s) Ok
integration.failover_stateful.stateboard.test_state_provider_restart ... (1.039s) Ok
integration.failover_stateful.stateboard.test_coordinator_restart ... (0.209s) Ok
integration.failover_stateful.stateboard.test_leader_restart ... (1.493s) Ok
integration.failover_stateful.stateboard.test_leader_promote ... (2.815s) Ok
integration.failover_stateful.stateboard.test_leaderless ... (5.380s) Ok
integration.failover_stateful.stateboard.test_issues ... (1.054s) Ok
integration.failover_stateful.stateboard.test_force_promote_timeout ... (2.028s) Ok
integration.feedback.test_feedback ... (0.000s) Ok
integration.feedback.test_rocks ... (0.000s) Ok
integration.fencing.etcd2.test_basics ... (1.600s) Ok
integration.fencing.stateboard.test_basics ... (1.992s) Ok
integration.force_reapply.test_twophase_config_locked ... (0.037s) Ok
integration.force_reapply.test_graphql_api ... (0.021s) Ok
integration.force_reapply.test_suggestions ... (0.322s) Ok
integration.graphql.test_simple ... (0.002s) Ok
integration.graphql.test_errors_in_handlers ... (0.010s) Ok
integration.graphql.test_reread_request ... (0.001s) Ok
integration.graphql.test_unknown_query_mutation ... (0.002s) Ok
integration.graphql.test_error_extensions ... (0.003s) Ok
integration.graphql.test_middleware ... (0.011s) Ok
integration.hidden_roles.test_graphql_known_roles ... (0.002s) Ok
integration.hidden_roles.test_rpc ... (0.010s) Ok
integration.hidden_roles.test_config_enable_none ... (0.008s) Ok
integration.hidden_roles.test_config_enable_myrole ... (0.007s) Ok
integration.hidden_roles.test_config_enable_hidden ... (0.007s) Ok
integration.hidden_roles.test_config_enable_permanent ... (0.009s) Ok
integration.hidden_roles.test_graphql_enable_none ... (0.018s) Ok
integration.hidden_roles.test_graphql_enable_myrole ... (0.012s) Ok
integration.hidden_roles.test_graphql_enable_hidden ... (0.013s) Ok
integration.hidden_roles.test_graphql_enable_permanent ... (0.012s) Ok
integration.issues.test_issues_limits ... (0.010s) Ok
integration.issues.test_broken_replica ... (0.135s) Ok
integration.issues.test_replication_idle ... (4.008s) Ok
integration.issues.test_config_mismatch ... (0.007s) Ok
integration.issues.test_twophase_config_locked ... (0.227s) Ok
integration.issues.test_state_hangs ... (1.034s) Ok
integration.issues.test_aliens ... (0.315s) Ok
integration.issues.test_custom_issues ... (0.020s) Ok
integration.join_synchronous.test_call ... (0.093s) Ok
integration.labels.test_servers_labels ... (0.016s) Ok
integration.labels.test_replicaset_labels ... (0.002s) Ok
integration.logger.test_cfg ... (0.310s) Ok
integration.logger.test_content_unconfigured ... (0.358s) Ok
integration.logger.test_content_bootstrapped ... (0.350s) Ok
integration.master_restart.test_master_restart_with_missing_xlog ... (2.798s) Ok
integration.multiboot.test_bootstrap ... (2.383s) Ok
integration.multijoin_create.test_patch_topology ... (1.369s) Ok
integration.multijoin_existing.test_patch_topology ... (1.172s) Ok
integration.multisharding_api.test_query ... (0.001s) Ok
integration.multisharding_api.test_mutations ... (0.011s) Ok
integration.multisharding_one.test_api ... (0.004s) Ok
integration.multisharding_one.test_router_role ... (0.001s) Ok
integration.multisharding_one.test_set_vshard_options_positive ... (0.029s) Ok
integration.multisharding_one.test_set_vshard_options_negative ... (0.009s) Ok
integration.multisharding_two.test_api ... (0.021s) Ok
integration.multisharding_two.test_mutations ... (0.007s) Ok
integration.multisharding_two.test_router_role ... (0.001s) Ok
integration.multisharding_two.test_set_vshard_options_positive ... (0.056s) Ok
integration.myrole.test_api ... (0.002s) Ok
integration.myrole.test_myrole ... (0.029s) Ok
integration.myrole.test_dependencies ... (0.013s) Ok
integration.myrole.test_rename ... (0.338s) Ok
integration.pool_connect.test_identity ... (0.029s) Ok
integration.pool_connect.test_errors ... (0.014s) Ok
integration.pool_connect.test_async_call_not_yeilds ... (0.014s) Ok
integration.pool_connect.test_async_call_wait_result_err ... (0.000s) Ok
integration.pool_connect.test_async_call_remote ... (0.001s) Ok
integration.pool_map_call.test_timeout ... (1.002s) Ok
integration.pool_map_call.test_parallel ... (0.002s) Ok
integration.pool_map_call.test_fiber_storage ... (0.001s) Ok
integration.pool_map_call.test_errors ... (0.000s) Ok
integration.pool_map_call.test_negative ... (0.002s) Ok
integration.pool_map_call.test_errors_united ... (0.002s) Ok
integration.pool_map_call.test_positive ... (0.000s) Ok
integration.pool_map_call.test_futures ... (1.001s) Ok
integration.proxy.test_alive_destination ... (0.823s) Ok
integration.proxy.test_dead_destination ... (0.773s) Ok
integration.proxy.test_issues ... (0.772s) Ok
integration.rebalancing.test ... (0.898s) Ok
integration.reboot.test_oldstyle_config ... (0.774s) Ok
integration.reboot.test_absent_config ... (0.770s) Ok
integration.reboot.test_absent_snapshot ... (0.760s) Ok
integration.reboot.test_invalid_config ... (0.763s) Ok
integration.reboot.test_advertise_change ... (0.760s) Ok
integration.rejoin.test_rebootstrap ... (4.057s) Ok
integration.rejoin.test_rejoin_slave ... (3.398s) Ok
integration.rejoin.test_rejoin_master ... (3.116s) Ok
integration.replicaset_alias.test_rename_replicaset ... (0.015s) Ok
integration.restart_replication.test_suggestion ... (2.237s) Ok
integration.restart_replication.test_errors ... (0.327s) Ok
integration.rpc.test_api ... (0.010s) Ok
integration.rpc.test_errors ... (0.003s) Ok
integration.rpc.test_routing ... (0.011s) Ok
integration.rpc.test_push ... (0.001s) Ok
integration.slow_requests.test_boxinfo ... (1.005s) Ok
integration.slow_requests.test_stat ... (1.005s) Ok
integration.slow_requests.test_issues ... (1.005s) Ok
integration.slow_requests.test_suggestions ... (1.009s) Ok
integration.slow_requests.test_netbox_timeouts ... (1.004s) Ok
integration.state_machine.test_failover ... (3.760s) Ok
integration.state_machine.test_confapplier_race ... (3.313s) Ok
integration.state_machine.test_leader_death ... (3.020s) Ok
integration.state_machine.test_blinking_slow ... (3.815s) Ok
integration.state_machine.test_blinking_fast ... (3.805s) Ok
integration.state_machine.test_fiber_cancel ... (3.010s) Ok
integration.state_machine.test_leader_recovery ... (3.424s) Ok
integration.state_machine.test_orphan_connect_timeout ... (5.351s) Ok
integration.state_machine.test_quorum_one ... (3.241s) Ok
integration.state_machine.test_restart_both ... (4.338s) Ok
integration.state_machine.test_operation_error ... (2.032s) Ok
integration.state_machine.test_prepare_state_error ... (2.804s) Ok
integration.state_machine.test_init_error ... (2.627s) Ok
integration.state_machine.test_boot_error ... (3.125s) Ok
integration.stateboard.test_locks ... (0.451s) Ok
integration.stateboard.test_appointments ... (0.354s) Ok
integration.stateboard.test_longpolling ... (1.660s) Ok
integration.stateboard.test_passwd ... (0.558s) Ok
integration.stateboard.test_outage ... (0.568s) Ok
integration.stateboard.test_client_session ... (0.365s) Ok
integration.stateboard.test_client_drop_session ... (0.366s) Ok
integration.stateboard.test_stateboard_console ... (0.348s) Ok
integration.stateboard.test_box_options ... (0.349s) Ok
integration.stateboard.test_vclockkeeper ... (0.359s) Ok
integration.switchover.etcd2.test_2pc_forceful ... (3.269s) Ok
integration.switchover.etcd2.test_promotion_forceful ... (0.234s) Ok
integration.switchover.etcd2.test_promotion_abortion ... (0.639s) Ok
integration.switchover.etcd2.test_promotion_late ... (0.226s) Ok
integration.switchover.etcd2.test_vclockkeeper_caching ... (0.123s) Ok
integration.switchover.etcd2.test_enabling ... (0.915s) Ok
integration.switchover.etcd2.test_api ... (0.560s) Ok
integration.switchover.etcd2.test_all_rw ... (0.262s) Ok
integration.switchover.etcd2.test_alone_instance ... (0.117s) Ok
integration.switchover.stateboard.test_2pc_forceful ... (3.060s) Ok
integration.switchover.stateboard.test_promotion_forceful ... (0.225s) Ok
integration.switchover.stateboard.test_promotion_abortion ... (0.633s) Ok
integration.switchover.stateboard.test_promotion_late ... (0.219s) Ok
integration.switchover.stateboard.test_vclockkeeper_caching ... (0.017s) Ok
integration.switchover.stateboard.test_enabling ... (0.532s) Ok
integration.switchover.stateboard.test_api ... (0.564s) Ok
integration.switchover.stateboard.test_all_rw ... (0.069s) Ok
integration.switchover.stateboard.test_alone_instance ... (0.117s) Ok
integration.twophase.test_errors ... (0.005s) Ok
integration.twophase.test_success ... (0.006s) Ok
integration.twophase.test_upload_skipped ... (0.002s) Ok
integration.twophase.test_prepare_fails ... (0.003s) Ok
integration.twophase.test_commit_fails ... (0.002s) Ok
integration.twophase.test_abort_fails ... (0.002s) Ok
integration.upload.test_begining_failure ... (2.306s) Ok
integration.upload.test_transmission_failure ... (0.305s) Ok
integration.upload.test_finish_failure ... (0.115s) Ok
integration.vshard_weight.test ... (0.041s) Ok
integration.vshardless.test_edit_replicaset ... (0.004s) Ok
integration.vshardless.test_package_loaded ... (0.000s) Ok
integration.vshardless.test_config ... (0.000s) Ok
integration.vshardless.test_api ... (0.002s) Ok
integration.workdir.test_defaults ... (0.453s) Ok
integration.workdir.test_abspath ... (0.452s) Ok
integration.workdir.test_relpath ... (0.452s) Ok
integration.workdir.test_chdir ... (0.453s) Ok
integration.zones.test_zones ... (0.099s) Ok
integration.zones.test_distances ... (0.048s) Ok
integration.zones.test_validation ... (0.028s) Ok
integration.zones.helpers.test_zones_distances ... (0.001s) Ok
unit.argparse.test_sections ... (0.371s) Ok
unit.argparse.test_priority ... (0.367s) Ok
unit.argparse.test_overrides ... (0.219s) Ok
unit.argparse.test_appname ... (0.065s) Ok
unit.argparse.test_confdir ... (0.098s) Ok
unit.argparse.test_badfile ... (0.150s) Ok
unit.argparse.test_box_opts ... (0.276s) Ok
unit.cartridge_failover.test_empty_state ... (0.125s) Ok
unit.cartridge_failover.test_unconfigured_state ... (0.187s) Ok
unit.cfg_errors.test_workdir ... (0.173s) Ok
unit.cfg_errors.test_advertise_uri ... (0.209s) Ok
unit.cfg_errors.test_http ... (0.192s) Ok
unit.cfg_errors.test_issues_limits ... (0.178s) Ok
unit.cfg_errors.test_roles ... (0.186s) Ok
unit.cfg_errors.test_custom_auth_backend ... (0.211s) Ok
unit.cfg_errors.test_default_auth_backend ... (0.174s) Ok
unit.cfg_errors.test_console_sock_enobufs ... (0.176s) Ok
unit.cfg_errors.test_console_sock_enoent ... (0.178s) Ok
unit.cfg_errors.test_dns_resolve_timeout ... (0.792s) Ok
unit.cfg_errors.test_positive ... (0.192s) Ok
unit.cfg_errors.test_webui_prefix ... (0.194s) Ok
unit.cluster_cookie.test_set_cookie ... (0.000s) Ok
unit.clusterwide_config.test_newstyle_ok ... (0.004s) Ok
unit.clusterwide_config.test_newstyle_err ... (0.003s) Ok
unit.clusterwide_config.test_oldstyle_ok ... (0.002s) Ok
unit.clusterwide_config.test_oldstyle_err ... (0.003s) Ok
unit.clusterwide_config.test_preserving_plaintext ... (0.001s) Ok
unit.clusterwide_config.test_delete_plaintext_key ... (0.001s) Ok
unit.clusterwide_config.test_create_err ... (0.001s) Ok
unit.clusterwide_config.test_get_readonly_ok ... (0.001s) Ok
unit.clusterwide_config.test_get_readonly_err ... (0.001s) Ok
unit.clusterwide_config.test_immutability ... (0.000s) Ok
unit.clusterwide_config.test_get_deepcopy_modify ... (0.001s) Ok
unit.clusterwide_config.test_save_empty_config ... (0.003s) Ok
unit.clusterwide_config.test_save_err ... (0.009s) Ok
unit.clusterwide_config.test_save_ok ... (0.003s) Ok
unit.clusterwide_config.test_checksum ... (0.001s) Ok
unit.helpers.test_cluster_bootstrap ... (0.000s) Ok
unit.helpers.test_config_management ... (0.051s) Ok
unit.helpers.test_servers_access ... (0.001s) Ok
unit.helpers.test_replicaset_uuid_generation ... (0.001s) Ok
unit.helpers.test_failover ... (0.001s) Ok
unit.helpers.test_new_with_servers_count ... (0.002s) Ok
unit.helpers.test_new_without_replicaset_and_server_alias ... (0.000s) Ok
unit.helpers.test_new_with_env ... (0.001s) Ok
unit.helpers.test_errno ... (0.000s) Ok
unit.issues_limits.test_positive ... (0.000s) Ok
unit.issues_limits.test_negative ... (0.001s) Ok
unit.labels.test_labels_ok ... (0.000s) Ok
unit.labels.test_labels_error ... (0.001s) Ok
unit.remote_control.test_start ... (0.063s) Ok
unit.remote_control.test_peer_uuid ... (0.009s) Ok
unit.remote_control.test_fiber_name ... (0.009s) Ok
unit.remote_control.test_drop_connections ... (0.016s) Ok
unit.remote_control.test_late_accept ... (0.209s) Ok
unit.remote_control.test_auth ... (0.005s) Ok
unit.remote_control.test_ping ... (0.006s) Ok
unit.remote_control.test_bytestream ... (0.006s) Ok
unit.remote_control.test_invalid_serialization ... (0.006s) Ok
unit.remote_control.test_large_payload ... (1.169s) Ok
unit.remote_control.test_async ... (0.006s) Ok
unit.remote_control.test_bad_username ... (0.006s) Ok
unit.remote_control.test_bad_password ... (0.006s) Ok
unit.remote_control.test_guest ... (0.008s) Ok
unit.remote_control.test_call ... (0.017s) Ok
unit.remote_control.test_eval ... (0.015s) Ok
unit.remote_control.test_timeout ... (0.412s) Ok
unit.remote_control.test_switch_box_to_rc ... (0.008s) Ok
unit.remote_control.test_switch_rc_to_box ... (0.008s) Ok
unit.remote_control.test_reconnect ... (0.513s) Ok
unit.remote_control.test_socket_gc ... (0.357s) Ok
unit.remote_control.test_fd_cloexec ... (0.250s) Ok
unit.roledeps.test_unknown ... (0.004s) Ok
unit.roledeps.test_error ... (0.001s) Ok
unit.roledeps.test_name_clash ... (0.000s) Ok
unit.roledeps.test_format ... (0.001s) Ok
unit.roledeps.test_circular_deps ... (0.001s) Ok
unit.roledeps.test_full_deps ... (0.008s) Ok
unit.roledeps.test_enabled_roles ... (0.001s) Ok
unit.rpc_candidates.test_all ... (0.134s) Ok
unit.tar.test_fixtures_pack ... (0.079s) Ok
unit.tar.test_fixtures_unpack ... (0.043s) Ok
unit.tar.test_truncated ... (0.001s) Ok
unit.tar.test_errors ... (0.000s) fail
...e/runner/work/tarantool/tarantool/test/unit/tar_test.lua:219: expected: nil, actual: {}
unit.topology.test_single_group ... (0.011s) Ok
unit.topology.test_multi_group ... (0.010s) Ok
unit.topology_leaders.test_leader_order ... (0.001s) Ok
unit.upload.test_begin ... (0.005s) Ok
unit.upload.test_transmit ... (0.003s) Ok
unit.upload.test_finish ... (0.004s) Ok
unit.upload.test_cleanup ... (0.004s) Ok
unit.upload.test_upload ... (0.002s) Ok
unit.utils.test_upvalues ... (0.000s) Ok
unit.utils.test_randomize_path ... (0.000s) Ok
unit.vshard_config.test_all ... (0.126s) Ok
unit.wait_lsn.test_zero_timeout ... (0.025s) Ok
unit.wait_lsn.test_timings ... (0.404s) Ok
unit.wait_lsn.test_absent_lsn ... (0.000s) Ok
upgrade.tarantool_upgrade.test_upgrade ... (0.009s) Ok
2021-11-03 19:44:25.657 [4383] main I> tx_binary: stopped
=========================================================
Failed tests:
-------------
1) unit.tar.test_errors
...e/runner/work/tarantool/tarantool/test/unit/tar_test.lua:219: expected: nil, actual: {}
stack traceback:
...ntool/tarantool/.rocks/share/tarantool/luatest/utils.lua:53: in function 'luatest_error'
.../tarantool/.rocks/share/tarantool/luatest/assertions.lua:61: in function 'failure'
.../tarantool/.rocks/share/tarantool/luatest/assertions.lua:181: in function 'assert_equals'
...e/runner/work/tarantool/tarantool/test/unit/tar_test.lua:219: in function 'unit.tar.test_errors'
...tool/tarantool/.rocks/share/tarantool/luatest/runner.lua:344: in function <...tool/tarantool/.rocks/share/tarantool/luatest/runner.lua:343>
[C]: in function 'xpcall'
...tool/tarantool/.rocks/share/tarantool/luatest/runner.lua:343: in function 'super'
...l/tarantool/.rocks/share/tarantool/luatest/capturing.lua:106: in function 'protected_call'
...tool/tarantool/.rocks/share/tarantool/luatest/runner.lua:420: in function 'super'
...
[C]: in function 'xpcall'
...ntool/tarantool/.rocks/share/tarantool/luatest/utils.lua:37: in function 'run_tests'
...tool/tarantool/.rocks/share/tarantool/luatest/runner.lua:258: in function <...tool/tarantool/.rocks/share/tarantool/luatest/runner.lua:254>
[C]: in function 'xpcall'
...l/tarantool/.rocks/share/tarantool/luatest/capturing.lua:74: in function <...l/tarantool/.rocks/share/tarantool/luatest/capturing.lua:72>
[C]: in function 'xpcall'
...tool/tarantool/.rocks/share/tarantool/luatest/runner.lua:50: in function 'fn'
...tool/.rocks/share/tarantool/luatest/sandboxed_runner.lua:14: in function 'run'
...antool/.rocks/share/tarantool/luatest/cli_entrypoint.lua:4: in function <...antool/.rocks/share/tarantool/luatest/cli_entrypoint.lua:3>
....rocks/share/tarantool/rocks/luatest/0.5.6-1/bin/luatest:3: in main chunk
Ran 371 tests in 303.206 seconds, 370 successes, 1 fail, 1 skipped
=========================================================
Failed tests:
unit.tar.test_errors
``` | 1.0 | flaky test: unit.tar.test_errors - From time to time the `unit.tar.test_errors` test fails. See the test run log below.
```
$ .rocks/bin/luatest -v -b
compatibility.cartridge_upgrade.test_upgrade ... (0.000s) skip
.../tarantool/test/compatibility/cartridge_upgrade_test.lua:61: No older version provided. Skipping
compatibility.config.test_failover_2_0_1_78 ... (0.470s) Ok
compatibility.config.test_failover_2_0_1_95 ... (0.318s) Ok
hotreload.forbidden.test_errors ... (0.000s) Ok
hotreload.myrole.test_events ... (0.020s) Ok
hotreload.myrole.test_errors ... (0.034s) Ok
hotreload.myrole.test_roledeps ... (0.031s) Ok
hotreload.myrole.test_rpc ... (0.033s) Ok
hotreload.myrole.test_netbox ... (0.035s) Ok
hotreload.myrole.test_routes ... (0.170s) Ok
hotreload.myrole.test_globals ... (0.035s) Ok
hotreload.myrole.test_fibers ... (0.035s) Ok
hotreload.myrole.test_console ... (0.016s) Ok
hotreload.vshard.test_router ... (0.236s) Ok
hotreload.vshard.test_storage ... (0.347s) Ok
hotreload.vshard.test_rebalancer ... (0.609s) Ok
integration.admin.test_api ... (0.010s) Ok
integration.admin.test_login ... (0.010s) Ok
integration.advertise_change.test_issues ... (0.026s) Ok
integration.advertise_change.test_topology_query ... (0.003s) Ok
integration.advertise_change.test_suggestion ... (0.003s) Ok
integration.advertise_change.test_2pc ... (0.263s) Ok
integration.advertise_change.test_failover ... (0.033s) Ok
integration.api_edit.test_edit_server ... (0.249s) Ok
integration.api_edit.test_edit_replicaset ... (0.090s) Ok
integration.api_edit.test_all_rw_false ... (0.035s) Ok
integration.api_edit.test_all_rw_true ... (0.108s) Ok
integration.api_join.test_join_server ... (0.379s) Ok
integration.api_query.test_self ... (0.726s) Ok
integration.api_query.test_suggestions ... (0.003s) Ok
integration.api_query.test_custom_http_endpoint ... (0.003s) Ok
integration.api_query.test_server_stat_schema ... (0.006s) Ok
integration.api_query.test_server_info_schema ... (0.008s) Ok
integration.api_query.test_replication_info_schema ... (0.006s) Ok
integration.api_query.test_servers ... (0.006s) Ok
integration.api_query.test_replicasets ... (0.003s) Ok
integration.api_query.test_probe_server ... (0.270s) Ok
integration.api_query.test_clock_delta ... (0.002s) Ok
integration.api_query.test_topology_caching ... (0.004s) Ok
integration.api_query.test_operation_error ... (0.345s) Ok
integration.api_query.test_webui_blacklist ... (0.004s) Ok
integration.api_query.test_app_name ... (0.315s) Ok
integration.api_query.test_membership_leave ... (0.002s) Ok
integration.api_query.test_issues ... (0.007s) Ok
integration.api_query.test_stop_roles_on_shutdown ... (0.001s) Ok
integration.api_uninitialized.test_uninitialized ... (0.216s) Ok
integration.api_uninitialized.test_membership_options ... (0.000s) Ok
integration.api_uninitialized.test_rpc ... (0.001s) Ok
integration.api_uninitialized.test_issues ... (0.001s) Ok
integration.auth.test_login_master_auth_enabled ... (0.083s) Ok
integration.auth.test_login_master_auth_disabled ... (0.056s) Ok
integration.auth.test_login_replica_auth_enabled ... (0.077s) Ok
integration.auth.test_login_replica_auth_disabled ... (0.049s) Ok
integration.auth.test_empty_list ... (0.016s) Ok
integration.auth.test_auth_disabled ... (0.083s) Ok
integration.auth.test_auth_enabled ... (0.024s) Ok
integration.auth.test_uninitialized ... (0.011s) Ok
integration.auth.test_keepalive ... (0.025s) Ok
integration.auth.test_basic_auth ... (0.029s) Ok
integration.auth.test_set_params_graphql ... (0.089s) Ok
integration.auth.test_cookie_renew ... (0.027s) Ok
integration.auth.test_cookie_expiry ... (0.043s) Ok
integration.auth.test_invalidate_cookie_on_password_change ... (0.042s) Ok
integration.auth.test_admin_disabled ... (0.324s) Ok
integration.bootstrap.test_cookie_change ... (4.208s) Ok
integration.bootstrap.test_workdir_collision ... (0.798s) Ok
integration.clock_delta.test_clock_delta ... (0.015s) Ok
integration.config.test_upload_good ... (0.056s) Ok
integration.config.test_upload_fail ... (0.019s) Ok
integration.config.test_validate ... (0.033s) Ok
integration.config.test_rollback ... (0.011s) Ok
integration.config.test_formatting ... (0.018s) Ok
integration.config.test_on_patch_trigger ... (0.014s) Ok
integration.config.test_patch_clusterwide ... (0.064s) Ok
integration.console_sock.test_console_sock ... (0.001s) Ok
integration.cookie_change.test_cluster_restart ... (2.906s) Ok
integration.cookie_change.test_server_restart ... (2.106s) Ok
integration.ddl.test_luaapi ... (0.034s) Ok
integration.ddl.test_formatting_preserved ... (0.014s) Ok
integration.ddl.test_replicas ... (0.009s) Ok
integration.ddl.test_graphql_errors ... (0.043s) Ok
integration.ddl.test_space_removal ... (0.025s) Ok
integration.ddl.test_example_schema ... (0.025s) Ok
integration.ddl.test_no_instances_to_check_schema ... (0.004s) Ok
integration.disable.test_api_disable ... (0.997s) Ok
integration.disable.test_suggestion ... (1.001s) Ok
integration.etcd2_client.test_locks ... (1.070s) Ok
integration.etcd2_client.test_appointments ... (1.056s) Ok
integration.etcd2_client.test_longpolling ... (1.258s) Ok
integration.etcd2_client.test_event_cleared ... (3.768s) Ok
integration.etcd2_client.test_client_drop_session ... (1.057s) Ok
integration.etcd2_client.test_outage ... (1.271s) Ok
integration.etcd2_client.test_client_session ... (1.056s) Ok
integration.etcd2_client.test_authentication ... (1.830s) Ok
integration.etcd2_client.test_vclockkeeper ... (1.066s) Ok
integration.etcd2_client.test_quorum ... (5.059s) Ok
integration.expel.test_api ... (0.003s) Ok
integration.failover_eventual.test_api_master ... (0.078s) Ok
integration.failover_eventual.test_api_failover ... (2.277s) Ok
integration.failover_eventual.test_switchover ... (0.081s) Ok
integration.failover_eventual.test_sigkill ... (0.675s) Ok
integration.failover_eventual.test_all_rw_failover ... (0.846s) Ok
integration.failover_eventual.test_sigstop ... (10.153s) Ok
integration.failover_stateful.etcd2.test_state_provider_restart ... (2.187s) Ok
integration.failover_stateful.etcd2.test_coordinator_restart ... (0.108s) Ok
integration.failover_stateful.etcd2.test_leader_restart ... (1.488s) Ok
integration.failover_stateful.etcd2.test_leader_promote ... (3.163s) Ok
integration.failover_stateful.etcd2.test_leaderless ... (2.675s) Ok
integration.failover_stateful.etcd2.test_issues ... (1.064s) Ok
integration.failover_stateful.etcd2.test_force_promote_timeout ... (2.025s) Ok
integration.failover_stateful.stateboard.test_state_provider_restart ... (1.039s) Ok
integration.failover_stateful.stateboard.test_coordinator_restart ... (0.209s) Ok
integration.failover_stateful.stateboard.test_leader_restart ... (1.493s) Ok
integration.failover_stateful.stateboard.test_leader_promote ... (2.815s) Ok
integration.failover_stateful.stateboard.test_leaderless ... (5.380s) Ok
integration.failover_stateful.stateboard.test_issues ... (1.054s) Ok
integration.failover_stateful.stateboard.test_force_promote_timeout ... (2.028s) Ok
integration.feedback.test_feedback ... (0.000s) Ok
integration.feedback.test_rocks ... (0.000s) Ok
integration.fencing.etcd2.test_basics ... (1.600s) Ok
integration.fencing.stateboard.test_basics ... (1.992s) Ok
integration.force_reapply.test_twophase_config_locked ... (0.037s) Ok
integration.force_reapply.test_graphql_api ... (0.021s) Ok
integration.force_reapply.test_suggestions ... (0.322s) Ok
integration.graphql.test_simple ... (0.002s) Ok
integration.graphql.test_errors_in_handlers ... (0.010s) Ok
integration.graphql.test_reread_request ... (0.001s) Ok
integration.graphql.test_unknown_query_mutation ... (0.002s) Ok
integration.graphql.test_error_extensions ... (0.003s) Ok
integration.graphql.test_middleware ... (0.011s) Ok
integration.hidden_roles.test_graphql_known_roles ... (0.002s) Ok
integration.hidden_roles.test_rpc ... (0.010s) Ok
integration.hidden_roles.test_config_enable_none ... (0.008s) Ok
integration.hidden_roles.test_config_enable_myrole ... (0.007s) Ok
integration.hidden_roles.test_config_enable_hidden ... (0.007s) Ok
integration.hidden_roles.test_config_enable_permanent ... (0.009s) Ok
integration.hidden_roles.test_graphql_enable_none ... (0.018s) Ok
integration.hidden_roles.test_graphql_enable_myrole ... (0.012s) Ok
integration.hidden_roles.test_graphql_enable_hidden ... (0.013s) Ok
integration.hidden_roles.test_graphql_enable_permanent ... (0.012s) Ok
integration.issues.test_issues_limits ... (0.010s) Ok
integration.issues.test_broken_replica ... (0.135s) Ok
integration.issues.test_replication_idle ... (4.008s) Ok
integration.issues.test_config_mismatch ... (0.007s) Ok
integration.issues.test_twophase_config_locked ... (0.227s) Ok
integration.issues.test_state_hangs ... (1.034s) Ok
integration.issues.test_aliens ... (0.315s) Ok
integration.issues.test_custom_issues ... (0.020s) Ok
integration.join_synchronous.test_call ... (0.093s) Ok
integration.labels.test_servers_labels ... (0.016s) Ok
integration.labels.test_replicaset_labels ... (0.002s) Ok
integration.logger.test_cfg ... (0.310s) Ok
integration.logger.test_content_unconfigured ... (0.358s) Ok
integration.logger.test_content_bootstrapped ... (0.350s) Ok
integration.master_restart.test_master_restart_with_missing_xlog ... (2.798s) Ok
integration.multiboot.test_bootstrap ... (2.383s) Ok
integration.multijoin_create.test_patch_topology ... (1.369s) Ok
integration.multijoin_existing.test_patch_topology ... (1.172s) Ok
integration.multisharding_api.test_query ... (0.001s) Ok
integration.multisharding_api.test_mutations ... (0.011s) Ok
integration.multisharding_one.test_api ... (0.004s) Ok
integration.multisharding_one.test_router_role ... (0.001s) Ok
integration.multisharding_one.test_set_vshard_options_positive ... (0.029s) Ok
integration.multisharding_one.test_set_vshard_options_negative ... (0.009s) Ok
integration.multisharding_two.test_api ... (0.021s) Ok
integration.multisharding_two.test_mutations ... (0.007s) Ok
integration.multisharding_two.test_router_role ... (0.001s) Ok
integration.multisharding_two.test_set_vshard_options_positive ... (0.056s) Ok
integration.myrole.test_api ... (0.002s) Ok
integration.myrole.test_myrole ... (0.029s) Ok
integration.myrole.test_dependencies ... (0.013s) Ok
integration.myrole.test_rename ... (0.338s) Ok
integration.pool_connect.test_identity ... (0.029s) Ok
integration.pool_connect.test_errors ... (0.014s) Ok
integration.pool_connect.test_async_call_not_yeilds ... (0.014s) Ok
integration.pool_connect.test_async_call_wait_result_err ... (0.000s) Ok
integration.pool_connect.test_async_call_remote ... (0.001s) Ok
integration.pool_map_call.test_timeout ... (1.002s) Ok
integration.pool_map_call.test_parallel ... (0.002s) Ok
integration.pool_map_call.test_fiber_storage ... (0.001s) Ok
integration.pool_map_call.test_errors ... (0.000s) Ok
integration.pool_map_call.test_negative ... (0.002s) Ok
integration.pool_map_call.test_errors_united ... (0.002s) Ok
integration.pool_map_call.test_positive ... (0.000s) Ok
integration.pool_map_call.test_futures ... (1.001s) Ok
integration.proxy.test_alive_destination ... (0.823s) Ok
integration.proxy.test_dead_destination ... (0.773s) Ok
integration.proxy.test_issues ... (0.772s) Ok
integration.rebalancing.test ... (0.898s) Ok
integration.reboot.test_oldstyle_config ... (0.774s) Ok
integration.reboot.test_absent_config ... (0.770s) Ok
integration.reboot.test_absent_snapshot ... (0.760s) Ok
integration.reboot.test_invalid_config ... (0.763s) Ok
integration.reboot.test_advertise_change ... (0.760s) Ok
integration.rejoin.test_rebootstrap ... (4.057s) Ok
integration.rejoin.test_rejoin_slave ... (3.398s) Ok
integration.rejoin.test_rejoin_master ... (3.116s) Ok
integration.replicaset_alias.test_rename_replicaset ... (0.015s) Ok
integration.restart_replication.test_suggestion ... (2.237s) Ok
integration.restart_replication.test_errors ... (0.327s) Ok
integration.rpc.test_api ... (0.010s) Ok
integration.rpc.test_errors ... (0.003s) Ok
integration.rpc.test_routing ... (0.011s) Ok
integration.rpc.test_push ... (0.001s) Ok
integration.slow_requests.test_boxinfo ... (1.005s) Ok
integration.slow_requests.test_stat ... (1.005s) Ok
integration.slow_requests.test_issues ... (1.005s) Ok
integration.slow_requests.test_suggestions ... (1.009s) Ok
integration.slow_requests.test_netbox_timeouts ... (1.004s) Ok
integration.state_machine.test_failover ... (3.760s) Ok
integration.state_machine.test_confapplier_race ... (3.313s) Ok
integration.state_machine.test_leader_death ... (3.020s) Ok
integration.state_machine.test_blinking_slow ... (3.815s) Ok
integration.state_machine.test_blinking_fast ... (3.805s) Ok
integration.state_machine.test_fiber_cancel ... (3.010s) Ok
integration.state_machine.test_leader_recovery ... (3.424s) Ok
integration.state_machine.test_orphan_connect_timeout ... (5.351s) Ok
integration.state_machine.test_quorum_one ... (3.241s) Ok
integration.state_machine.test_restart_both ... (4.338s) Ok
integration.state_machine.test_operation_error ... (2.032s) Ok
integration.state_machine.test_prepare_state_error ... (2.804s) Ok
integration.state_machine.test_init_error ... (2.627s) Ok
integration.state_machine.test_boot_error ... (3.125s) Ok
integration.stateboard.test_locks ... (0.451s) Ok
integration.stateboard.test_appointments ... (0.354s) Ok
integration.stateboard.test_longpolling ... (1.660s) Ok
integration.stateboard.test_passwd ... (0.558s) Ok
integration.stateboard.test_outage ... (0.568s) Ok
integration.stateboard.test_client_session ... (0.365s) Ok
integration.stateboard.test_client_drop_session ... (0.366s) Ok
integration.stateboard.test_stateboard_console ... (0.348s) Ok
integration.stateboard.test_box_options ... (0.349s) Ok
integration.stateboard.test_vclockkeeper ... (0.359s) Ok
integration.switchover.etcd2.test_2pc_forceful ... (3.269s) Ok
integration.switchover.etcd2.test_promotion_forceful ... (0.234s) Ok
integration.switchover.etcd2.test_promotion_abortion ... (0.639s) Ok
integration.switchover.etcd2.test_promotion_late ... (0.226s) Ok
integration.switchover.etcd2.test_vclockkeeper_caching ... (0.123s) Ok
integration.switchover.etcd2.test_enabling ... (0.915s) Ok
integration.switchover.etcd2.test_api ... (0.560s) Ok
integration.switchover.etcd2.test_all_rw ... (0.262s) Ok
integration.switchover.etcd2.test_alone_instance ... (0.117s) Ok
integration.switchover.stateboard.test_2pc_forceful ... (3.060s) Ok
integration.switchover.stateboard.test_promotion_forceful ... (0.225s) Ok
integration.switchover.stateboard.test_promotion_abortion ... (0.633s) Ok
integration.switchover.stateboard.test_promotion_late ... (0.219s) Ok
integration.switchover.stateboard.test_vclockkeeper_caching ... (0.017s) Ok
integration.switchover.stateboard.test_enabling ... (0.532s) Ok
integration.switchover.stateboard.test_api ... (0.564s) Ok
integration.switchover.stateboard.test_all_rw ... (0.069s) Ok
integration.switchover.stateboard.test_alone_instance ... (0.117s) Ok
integration.twophase.test_errors ... (0.005s) Ok
integration.twophase.test_success ... (0.006s) Ok
integration.twophase.test_upload_skipped ... (0.002s) Ok
integration.twophase.test_prepare_fails ... (0.003s) Ok
integration.twophase.test_commit_fails ... (0.002s) Ok
integration.twophase.test_abort_fails ... (0.002s) Ok
integration.upload.test_begining_failure ... (2.306s) Ok
integration.upload.test_transmission_failure ... (0.305s) Ok
integration.upload.test_finish_failure ... (0.115s) Ok
integration.vshard_weight.test ... (0.041s) Ok
integration.vshardless.test_edit_replicaset ... (0.004s) Ok
integration.vshardless.test_package_loaded ... (0.000s) Ok
integration.vshardless.test_config ... (0.000s) Ok
integration.vshardless.test_api ... (0.002s) Ok
integration.workdir.test_defaults ... (0.453s) Ok
integration.workdir.test_abspath ... (0.452s) Ok
integration.workdir.test_relpath ... (0.452s) Ok
integration.workdir.test_chdir ... (0.453s) Ok
integration.zones.test_zones ... (0.099s) Ok
integration.zones.test_distances ... (0.048s) Ok
integration.zones.test_validation ... (0.028s) Ok
integration.zones.helpers.test_zones_distances ... (0.001s) Ok
unit.argparse.test_sections ... (0.371s) Ok
unit.argparse.test_priority ... (0.367s) Ok
unit.argparse.test_overrides ... (0.219s) Ok
unit.argparse.test_appname ... (0.065s) Ok
unit.argparse.test_confdir ... (0.098s) Ok
unit.argparse.test_badfile ... (0.150s) Ok
unit.argparse.test_box_opts ... (0.276s) Ok
unit.cartridge_failover.test_empty_state ... (0.125s) Ok
unit.cartridge_failover.test_unconfigured_state ... (0.187s) Ok
unit.cfg_errors.test_workdir ... (0.173s) Ok
unit.cfg_errors.test_advertise_uri ... (0.209s) Ok
unit.cfg_errors.test_http ... (0.192s) Ok
unit.cfg_errors.test_issues_limits ... (0.178s) Ok
unit.cfg_errors.test_roles ... (0.186s) Ok
unit.cfg_errors.test_custom_auth_backend ... (0.211s) Ok
unit.cfg_errors.test_default_auth_backend ... (0.174s) Ok
unit.cfg_errors.test_console_sock_enobufs ... (0.176s) Ok
unit.cfg_errors.test_console_sock_enoent ... (0.178s) Ok
unit.cfg_errors.test_dns_resolve_timeout ... (0.792s) Ok
unit.cfg_errors.test_positive ... (0.192s) Ok
unit.cfg_errors.test_webui_prefix ... (0.194s) Ok
unit.cluster_cookie.test_set_cookie ... (0.000s) Ok
unit.clusterwide_config.test_newstyle_ok ... (0.004s) Ok
unit.clusterwide_config.test_newstyle_err ... (0.003s) Ok
unit.clusterwide_config.test_oldstyle_ok ... (0.002s) Ok
unit.clusterwide_config.test_oldstyle_err ... (0.003s) Ok
unit.clusterwide_config.test_preserving_plaintext ... (0.001s) Ok
unit.clusterwide_config.test_delete_plaintext_key ... (0.001s) Ok
unit.clusterwide_config.test_create_err ... (0.001s) Ok
unit.clusterwide_config.test_get_readonly_ok ... (0.001s) Ok
unit.clusterwide_config.test_get_readonly_err ... (0.001s) Ok
unit.clusterwide_config.test_immutability ... (0.000s) Ok
unit.clusterwide_config.test_get_deepcopy_modify ... (0.001s) Ok
unit.clusterwide_config.test_save_empty_config ... (0.003s) Ok
unit.clusterwide_config.test_save_err ... (0.009s) Ok
unit.clusterwide_config.test_save_ok ... (0.003s) Ok
unit.clusterwide_config.test_checksum ... (0.001s) Ok
unit.helpers.test_cluster_bootstrap ... (0.000s) Ok
unit.helpers.test_config_management ... (0.051s) Ok
unit.helpers.test_servers_access ... (0.001s) Ok
unit.helpers.test_replicaset_uuid_generation ... (0.001s) Ok
unit.helpers.test_failover ... (0.001s) Ok
unit.helpers.test_new_with_servers_count ... (0.002s) Ok
unit.helpers.test_new_without_replicaset_and_server_alias ... (0.000s) Ok
unit.helpers.test_new_with_env ... (0.001s) Ok
unit.helpers.test_errno ... (0.000s) Ok
unit.issues_limits.test_positive ... (0.000s) Ok
unit.issues_limits.test_negative ... (0.001s) Ok
unit.labels.test_labels_ok ... (0.000s) Ok
unit.labels.test_labels_error ... (0.001s) Ok
unit.remote_control.test_start ... (0.063s) Ok
unit.remote_control.test_peer_uuid ... (0.009s) Ok
unit.remote_control.test_fiber_name ... (0.009s) Ok
unit.remote_control.test_drop_connections ... (0.016s) Ok
unit.remote_control.test_late_accept ... (0.209s) Ok
unit.remote_control.test_auth ... (0.005s) Ok
unit.remote_control.test_ping ... (0.006s) Ok
unit.remote_control.test_bytestream ... (0.006s) Ok
unit.remote_control.test_invalid_serialization ... (0.006s) Ok
unit.remote_control.test_large_payload ... (1.169s) Ok
unit.remote_control.test_async ... (0.006s) Ok
unit.remote_control.test_bad_username ... (0.006s) Ok
unit.remote_control.test_bad_password ... (0.006s) Ok
unit.remote_control.test_guest ... (0.008s) Ok
unit.remote_control.test_call ... (0.017s) Ok
unit.remote_control.test_eval ... (0.015s) Ok
unit.remote_control.test_timeout ... (0.412s) Ok
unit.remote_control.test_switch_box_to_rc ... (0.008s) Ok
unit.remote_control.test_switch_rc_to_box ... (0.008s) Ok
unit.remote_control.test_reconnect ... (0.513s) Ok
unit.remote_control.test_socket_gc ... (0.357s) Ok
unit.remote_control.test_fd_cloexec ... (0.250s) Ok
unit.roledeps.test_unknown ... (0.004s) Ok
unit.roledeps.test_error ... (0.001s) Ok
unit.roledeps.test_name_clash ... (0.000s) Ok
unit.roledeps.test_format ... (0.001s) Ok
unit.roledeps.test_circular_deps ... (0.001s) Ok
unit.roledeps.test_full_deps ... (0.008s) Ok
unit.roledeps.test_enabled_roles ... (0.001s) Ok
unit.rpc_candidates.test_all ... (0.134s) Ok
unit.tar.test_fixtures_pack ... (0.079s) Ok
unit.tar.test_fixtures_unpack ... (0.043s) Ok
unit.tar.test_truncated ... (0.001s) Ok
unit.tar.test_errors ... (0.000s) fail
...e/runner/work/tarantool/tarantool/test/unit/tar_test.lua:219: expected: nil, actual: {}
unit.topology.test_single_group ... (0.011s) Ok
unit.topology.test_multi_group ... (0.010s) Ok
unit.topology_leaders.test_leader_order ... (0.001s) Ok
unit.upload.test_begin ... (0.005s) Ok
unit.upload.test_transmit ... (0.003s) Ok
unit.upload.test_finish ... (0.004s) Ok
unit.upload.test_cleanup ... (0.004s) Ok
unit.upload.test_upload ... (0.002s) Ok
unit.utils.test_upvalues ... (0.000s) Ok
unit.utils.test_randomize_path ... (0.000s) Ok
unit.vshard_config.test_all ... (0.126s) Ok
unit.wait_lsn.test_zero_timeout ... (0.025s) Ok
unit.wait_lsn.test_timings ... (0.404s) Ok
unit.wait_lsn.test_absent_lsn ... (0.000s) Ok
upgrade.tarantool_upgrade.test_upgrade ... (0.009s) Ok
2021-11-03 19:44:25.657 [4383] main I> tx_binary: stopped
=========================================================
Failed tests:
-------------
1) unit.tar.test_errors
...e/runner/work/tarantool/tarantool/test/unit/tar_test.lua:219: expected: nil, actual: {}
stack traceback:
...ntool/tarantool/.rocks/share/tarantool/luatest/utils.lua:53: in function 'luatest_error'
.../tarantool/.rocks/share/tarantool/luatest/assertions.lua:61: in function 'failure'
.../tarantool/.rocks/share/tarantool/luatest/assertions.lua:181: in function 'assert_equals'
...e/runner/work/tarantool/tarantool/test/unit/tar_test.lua:219: in function 'unit.tar.test_errors'
...tool/tarantool/.rocks/share/tarantool/luatest/runner.lua:344: in function <...tool/tarantool/.rocks/share/tarantool/luatest/runner.lua:343>
[C]: in function 'xpcall'
...tool/tarantool/.rocks/share/tarantool/luatest/runner.lua:343: in function 'super'
...l/tarantool/.rocks/share/tarantool/luatest/capturing.lua:106: in function 'protected_call'
...tool/tarantool/.rocks/share/tarantool/luatest/runner.lua:420: in function 'super'
...
[C]: in function 'xpcall'
...ntool/tarantool/.rocks/share/tarantool/luatest/utils.lua:37: in function 'run_tests'
...tool/tarantool/.rocks/share/tarantool/luatest/runner.lua:258: in function <...tool/tarantool/.rocks/share/tarantool/luatest/runner.lua:254>
[C]: in function 'xpcall'
...l/tarantool/.rocks/share/tarantool/luatest/capturing.lua:74: in function <...l/tarantool/.rocks/share/tarantool/luatest/capturing.lua:72>
[C]: in function 'xpcall'
...tool/tarantool/.rocks/share/tarantool/luatest/runner.lua:50: in function 'fn'
...tool/.rocks/share/tarantool/luatest/sandboxed_runner.lua:14: in function 'run'
...antool/.rocks/share/tarantool/luatest/cli_entrypoint.lua:4: in function <...antool/.rocks/share/tarantool/luatest/cli_entrypoint.lua:3>
....rocks/share/tarantool/rocks/luatest/0.5.6-1/bin/luatest:3: in main chunk
Ran 371 tests in 303.206 seconds, 370 successes, 1 fail, 1 skipped
=========================================================
Failed tests:
unit.tar.test_errors
``` | non_priority | flaky test unit tar test errors from time to time the unit tar test errors test fails see the test run log below rocks bin luatest v b compatibility cartridge upgrade test upgrade skip tarantool test compatibility cartridge upgrade test lua no older version provided skipping compatibility config test failover ok compatibility config test failover ok hotreload forbidden test errors ok hotreload myrole test events ok hotreload myrole test errors ok hotreload myrole test roledeps ok hotreload myrole test rpc ok hotreload myrole test netbox ok hotreload myrole test routes ok hotreload myrole test globals ok hotreload myrole test fibers ok hotreload myrole test console ok hotreload vshard test router ok hotreload vshard test storage ok hotreload vshard test rebalancer ok integration admin test api ok integration admin test login ok integration advertise change test issues ok integration advertise change test topology query ok integration advertise change test suggestion ok integration advertise change test ok integration advertise change test failover ok integration api edit test edit server ok integration api edit test edit replicaset ok integration api edit test all rw false ok integration api edit test all rw true ok integration api join test join server ok integration api query test self ok integration api query test suggestions ok integration api query test custom http endpoint ok integration api query test server stat schema ok integration api query test server info schema ok integration api query test replication info schema ok integration api query test servers ok integration api query test replicasets ok integration api query test probe server ok integration api query test clock delta ok integration api query test topology caching ok integration api query test operation error ok integration api query test webui blacklist ok integration api query test app name ok integration api query test membership leave ok integration api query test issues ok integration api query test stop roles on shutdown ok integration api uninitialized test uninitialized ok integration api uninitialized test membership options ok integration api uninitialized test rpc ok integration api uninitialized test issues ok integration auth test login master auth enabled ok integration auth test login master auth disabled ok integration auth test login replica auth enabled ok integration auth test login replica auth disabled ok integration auth test empty list ok integration auth test auth disabled ok integration auth test auth enabled ok integration auth test uninitialized ok integration auth test keepalive ok integration auth test basic auth ok integration auth test set params graphql ok integration auth test cookie renew ok integration auth test cookie expiry ok integration auth test invalidate cookie on password change ok integration auth test admin disabled ok integration bootstrap test cookie change ok integration bootstrap test workdir collision ok integration clock delta test clock delta ok integration config test upload good ok integration config test upload fail ok integration config test validate ok integration config test rollback ok integration config test formatting ok integration config test on patch trigger ok integration config test patch clusterwide ok integration console sock test console sock ok integration cookie change test cluster restart ok integration cookie change test server restart ok integration ddl test luaapi ok integration ddl test formatting preserved ok integration ddl test replicas ok integration ddl test graphql errors ok integration ddl test space removal ok integration ddl test example schema ok integration ddl test no instances to check schema ok integration disable test api disable ok integration disable test suggestion ok integration client test locks ok integration client test appointments ok integration client test longpolling ok integration client test event cleared ok integration client test client drop session ok integration client test outage ok integration client test client session ok integration client test authentication ok integration client test vclockkeeper ok integration client test quorum ok integration expel test api ok integration failover eventual test api master ok integration failover eventual test api failover ok integration failover eventual test switchover ok integration failover eventual test sigkill ok integration failover eventual test all rw failover ok integration failover eventual test sigstop ok integration failover stateful test state provider restart ok integration failover stateful test coordinator restart ok integration failover stateful test leader restart ok integration failover stateful test leader promote ok integration failover stateful test leaderless ok integration failover stateful test issues ok integration failover stateful test force promote timeout ok integration failover stateful stateboard test state provider restart ok integration failover stateful stateboard test coordinator restart ok integration failover stateful stateboard test leader restart ok integration failover stateful stateboard test leader promote ok integration failover stateful stateboard test leaderless ok integration failover stateful stateboard test issues ok integration failover stateful stateboard test force promote timeout ok integration feedback test feedback ok integration feedback test rocks ok integration fencing test basics ok integration fencing stateboard test basics ok integration force reapply test twophase config locked ok integration force reapply test graphql api ok integration force reapply test suggestions ok integration graphql test simple ok integration graphql test errors in handlers ok integration graphql test reread request ok integration graphql test unknown query mutation ok integration graphql test error extensions ok integration graphql test middleware ok integration hidden roles test graphql known roles ok integration hidden roles test rpc ok integration hidden roles test config enable none ok integration hidden roles test config enable myrole ok integration hidden roles test config enable hidden ok integration hidden roles test config enable permanent ok integration hidden roles test graphql enable none ok integration hidden roles test graphql enable myrole ok integration hidden roles test graphql enable hidden ok integration hidden roles test graphql enable permanent ok integration issues test issues limits ok integration issues test broken replica ok integration issues test replication idle ok integration issues test config mismatch ok integration issues test twophase config locked ok integration issues test state hangs ok integration issues test aliens ok integration issues test custom issues ok integration join synchronous test call ok integration labels test servers labels ok integration labels test replicaset labels ok integration logger test cfg ok integration logger test content unconfigured ok integration logger test content bootstrapped ok integration master restart test master restart with missing xlog ok integration multiboot test bootstrap ok integration multijoin create test patch topology ok integration multijoin existing test patch topology ok integration multisharding api test query ok integration multisharding api test mutations ok integration multisharding one test api ok integration multisharding one test router role ok integration multisharding one test set vshard options positive ok integration multisharding one test set vshard options negative ok integration multisharding two test api ok integration multisharding two test mutations ok integration multisharding two test router role ok integration multisharding two test set vshard options positive ok integration myrole test api ok integration myrole test myrole ok integration myrole test dependencies ok integration myrole test rename ok integration pool connect test identity ok integration pool connect test errors ok integration pool connect test async call not yeilds ok integration pool connect test async call wait result err ok integration pool connect test async call remote ok integration pool map call test timeout ok integration pool map call test parallel ok integration pool map call test fiber storage ok integration pool map call test errors ok integration pool map call test negative ok integration pool map call test errors united ok integration pool map call test positive ok integration pool map call test futures ok integration proxy test alive destination ok integration proxy test dead destination ok integration proxy test issues ok integration rebalancing test ok integration reboot test oldstyle config ok integration reboot test absent config ok integration reboot test absent snapshot ok integration reboot test invalid config ok integration reboot test advertise change ok integration rejoin test rebootstrap ok integration rejoin test rejoin slave ok integration rejoin test rejoin master ok integration replicaset alias test rename replicaset ok integration restart replication test suggestion ok integration restart replication test errors ok integration rpc test api ok integration rpc test errors ok integration rpc test routing ok integration rpc test push ok integration slow requests test boxinfo ok integration slow requests test stat ok integration slow requests test issues ok integration slow requests test suggestions ok integration slow requests test netbox timeouts ok integration state machine test failover ok integration state machine test confapplier race ok integration state machine test leader death ok integration state machine test blinking slow ok integration state machine test blinking fast ok integration state machine test fiber cancel ok integration state machine test leader recovery ok integration state machine test orphan connect timeout ok integration state machine test quorum one ok integration state machine test restart both ok integration state machine test operation error ok integration state machine test prepare state error ok integration state machine test init error ok integration state machine test boot error ok integration stateboard test locks ok integration stateboard test appointments ok integration stateboard test longpolling ok integration stateboard test passwd ok integration stateboard test outage ok integration stateboard test client session ok integration stateboard test client drop session ok integration stateboard test stateboard console ok integration stateboard test box options ok integration stateboard test vclockkeeper ok integration switchover test forceful ok integration switchover test promotion forceful ok integration switchover test promotion abortion ok integration switchover test promotion late ok integration switchover test vclockkeeper caching ok integration switchover test enabling ok integration switchover test api ok integration switchover test all rw ok integration switchover test alone instance ok integration switchover stateboard test forceful ok integration switchover stateboard test promotion forceful ok integration switchover stateboard test promotion abortion ok integration switchover stateboard test promotion late ok integration switchover stateboard test vclockkeeper caching ok integration switchover stateboard test enabling ok integration switchover stateboard test api ok integration switchover stateboard test all rw ok integration switchover stateboard test alone instance ok integration twophase test errors ok integration twophase test success ok integration twophase test upload skipped ok integration twophase test prepare fails ok integration twophase test commit fails ok integration twophase test abort fails ok integration upload test begining failure ok integration upload test transmission failure ok integration upload test finish failure ok integration vshard weight test ok integration vshardless test edit replicaset ok integration vshardless test package loaded ok integration vshardless test config ok integration vshardless test api ok integration workdir test defaults ok integration workdir test abspath ok integration workdir test relpath ok integration workdir test chdir ok integration zones test zones ok integration zones test distances ok integration zones test validation ok integration zones helpers test zones distances ok unit argparse test sections ok unit argparse test priority ok unit argparse test overrides ok unit argparse test appname ok unit argparse test confdir ok unit argparse test badfile ok unit argparse test box opts ok unit cartridge failover test empty state ok unit cartridge failover test unconfigured state ok unit cfg errors test workdir ok unit cfg errors test advertise uri ok unit cfg errors test http ok unit cfg errors test issues limits ok unit cfg errors test roles ok unit cfg errors test custom auth backend ok unit cfg errors test default auth backend ok unit cfg errors test console sock enobufs ok unit cfg errors test console sock enoent ok unit cfg errors test dns resolve timeout ok unit cfg errors test positive ok unit cfg errors test webui prefix ok unit cluster cookie test set cookie ok unit clusterwide config test newstyle ok ok unit clusterwide config test newstyle err ok unit clusterwide config test oldstyle ok ok unit clusterwide config test oldstyle err ok unit clusterwide config test preserving plaintext ok unit clusterwide config test delete plaintext key ok unit clusterwide config test create err ok unit clusterwide config test get readonly ok ok unit clusterwide config test get readonly err ok unit clusterwide config test immutability ok unit clusterwide config test get deepcopy modify ok unit clusterwide config test save empty config ok unit clusterwide config test save err ok unit clusterwide config test save ok ok unit clusterwide config test checksum ok unit helpers test cluster bootstrap ok unit helpers test config management ok unit helpers test servers access ok unit helpers test replicaset uuid generation ok unit helpers test failover ok unit helpers test new with servers count ok unit helpers test new without replicaset and server alias ok unit helpers test new with env ok unit helpers test errno ok unit issues limits test positive ok unit issues limits test negative ok unit labels test labels ok ok unit labels test labels error ok unit remote control test start ok unit remote control test peer uuid ok unit remote control test fiber name ok unit remote control test drop connections ok unit remote control test late accept ok unit remote control test auth ok unit remote control test ping ok unit remote control test bytestream ok unit remote control test invalid serialization ok unit remote control test large payload ok unit remote control test async ok unit remote control test bad username ok unit remote control test bad password ok unit remote control test guest ok unit remote control test call ok unit remote control test eval ok unit remote control test timeout ok unit remote control test switch box to rc ok unit remote control test switch rc to box ok unit remote control test reconnect ok unit remote control test socket gc ok unit remote control test fd cloexec ok unit roledeps test unknown ok unit roledeps test error ok unit roledeps test name clash ok unit roledeps test format ok unit roledeps test circular deps ok unit roledeps test full deps ok unit roledeps test enabled roles ok unit rpc candidates test all ok unit tar test fixtures pack ok unit tar test fixtures unpack ok unit tar test truncated ok unit tar test errors fail e runner work tarantool tarantool test unit tar test lua expected nil actual unit topology test single group ok unit topology test multi group ok unit topology leaders test leader order ok unit upload test begin ok unit upload test transmit ok unit upload test finish ok unit upload test cleanup ok unit upload test upload ok unit utils test upvalues ok unit utils test randomize path ok unit vshard config test all ok unit wait lsn test zero timeout ok unit wait lsn test timings ok unit wait lsn test absent lsn ok upgrade tarantool upgrade test upgrade ok main i tx binary stopped failed tests unit tar test errors e runner work tarantool tarantool test unit tar test lua expected nil actual stack traceback ntool tarantool rocks share tarantool luatest utils lua in function luatest error tarantool rocks share tarantool luatest assertions lua in function failure tarantool rocks share tarantool luatest assertions lua in function assert equals e runner work tarantool tarantool test unit tar test lua in function unit tar test errors tool tarantool rocks share tarantool luatest runner lua in function in function xpcall tool tarantool rocks share tarantool luatest runner lua in function super l tarantool rocks share tarantool luatest capturing lua in function protected call tool tarantool rocks share tarantool luatest runner lua in function super in function xpcall ntool tarantool rocks share tarantool luatest utils lua in function run tests tool tarantool rocks share tarantool luatest runner lua in function in function xpcall l tarantool rocks share tarantool luatest capturing lua in function in function xpcall tool tarantool rocks share tarantool luatest runner lua in function fn tool rocks share tarantool luatest sandboxed runner lua in function run antool rocks share tarantool luatest cli entrypoint lua in function rocks share tarantool rocks luatest bin luatest in main chunk ran tests in seconds successes fail skipped failed tests unit tar test errors | 0 |
433,386 | 30,324,982,831 | IssuesEvent | 2023-07-10 22:48:11 | PlasmoHQ/plasmo | https://api.github.com/repos/PlasmoHQ/plasmo | closed | [EXP] A sidebar or panel implementation | documentation | ### What is the example you wish to see?
An implementation of a panel or sidebar such as:
<img width="608" alt="image" src="https://github.com/PlasmoHQ/plasmo/assets/48488488/93e4ddff-c685-4310-b76b-24bfc0638f90">
### Is there any context that might help us understand?
Chrome provides APIs for creating such panels:
https://developer.chrome.com/docs/extensions/reference/devtools_panels/
### Code of Conduct
- [X] I agree to follow this project's Code of Conduct
- [X] I checked the [current issues](https://github.com/PlasmoHQ/plasmo/issues) for duplicate problems. | 1.0 | [EXP] A sidebar or panel implementation - ### What is the example you wish to see?
An implementation of a panel or sidebar such as:
<img width="608" alt="image" src="https://github.com/PlasmoHQ/plasmo/assets/48488488/93e4ddff-c685-4310-b76b-24bfc0638f90">
### Is there any context that might help us understand?
Chrome provides APIs for creating such panels:
https://developer.chrome.com/docs/extensions/reference/devtools_panels/
### Code of Conduct
- [X] I agree to follow this project's Code of Conduct
- [X] I checked the [current issues](https://github.com/PlasmoHQ/plasmo/issues) for duplicate problems. | non_priority | a sidebar or panel implementation what is the example you wish to see an implementation of a panel or sidebar such as img width alt image src is there any context that might help us understand chrome provides apis for creating such panels code of conduct i agree to follow this project s code of conduct i checked the for duplicate problems | 0 |
3,466 | 2,538,462,689 | IssuesEvent | 2015-01-27 07:04:01 | newca12/gapt | https://api.github.com/repos/newca12/gapt | closed | Specification of HandyRes | 1 star imported Priority-Medium Type-Task | _From [shaoli...@gmail.com](https://code.google.com/u/113190107447576027220/) on August 07, 2010 11:45:52_
HandyRes is a specification language for resolution proofs similar to handyLK.
It should support schematization of resolution proofs a well as other features which might simplify the writing of resolution proofs (automatic computations of unifiers, variants, factors..). It should create a resolution proof from our data structures.
The specification team should include 2-3 people, among them Daniel, which has most of the knowledge of HandyLK.
After the specifications will be ready, the implementation team should include at least one member from the specification team. Cvetan expressed a wish to be in this team.
_Original issue: http://code.google.com/p/gapt/issues/detail?id=78_ | 1.0 | Specification of HandyRes - _From [shaoli...@gmail.com](https://code.google.com/u/113190107447576027220/) on August 07, 2010 11:45:52_
HandyRes is a specification language for resolution proofs similar to handyLK.
It should support schematization of resolution proofs a well as other features which might simplify the writing of resolution proofs (automatic computations of unifiers, variants, factors..). It should create a resolution proof from our data structures.
The specification team should include 2-3 people, among them Daniel, which has most of the knowledge of HandyLK.
After the specifications will be ready, the implementation team should include at least one member from the specification team. Cvetan expressed a wish to be in this team.
_Original issue: http://code.google.com/p/gapt/issues/detail?id=78_ | priority | specification of handyres from on august handyres is a specification language for resolution proofs similar to handylk it should support schematization of resolution proofs a well as other features which might simplify the writing of resolution proofs automatic computations of unifiers variants factors it should create a resolution proof from our data structures the specification team should include people among them daniel which has most of the knowledge of handylk after the specifications will be ready the implementation team should include at least one member from the specification team cvetan expressed a wish to be in this team original issue | 1 |
17,635 | 12,218,521,774 | IssuesEvent | 2020-05-01 19:32:05 | solo-io/gloo | https://api.github.com/repos/solo-io/gloo | closed | glooctl requires clusterrole | Area: Usability Type: Bug | Install Gloo with glooRbac.namespaced=true:
```
global:
glooRbac:
namespaced: true
settings:
singleNamespace: true
gloo:
discovery:
fdsMode: BLACKLIST
```
Create testuser with admin role:
```
kubectl -n gloo-system create serviceaccount testuser
kubectl config set-context testcontext --cluster=gke_solo-public_us-west1-b_decoste-cluster-2 --user=testuser
kubectl -n gloo-system create role admin --verb=get,list,create,update,patch,watch --resource=virtualservice,upstream,settings,proxy
kubectl create rolebinding admin-binding --role admin --user system:serviceaccount:gloo-system:testuser -n gloo-system
kubectl config use-context testcontext
kubectl config set-credentials testuser --token="<TOKEN>" # use base64 decoded token from secret generated for testuser in gloo-system
```
Test kubectl
```
$ kubectl -n gloo-system get vs
NAME AGE
default 23h
```
```
Test glooctl:
$ glooctl get vs
Warning: Could not determine gloo client/server versions (is Gloo running outside of kubernetes?): deployments.apps is forbidden: User "system:serviceaccount:gloo-system:testuser" cannot list resource "deployments" in API group "apps" in the namespace "gloo-system"
"Fri, 07 Feb 2020 09:55:54 EST: github.com/solo-io/gloo/projects/gloo/cli/pkg/helpers/clients.go:316" failed to create virtualService client: &errors.withStack{
error: &errors.withMessage{
cause: &errors.withStack{
error: &errors.withMessage{
cause: &errors.withStack{
error: &errors.withMessage{
cause: &errors.StatusError{
ErrStatus: v1.Status{
TypeMeta: v1.TypeMeta{
Kind: "",
APIVersion: "",
},
ListMeta: v1.ListMeta{
SelfLink: "",
ResourceVersion: "",
Continue: "",
RemainingItemCount: (*int64)(nil),
},
Status: "Failure",
Message: "virtualservices.gateway.solo.io is forbidden: User \"system:serviceaccount:gloo-system:testuser\" cannot list resource \"virtualservices\" in API group \"gateway.solo.io\" at the cluster scope",
Reason: "Forbidden",
Details: &v1.StatusDetails{
Name: "",
Group: "gateway.solo.io",
Kind: "virtualservices",
UID: "",
Causes: []v1.StatusCause{},
RetryAfterSeconds: 0,
},
Code: 403,
},
},
msg: "list check failed",
},
stack: &errors.stack{
0x1957f92,
0x26a8957,
0x26a9e50,
0x2ab2da3,
0x2ab2bbb,
0x3338ed1,
0x3338972,
0x339c240,
0x33b712d,
0x128be51,
0x128caa8,
0x128c3cb,
0x33c6084,
0x1034bf4,
0x10634d1,
},
},
msg: "creating base VirtualService resource client",
},
stack: &errors.stack{
0x1957f92,
0x2ab2e50,
0x2ab2bbb,
0x3338ed1,
0x3338972,
0x339c240,
0x33b712d,
0x128be51,
0x128caa8,
0x128c3cb,
0x33c6084,
0x1034bf4,
0x10634d1,
},
},
msg: "creating virtualServices client",
},
stack: &errors.stack{
0x1957f92,
0x3338f8a,
0x3338972,
0x339c240,
0x33b712d,
0x128be51,
0x128caa8,
0x128c3cb,
0x33c6084,
0x1034bf4,
0x10634d1,
},
}
```
| True | glooctl requires clusterrole - Install Gloo with glooRbac.namespaced=true:
```
global:
glooRbac:
namespaced: true
settings:
singleNamespace: true
gloo:
discovery:
fdsMode: BLACKLIST
```
Create testuser with admin role:
```
kubectl -n gloo-system create serviceaccount testuser
kubectl config set-context testcontext --cluster=gke_solo-public_us-west1-b_decoste-cluster-2 --user=testuser
kubectl -n gloo-system create role admin --verb=get,list,create,update,patch,watch --resource=virtualservice,upstream,settings,proxy
kubectl create rolebinding admin-binding --role admin --user system:serviceaccount:gloo-system:testuser -n gloo-system
kubectl config use-context testcontext
kubectl config set-credentials testuser --token="<TOKEN>" # use base64 decoded token from secret generated for testuser in gloo-system
```
Test kubectl
```
$ kubectl -n gloo-system get vs
NAME AGE
default 23h
```
```
Test glooctl:
$ glooctl get vs
Warning: Could not determine gloo client/server versions (is Gloo running outside of kubernetes?): deployments.apps is forbidden: User "system:serviceaccount:gloo-system:testuser" cannot list resource "deployments" in API group "apps" in the namespace "gloo-system"
"Fri, 07 Feb 2020 09:55:54 EST: github.com/solo-io/gloo/projects/gloo/cli/pkg/helpers/clients.go:316" failed to create virtualService client: &errors.withStack{
error: &errors.withMessage{
cause: &errors.withStack{
error: &errors.withMessage{
cause: &errors.withStack{
error: &errors.withMessage{
cause: &errors.StatusError{
ErrStatus: v1.Status{
TypeMeta: v1.TypeMeta{
Kind: "",
APIVersion: "",
},
ListMeta: v1.ListMeta{
SelfLink: "",
ResourceVersion: "",
Continue: "",
RemainingItemCount: (*int64)(nil),
},
Status: "Failure",
Message: "virtualservices.gateway.solo.io is forbidden: User \"system:serviceaccount:gloo-system:testuser\" cannot list resource \"virtualservices\" in API group \"gateway.solo.io\" at the cluster scope",
Reason: "Forbidden",
Details: &v1.StatusDetails{
Name: "",
Group: "gateway.solo.io",
Kind: "virtualservices",
UID: "",
Causes: []v1.StatusCause{},
RetryAfterSeconds: 0,
},
Code: 403,
},
},
msg: "list check failed",
},
stack: &errors.stack{
0x1957f92,
0x26a8957,
0x26a9e50,
0x2ab2da3,
0x2ab2bbb,
0x3338ed1,
0x3338972,
0x339c240,
0x33b712d,
0x128be51,
0x128caa8,
0x128c3cb,
0x33c6084,
0x1034bf4,
0x10634d1,
},
},
msg: "creating base VirtualService resource client",
},
stack: &errors.stack{
0x1957f92,
0x2ab2e50,
0x2ab2bbb,
0x3338ed1,
0x3338972,
0x339c240,
0x33b712d,
0x128be51,
0x128caa8,
0x128c3cb,
0x33c6084,
0x1034bf4,
0x10634d1,
},
},
msg: "creating virtualServices client",
},
stack: &errors.stack{
0x1957f92,
0x3338f8a,
0x3338972,
0x339c240,
0x33b712d,
0x128be51,
0x128caa8,
0x128c3cb,
0x33c6084,
0x1034bf4,
0x10634d1,
},
}
```
| non_priority | glooctl requires clusterrole install gloo with gloorbac namespaced true global gloorbac namespaced true settings singlenamespace true gloo discovery fdsmode blacklist create testuser with admin role kubectl n gloo system create serviceaccount testuser kubectl config set context testcontext cluster gke solo public us b decoste cluster user testuser kubectl n gloo system create role admin verb get list create update patch watch resource virtualservice upstream settings proxy kubectl create rolebinding admin binding role admin user system serviceaccount gloo system testuser n gloo system kubectl config use context testcontext kubectl config set credentials testuser token use decoded token from secret generated for testuser in gloo system test kubectl kubectl n gloo system get vs name age default test glooctl glooctl get vs warning could not determine gloo client server versions is gloo running outside of kubernetes deployments apps is forbidden user system serviceaccount gloo system testuser cannot list resource deployments in api group apps in the namespace gloo system fri feb est github com solo io gloo projects gloo cli pkg helpers clients go failed to create virtualservice client errors withstack error errors withmessage cause errors withstack error errors withmessage cause errors withstack error errors withmessage cause errors statuserror errstatus status typemeta typemeta kind apiversion listmeta listmeta selflink resourceversion continue remainingitemcount nil status failure message virtualservices gateway solo io is forbidden user system serviceaccount gloo system testuser cannot list resource virtualservices in api group gateway solo io at the cluster scope reason forbidden details statusdetails name group gateway solo io kind virtualservices uid causes statuscause retryafterseconds code msg list check failed stack errors stack msg creating base virtualservice resource client stack errors stack msg creating virtualservices client stack errors stack | 0 |
18,890 | 26,244,662,633 | IssuesEvent | 2023-01-05 14:21:53 | TeamGalacticraft/Galacticraft-Legacy | https://api.github.com/repos/TeamGalacticraft/Galacticraft-Legacy | closed | Overlapping inventory tabs | Mod Incompatibility [Type] Bug Report | ### Forge Version
14.23.5.2860
### Galacticraft Version
4.0.4
### Log or Crash Report
there are two tabs in inventory that are overlapping one is the space equipment tab and another I don't know
### Reproduction steps
Idk
| True | Overlapping inventory tabs - ### Forge Version
14.23.5.2860
### Galacticraft Version
4.0.4
### Log or Crash Report
there are two tabs in inventory that are overlapping one is the space equipment tab and another I don't know
### Reproduction steps
Idk
| non_priority | overlapping inventory tabs forge version galacticraft version log or crash report there are two tabs in inventory that are overlapping one is the space equipment tab and another i don t know reproduction steps idk | 0 |
494,108 | 14,245,330,783 | IssuesEvent | 2020-11-19 08:30:17 | webcompat/web-bugs | https://api.github.com/repos/webcompat/web-bugs | closed | itags.literotica.com - site is not usable | browser-fenix engine-gecko ml-needsdiagnosis-false priority-normal | <!-- @browser: Firefox Mobile 83.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 9; Mobile; rv:83.0) Gecko/83.0 Firefox/83.0 -->
<!-- @reported_with: android-components-reporter -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/62067 -->
<!-- @extra_labels: browser-fenix -->
**URL**: https://itags.literotica.com/incest/slave/?page=1
**Browser / Version**: Firefox Mobile 83.0
**Operating System**: Android
**Tested Another Browser**: Yes Chrome
**Problem type**: Site is not usable
**Description**: Browser unsupported
**Steps to Reproduce**:
<details>
<summary>View the screenshot</summary>
<img alt="Screenshot" src="https://webcompat.com/uploads/2020/11/1f064e32-f594-4828-a76a-356fcac12edb.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: 20201108174701</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/11/0752f629-970e-451d-bbaf-08ac4b5cb251)
_From [webcompat.com](https://webcompat.com/) with ❤️_ | 1.0 | itags.literotica.com - site is not usable - <!-- @browser: Firefox Mobile 83.0 -->
<!-- @ua_header: Mozilla/5.0 (Android 9; Mobile; rv:83.0) Gecko/83.0 Firefox/83.0 -->
<!-- @reported_with: android-components-reporter -->
<!-- @public_url: https://github.com/webcompat/web-bugs/issues/62067 -->
<!-- @extra_labels: browser-fenix -->
**URL**: https://itags.literotica.com/incest/slave/?page=1
**Browser / Version**: Firefox Mobile 83.0
**Operating System**: Android
**Tested Another Browser**: Yes Chrome
**Problem type**: Site is not usable
**Description**: Browser unsupported
**Steps to Reproduce**:
<details>
<summary>View the screenshot</summary>
<img alt="Screenshot" src="https://webcompat.com/uploads/2020/11/1f064e32-f594-4828-a76a-356fcac12edb.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: 20201108174701</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/11/0752f629-970e-451d-bbaf-08ac4b5cb251)
_From [webcompat.com](https://webcompat.com/) with ❤️_ | priority | itags literotica com site is not usable url browser version firefox mobile operating system android tested another browser yes chrome problem type site is not usable description browser unsupported 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 ❤️ | 1 |
176,863 | 6,565,905,707 | IssuesEvent | 2017-09-08 10:13:41 | NHSLeadership/nightingale | https://api.github.com/repos/NHSLeadership/nightingale | opened | Quotes | Priority: Low Status: Available Type: Enhancement | <img width="663" alt="screen shot 2017-09-08 at 11 12 49" src="https://user-images.githubusercontent.com/23170050/30207216-a95b448a-9486-11e7-9589-975a6f7ec67b.png">
@cehwitham set priority please. | 1.0 | Quotes - <img width="663" alt="screen shot 2017-09-08 at 11 12 49" src="https://user-images.githubusercontent.com/23170050/30207216-a95b448a-9486-11e7-9589-975a6f7ec67b.png">
@cehwitham set priority please. | priority | quotes img width alt screen shot at src cehwitham set priority please | 1 |
190,591 | 6,820,335,588 | IssuesEvent | 2017-11-07 13:35:34 | carboncoop/home-energy-health-check | https://api.github.com/repos/carboncoop/home-energy-health-check | closed | 'This assessment has already been submitted.' message | bug High Priority | A new assessment is created. Changes are made eg measures are recommended. Clicking to the 'Done' tab, a message appears: 'This assessment has already been submitted.'
Some users report that this message leads to loss of data.
| 1.0 | 'This assessment has already been submitted.' message - A new assessment is created. Changes are made eg measures are recommended. Clicking to the 'Done' tab, a message appears: 'This assessment has already been submitted.'
Some users report that this message leads to loss of data.
| priority | this assessment has already been submitted message a new assessment is created changes are made eg measures are recommended clicking to the done tab a message appears this assessment has already been submitted some users report that this message leads to loss of data | 1 |
49,616 | 12,391,995,390 | IssuesEvent | 2020-05-20 13:22:51 | opencv/opencv | https://api.github.com/repos/opencv/opencv | closed | Mac Catalyst / xcframework support | category: build/install feature platform: ios/osx | ##### System information (version)
<!-- Example
- OpenCV => 4.2
- Operating System / Platform => Windows 64 Bit
- Compiler => Visual Studio 2017
-->
- OpenCV => 4.3 / master
- Operating System / Platform => Mac Catalyst
- Compiler => Xcode 11.4.1
##### Detailed description
The `build_framework.py` build scripts for iOS and macOS should be updated to create `xcframeworks` instead of `lipo`'d frameworks. This is required in order to support Mac Catalyst, because the iOS simulator `x86_64` slice conflicts with the `x86_64-apple-ios-macabi` slice.
Although there is an existing approach [here](https://answers.opencv.org/question/216407/opencv-build-for-mac-catalystios-13-ios-app-on-mac-support/), ideally it should be resolved in the platform build scripts, and ultimately the official binary releases should be a multi-platform `.xcframework` instead of a `.framework`.
##### Issue submission checklist
- [x] I report the issue, it's not a question
<!--
OpenCV team works with answers.opencv.org, Stack Overflow and other communities
to discuss problems. Tickets with question without real issue statement will be
closed.
-->
- [x] I checked the problem with documentation, FAQ, open issues,
answers.opencv.org, Stack Overflow, etc and have not found solution
<!--
Places to check:
* OpenCV documentation: https://docs.opencv.org
* FAQ page: https://github.com/opencv/opencv/wiki/FAQ
* OpenCV forum: https://answers.opencv.org
* OpenCV issue tracker: https://github.com/opencv/opencv/issues?q=is%3Aissue
* Stack Overflow branch: https://stackoverflow.com/questions/tagged/opencv
-->
- [x] I updated to latest OpenCV version and the issue is still there
<!--
master branch for OpenCV 4.x and 3.4 branch for OpenCV 3.x releases.
OpenCV team supports only latest release for each branch.
The ticket is closed, if the problem is not reproduced with modern version.
-->
- [x] There is reproducer code and related data files: videos, images, onnx, etc
<!--
The best reproducer -- test case for OpenCV that we can add to the library.
Recommendations for media files and binary files:
* Try to reproduce the issue with images and videos in opencv_extra repository
to reduce attachment size
* Use PNG for images, if you report some CV related bug, but not image reader
issue
* Attach the image as archite to the ticket, if you report some reader issue.
Image hosting services compress images and it breaks the repro code.
* Provide ONNX file for some public model or ONNX file with with random weights,
if you report ONNX parsing or handling issue. Architecture details diagram
from netron tool can be very useful too. See https://lutzroeder.github.io/netron/
-->
| 1.0 | Mac Catalyst / xcframework support - ##### System information (version)
<!-- Example
- OpenCV => 4.2
- Operating System / Platform => Windows 64 Bit
- Compiler => Visual Studio 2017
-->
- OpenCV => 4.3 / master
- Operating System / Platform => Mac Catalyst
- Compiler => Xcode 11.4.1
##### Detailed description
The `build_framework.py` build scripts for iOS and macOS should be updated to create `xcframeworks` instead of `lipo`'d frameworks. This is required in order to support Mac Catalyst, because the iOS simulator `x86_64` slice conflicts with the `x86_64-apple-ios-macabi` slice.
Although there is an existing approach [here](https://answers.opencv.org/question/216407/opencv-build-for-mac-catalystios-13-ios-app-on-mac-support/), ideally it should be resolved in the platform build scripts, and ultimately the official binary releases should be a multi-platform `.xcframework` instead of a `.framework`.
##### Issue submission checklist
- [x] I report the issue, it's not a question
<!--
OpenCV team works with answers.opencv.org, Stack Overflow and other communities
to discuss problems. Tickets with question without real issue statement will be
closed.
-->
- [x] I checked the problem with documentation, FAQ, open issues,
answers.opencv.org, Stack Overflow, etc and have not found solution
<!--
Places to check:
* OpenCV documentation: https://docs.opencv.org
* FAQ page: https://github.com/opencv/opencv/wiki/FAQ
* OpenCV forum: https://answers.opencv.org
* OpenCV issue tracker: https://github.com/opencv/opencv/issues?q=is%3Aissue
* Stack Overflow branch: https://stackoverflow.com/questions/tagged/opencv
-->
- [x] I updated to latest OpenCV version and the issue is still there
<!--
master branch for OpenCV 4.x and 3.4 branch for OpenCV 3.x releases.
OpenCV team supports only latest release for each branch.
The ticket is closed, if the problem is not reproduced with modern version.
-->
- [x] There is reproducer code and related data files: videos, images, onnx, etc
<!--
The best reproducer -- test case for OpenCV that we can add to the library.
Recommendations for media files and binary files:
* Try to reproduce the issue with images and videos in opencv_extra repository
to reduce attachment size
* Use PNG for images, if you report some CV related bug, but not image reader
issue
* Attach the image as archite to the ticket, if you report some reader issue.
Image hosting services compress images and it breaks the repro code.
* Provide ONNX file for some public model or ONNX file with with random weights,
if you report ONNX parsing or handling issue. Architecture details diagram
from netron tool can be very useful too. See https://lutzroeder.github.io/netron/
-->
| non_priority | mac catalyst xcframework support system information version example opencv operating system platform windows bit compiler visual studio opencv master operating system platform mac catalyst compiler xcode detailed description the build framework py build scripts for ios and macos should be updated to create xcframeworks instead of lipo d frameworks this is required in order to support mac catalyst because the ios simulator slice conflicts with the apple ios macabi slice although there is an existing approach ideally it should be resolved in the platform build scripts and ultimately the official binary releases should be a multi platform xcframework instead of a framework issue submission checklist i report the issue it s not a question opencv team works with answers opencv org stack overflow and other communities to discuss problems tickets with question without real issue statement will be closed i checked the problem with documentation faq open issues answers opencv org stack overflow etc and have not found solution places to check opencv documentation faq page opencv forum opencv issue tracker stack overflow branch i updated to latest opencv version and the issue is still there master branch for opencv x and branch for opencv x releases opencv team supports only latest release for each branch the ticket is closed if the problem is not reproduced with modern version there is reproducer code and related data files videos images onnx etc the best reproducer test case for opencv that we can add to the library recommendations for media files and binary files try to reproduce the issue with images and videos in opencv extra repository to reduce attachment size use png for images if you report some cv related bug but not image reader issue attach the image as archite to the ticket if you report some reader issue image hosting services compress images and it breaks the repro code provide onnx file for some public model or onnx file with with random weights if you report onnx parsing or handling issue architecture details diagram from netron tool can be very useful too see | 0 |
653,772 | 21,626,131,651 | IssuesEvent | 2022-05-05 02:34:32 | kubesphere/console | https://api.github.com/repos/kubesphere/console | closed | Environment variables do not support key names containing hyphens (-) and periods (.) | kind/bug kind/need-to-verify priority/low | **Describe the bug**
**Versions used(KubeSphere/Kubernetes)**
KubeSphere: `v3.3.0-alpha.0`
/assgign @kubesphere/sig-console
/priority low | 1.0 | Environment variables do not support key names containing hyphens (-) and periods (.) - **Describe the bug**
**Versions used(KubeSphere/Kubernetes)**
KubeSphere: `v3.3.0-alpha.0`
/assgign @kubesphere/sig-console
/priority low | priority | environment variables do not support key names containing hyphens and periods describe the bug versions used kubesphere kubernetes kubesphere alpha assgign kubesphere sig console priority low | 1 |
387,825 | 11,470,803,579 | IssuesEvent | 2020-02-09 06:27:07 | IlchCMS/Ilch-2.0 | https://api.github.com/repos/IlchCMS/Ilch-2.0 | opened | Benutzer-Modul: Benutzer im Admincenter sortierbar/durchsuchbar machen | Priority: Medium Type: Enhancement | http://www.ilch.de/forum-showposts-54202.html
> Man könnte zur besseren Durchsicht einfügen das man die Reihenfolge ändern kann, um es sich selbst übersichtlicher zu gestalten.
Zum Beispiel die Möglichkeit bieten die Benutzerliste alphabetisch aufsteigend/absteigend nach Benutzername zu sortieren und/oder auch die Liste der Benutzer durchsuchen zu können. | 1.0 | Benutzer-Modul: Benutzer im Admincenter sortierbar/durchsuchbar machen - http://www.ilch.de/forum-showposts-54202.html
> Man könnte zur besseren Durchsicht einfügen das man die Reihenfolge ändern kann, um es sich selbst übersichtlicher zu gestalten.
Zum Beispiel die Möglichkeit bieten die Benutzerliste alphabetisch aufsteigend/absteigend nach Benutzername zu sortieren und/oder auch die Liste der Benutzer durchsuchen zu können. | priority | benutzer modul benutzer im admincenter sortierbar durchsuchbar machen man könnte zur besseren durchsicht einfügen das man die reihenfolge ändern kann um es sich selbst übersichtlicher zu gestalten zum beispiel die möglichkeit bieten die benutzerliste alphabetisch aufsteigend absteigend nach benutzername zu sortieren und oder auch die liste der benutzer durchsuchen zu können | 1 |
363,372 | 25,447,611,229 | IssuesEvent | 2022-11-24 07:51:22 | Telefonica/mistica-design | https://api.github.com/repos/Telefonica/mistica-design | closed | IconButton in design documentation | component: buttons category: documentation added | Añadir los iconButtons a la documentación de BF de botones
https://brandfactory.telefonica.com/document/1846#/components/buttons | 1.0 | IconButton in design documentation - Añadir los iconButtons a la documentación de BF de botones
https://brandfactory.telefonica.com/document/1846#/components/buttons | non_priority | iconbutton in design documentation añadir los iconbuttons a la documentación de bf de botones | 0 |
9,918 | 2,608,797,329 | IssuesEvent | 2015-02-26 10:02:57 | mPowering/django-mpowering | https://api.github.com/repos/mPowering/django-mpowering | opened | Consider navigation methods | Effort: less than week enhancement high priority question | User feedback:
"Navigation is currently all by health topic – do you plan to keep it this way or develop it further so that as a user I might be able to identify myself on there i.e. a CHW etc? I realise this is all introductory/basic info but as I user I can’t really see myself on there?" | 1.0 | Consider navigation methods - User feedback:
"Navigation is currently all by health topic – do you plan to keep it this way or develop it further so that as a user I might be able to identify myself on there i.e. a CHW etc? I realise this is all introductory/basic info but as I user I can’t really see myself on there?" | priority | consider navigation methods user feedback navigation is currently all by health topic – do you plan to keep it this way or develop it further so that as a user i might be able to identify myself on there i e a chw etc i realise this is all introductory basic info but as i user i can’t really see myself on there | 1 |
25,206 | 4,233,653,478 | IssuesEvent | 2016-07-05 08:48:24 | arkayenro/arkinventory | https://api.github.com/repos/arkayenro/arkinventory | closed | Problem loading ARKINV_Frame4 frame (guild bank) | auto-migrated Priority-Medium Type-Defect | ```
Downloaded from > curse client
(specify)
What steps will reproduce the problem?
1. Define custom window options for main bag window
2. navigate to the "guild bank" "controls" tabs
3. set the "settings" dropdown box to "bag"
4. Open guild bank
What is the expected output?
I expect the guild bank frame to open with the settings I've previously defined under "bag" settings (this used to work, but was apparently broken in a recent patch) because the controls for the guild bank are set to "bag"
What do you see instead?
The frame is only rendered half way, no items in the bank, the "ARKINV_Frame4ChangerWindowBag" bar is in the middle of the screen towards the top, and the frame is unable to be moved by click and drag
What version of the product are you using?
version 3.04.22
On what operating system?
Windows 7 Ultimate x64
Please provide any additional information below.
When I set the dropdown box to "guild bank" which is the default setting, the frame renders under the defaults of arkinventory, however the dropdown box back to "bag" the frame doesn't change, no action appears to be taken.
```
Original issue reported on code.google.com by `battlema...@gmail.com` on 9 Feb 2015 at 7:35
Attachments:
* [WoWScrnShot_020915_123231.jpg](https://storage.googleapis.com/google-code-attachments/arkinventory/issue-700/comment-0/WoWScrnShot_020915_123231.jpg)
* [WoWScrnShot_020915_123051.jpg](https://storage.googleapis.com/google-code-attachments/arkinventory/issue-700/comment-0/WoWScrnShot_020915_123051.jpg)
* [WoWScrnShot_020915_123315.jpg](https://storage.googleapis.com/google-code-attachments/arkinventory/issue-700/comment-0/WoWScrnShot_020915_123315.jpg)
| 1.0 | Problem loading ARKINV_Frame4 frame (guild bank) - ```
Downloaded from > curse client
(specify)
What steps will reproduce the problem?
1. Define custom window options for main bag window
2. navigate to the "guild bank" "controls" tabs
3. set the "settings" dropdown box to "bag"
4. Open guild bank
What is the expected output?
I expect the guild bank frame to open with the settings I've previously defined under "bag" settings (this used to work, but was apparently broken in a recent patch) because the controls for the guild bank are set to "bag"
What do you see instead?
The frame is only rendered half way, no items in the bank, the "ARKINV_Frame4ChangerWindowBag" bar is in the middle of the screen towards the top, and the frame is unable to be moved by click and drag
What version of the product are you using?
version 3.04.22
On what operating system?
Windows 7 Ultimate x64
Please provide any additional information below.
When I set the dropdown box to "guild bank" which is the default setting, the frame renders under the defaults of arkinventory, however the dropdown box back to "bag" the frame doesn't change, no action appears to be taken.
```
Original issue reported on code.google.com by `battlema...@gmail.com` on 9 Feb 2015 at 7:35
Attachments:
* [WoWScrnShot_020915_123231.jpg](https://storage.googleapis.com/google-code-attachments/arkinventory/issue-700/comment-0/WoWScrnShot_020915_123231.jpg)
* [WoWScrnShot_020915_123051.jpg](https://storage.googleapis.com/google-code-attachments/arkinventory/issue-700/comment-0/WoWScrnShot_020915_123051.jpg)
* [WoWScrnShot_020915_123315.jpg](https://storage.googleapis.com/google-code-attachments/arkinventory/issue-700/comment-0/WoWScrnShot_020915_123315.jpg)
| non_priority | problem loading arkinv frame guild bank downloaded from curse client specify what steps will reproduce the problem define custom window options for main bag window navigate to the guild bank controls tabs set the settings dropdown box to bag open guild bank what is the expected output i expect the guild bank frame to open with the settings i ve previously defined under bag settings this used to work but was apparently broken in a recent patch because the controls for the guild bank are set to bag what do you see instead the frame is only rendered half way no items in the bank the arkinv bar is in the middle of the screen towards the top and the frame is unable to be moved by click and drag what version of the product are you using version on what operating system windows ultimate please provide any additional information below when i set the dropdown box to guild bank which is the default setting the frame renders under the defaults of arkinventory however the dropdown box back to bag the frame doesn t change no action appears to be taken original issue reported on code google com by battlema gmail com on feb at attachments | 0 |
633,835 | 20,267,689,608 | IssuesEvent | 2022-02-15 13:37:17 | lowRISC/opentitan | https://api.github.com/repos/lowRISC/opentitan | closed | [sw, dif, aes] The AES DIF is mixing up MODE and OPERATION | Component:SW Priority:P2 Type:Bug IP:aes | The AES DIF is currently mixing up different fields of the AES main control register such as MODE, OPERATION and MANUAL_OPERATION. From the documentation, the meaning of these fields should be pretty clear:
Instead the `configure` function in the AES DIF looks as follows:
```c
/**
* Configures AES. Is used by every `dif_aes_start_<mode>` function.
*
* @param aes AES state data.
* @param transaction Configuration data, common across all Cipher modes.
* @param cipher_mode_val Cipher Mode register write value.
* @return `dif_result_t`.
*/
static dif_result_t configure(const dif_aes_t *aes,
const dif_aes_transaction_t *transaction,
aes_mode_field_val_t cipher_mode_val) { // <--- the MODE is actually already part of the transaction.
aes_key_field_val_t key_len_val = key_to_field(transaction->key_len);
if (key_len_val == kAesKeyFieldValInvalid) {
return kDifError;
}
uint32_t reg =
bitfield_field32_write(0, AES_CTRL_SHADOWED_KEY_LEN_FIELD, key_len_val);
reg = bitfield_field32_write(reg, AES_CTRL_SHADOWED_MODE_FIELD,
cipher_mode_val);
if (transaction->mode == kDifAesModeDecrypt) { // <-- comparing MODE with OPERATION values
reg = bitfield_bit32_write(reg, AES_CTRL_SHADOWED_OPERATION_BIT, true);
} else {
reg = bitfield_bit32_write(reg, AES_CTRL_SHADOWED_OPERATION_BIT, false);
}
if (transaction->operation == kDifAesOperationManual) { // <-- comparing OPERATION with MANUAL_OPERATION values
reg =
bitfield_bit32_write(reg, AES_CTRL_SHADOWED_MANUAL_OPERATION_BIT, true);
} else {
reg = bitfield_bit32_write(reg, AES_CTRL_SHADOWED_MANUAL_OPERATION_BIT,
false);
}
if (transaction->masking == kDifAesMaskingForceZero) {
reg =
bitfield_bit32_write(reg, AES_CTRL_SHADOWED_FORCE_ZERO_MASKS_BIT, true);
} else {
reg = bitfield_bit32_write(reg, AES_CTRL_SHADOWED_FORCE_ZERO_MASKS_BIT,
false);
}
aes_shadowed_write(aes->base_addr, AES_CTRL_SHADOWED_REG_OFFSET, reg);
return kDifOk;
}
```
The following things are wrong
- [ ] The MODE field from the `transaction` isn't used at all. This means we actually can't configure modes other than ECB. What the unit tests do instead is to provide a separate MODE value with the `cipher_mode_val` argument. The unit tests should probably set up separate transactions instead of calling the configure with the same `transaction` argument but varying `cipher_mode_val`.
- [x] The transaction's MODE is compared against OPERATION values to decide what OPERATION to configure. See #10483
- [x] The transaction's OPERATION is compared with MANUAL_OPERATION values to decide what MANUAL_OPERATION to configure. See #10483
- [ ] I has been brought up by @timothytrippel https://github.com/lowRISC/opentitan/pull/10483#discussion_r796076893 that to simplify things we could replace `manual_operation_t` by a `dif_toggle_t`.
I will do a PR to fix 2 and 3 but someone from the software team should probably have a look at the unit tests (Point 1).
| 1.0 | [sw, dif, aes] The AES DIF is mixing up MODE and OPERATION - The AES DIF is currently mixing up different fields of the AES main control register such as MODE, OPERATION and MANUAL_OPERATION. From the documentation, the meaning of these fields should be pretty clear:
Instead the `configure` function in the AES DIF looks as follows:
```c
/**
* Configures AES. Is used by every `dif_aes_start_<mode>` function.
*
* @param aes AES state data.
* @param transaction Configuration data, common across all Cipher modes.
* @param cipher_mode_val Cipher Mode register write value.
* @return `dif_result_t`.
*/
static dif_result_t configure(const dif_aes_t *aes,
const dif_aes_transaction_t *transaction,
aes_mode_field_val_t cipher_mode_val) { // <--- the MODE is actually already part of the transaction.
aes_key_field_val_t key_len_val = key_to_field(transaction->key_len);
if (key_len_val == kAesKeyFieldValInvalid) {
return kDifError;
}
uint32_t reg =
bitfield_field32_write(0, AES_CTRL_SHADOWED_KEY_LEN_FIELD, key_len_val);
reg = bitfield_field32_write(reg, AES_CTRL_SHADOWED_MODE_FIELD,
cipher_mode_val);
if (transaction->mode == kDifAesModeDecrypt) { // <-- comparing MODE with OPERATION values
reg = bitfield_bit32_write(reg, AES_CTRL_SHADOWED_OPERATION_BIT, true);
} else {
reg = bitfield_bit32_write(reg, AES_CTRL_SHADOWED_OPERATION_BIT, false);
}
if (transaction->operation == kDifAesOperationManual) { // <-- comparing OPERATION with MANUAL_OPERATION values
reg =
bitfield_bit32_write(reg, AES_CTRL_SHADOWED_MANUAL_OPERATION_BIT, true);
} else {
reg = bitfield_bit32_write(reg, AES_CTRL_SHADOWED_MANUAL_OPERATION_BIT,
false);
}
if (transaction->masking == kDifAesMaskingForceZero) {
reg =
bitfield_bit32_write(reg, AES_CTRL_SHADOWED_FORCE_ZERO_MASKS_BIT, true);
} else {
reg = bitfield_bit32_write(reg, AES_CTRL_SHADOWED_FORCE_ZERO_MASKS_BIT,
false);
}
aes_shadowed_write(aes->base_addr, AES_CTRL_SHADOWED_REG_OFFSET, reg);
return kDifOk;
}
```
The following things are wrong
- [ ] The MODE field from the `transaction` isn't used at all. This means we actually can't configure modes other than ECB. What the unit tests do instead is to provide a separate MODE value with the `cipher_mode_val` argument. The unit tests should probably set up separate transactions instead of calling the configure with the same `transaction` argument but varying `cipher_mode_val`.
- [x] The transaction's MODE is compared against OPERATION values to decide what OPERATION to configure. See #10483
- [x] The transaction's OPERATION is compared with MANUAL_OPERATION values to decide what MANUAL_OPERATION to configure. See #10483
- [ ] I has been brought up by @timothytrippel https://github.com/lowRISC/opentitan/pull/10483#discussion_r796076893 that to simplify things we could replace `manual_operation_t` by a `dif_toggle_t`.
I will do a PR to fix 2 and 3 but someone from the software team should probably have a look at the unit tests (Point 1).
| priority | the aes dif is mixing up mode and operation the aes dif is currently mixing up different fields of the aes main control register such as mode operation and manual operation from the documentation the meaning of these fields should be pretty clear instead the configure function in the aes dif looks as follows c configures aes is used by every dif aes start function param aes aes state data param transaction configuration data common across all cipher modes param cipher mode val cipher mode register write value return dif result t static dif result t configure const dif aes t aes const dif aes transaction t transaction aes mode field val t cipher mode val the mode is actually already part of the transaction aes key field val t key len val key to field transaction key len if key len val kaeskeyfieldvalinvalid return kdiferror t reg bitfield write aes ctrl shadowed key len field key len val reg bitfield write reg aes ctrl shadowed mode field cipher mode val if transaction mode kdifaesmodedecrypt comparing mode with operation values reg bitfield write reg aes ctrl shadowed operation bit true else reg bitfield write reg aes ctrl shadowed operation bit false if transaction operation kdifaesoperationmanual comparing operation with manual operation values reg bitfield write reg aes ctrl shadowed manual operation bit true else reg bitfield write reg aes ctrl shadowed manual operation bit false if transaction masking kdifaesmaskingforcezero reg bitfield write reg aes ctrl shadowed force zero masks bit true else reg bitfield write reg aes ctrl shadowed force zero masks bit false aes shadowed write aes base addr aes ctrl shadowed reg offset reg return kdifok the following things are wrong the mode field from the transaction isn t used at all this means we actually can t configure modes other than ecb what the unit tests do instead is to provide a separate mode value with the cipher mode val argument the unit tests should probably set up separate transactions instead of calling the configure with the same transaction argument but varying cipher mode val the transaction s mode is compared against operation values to decide what operation to configure see the transaction s operation is compared with manual operation values to decide what manual operation to configure see i has been brought up by timothytrippel that to simplify things we could replace manual operation t by a dif toggle t i will do a pr to fix and but someone from the software team should probably have a look at the unit tests point | 1 |
113,897 | 24,508,789,636 | IssuesEvent | 2022-10-10 19:06:12 | creativecommons/search | https://api.github.com/repos/creativecommons/search | closed | [Change] Rename project to CC Search Portal, all text occurrences | good first issue 🟨 priority: medium 🚦 status: awaiting triage 🛠 goal: fix 💻 aspect: code 🕹 aspect: interface | ## Description
The project known as CC Search, CC Meta Search, Old Search, and Legacy CC Search needs all text occurrences to be changed to the new title: `CC Search Portal`.
Additionally, the wording `oldsearch.creativecommons.org` in the footer, needs to be changed to `CC Search Portal`
## Resolution
<!-- Replace the [ ] with [x] to check the box. -->
- [ ] I would be interested in resolving this bug.
| 1.0 | [Change] Rename project to CC Search Portal, all text occurrences - ## Description
The project known as CC Search, CC Meta Search, Old Search, and Legacy CC Search needs all text occurrences to be changed to the new title: `CC Search Portal`.
Additionally, the wording `oldsearch.creativecommons.org` in the footer, needs to be changed to `CC Search Portal`
## Resolution
<!-- Replace the [ ] with [x] to check the box. -->
- [ ] I would be interested in resolving this bug.
| non_priority | rename project to cc search portal all text occurrences description the project known as cc search cc meta search old search and legacy cc search needs all text occurrences to be changed to the new title cc search portal additionally the wording oldsearch creativecommons org in the footer needs to be changed to cc search portal resolution i would be interested in resolving this bug | 0 |
284,328 | 8,737,337,864 | IssuesEvent | 2018-12-11 22:15:28 | aowen87/TicketTester | https://api.github.com/repos/aowen87/TicketTester | closed | Xrayimage query doesn't support non-square images | bug crash likelihood medium priority reviewed severity high wontfix wrong results | Joshua Kallman reported that when he specifies a non-square image, he still ends up getting a square image and the image is distorted. I haven't actually verified this yet.
-----------------------REDMINE MIGRATION-----------------------
This ticket was migrated from Redmine. As such, not all
information was able to be captured in the transition. Below is
a complete record of the original redmine ticket.
Ticket number: 1217
Status: Rejected
Project: VisIt
Tracker: Bug
Priority: High
Subject: Xrayimage query doesn't support non-square images
Assigned to:
Category:
Target version:
Author: Eric Brugger
Start: 10/17/2012
Due date:
% Done: 0
Estimated time: 2.0
Created: 10/17/2012 11:20 am
Updated: 01/29/2013 05:24 pm
Likelihood: 3 - Occasional
Severity: 4 - Crash / Wrong Results
Found in version: 2.5.2
Impact:
Expected Use:
OS: All
Support Group: Any
Description:
Joshua Kallman reported that when he specifies a non-square image, he still ends up getting a square image and the image is distorted. I haven't actually verified this yet.
Comments:
This is not a bug and works as expected.
| 1.0 | Xrayimage query doesn't support non-square images - Joshua Kallman reported that when he specifies a non-square image, he still ends up getting a square image and the image is distorted. I haven't actually verified this yet.
-----------------------REDMINE MIGRATION-----------------------
This ticket was migrated from Redmine. As such, not all
information was able to be captured in the transition. Below is
a complete record of the original redmine ticket.
Ticket number: 1217
Status: Rejected
Project: VisIt
Tracker: Bug
Priority: High
Subject: Xrayimage query doesn't support non-square images
Assigned to:
Category:
Target version:
Author: Eric Brugger
Start: 10/17/2012
Due date:
% Done: 0
Estimated time: 2.0
Created: 10/17/2012 11:20 am
Updated: 01/29/2013 05:24 pm
Likelihood: 3 - Occasional
Severity: 4 - Crash / Wrong Results
Found in version: 2.5.2
Impact:
Expected Use:
OS: All
Support Group: Any
Description:
Joshua Kallman reported that when he specifies a non-square image, he still ends up getting a square image and the image is distorted. I haven't actually verified this yet.
Comments:
This is not a bug and works as expected.
| priority | xrayimage query doesn t support non square images joshua kallman reported that when he specifies a non square image he still ends up getting a square image and the image is distorted i haven t actually verified this yet redmine migration this ticket was migrated from redmine as such not all information was able to be captured in the transition below is a complete record of the original redmine ticket ticket number status rejected project visit tracker bug priority high subject xrayimage query doesn t support non square images assigned to category target version author eric brugger start due date done estimated time created am updated pm likelihood occasional severity crash wrong results found in version impact expected use os all support group any description joshua kallman reported that when he specifies a non square image he still ends up getting a square image and the image is distorted i haven t actually verified this yet comments this is not a bug and works as expected | 1 |
434,648 | 30,460,303,057 | IssuesEvent | 2023-07-17 06:13:14 | teksi/Home | https://api.github.com/repos/teksi/Home | opened | Procedure, rights and prerequisites to create Releases | documentation feature Sustainability | **Description**
On all TEKSI modules, we should be able :
- [ ] To see the steps of a release creation
- [ ] To know every prerequisites (rights, access, software, ... )
- [ ] To train someone to become the Release Manager
The Release Manager(s) of every TEKSI module should be able to create test releases and production releases.
**Related issues**
- [ ] Issue
**Related pull requests**
- [ ] PR
| 1.0 | Procedure, rights and prerequisites to create Releases - **Description**
On all TEKSI modules, we should be able :
- [ ] To see the steps of a release creation
- [ ] To know every prerequisites (rights, access, software, ... )
- [ ] To train someone to become the Release Manager
The Release Manager(s) of every TEKSI module should be able to create test releases and production releases.
**Related issues**
- [ ] Issue
**Related pull requests**
- [ ] PR
| non_priority | procedure rights and prerequisites to create releases description on all teksi modules we should be able to see the steps of a release creation to know every prerequisites rights access software to train someone to become the release manager the release manager s of every teksi module should be able to create test releases and production releases related issues issue related pull requests pr | 0 |
561,063 | 16,610,474,911 | IssuesEvent | 2021-06-02 10:50:51 | Systems-Learning-and-Development-Lab/MMM | https://api.github.com/repos/Systems-Learning-and-Development-Lab/MMM | closed | Molecules' shape | priority-high | 1. Enable changing properties only after "New task".
2. If user try changing, have an alert: ניתן לשנות תכונות של כדורים רק אחרי לחיצה על כפתור משימה חדשה.
3. The delete balls button does not work, I think it is after changing the shape (maybe it "remembers" the previuos population)
@Ron-Teller
| 1.0 | Molecules' shape - 1. Enable changing properties only after "New task".
2. If user try changing, have an alert: ניתן לשנות תכונות של כדורים רק אחרי לחיצה על כפתור משימה חדשה.
3. The delete balls button does not work, I think it is after changing the shape (maybe it "remembers" the previuos population)
@Ron-Teller
| priority | molecules shape enable changing properties only after new task if user try changing have an alert ניתן לשנות תכונות של כדורים רק אחרי לחיצה על כפתור משימה חדשה the delete balls button does not work i think it is after changing the shape maybe it remembers the previuos population ron teller | 1 |
80,991 | 7,762,819,048 | IssuesEvent | 2018-06-01 14:39:54 | lintol/lintol-frontend | https://api.github.com/repos/lintol/lintol-frontend | closed | Sign in - CKAN button goes outside container box | 0.12 bug ready for test | When you click on the "Sign in with CKAN" button, the dropdown for the CKAN server appears but the containing white box doesn't expand so the the button gets pushed outside it. Also the button changes size which seems odd.
| 1.0 | Sign in - CKAN button goes outside container box - When you click on the "Sign in with CKAN" button, the dropdown for the CKAN server appears but the containing white box doesn't expand so the the button gets pushed outside it. Also the button changes size which seems odd.
| non_priority | sign in ckan button goes outside container box when you click on the sign in with ckan button the dropdown for the ckan server appears but the containing white box doesn t expand so the the button gets pushed outside it also the button changes size which seems odd | 0 |
130,606 | 5,118,318,495 | IssuesEvent | 2017-01-08 03:37:21 | Ks89/My-MEAN-website-client | https://api.github.com/repos/Ks89/My-MEAN-website-client | closed | Remove all `export default` to be able to try AOT | comp:client effort1:easy (hours) priority:low type:refactor | Remove all `export default` to be able to try AOT | 1.0 | Remove all `export default` to be able to try AOT - Remove all `export default` to be able to try AOT | priority | remove all export default to be able to try aot remove all export default to be able to try aot | 1 |
47,685 | 19,698,424,989 | IssuesEvent | 2022-01-12 14:28:03 | hashicorp/terraform-provider-azurerm | https://api.github.com/repos/hashicorp/terraform-provider-azurerm | closed | azurerm_log_analytics_datasource_windows_performance_counter regression in 2.89.0 | bug regression service/log-analytics | upgrading to 2.89.0 (from, eg, 2.88.1) fails on azurerm_log_analytics_datasource_windows_performance_counter
with
Error: ID was missing the `dataSources` element
is this a regression in the provider or the documentation?
previously working module
```
resource "azurerm_log_analytics_datasource_windows_performance_counter" "perf" {
count = length(local.windows_perf_counters_map)
name = format("%s-%s", local.windows_perf_counters_map[count.index].object_name, replace(replace(replace(replace(local.windows_perf_counters_map[count.index].counter_name, "/ ()/", ""), "%", "Percent"), "/", "Per"), "&", "And"))
resource_group_name = local.windows_perf_counters_map[count.index].resource_group_name
workspace_name = local.windows_perf_counters_map[count.index].workspace_name
object_name = local.windows_perf_counters_map[count.index].object_name
instance_name = local.windows_perf_counters_map[count.index].instance_name
counter_name = local.windows_perf_counters_map[count.index].counter_name
interval_seconds = local.windows_perf_counters_map[count.index].interval_seconds
depends_on = [azurerm_log_analytics_workspace.law]
} | 1.0 | azurerm_log_analytics_datasource_windows_performance_counter regression in 2.89.0 - upgrading to 2.89.0 (from, eg, 2.88.1) fails on azurerm_log_analytics_datasource_windows_performance_counter
with
Error: ID was missing the `dataSources` element
is this a regression in the provider or the documentation?
previously working module
```
resource "azurerm_log_analytics_datasource_windows_performance_counter" "perf" {
count = length(local.windows_perf_counters_map)
name = format("%s-%s", local.windows_perf_counters_map[count.index].object_name, replace(replace(replace(replace(local.windows_perf_counters_map[count.index].counter_name, "/ ()/", ""), "%", "Percent"), "/", "Per"), "&", "And"))
resource_group_name = local.windows_perf_counters_map[count.index].resource_group_name
workspace_name = local.windows_perf_counters_map[count.index].workspace_name
object_name = local.windows_perf_counters_map[count.index].object_name
instance_name = local.windows_perf_counters_map[count.index].instance_name
counter_name = local.windows_perf_counters_map[count.index].counter_name
interval_seconds = local.windows_perf_counters_map[count.index].interval_seconds
depends_on = [azurerm_log_analytics_workspace.law]
} | non_priority | azurerm log analytics datasource windows performance counter regression in upgrading to from eg fails on azurerm log analytics datasource windows performance counter with error id was missing the datasources element is this a regression in the provider or the documentation previously working module resource azurerm log analytics datasource windows performance counter perf count length local windows perf counters map name format s s local windows perf counters map object name replace replace replace replace local windows perf counters map counter name percent per and resource group name local windows perf counters map resource group name workspace name local windows perf counters map workspace name object name local windows perf counters map object name instance name local windows perf counters map instance name counter name local windows perf counters map counter name interval seconds local windows perf counters map interval seconds depends on | 0 |
270,471 | 28,960,724,686 | IssuesEvent | 2023-05-10 02:04:55 | mattdanielbrown/primed | https://api.github.com/repos/mattdanielbrown/primed | closed | CVE-2021-29059 (High) detected in is-svg-3.0.0.tgz, is-svg-4.2.1.tgz - autoclosed | Mend: dependency security vulnerability | ## CVE-2021-29059 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>is-svg-3.0.0.tgz</b>, <b>is-svg-4.2.1.tgz</b></p></summary>
<p>
<details><summary><b>is-svg-3.0.0.tgz</b></p></summary>
<p>Check if a string or buffer is SVG</p>
<p>Library home page: <a href="https://registry.npmjs.org/is-svg/-/is-svg-3.0.0.tgz">https://registry.npmjs.org/is-svg/-/is-svg-3.0.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/postcss-svgo/node_modules/is-svg/package.json</p>
<p>
Dependency Hierarchy:
- cssnano-4.1.10.tgz (Root Library)
- cssnano-preset-default-4.0.7.tgz
- postcss-svgo-4.0.2.tgz
- :x: **is-svg-3.0.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>is-svg-4.2.1.tgz</b></p></summary>
<p>Check if a string or buffer is SVG</p>
<p>Library home page: <a href="https://registry.npmjs.org/is-svg/-/is-svg-4.2.1.tgz">https://registry.npmjs.org/is-svg/-/is-svg-4.2.1.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/is-svg/package.json</p>
<p>
Dependency Hierarchy:
- gulp-imagemin-6.2.0.tgz (Root Library)
- imagemin-svgo-7.1.0.tgz
- :x: **is-svg-4.2.1.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/mattdanielbrown/primed/commit/4c04dadd915d6323f64b1d98dcdbc29df3b57cbb">4c04dadd915d6323f64b1d98dcdbc29df3b57cbb</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 vulnerability was discovered in IS-SVG version 2.1.0 to 4.2.2 and below where a Regular Expression Denial of Service (ReDOS) occurs if the application is provided and checks a crafted invalid SVG string.
<p>Publish Date: 2021-06-21
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-29059>CVE-2021-29059</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>Release Date: 2021-06-21</p>
<p>Fix Resolution (is-svg): 4.3.0</p>
<p>Direct dependency fix Resolution (cssnano): 4.1.11</p><p>Fix Resolution (is-svg): 4.3.0</p>
<p>Direct dependency fix Resolution (gulp-imagemin): 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-29059 (High) detected in is-svg-3.0.0.tgz, is-svg-4.2.1.tgz - autoclosed - ## CVE-2021-29059 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>is-svg-3.0.0.tgz</b>, <b>is-svg-4.2.1.tgz</b></p></summary>
<p>
<details><summary><b>is-svg-3.0.0.tgz</b></p></summary>
<p>Check if a string or buffer is SVG</p>
<p>Library home page: <a href="https://registry.npmjs.org/is-svg/-/is-svg-3.0.0.tgz">https://registry.npmjs.org/is-svg/-/is-svg-3.0.0.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/postcss-svgo/node_modules/is-svg/package.json</p>
<p>
Dependency Hierarchy:
- cssnano-4.1.10.tgz (Root Library)
- cssnano-preset-default-4.0.7.tgz
- postcss-svgo-4.0.2.tgz
- :x: **is-svg-3.0.0.tgz** (Vulnerable Library)
</details>
<details><summary><b>is-svg-4.2.1.tgz</b></p></summary>
<p>Check if a string or buffer is SVG</p>
<p>Library home page: <a href="https://registry.npmjs.org/is-svg/-/is-svg-4.2.1.tgz">https://registry.npmjs.org/is-svg/-/is-svg-4.2.1.tgz</a></p>
<p>Path to dependency file: /package.json</p>
<p>Path to vulnerable library: /node_modules/is-svg/package.json</p>
<p>
Dependency Hierarchy:
- gulp-imagemin-6.2.0.tgz (Root Library)
- imagemin-svgo-7.1.0.tgz
- :x: **is-svg-4.2.1.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/mattdanielbrown/primed/commit/4c04dadd915d6323f64b1d98dcdbc29df3b57cbb">4c04dadd915d6323f64b1d98dcdbc29df3b57cbb</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 vulnerability was discovered in IS-SVG version 2.1.0 to 4.2.2 and below where a Regular Expression Denial of Service (ReDOS) occurs if the application is provided and checks a crafted invalid SVG string.
<p>Publish Date: 2021-06-21
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-29059>CVE-2021-29059</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>Release Date: 2021-06-21</p>
<p>Fix Resolution (is-svg): 4.3.0</p>
<p>Direct dependency fix Resolution (cssnano): 4.1.11</p><p>Fix Resolution (is-svg): 4.3.0</p>
<p>Direct dependency fix Resolution (gulp-imagemin): 7.0.0</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in is svg tgz is svg tgz autoclosed cve high severity vulnerability vulnerable libraries is svg tgz is svg tgz is svg tgz check if a string or buffer is svg library home page a href path to dependency file package json path to vulnerable library node modules postcss svgo node modules is svg package json dependency hierarchy cssnano tgz root library cssnano preset default tgz postcss svgo tgz x is svg tgz vulnerable library is svg tgz check if a string or buffer is svg library home page a href path to dependency file package json path to vulnerable library node modules is svg package json dependency hierarchy gulp imagemin tgz root library imagemin svgo tgz x is svg tgz vulnerable library found in head commit a href found in base branch master vulnerability details a vulnerability was discovered in is svg version to and below where a regular expression denial of service redos occurs if the application is provided and checks a crafted invalid svg 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 release date fix resolution is svg direct dependency fix resolution cssnano fix resolution is svg direct dependency fix resolution gulp imagemin step up your open source security game with mend | 0 |
7,971 | 2,611,070,318 | IssuesEvent | 2015-02-27 00:32:50 | alistairreilly/andors-trail | https://api.github.com/repos/alistairreilly/andors-trail | closed | Loading game with selected movement destination in combat | auto-migrated Milestone-0.6.12 Priority-Low Type-Defect | ```
What steps will reproduce the problem?
1. Engage in combat
2. Long-click a tile to flee to (but don't flee)
3. Save the game (or exit to title screen)
4. Load the savegame
5. Notice how the combat bar is incorrectly populated. For example, the attack
button displays "Attack (%1$d AP)" instead of "Move (6AP)", and the monster HP
bar is visible even though no monster is selected.
Confirmed on v0.6.11 on Google Play.
```
Original issue reported on code.google.com by `oskar.wi...@gmail.com` on 12 Jun 2012 at 8:31 | 1.0 | Loading game with selected movement destination in combat - ```
What steps will reproduce the problem?
1. Engage in combat
2. Long-click a tile to flee to (but don't flee)
3. Save the game (or exit to title screen)
4. Load the savegame
5. Notice how the combat bar is incorrectly populated. For example, the attack
button displays "Attack (%1$d AP)" instead of "Move (6AP)", and the monster HP
bar is visible even though no monster is selected.
Confirmed on v0.6.11 on Google Play.
```
Original issue reported on code.google.com by `oskar.wi...@gmail.com` on 12 Jun 2012 at 8:31 | non_priority | loading game with selected movement destination in combat what steps will reproduce the problem engage in combat long click a tile to flee to but don t flee save the game or exit to title screen load the savegame notice how the combat bar is incorrectly populated for example the attack button displays attack d ap instead of move and the monster hp bar is visible even though no monster is selected confirmed on on google play original issue reported on code google com by oskar wi gmail com on jun at | 0 |
25,003 | 18,024,091,998 | IssuesEvent | 2021-09-17 00:31:40 | APSIMInitiative/ApsimX | https://api.github.com/repos/APSIMInitiative/ApsimX | closed | Refactor and implement new list filtering and sorting by properties and attributes | interface/infrastructure refactor CLEM | After the initial release and user requested improvements made to CLEM it needs a code clean up and some improvements with respect to memory and performance. This includes better management of individuals (ruminant and labour) throughout in preparation for the new implementation of generic filtering and sorting of lists for activities that allows the user to filter and sort on any property or attributes tags assigned to individuals. | 1.0 | Refactor and implement new list filtering and sorting by properties and attributes - After the initial release and user requested improvements made to CLEM it needs a code clean up and some improvements with respect to memory and performance. This includes better management of individuals (ruminant and labour) throughout in preparation for the new implementation of generic filtering and sorting of lists for activities that allows the user to filter and sort on any property or attributes tags assigned to individuals. | non_priority | refactor and implement new list filtering and sorting by properties and attributes after the initial release and user requested improvements made to clem it needs a code clean up and some improvements with respect to memory and performance this includes better management of individuals ruminant and labour throughout in preparation for the new implementation of generic filtering and sorting of lists for activities that allows the user to filter and sort on any property or attributes tags assigned to individuals | 0 |
120,442 | 15,766,750,620 | IssuesEvent | 2021-03-31 15:22:17 | the-bat-signal/rooted | https://api.github.com/repos/the-bat-signal/rooted | reopened | Optimize Geolocate feature | Tier 1 bug ~*~Design/Aesthetic~*~ | - [ ] No auto geolocate when you click around on map
- per Code Review:
- make this more user-friendly; filters? toggles? “this is what you see now”, “this is what you should acknowledge”
makes this more digestible for users
could use useEffect to not have it auto-zoom as well because useEffect encompasses componentDidMount too
check the radius of the area you’re around based on Geolocate
a lot more digestible to go from in to out as opposed to from out to in
- tilt the map so that the raised polygons are somewhat visible ~ UX | 1.0 | Optimize Geolocate feature - - [ ] No auto geolocate when you click around on map
- per Code Review:
- make this more user-friendly; filters? toggles? “this is what you see now”, “this is what you should acknowledge”
makes this more digestible for users
could use useEffect to not have it auto-zoom as well because useEffect encompasses componentDidMount too
check the radius of the area you’re around based on Geolocate
a lot more digestible to go from in to out as opposed to from out to in
- tilt the map so that the raised polygons are somewhat visible ~ UX | non_priority | optimize geolocate feature no auto geolocate when you click around on map per code review make this more user friendly filters toggles “this is what you see now” “this is what you should acknowledge” makes this more digestible for users could use useeffect to not have it auto zoom as well because useeffect encompasses componentdidmount too check the radius of the area you’re around based on geolocate a lot more digestible to go from in to out as opposed to from out to in tilt the map so that the raised polygons are somewhat visible ux | 0 |
265,093 | 28,241,167,271 | IssuesEvent | 2023-04-06 07:17:11 | hshivhare67/platform_external_tcpdump_AOSP10_r33_4.9.2-_CVE-2018-14463 | https://api.github.com/repos/hshivhare67/platform_external_tcpdump_AOSP10_r33_4.9.2-_CVE-2018-14463 | closed | CVE-2019-15166 (High) detected in platform_external_tcpdumpandroid-mainline-12.0.0_r17 - autoclosed | Mend: dependency security vulnerability | ## CVE-2019-15166 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>platform_external_tcpdumpandroid-mainline-12.0.0_r17</b></p></summary>
<p>
<p>Library home page: <a href=https://github.com/aosp-mirror/platform_external_tcpdump.git>https://github.com/aosp-mirror/platform_external_tcpdump.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/hshivhare67/platform_external_tcpdump_AOSP10_r33_4.9.2-_CVE-2018-14463/commit/bbbeaf9401e962d6d2f47242b486e07478f38224">bbbeaf9401e962d6d2f47242b486e07478f38224</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 (1)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/print-lmp.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>
lmp_print_data_link_subobjs() in print-lmp.c in tcpdump before 4.9.3 lacks certain bounds checks.
<p>Publish Date: 2019-10-03
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-15166>CVE-2019-15166</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-2019-15166">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-15166</a></p>
<p>Release Date: 2019-10-03</p>
<p>Fix Resolution: 4.9.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-2019-15166 (High) detected in platform_external_tcpdumpandroid-mainline-12.0.0_r17 - autoclosed - ## CVE-2019-15166 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>platform_external_tcpdumpandroid-mainline-12.0.0_r17</b></p></summary>
<p>
<p>Library home page: <a href=https://github.com/aosp-mirror/platform_external_tcpdump.git>https://github.com/aosp-mirror/platform_external_tcpdump.git</a></p>
<p>Found in HEAD commit: <a href="https://github.com/hshivhare67/platform_external_tcpdump_AOSP10_r33_4.9.2-_CVE-2018-14463/commit/bbbeaf9401e962d6d2f47242b486e07478f38224">bbbeaf9401e962d6d2f47242b486e07478f38224</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 (1)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/print-lmp.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>
lmp_print_data_link_subobjs() in print-lmp.c in tcpdump before 4.9.3 lacks certain bounds checks.
<p>Publish Date: 2019-10-03
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2019-15166>CVE-2019-15166</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-2019-15166">https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-15166</a></p>
<p>Release Date: 2019-10-03</p>
<p>Fix Resolution: 4.9.3</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | cve high detected in platform external tcpdumpandroid mainline autoclosed cve high severity vulnerability vulnerable library platform external tcpdumpandroid mainline library home page a href found in head commit a href found in base branch main vulnerable source files print lmp c vulnerability details lmp print data link subobjs in print lmp c in tcpdump before lacks certain bounds checks 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 mend | 0 |
18,765 | 24,669,222,636 | IssuesEvent | 2022-10-18 12:40:31 | MasterPlayer/adxl345-sv | https://api.github.com/repos/MasterPlayer/adxl345-sv | opened | FIFO interrupt processing support | enhancement hardware process software process | There are needed for special processing for FIFO interrupts, because sw must read series of samples.
Possible mechanism may be realized as next scheme: | 2.0 | FIFO interrupt processing support - There are needed for special processing for FIFO interrupts, because sw must read series of samples.
Possible mechanism may be realized as next scheme: | non_priority | fifo interrupt processing support there are needed for special processing for fifo interrupts because sw must read series of samples possible mechanism may be realized as next scheme | 0 |
214,198 | 24,040,651,478 | IssuesEvent | 2022-09-16 01:11:07 | AlexRogalskiy/weather-sprites | https://api.github.com/repos/AlexRogalskiy/weather-sprites | opened | WS-2022-0239 (Medium) detected in parse-url-6.0.0.tgz | security vulnerability | ## WS-2022-0239 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>parse-url-6.0.0.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-6.0.0.tgz">https://registry.npmjs.org/parse-url/-/parse-url-6.0.0.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-4.0.0.tgz (Root Library)
- version-4.0.0.tgz
- github-client-4.0.0.tgz
- git-url-parse-11.6.0.tgz
- git-up-4.0.5.tgz
- :x: **parse-url-6.0.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/AlexRogalskiy/weather-sprites/commit/52693f2ddee1582e6dd5ac2903f9f26f11e0948f">52693f2ddee1582e6dd5ac2903f9f26f11e0948f</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>
Cross-Site Scripting via Improper Input Validation (parser differential) in parse-url before 8.0.0.
Through this vulnerability, an attacker is capable to execute malicious JS codes.
<p>Publish Date: 2022-07-02
<p>URL: <a href=https://github.com/ionicabizau/parse-url/commit/b88c81df8f4c5168af454eaa4f92afa9349e4e13>WS-2022-0239</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://huntr.dev/bounties/5fa3115f-5c97-4928-874c-3cc6302e154e">https://huntr.dev/bounties/5fa3115f-5c97-4928-874c-3cc6302e154e</a></p>
<p>Release Date: 2022-07-02</p>
<p>Fix Resolution (parse-url): 8.0.0</p>
<p>Direct dependency fix Resolution (lerna): 5.1.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 | WS-2022-0239 (Medium) detected in parse-url-6.0.0.tgz - ## WS-2022-0239 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>parse-url-6.0.0.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-6.0.0.tgz">https://registry.npmjs.org/parse-url/-/parse-url-6.0.0.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-4.0.0.tgz (Root Library)
- version-4.0.0.tgz
- github-client-4.0.0.tgz
- git-url-parse-11.6.0.tgz
- git-up-4.0.5.tgz
- :x: **parse-url-6.0.0.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/AlexRogalskiy/weather-sprites/commit/52693f2ddee1582e6dd5ac2903f9f26f11e0948f">52693f2ddee1582e6dd5ac2903f9f26f11e0948f</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>
Cross-Site Scripting via Improper Input Validation (parser differential) in parse-url before 8.0.0.
Through this vulnerability, an attacker is capable to execute malicious JS codes.
<p>Publish Date: 2022-07-02
<p>URL: <a href=https://github.com/ionicabizau/parse-url/commit/b88c81df8f4c5168af454eaa4f92afa9349e4e13>WS-2022-0239</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://huntr.dev/bounties/5fa3115f-5c97-4928-874c-3cc6302e154e">https://huntr.dev/bounties/5fa3115f-5c97-4928-874c-3cc6302e154e</a></p>
<p>Release Date: 2022-07-02</p>
<p>Fix Resolution (parse-url): 8.0.0</p>
<p>Direct dependency fix Resolution (lerna): 5.1.8</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_priority | ws medium detected in parse url tgz ws medium 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 master vulnerability details cross site scripting via improper input validation parser differential in parse url before through this vulnerability an attacker is capable to execute malicious js codes 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 parse url direct dependency fix resolution lerna step up your open source security game with mend | 0 |
813,301 | 30,452,695,712 | IssuesEvent | 2023-07-16 13:53:45 | priyankarpal/ProjectsHut | https://api.github.com/repos/priyankarpal/ProjectsHut | closed | chore: project addition by sahil chalke | good first issue 🟩 priority: low 🏁 status: ready for dev projects addition | ### Add a new project to the list
i want to few of my projects
### Record
- [X] I agree to follow this project's Code of Conduct
- [X] I want to work on this issue | 1.0 | chore: project addition by sahil chalke - ### Add a new project to the list
i want to few of my projects
### Record
- [X] I agree to follow this project's Code of Conduct
- [X] I want to work on this issue | priority | chore project addition by sahil chalke add a new project to the list i want to few of my projects record i agree to follow this project s code of conduct i want to work on this issue | 1 |
292,601 | 25,225,234,238 | IssuesEvent | 2022-11-14 15:31:36 | wazuh/wazuh | https://api.github.com/repos/wazuh/wazuh | opened | 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 | --- |
| ⚫ | Ubuntu Bionic | --- |
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 | --- |
| ⚫ | Ubuntu Bionic | --- |
Status legend:
⚫ - Pending/In progress
⚪ - Skipped
🔴 - Rejected
🟢 - Approved
| non_priority | 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 |
526,273 | 15,285,105,960 | IssuesEvent | 2021-02-23 13:08:16 | onaio/reveal-frontend | https://api.github.com/repos/onaio/reveal-frontend | closed | Allow user to export student list at any level of the location hierarchy | Priority: High Reveal-NTD | The "Export Student List" feature is accessed by navigating to "admin" --> "clients."
Right now, when a user tries to download the student list, they are forced to click all the way through the location hierarchy in the dropdown to choose only the school level.
<img width="1077" alt="Screen Shot 2021-02-09 at 8 17 58 AM" src="https://user-images.githubusercontent.com/12836913/107393172-556d9c80-6aaf-11eb-9b80-182408f64f6e.png">
The expected behavior is for the user to be able to select any level of the hierarchy in the dropdown, whether it is a region, a district, or a school. If they want to be able to export all of the children in their campaign, we don't want them to have to go school by school in order to do so.
@rkodev has already completed the backend work on his side for allow for these changes to be made. He'll add some more context in the comments below.
| 1.0 | Allow user to export student list at any level of the location hierarchy - The "Export Student List" feature is accessed by navigating to "admin" --> "clients."
Right now, when a user tries to download the student list, they are forced to click all the way through the location hierarchy in the dropdown to choose only the school level.
<img width="1077" alt="Screen Shot 2021-02-09 at 8 17 58 AM" src="https://user-images.githubusercontent.com/12836913/107393172-556d9c80-6aaf-11eb-9b80-182408f64f6e.png">
The expected behavior is for the user to be able to select any level of the hierarchy in the dropdown, whether it is a region, a district, or a school. If they want to be able to export all of the children in their campaign, we don't want them to have to go school by school in order to do so.
@rkodev has already completed the backend work on his side for allow for these changes to be made. He'll add some more context in the comments below.
| priority | allow user to export student list at any level of the location hierarchy the export student list feature is accessed by navigating to admin clients right now when a user tries to download the student list they are forced to click all the way through the location hierarchy in the dropdown to choose only the school level img width alt screen shot at am src the expected behavior is for the user to be able to select any level of the hierarchy in the dropdown whether it is a region a district or a school if they want to be able to export all of the children in their campaign we don t want them to have to go school by school in order to do so rkodev has already completed the backend work on his side for allow for these changes to be made he ll add some more context in the comments below | 1 |
22,805 | 20,202,718,148 | IssuesEvent | 2022-02-11 16:47:33 | godotengine/godot | https://api.github.com/repos/godotengine/godot | closed | Select current project does nothing if scene is not saved. | bug topic:editor confirmed usability | ### Godot version
3.4.2
### System information
Manjaro, Vega 8 with Ryzen 3200 G
### Issue description
When you hit play for the first time, a window pop up appears if default scene is not selected.
However the select current button does nothing if the current scene being used is not saved yet.
### Steps to reproduce
Create new project.
Create new scene.
Hit play without saving the scene.
Hit select current scene button.
### Minimal reproduction project
_No response_ | True | Select current project does nothing if scene is not saved. - ### Godot version
3.4.2
### System information
Manjaro, Vega 8 with Ryzen 3200 G
### Issue description
When you hit play for the first time, a window pop up appears if default scene is not selected.
However the select current button does nothing if the current scene being used is not saved yet.
### Steps to reproduce
Create new project.
Create new scene.
Hit play without saving the scene.
Hit select current scene button.
### Minimal reproduction project
_No response_ | non_priority | select current project does nothing if scene is not saved godot version system information manjaro vega with ryzen g issue description when you hit play for the first time a window pop up appears if default scene is not selected however the select current button does nothing if the current scene being used is not saved yet steps to reproduce create new project create new scene hit play without saving the scene hit select current scene button minimal reproduction project no response | 0 |
388,880 | 26,785,956,247 | IssuesEvent | 2023-02-01 02:47:28 | idaholab/moose | https://api.github.com/repos/idaholab/moose | closed | Update NCRC Application page(s) | T: task C: Documentation | ## Reason
There still exists some TLC needed. We need to update the page folks land on, to include all applications up front, with itemized level access links.
## Design
Modify the markdown accordingly, to include all applications on one page (the first page), with itemized level access instructions for each.
## Impact
A better end-user experience
| 1.0 | Update NCRC Application page(s) - ## Reason
There still exists some TLC needed. We need to update the page folks land on, to include all applications up front, with itemized level access links.
## Design
Modify the markdown accordingly, to include all applications on one page (the first page), with itemized level access instructions for each.
## Impact
A better end-user experience
| non_priority | update ncrc application page s reason there still exists some tlc needed we need to update the page folks land on to include all applications up front with itemized level access links design modify the markdown accordingly to include all applications on one page the first page with itemized level access instructions for each impact a better end user experience | 0 |
694,284 | 23,809,221,193 | IssuesEvent | 2022-09-04 14:03:31 | gotti/meshover | https://api.github.com/repos/gotti/meshover | closed | ダッシュボード作成 | priority/1 | ダッシュボードほしい、見栄えとトラシュー効率のため。
コンポーネントをどこまで共通にする？
- 今のserverに送るのが一番楽だけど全然やること違う
- 別にダッシュボードサーバを立ててgRPCでpush型な感じで収集しようかな
- ダッシュボードサーバにprometheus exporterもあると嬉しいね
収集するもの
- ほかの全ノードへのping状況
- BGP接続状況
参考: https://github.com/tynany/frr_exporter
frrに接続する部分がinternalでシクシク泣いてる、参考にして自分で書くか...
- WireguardのTx/Rx
表示
- 慣れてるのでNext.jsで
- ページは下のような感じで用意する
- ノードステータス一覧
- ノードトポロジ
- pingが到達したものを抜きだし有向グラフを描画
- なんかNext.jsで自作しなくても全部grafanaでいけそうだな...
- https://grafana.com/docs/grafana/latest/visualizations/node-graph/
- よくわからん、datasourceがprometheusは向いてなさそう | 1.0 | ダッシュボード作成 - ダッシュボードほしい、見栄えとトラシュー効率のため。
コンポーネントをどこまで共通にする？
- 今のserverに送るのが一番楽だけど全然やること違う
- 別にダッシュボードサーバを立ててgRPCでpush型な感じで収集しようかな
- ダッシュボードサーバにprometheus exporterもあると嬉しいね
収集するもの
- ほかの全ノードへのping状況
- BGP接続状況
参考: https://github.com/tynany/frr_exporter
frrに接続する部分がinternalでシクシク泣いてる、参考にして自分で書くか...
- WireguardのTx/Rx
表示
- 慣れてるのでNext.jsで
- ページは下のような感じで用意する
- ノードステータス一覧
- ノードトポロジ
- pingが到達したものを抜きだし有向グラフを描画
- なんかNext.jsで自作しなくても全部grafanaでいけそうだな...
- https://grafana.com/docs/grafana/latest/visualizations/node-graph/
- よくわからん、datasourceがprometheusは向いてなさそう | priority | ダッシュボード作成 ダッシュボードほしい、見栄えとトラシュー効率のため。 コンポーネントをどこまで共通にする？ 今のserverに送るのが一番楽だけど全然やること違う 別にダッシュボードサーバを立ててgrpcでpush型な感じで収集しようかな ダッシュボードサーバにprometheus exporterもあると嬉しいね 収集するもの ほかの全ノードへのping状況 bgp接続状況 参考 frrに接続する部分がinternalでシクシク泣いてる、参考にして自分で書くか wireguardのtx rx 表示 慣れてるのでnext jsで ページは下のような感じで用意する ノードステータス一覧 ノードトポロジ pingが到達したものを抜きだし有向グラフを描画 なんかnext jsで自作しなくても全部grafanaでいけそうだな よくわからん、datasourceがprometheusは向いてなさそう | 1 |
127,430 | 17,269,892,203 | IssuesEvent | 2021-07-22 18:18:09 | flutter/flutter | https://api.github.com/repos/flutter/flutter | closed | [desktop] Ability to get field submitted event in SwitchListTile | a: desktop f: material design framework passed first triage proposal | Hi,
With the TextFormField widget you can, by clicking ENTER, use onFieldSubmitted to execute the saving of the form in the database, however, if the SwitchListTile widget is used in this form, which does not have onFieldSubmitted, and the focus is on the SwitchListTile widget, ENTER would not do any kind of effect.
Is there a way to solve this problem or should the SwitchListTile widget have a onFieldSubmitted event or some other event through which the default windows button can be simulated?
In windows, the standard operation of a form is that by clicking on any of the fields of that form, the code of the default button of the form is executed to avoid having to click on the button with the mouse.
Thanks.
Regards,
Jose | 1.0 | [desktop] Ability to get field submitted event in SwitchListTile - Hi,
With the TextFormField widget you can, by clicking ENTER, use onFieldSubmitted to execute the saving of the form in the database, however, if the SwitchListTile widget is used in this form, which does not have onFieldSubmitted, and the focus is on the SwitchListTile widget, ENTER would not do any kind of effect.
Is there a way to solve this problem or should the SwitchListTile widget have a onFieldSubmitted event or some other event through which the default windows button can be simulated?
In windows, the standard operation of a form is that by clicking on any of the fields of that form, the code of the default button of the form is executed to avoid having to click on the button with the mouse.
Thanks.
Regards,
Jose | non_priority | ability to get field submitted event in switchlisttile hi with the textformfield widget you can by clicking enter use onfieldsubmitted to execute the saving of the form in the database however if the switchlisttile widget is used in this form which does not have onfieldsubmitted and the focus is on the switchlisttile widget enter would not do any kind of effect is there a way to solve this problem or should the switchlisttile widget have a onfieldsubmitted event or some other event through which the default windows button can be simulated in windows the standard operation of a form is that by clicking on any of the fields of that form the code of the default button of the form is executed to avoid having to click on the button with the mouse thanks regards jose | 0 |
66,566 | 3,255,851,191 | IssuesEvent | 2015-10-20 10:48:50 | coreos/rkt | https://api.github.com/repos/coreos/rkt | closed | rkt doesn't work with current systemd v227 | component/stage1 dependency/external kind/bug priority/P2 technology/systemd | It shows this error:
```
Failed to mount sysfs to /sys/full: No such file or directory
``` | 1.0 | rkt doesn't work with current systemd v227 - It shows this error:
```
Failed to mount sysfs to /sys/full: No such file or directory
``` | priority | rkt doesn t work with current systemd it shows this error failed to mount sysfs to sys full no such file or directory | 1 |
13,738 | 9,039,024,928 | IssuesEvent | 2019-02-10 01:28:00 | ZoneMinder/zoneminder | https://api.github.com/repos/ZoneMinder/zoneminder | closed | Reflected Cross Site Scripting(XSS) - events.php | Security Issue | **Describe Your Environment**
- ZoneMinder v1.33.1
- Installed from - ppa:iconnor/zoneminder-master
**Describe the bug**
The view `events`, insecurely displays the `limit` parameter value, without applying any proper output filtration leading to XSS. This issue exists because of function `sortHeader()` in `functions.php` which insecurely returns the value of `limit` query string parameter without applying any filtration.
**To Reproduce**
Affected URL :
http://localhost/zm/index.php?view=events&filter[Query][terms][0][attr]=Archived&filter[Query][terms][0][op]==&filter[Query][terms][0][val]=0&filter[Query][terms][1][cnj]=-3439)OR1=1-&filter[Query][terms][1][attr]=DiskPercent&filter[Query][terms][1][op]=>=&filter[Query][terms][1][val]=95&sort_field=Id&sort_asc=2&limit="><img src=x onerror-prompt('1');>&page=2
Payload used - `"><img src=x onerror-prompt('1');>`
- Navigate to the Affected URL, Payload would be triggered.
<img width="655" alt="events 2" src="https://user-images.githubusercontent.com/47003572/51705245-16438e80-2041-11e9-9db8-943fb8a43eb1.png">
**Expected behavior**
- Proper escaping of special characters.
**Debug Logs**
```
None
``` | True | Reflected Cross Site Scripting(XSS) - events.php - **Describe Your Environment**
- ZoneMinder v1.33.1
- Installed from - ppa:iconnor/zoneminder-master
**Describe the bug**
The view `events`, insecurely displays the `limit` parameter value, without applying any proper output filtration leading to XSS. This issue exists because of function `sortHeader()` in `functions.php` which insecurely returns the value of `limit` query string parameter without applying any filtration.
**To Reproduce**
Affected URL :
http://localhost/zm/index.php?view=events&filter[Query][terms][0][attr]=Archived&filter[Query][terms][0][op]==&filter[Query][terms][0][val]=0&filter[Query][terms][1][cnj]=-3439)OR1=1-&filter[Query][terms][1][attr]=DiskPercent&filter[Query][terms][1][op]=>=&filter[Query][terms][1][val]=95&sort_field=Id&sort_asc=2&limit="><img src=x onerror-prompt('1');>&page=2
Payload used - `"><img src=x onerror-prompt('1');>`
- Navigate to the Affected URL, Payload would be triggered.
<img width="655" alt="events 2" src="https://user-images.githubusercontent.com/47003572/51705245-16438e80-2041-11e9-9db8-943fb8a43eb1.png">
**Expected behavior**
- Proper escaping of special characters.
**Debug Logs**
```
None
``` | non_priority | reflected cross site scripting xss events php describe your environment zoneminder installed from ppa iconnor zoneminder master describe the bug the view events insecurely displays the limit parameter value without applying any proper output filtration leading to xss this issue exists because of function sortheader in functions php which insecurely returns the value of limit query string parameter without applying any filtration to reproduce affected url archived filter filter filter filter diskpercent filter filter sort field id sort asc limit page payload used navigate to the affected url payload would be triggered img width alt events src expected behavior proper escaping of special characters debug logs none | 0 |
21,296 | 2,637,596,429 | IssuesEvent | 2015-03-10 14:16:41 | neuropoly/spinalcordtoolbox | https://api.github.com/repos/neuropoly/spinalcordtoolbox | opened | better management of ML or MAP in the full WM or SC | enhancement priority: high sct_extract_metric | need to find a better way to cluster all tracts, take the whole SC into account if asked by the user.
| 1.0 | better management of ML or MAP in the full WM or SC - need to find a better way to cluster all tracts, take the whole SC into account if asked by the user.
| priority | better management of ml or map in the full wm or sc need to find a better way to cluster all tracts take the whole sc into account if asked by the user | 1 |
100,131 | 8,724,298,623 | IssuesEvent | 2018-12-10 04:17:47 | humera987/FXLabs-Test-Automation | https://api.github.com/repos/humera987/FXLabs-Test-Automation | reopened | app testing 10 : ApiV1EnvsProjectIdIdGetQueryParamPageNegativeNumber | app testing 10 app testing 10 | Project : app testing 10
Job : UAT
Env : UAT
Region : US_WEST
Result : fail
Status Code : 404
Headers : {X-Content-Type-Options=[nosniff], X-XSS-Protection=[1; mode=block], Cache-Control=[no-cache, no-store, max-age=0, must-revalidate], Pragma=[no-cache], Expires=[0], X-Frame-Options=[DENY], Set-Cookie=[SESSION=YjliOWUzNDItM2YxZi00OGQ4LWFmZjAtZWU2MjJhNTJlMmE2; Path=/; HttpOnly], Content-Type=[application/json;charset=UTF-8], Transfer-Encoding=[chunked], Date=[Mon, 10 Dec 2018 04:13:04 GMT]}
Endpoint : http://13.56.210.25/api/v1/api/v1/envs/project-id/OeASDbwL?page=-1
Request :
Response :
{
"timestamp" : "2018-12-10T04:13:04.529+0000",
"status" : 404,
"error" : "Not Found",
"message" : "No message available",
"path" : "/api/v1/api/v1/envs/project-id/OeASDbwL"
}
Logs :
Assertion [@StatusCode != 401] resolved-to [404 != 401] result [Passed]Assertion [@StatusCode != 404] resolved-to [404 != 404] result [Failed]
--- FX Bot --- | 2.0 | app testing 10 : ApiV1EnvsProjectIdIdGetQueryParamPageNegativeNumber - Project : app testing 10
Job : UAT
Env : UAT
Region : US_WEST
Result : fail
Status Code : 404
Headers : {X-Content-Type-Options=[nosniff], X-XSS-Protection=[1; mode=block], Cache-Control=[no-cache, no-store, max-age=0, must-revalidate], Pragma=[no-cache], Expires=[0], X-Frame-Options=[DENY], Set-Cookie=[SESSION=YjliOWUzNDItM2YxZi00OGQ4LWFmZjAtZWU2MjJhNTJlMmE2; Path=/; HttpOnly], Content-Type=[application/json;charset=UTF-8], Transfer-Encoding=[chunked], Date=[Mon, 10 Dec 2018 04:13:04 GMT]}
Endpoint : http://13.56.210.25/api/v1/api/v1/envs/project-id/OeASDbwL?page=-1
Request :
Response :
{
"timestamp" : "2018-12-10T04:13:04.529+0000",
"status" : 404,
"error" : "Not Found",
"message" : "No message available",
"path" : "/api/v1/api/v1/envs/project-id/OeASDbwL"
}
Logs :
Assertion [@StatusCode != 401] resolved-to [404 != 401] result [Passed]Assertion [@StatusCode != 404] resolved-to [404 != 404] result [Failed]
--- FX Bot --- | non_priority | app testing project app testing job uat env uat region us west result fail status code headers x content type options x xss protection cache control pragma expires x frame options set cookie content type transfer encoding date endpoint request response timestamp status error not found message no message available path api api envs project id oeasdbwl logs assertion resolved to result assertion resolved to result fx bot | 0 |
71,313 | 8,643,675,337 | IssuesEvent | 2018-11-25 20:10:47 | cockpit-project/cockpit | https://api.github.com/repos/cockpit-project/cockpit | closed | persistent metrics vs. Store Performance data | needsdesign | It's called one thing before it's installed, and another once it's installed.
Maybe best to call it Persistent metrics in both places, since it's the shorter label.
@garrett thoughts? | 1.0 | persistent metrics vs. Store Performance data - It's called one thing before it's installed, and another once it's installed.
Maybe best to call it Persistent metrics in both places, since it's the shorter label.
@garrett thoughts? | non_priority | persistent metrics vs store performance data it s called one thing before it s installed and another once it s installed maybe best to call it persistent metrics in both places since it s the shorter label garrett thoughts | 0 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.