Unnamed: 0 int64 3 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 2 430 | labels stringlengths 4 347 | body stringlengths 5 237k | index stringclasses 7
values | text_combine stringlengths 96 237k | label stringclasses 2
values | text stringlengths 96 219k | binary_label int64 0 1 |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
17,588 | 24,258,391,883 | IssuesEvent | 2022-09-27 19:58:18 | FrozenBlock/WilderWild | https://api.github.com/repos/FrozenBlock/WilderWild | opened | Add Termite stripping support for other mods' logs | block mod compatibility | idk how this would work tbh but it would be neat
In addition to this, we could maybe add support for hollowed versions of other mods' logs.. we would just have to remove the center pixels and maybe add contrast to the side texture. could look into mods that do something similar to figure out how we can do it | True | Add Termite stripping support for other mods' logs - idk how this would work tbh but it would be neat
In addition to this, we could maybe add support for hollowed versions of other mods' logs.. we would just have to remove the center pixels and maybe add contrast to the side texture. could look into mods that do something similar to figure out how we can do it | comp | add termite stripping support for other mods logs idk how this would work tbh but it would be neat in addition to this we could maybe add support for hollowed versions of other mods logs we would just have to remove the center pixels and maybe add contrast to the side texture could look into mods that do something similar to figure out how we can do it | 1 |
124 | 2,585,646,619 | IssuesEvent | 2015-02-17 02:02:11 | neovim/neovim | https://api.github.com/repos/neovim/neovim | closed | Remove 'edcompatible' | compatibility | When this option is on, the `g` and `c` substitute-flags are remembered globally, and toggled whenever they are given. For example:
:set edcompatible
:s/foo/bar/c " ask confirmation
:s/bar/baz/ " ask confirmation
:s/baz/foo/c " do not ask
This is as stupid as it sounds. The doc actually discourages setting this option. I think we should remove it entirely. We could make `set noedcompatible` a noop like we did for `set nocompatible`; since `edcompatible` is used much less than `compatible`, I’m not sure that’s necessary. | True | Remove 'edcompatible' - When this option is on, the `g` and `c` substitute-flags are remembered globally, and toggled whenever they are given. For example:
:set edcompatible
:s/foo/bar/c " ask confirmation
:s/bar/baz/ " ask confirmation
:s/baz/foo/c " do not ask
This is as stupid as it sounds. The doc actually discourages setting this option. I think we should remove it entirely. We could make `set noedcompatible` a noop like we did for `set nocompatible`; since `edcompatible` is used much less than `compatible`, I’m not sure that’s necessary. | comp | remove edcompatible when this option is on the g and c substitute flags are remembered globally and toggled whenever they are given for example set edcompatible s foo bar c ask confirmation s bar baz ask confirmation s baz foo c do not ask this is as stupid as it sounds the doc actually discourages setting this option i think we should remove it entirely we could make set noedcompatible a noop like we did for set nocompatible since edcompatible is used much less than compatible i’m not sure that’s necessary | 1 |
57,164 | 6,539,620,124 | IssuesEvent | 2017-09-01 12:11:46 | edenlabllc/ehealth.api | https://api.github.com/repos/edenlabllc/ehealth.api | closed | Capitation - Signed content validation | epic/capitation kind/user_story status/test | As NHS admin
I want
- [x] legal_entity.edrpou for every declaration record from the billing report should be compared with the edrpou from the declaration signed content.validation result (true/false) should be stored in the billing table.
So that
- [x] I can be sure that data for the capitation report are consistent and hasn't been changed
relates to #219 | 1.0 | Capitation - Signed content validation - As NHS admin
I want
- [x] legal_entity.edrpou for every declaration record from the billing report should be compared with the edrpou from the declaration signed content.validation result (true/false) should be stored in the billing table.
So that
- [x] I can be sure that data for the capitation report are consistent and hasn't been changed
relates to #219 | non_comp | capitation signed content validation as nhs admin i want legal entity edrpou for every declaration record from the billing report should be compared with the edrpou from the declaration signed content validation result true false should be stored in the billing table so that i can be sure that data for the capitation report are consistent and hasn t been changed relates to | 0 |
18,429 | 25,489,690,072 | IssuesEvent | 2022-11-26 22:34:08 | jbredwards/Fluidlogged-API | https://api.github.com/repos/jbredwards/Fluidlogged-API | closed | Water Rendering Issue | bug incompatibility fixed in dev | **Describe the bug**
When a waterloggable block is placed in one of the corners of a pool of water, the water fails to render.
**To Reproduce**
Steps to reproduce the behavior:
1. create a pool of water.
2. try placing a waterloggable block in any of the corners.
3. watch water disappear.
**Expected behavior**
Water should not become invisible.
**Screenshots**
**Logs**
https://gist.github.com/SaltSouls/bee33e532aadeb9290b0bbcf29f17e92
**Additional context**
It seems to be some kind of compatibility issue with Optifine as removing it fixes the issue.
| True | Water Rendering Issue - **Describe the bug**
When a waterloggable block is placed in one of the corners of a pool of water, the water fails to render.
**To Reproduce**
Steps to reproduce the behavior:
1. create a pool of water.
2. try placing a waterloggable block in any of the corners.
3. watch water disappear.
**Expected behavior**
Water should not become invisible.
**Screenshots**
**Logs**
https://gist.github.com/SaltSouls/bee33e532aadeb9290b0bbcf29f17e92
**Additional context**
It seems to be some kind of compatibility issue with Optifine as removing it fixes the issue.
| comp | water rendering issue describe the bug when a waterloggable block is placed in one of the corners of a pool of water the water fails to render to reproduce steps to reproduce the behavior create a pool of water try placing a waterloggable block in any of the corners watch water disappear expected behavior water should not become invisible screenshots logs additional context it seems to be some kind of compatibility issue with optifine as removing it fixes the issue | 1 |
17,042 | 23,512,751,217 | IssuesEvent | 2022-08-18 18:14:05 | bitcoindevkit/bdk-ffi | https://api.github.com/repos/bitcoindevkit/bdk-ffi | closed | Add functions to get current block height and hash | ldk-compatibility | Once getting a block hash is supported in `bdk` then should add ability to get current block height and block hash at a given height to the `Blockchain` interface. These functions are needed to help support wallets that also use LDK, See https://github.com/bitcoindevkit/bdk-swift/issues/10.
Depends on:
- [x] https://github.com/bitcoindevkit/bdk/issues/603 | True | Add functions to get current block height and hash - Once getting a block hash is supported in `bdk` then should add ability to get current block height and block hash at a given height to the `Blockchain` interface. These functions are needed to help support wallets that also use LDK, See https://github.com/bitcoindevkit/bdk-swift/issues/10.
Depends on:
- [x] https://github.com/bitcoindevkit/bdk/issues/603 | comp | add functions to get current block height and hash once getting a block hash is supported in bdk then should add ability to get current block height and block hash at a given height to the blockchain interface these functions are needed to help support wallets that also use ldk see depends on | 1 |
8,492 | 10,516,234,434 | IssuesEvent | 2019-09-28 16:03:33 | OpenXRay/xray-16 | https://api.github.com/repos/OpenXRay/xray-16 | opened | Teach renderer to work with and without HQ Geometry fix | Compatibility Modmaker Experience Player Experience Render | Check out this commit: https://github.com/OpenXRay/xray-16/commit/2a91825eeb30b3cf8af6b91201a25bd4a90cd01e
This introduced support for high quality models along with the loss of compatibility with the original `skin.h` shader.
Renderer should dynamically detect if shaders has installed HQ geometry fix, and work correctly no matter if it's installed or not. | True | Teach renderer to work with and without HQ Geometry fix - Check out this commit: https://github.com/OpenXRay/xray-16/commit/2a91825eeb30b3cf8af6b91201a25bd4a90cd01e
This introduced support for high quality models along with the loss of compatibility with the original `skin.h` shader.
Renderer should dynamically detect if shaders has installed HQ geometry fix, and work correctly no matter if it's installed or not. | comp | teach renderer to work with and without hq geometry fix check out this commit this introduced support for high quality models along with the loss of compatibility with the original skin h shader renderer should dynamically detect if shaders has installed hq geometry fix and work correctly no matter if it s installed or not | 1 |
4,402 | 7,091,500,981 | IssuesEvent | 2018-01-12 13:20:58 | Yoast/wordpress-seo | https://api.github.com/repos/Yoast/wordpress-seo | closed | Priority column in sitemap needed for W3 Total Cache Priming | compatibility component: xml sitemap needs-decision | ### What did you expect to happen?
Priority column to be present. I think it's needed for W3 Total Cache to work.
### What happened instead?
Removed
### How can we reproduce this behavior?
No need as Yoast has removed it.
Can you provide a link to a page which shows this issue?
### Technical info
- WordPress version: 4.6.1
- Yoast SEO version: 3.5
Although, I am not sure, but I think W3 Total Cache relies on priority to work and prime pages. Can we please have priority back as a default?
| True | Priority column in sitemap needed for W3 Total Cache Priming - ### What did you expect to happen?
Priority column to be present. I think it's needed for W3 Total Cache to work.
### What happened instead?
Removed
### How can we reproduce this behavior?
No need as Yoast has removed it.
Can you provide a link to a page which shows this issue?
### Technical info
- WordPress version: 4.6.1
- Yoast SEO version: 3.5
Although, I am not sure, but I think W3 Total Cache relies on priority to work and prime pages. Can we please have priority back as a default?
| comp | priority column in sitemap needed for total cache priming what did you expect to happen priority column to be present i think it s needed for total cache to work what happened instead removed how can we reproduce this behavior no need as yoast has removed it can you provide a link to a page which shows this issue technical info wordpress version yoast seo version although i am not sure but i think total cache relies on priority to work and prime pages can we please have priority back as a default | 1 |
10,157 | 12,167,262,000 | IssuesEvent | 2020-04-27 10:36:14 | ionic-team/capacitor | https://api.github.com/repos/ionic-team/capacitor | closed | cordova-hot-code-push cannot be use incapacitor | known incompatible cordova plugin | Because ionic react's capacitor project doesn't even have config.xml anymore,and Ionic react doesn't have the WWW folder, just the build folder
So can't set in config.xml like:
And the command cordobia-hcp build will not live in the WWW files
| True | cordova-hot-code-push cannot be use incapacitor - Because ionic react's capacitor project doesn't even have config.xml anymore,and Ionic react doesn't have the WWW folder, just the build folder
So can't set in config.xml like:
And the command cordobia-hcp build will not live in the WWW files
| comp | cordova hot code push cannot be use incapacitor because ionic react s capacitor project doesn t even have config xml anymore and ionic react doesn t have the www folder just the build folder so can t set in config xml like and the command cordobia hcp build will not live in the www files | 1 |
429,414 | 12,424,185,668 | IssuesEvent | 2020-05-24 10:15:15 | Warcraft-GoA-Development-Team/Warcraft-Guardians-of-Azeroth | https://api.github.com/repos/Warcraft-GoA-Development-Team/Warcraft-Guardians-of-Azeroth | closed | Waterspeaking | :exclamation: priority high :question: suggestion - feature :star: :question: suggestion - localisation :pen: :question: suggestion - lore :books: :question: suggestion :question: | <!--
DO NOT REMOVE PRE-EXISTING LINES
IF YOU WANT TO SUGGEST A FEW THINGS, OPEN A NEW ISSUE PER EVERY SUGGESTION
----------------------------------------------------------------------------------------------------------
-->
**Describe your suggestion in full detail below:**
Add a decision to speak with water (adding it for the jinyu but the murlocs can use it too) to find out your near feature and be prepared. It should work like Hermetics' horoscope but for adults.
https://wow.gamepedia.com/Waterspeaker | 1.0 | Waterspeaking - <!--
DO NOT REMOVE PRE-EXISTING LINES
IF YOU WANT TO SUGGEST A FEW THINGS, OPEN A NEW ISSUE PER EVERY SUGGESTION
----------------------------------------------------------------------------------------------------------
-->
**Describe your suggestion in full detail below:**
Add a decision to speak with water (adding it for the jinyu but the murlocs can use it too) to find out your near feature and be prepared. It should work like Hermetics' horoscope but for adults.
https://wow.gamepedia.com/Waterspeaker | non_comp | waterspeaking do not remove pre existing lines if you want to suggest a few things open a new issue per every suggestion describe your suggestion in full detail below add a decision to speak with water adding it for the jinyu but the murlocs can use it too to find out your near feature and be prepared it should work like hermetics horoscope but for adults | 0 |
3,727 | 6,586,552,808 | IssuesEvent | 2017-09-13 17:42:06 | AdguardTeam/AdguardForAndroid | https://api.github.com/repos/AdguardTeam/AdguardForAndroid | reopened | Speed testing app can't measure upload speed | bug compatibility wontfix | Happens **only** with HTTP proxy filtering mode (Automatic) on rooted device
All other settings are default.
[This ](https://play.google.com/store/apps/details?id=com.staircase3.opensignal&hl=en) is the app.
Debug log: [adguard.log.zip](https://github.com/AdguardTeam/AdguardForAndroid/files/1039016/adguard.log.zip)
STR:
* hit the "Test" button
* 0 kb/s upload speed will be displayed after the test
<details>
</details>
<br>
| True | Speed testing app can't measure upload speed - Happens **only** with HTTP proxy filtering mode (Automatic) on rooted device
All other settings are default.
[This ](https://play.google.com/store/apps/details?id=com.staircase3.opensignal&hl=en) is the app.
Debug log: [adguard.log.zip](https://github.com/AdguardTeam/AdguardForAndroid/files/1039016/adguard.log.zip)
STR:
* hit the "Test" button
* 0 kb/s upload speed will be displayed after the test
<details>
</details>
<br>
| comp | speed testing app can t measure upload speed happens only with http proxy filtering mode automatic on rooted device all other settings are default is the app debug log str hit the test button kb s upload speed will be displayed after the test | 1 |
20,313 | 29,737,531,800 | IssuesEvent | 2023-06-14 03:02:23 | storybookjs/storybook | https://api.github.com/repos/storybookjs/storybook | closed | Addon docs: Unwanted props appearing on the generated docs props. | compatibility with other tools has workaround todo block: props | When viewing props from jsx using `styled-components` the props table will contain all props passed what seems to be `styled-components`
Example:
Also, for some reason, my docs page is not centered
**Expected behavior**
Only direct component props will be shown.
Docs are centered
My config:
```js import { Fragment } from 'react';
import { configure, addDecorator } from '@storybook/react';
import { withOptions } from '@storybook/addon-options';
import { withKnobs } from '@storybook/addon-knobs';
import { bootstrap } from '@logz-ui/styleguide';
bootstrap();
const storyBookDecorators = [
withKnobs,
withOptions({
name: `@logz-ui/styleguide`,
url: 'https://github.com/logzio/gaia-hermes-ws/tree/master/styleguide',
hierarchyRootSeparator: /\|/,
}),
];
storyBookDecorators.forEach(addon => addDecorator(addon));
configure(require.context('../stories', true, /\.story\.jsx?$/), module);
```
My Presets:
```js const path = require("path");
module.exports = [
{
name: '@storybook/addon-docs/react/preset',
options: {
configureJSX: true,
babelOptions: {
babelrc: path ,
presets: [],
plugins: ['emotion'],
},
sourceLoaderOptions: null,
},
},
{
name: "@storybook/preset-typescript",
options: {
tsDocgenLoaderOptions: {
tsconfigPath: path.resolve(__dirname, "../tsconfig.json")
},
include: [path.resolve(__dirname, "../stories")]
}
}
];
```
Will provide more context if needed. would love to know the solution to thesetwo problems :) | True | Addon docs: Unwanted props appearing on the generated docs props. - When viewing props from jsx using `styled-components` the props table will contain all props passed what seems to be `styled-components`
Example:
Also, for some reason, my docs page is not centered
**Expected behavior**
Only direct component props will be shown.
Docs are centered
My config:
```js import { Fragment } from 'react';
import { configure, addDecorator } from '@storybook/react';
import { withOptions } from '@storybook/addon-options';
import { withKnobs } from '@storybook/addon-knobs';
import { bootstrap } from '@logz-ui/styleguide';
bootstrap();
const storyBookDecorators = [
withKnobs,
withOptions({
name: `@logz-ui/styleguide`,
url: 'https://github.com/logzio/gaia-hermes-ws/tree/master/styleguide',
hierarchyRootSeparator: /\|/,
}),
];
storyBookDecorators.forEach(addon => addDecorator(addon));
configure(require.context('../stories', true, /\.story\.jsx?$/), module);
```
My Presets:
```js const path = require("path");
module.exports = [
{
name: '@storybook/addon-docs/react/preset',
options: {
configureJSX: true,
babelOptions: {
babelrc: path ,
presets: [],
plugins: ['emotion'],
},
sourceLoaderOptions: null,
},
},
{
name: "@storybook/preset-typescript",
options: {
tsDocgenLoaderOptions: {
tsconfigPath: path.resolve(__dirname, "../tsconfig.json")
},
include: [path.resolve(__dirname, "../stories")]
}
}
];
```
Will provide more context if needed. would love to know the solution to thesetwo problems :) | comp | addon docs unwanted props appearing on the generated docs props when viewing props from jsx using styled components the props table will contain all props passed what seems to be styled components example also for some reason my docs page is not centered expected behavior only direct component props will be shown docs are centered my config js import fragment from react import configure adddecorator from storybook react import withoptions from storybook addon options import withknobs from storybook addon knobs import bootstrap from logz ui styleguide bootstrap const storybookdecorators withknobs withoptions name logz ui styleguide url hierarchyrootseparator storybookdecorators foreach addon adddecorator addon configure require context stories true story jsx module my presets js const path require path module exports name storybook addon docs react preset options configurejsx true babeloptions babelrc path presets plugins sourceloaderoptions null name storybook preset typescript options tsdocgenloaderoptions tsconfigpath path resolve dirname tsconfig json include will provide more context if needed would love to know the solution to thesetwo problems | 1 |
20,541 | 30,457,547,234 | IssuesEvent | 2023-07-17 02:05:48 | uqfoundation/klepto | https://api.github.com/repos/uqfoundation/klepto | closed | klepto breaks on SQLAlchemy 2.0 | compatibility | `SQLAlchemy` made backward incompatible changes in version 2.0, some of which cause errors:
https://app.travis-ci.com/github/uqfoundation/klepto/jobs/594440786
Need to update `klepto` for `SQLAlchemy` 2.0 | True | klepto breaks on SQLAlchemy 2.0 - `SQLAlchemy` made backward incompatible changes in version 2.0, some of which cause errors:
https://app.travis-ci.com/github/uqfoundation/klepto/jobs/594440786
Need to update `klepto` for `SQLAlchemy` 2.0 | comp | klepto breaks on sqlalchemy sqlalchemy made backward incompatible changes in version some of which cause errors need to update klepto for sqlalchemy | 1 |
412,658 | 12,054,094,744 | IssuesEvent | 2020-04-15 10:30:15 | fritzing/fritzing-app | https://api.github.com/repos/fritzing/fritzing-app | closed | deal with em and ex units | Priority-Low enhancement imported | _From [irasc...@gmail.com](https://code.google.com/u/104729248032245122687/) on September 22, 2012 12:38:05_
"As in CSS, the em and ex unit identifiers are relative to the current font's font-size and x-height, respectively."
Haven't seen these come up in practice. As I understand it, these would only appear as internal units.
_Original issue: http://code.google.com/p/fritzing/issues/detail?id=2217_
| 1.0 | deal with em and ex units - _From [irasc...@gmail.com](https://code.google.com/u/104729248032245122687/) on September 22, 2012 12:38:05_
"As in CSS, the em and ex unit identifiers are relative to the current font's font-size and x-height, respectively."
Haven't seen these come up in practice. As I understand it, these would only appear as internal units.
_Original issue: http://code.google.com/p/fritzing/issues/detail?id=2217_
| non_comp | deal with em and ex units from on september as in css the em and ex unit identifiers are relative to the current font s font size and x height respectively haven t seen these come up in practice as i understand it these would only appear as internal units original issue | 0 |
19,773 | 27,422,198,659 | IssuesEvent | 2023-03-01 17:28:32 | elementor/elementor | https://api.github.com/repos/elementor/elementor | closed | ⛔ 🐞 Bug Report: lementor gets affected with WooCommerence | bug compatibility/3rd_party product/pro component/woocommerce | ### Prerequisites
- [X] I have searched for similar issues in both open and closed tickets and cannot find a duplicate.
- [X] The issue still exists against the latest stable version of Elementor.
### Description
Whenever I activate any WooCommerce plugin Elementor gets affected.
### Steps to reproduce
I have updated Elementor and Elementor Pro Plugin. After updating that My website get down and got a email notification "[MySDS.ca LMS] Your Site is Experiencing a Technical Issue" and they provide me a recovery mode link. Whenever I activate any WooCommerce plugin Elementor gets affected.
### Isolating the problem
- [X] This bug happens with only Elementor plugin active (and Elementor Pro).
- [ ] This bug happens with a Blank WordPress theme active ([Hello theme](https://wordpress.org/themes/hello-elementor/)).
- [ ] I can reproduce this bug consistently following the steps above.
### System Info
== Server Environment ==
Operating System: Linux
Software: Apache
MySQL version: MariaDB Server v5.7.38
PHP Version: 7.4.33
PHP Memory Limit: 32M
PHP Max Input Vars: 1000
PHP Max Post Size: 600M
GD Installed: Yes
ZIP Installed: Yes
Write Permissions: All right
Elementor Library: Connected
== WordPress Environment ==
Version: 6.1.1
Site URL: https://lms.mysds.ca
Home URL: https://lms.mysds.ca
WP Multisite: No
Max Upload Size: 64 MB
Memory limit: 40M
Max Memory limit: 512M
Permalink Structure: /%year%/%monthnum%/%day%/%postname%/
Language: en-US
Timezone: America/Toronto
Admin Email: kamljeet@mysds.ca
Debug Mode: Inactive
== Theme ==
Name: REIGN
Version: 2.8.4
Author: Wbcom Designs
Child Theme: No
== User ==
Role: administrator
WP Profile lang: en_US
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/110.0.0.0 Safari/537.36
== Active Plugins ==
Admin Menu Editor
Version: 1.10.4
Author: Janis Elsts
Advanced Custom Fields
Version: 6.0.7
Author: WP Engine
Autocomplete WooCommerce Orders
Version: 3.0.3
Author: QuadLayers
Backup Duplicator & Migration - WP STAGING
Version: 2.12.0
Author: WP-STAGING, WPStagingBackup
Clean WP Dashboard
Version: 1.0
Author: Jerod Santo
Contact Form DB - Elementor
Version: 1.8.0
Author: Web Ace Tech Services
Course Scheduler for LearnDash
Version: 1.5.1
Author: WooNinjas
Custom Template for LearnDash
Version: 1.0.5
Author: Pratik Chaskar
Debug This
Version: 0.6.4
Author: WPChill
Design Upgrade for LearnDash
Version: 2.12
Author: Escape Creative
Disable Admin Notices Individually
Version: 1.3.2
Author: Creative Motion <info@cm-wp.com>
Elementor
Version: 3.11.2
Author: Elementor.com
Elementor Pro
Version: 3.11.3
Author: Elementor.com
Frontend Reset Password
Version: 1.2.1
Author: WP Enhanced
Increase Maximum Upload File Size
Version: 2.0.4
Author: Imagify
LearnDash - Exporter
Version: 1.0
Author: Manuel Costales
LearnDash GravityForms Addon
Version: 2.0.1
Author: LearnDash
LearnDash Licensing & Management
Version: 1.1.6
Author: LearnDash
LearnDash LMS
Version: 4.5.1.1
Author: LearnDash
LearnDash LMS - Course Grid
Version: 2.0.7
Author: LearnDash
LearnDash LMS - Notifications
Version: 1.6
Author: LearnDash
LearnDash LMS - ProPanel
Version: 2.1.4.2
Author: LearnDash
LearnDash Notes
Version: 1.4.3
Author: SnapOrbital
LoginWP (Formerly Peter's Login Redirect)
Version: 3.0.7.0
Author: LoginWP Team
Privileged Menu
Version: 1.8.4
Author: <a href="http://www.fuzzguard.com.au/"><strong>Benjamin Guy</strong></a>
Tin Canny LearnDash Reporting
Version: 3.3.3
Author: Uncanny Owl
Uncanny Codes
Version: 4.2.0.1
Author: Uncanny Owl
Uncanny Groups for LearnDash
Version: 4.2
Author: Uncanny Owl
Uncanny Toolkit for LearnDash
Version: 3.6.4.2
Author: Uncanny Owl
Uncanny Toolkit Pro for LearnDash
Version: 3.10
Author: Uncanny Owl
WP Htaccess Editor
Version: 1.71
Author: WebFactory Ltd
WP Rollback
Version: 1.7.3
Author: GiveWP.com
== Must-Use Plugins ==
LearnDash LMS Multisite
Version: 1.0.0
Author: LearnDash
WP STAGING Optimizer
Version: 1.5.1
Author: René Hermenau
== Features ==
Custom Fonts: 0
Custom Icons: 0
== Integrations ==
== Elementor Experiments ==
Optimized DOM Output: Inactive by default
Improved Asset Loading: Inactive by default
Improved CSS Loading: Inactive by default
Inline Font Icons: Inactive by default
Accessibility Improvements: Inactive by default
Additional Custom Breakpoints: Inactive by default
admin_menu_rearrangement: Inactive by default
Flexbox Container: Inactive by default
Upgrade Swiper Library: Inactive by default
Default to New Theme Builder: Active by default
Editor V2: Inactive by default
Landing Pages: Active by default
Nested Elements: Inactive by default
Lazy Load Background Images: Inactive by default
Save as Default: Active by default
Page Transitions: Active by default
Notes: Active by default
Loop: Active by default
Form Submissions: Active by default
Scroll Snap: Active by default
Mega Menu: Inactive by default
== Log ==
Log: showing 20 of 342021-06-21 12:14:36 [info] elementor-pro::elementor_pro_updater Started
2021-06-21 12:14:36 [info] Elementor Pro/Upgrades - _v_3_1_0_media_carousel Start
2021-06-21 12:14:36 [info] Elementor data updater process has been queued. [array (
'plugin' => 'Elementor Pro',
'from' => '3.0.6',
'to' => '3.3.1',
)]
2021-06-21 12:14:36 [info] Elementor Pro/Upgrades - _v_3_1_0_media_carousel Finished
2021-06-21 12:14:36 [info] Elementor Pro/Upgrades - _v_3_1_0_reviews Start
2021-06-21 12:14:36 [info] Elementor Pro/Upgrades - _v_3_1_0_reviews Finished
2021-06-21 12:14:36 [info] Elementor Pro/Upgrades - _v_3_1_0_testimonial_carousel Start
2021-06-21 12:14:37 [info] Elementor Pro/Upgrades - _v_3_1_0_testimonial_carousel Finished
2021-06-21 12:14:37 [info] Elementor Pro/Upgrades - _v_3_1_0_slides Start
2021-06-21 12:14:37 [info] Elementor Pro/Upgrades - _v_3_1_0_slides Finished
2021-06-21 12:14:37 [info] Elementor Pro/Upgrades - _v_3_3_0_nav_menu_icon Start
2021-06-21 12:14:37 [info] Elementor Pro/Upgrades - _v_3_3_0_nav_menu_icon Finished
2021-06-21 12:14:37 [info] Elementor Pro/Upgrades - _v_3_3_0_recalc_usage_data Start
2021-06-21 12:14:38 [info] Elementor Pro/Upgrades - _v_3_3_0_recalc_usage_data callback needs to run again
2021-06-21 12:14:38 [info] Elementor Pro/Upgrades - _v_3_3_0_recalc_usage_data Start (x2)
2021-06-21 12:14:38 [info] Elementor Pro/Upgrades - _v_3_3_0_recalc_usage_data Finished
2021-06-21 12:14:38 [info] Elementor data updater process has been completed. [array (
'plugin' => 'Elementor Pro',
'from' => '3.0.6',
'to' => '3.3.1',
)]
2023-02-23 10:17:33 [info] Elementor data updater process has been queued. [array (
'plugin' => 'Elementor',
'from' => '3.2.5',
'to' => '3.11.2',
)]
2023-02-23 10:17:33 [info] Elementor data updater process has been completed. [array (
'plugin' => 'Elementor Pro',
'from' => '3.3.1',
'to' => '3.4.2',
)]
2023-02-27 10:42:59 [info] Elementor data updater process has been queued. [array (
'plugin' => 'Elementor Pro',
'from' => '3.4.2',
'to' => '3.11.2',
)]
PHP: showing 8 of 8PHP: 2021-03-28 20:07:24 [error X 1][/home/lmsmysds/public_html/wp-content/plugins/elementor/includes/autoloader.php::269] Allowed memory size of 134217728 bytes exhausted (tried to allocate 73728 bytes) [array (
'trace' => '
#0: Elementor\Core\Logger\Manager -> shutdown()
',
)]
PHP: 2021-03-28 21:36:05 [error X 1][/home/lmsmysds/public_html/wp-content/plugins/elementor/includes/frontend.php::977] Allowed memory size of 134217728 bytes exhausted (tried to allocate 69632 bytes) [array (
'trace' => '
#0: Elementor\Core\Logger\Manager -> shutdown()
',
)]
PHP: 2023-02-23 10:02:34 [error X 185][/home/lmsmysds/public_html/wp-content/plugins/elementor/includes/frontend.php::339] Uncaught Error: Call to a member function is_feature_active() on null in /home/lmsmysds/public_html/wp-content/plugins/elementor/includes/frontend.php:339
Stack trace:
#0 /home/lmsmysds/public_html/wp-content/plugins/elementor/includes/frontend.php(176): Elementor\Frontend->init_swiper_settings()
#1 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/includes/global-header-footer.php(41): Elementor\Frontend->__construct()
#2 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/includes/global-header-footer.php(33): WBCOM_Elementor_Global_Header_Footer->__construct()
#3 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/includes/global-header-footer.php(741): WBCOM_Elementor_Global_Header_Footer::instance()
#4 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/plugin.php(67): require('/home/lmsmysds/...')
#5 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/plugin.php(239): WbcomElementorAddons\Plugin->includes()
#6 /home/lmsmysds/public_html/wp-content/plug [array (
'trace' => '
#0: Elementor\Core\Logger\Manager -> shutdown()
',
)]
PHP: 2023-02-27 10:42:33 [error X 611][/home/lmsmysds/public_html/wp-content/plugins/elementor_bak/includes/frontend.php::339] Uncaught Error: Call to a member function is_feature_active() on null in /home/lmsmysds/public_html/wp-content/plugins/elementor_bak/includes/frontend.php:339
Stack trace:
#0 /home/lmsmysds/public_html/wp-content/plugins/elementor_bak/includes/frontend.php(176): Elementor\Frontend->init_swiper_settings()
#1 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/includes/global-header-footer.php(41): Elementor\Frontend->__construct()
#2 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/includes/global-header-footer.php(33): WBCOM_Elementor_Global_Header_Footer->__construct()
#3 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/includes/global-header-footer.php(741): WBCOM_Elementor_Global_Header_Footer::instance()
#4 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/plugin.php(67): require('/home/lmsmysds/...')
#5 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/plugin.php(239): WbcomElementorAddons\Plugin->includes()
#6 /home/lmsmysds/public_html/wp-cont [array (
'trace' => '
#0: Elementor\Core\Logger\Manager -> shutdown()
',
)]
PHP: 2023-02-28 11:19:30 [error X 22][/home/lmsmysds/public_html/wp-content/plugins/elementor_bak/includes/frontend.php::339] Uncaught Error: Call to a member function is_feature_active() on null in /home/lmsmysds/public_html/wp-content/plugins/elementor_bak/includes/frontend.php:339
Stack trace:
#0 /home/lmsmysds/public_html/wp-content/plugins/elementor_bak/includes/frontend.php(176): Elementor\Frontend->init_swiper_settings()
#1 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/includes/global-header-footer.php(41): Elementor\Frontend->__construct()
#2 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/includes/global-header-footer.php(33): WBCOM_Elementor_Global_Header_Footer->__construct()
#3 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/includes/global-header-footer.php(741): WBCOM_Elementor_Global_Header_Footer::instance()
#4 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/plugin.php(67): require('/home/lmsmysds/...')
#5 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/plugin.php(239): WbcomElementorAddons\Plugin->includes()
#6 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/plugin.php(59): WbcomElementorAddons\Plugin->__construct()
#7 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/plugin.php(245): WbcomElementorAddons\Plugin::instance()
#8 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/wbcom-essential.php(55): require('/home/lmsmysds/...')
#9 /home/lmsmysds/public_html/wp-includes/class-wp-hook.php(308): wbcom_elementor_addons_load_plugin('')
#10 /home/lmsmysds/public_html/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters(NULL, Array)
#11 /home/lmsmysds/public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
#12 /home/lmsmysds/public_html/wp-settings.php(480): do_action('plugins_loaded')
#13 /home/lmsmysds/public_html/wp-config.php(93): require_once('/home/lmsmysds/...')
#14 /home/lmsmysds/public_html/wp-load.php(50): require_once('/home/lmsmysds/...')
#15 /home/lmsmysds/public_html/wp-blog-header.php(13): require_once('/home/lmsmysds/...')
#16 /home/lmsmysds/public_html/index.php(17): require('/home/lmsmysds/...')
#17 {main}
thrown [array (
'trace' => '
#0: Elementor\Core\Logger\Manager -> shutdown()
',
)]
PHP: 2023-02-28 11:19:48 [error X 10][/home/lmsmysds/public_html/wp-content/plugins/elementor_bak/includes/frontend.php::339] Uncaught Error: Call to a member function is_feature_active() on null in /home/lmsmysds/public_html/wp-content/plugins/elementor_bak/includes/frontend.php:339
Stack trace:
#0 /home/lmsmysds/public_html/wp-content/plugins/elementor_bak/includes/frontend.php(176): Elementor\Frontend->init_swiper_settings()
#1 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/includes/global-header-footer.php(41): Elementor\Frontend->__construct()
#2 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/includes/global-header-footer.php(33): WBCOM_Elementor_Global_Header_Footer->__construct()
#3 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/includes/global-header-footer.php(741): WBCOM_Elementor_Global_Header_Footer::instance()
#4 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/plugin.php(67): require('/home/lmsmysds/...')
#5 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/plugin.php(239): WbcomElementorAddons\Plugin->includes()
#6 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/plugin.php(59): WbcomElementorAddons\Plugin->__construct()
#7 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/plugin.php(245): WbcomElementorAddons\Plugin::instance()
#8 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/wbcom-essential.php(55): require('/home/lmsmysds/...')
#9 /home/lmsmysds/public_html/wp-includes/class-wp-hook.php(308): wbcom_elementor_addons_load_plugin('')
#10 /home/lmsmysds/public_html/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters(NULL, Array)
#11 /home/lmsmysds/public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
#12 /home/lmsmysds/public_html/wp-settings.php(480): do_action('plugins_loaded')
#13 /home/lmsmysds/public_html/wp-config.php(93): require_once('/home/lmsmysds/...')
#14 /home/lmsmysds/public_html/wp-load.php(50): require_once('/home/lmsmysds/...')
#15 /home/lmsmysds/public_html/wp-cron.php(46): require_once('/home/lmsmysds/...')
#16 {main}
thrown [array (
'trace' => '
#0: Elementor\Core\Logger\Manager -> shutdown()
',
)]
PHP: 2023-02-28 11:20:36 [error X 3][/home/lmsmysds/public_html/wp-content/plugins/elementor_bak/includes/frontend.php::339] Uncaught Error: Call to a member function is_feature_active() on null in /home/lmsmysds/public_html/wp-content/plugins/elementor_bak/includes/frontend.php:339
Stack trace:
#0 /home/lmsmysds/public_html/wp-content/plugins/elementor_bak/includes/frontend.php(176): Elementor\Frontend->init_swiper_settings()
#1 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/includes/global-header-footer.php(41): Elementor\Frontend->__construct()
#2 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/includes/global-header-footer.php(33): WBCOM_Elementor_Global_Header_Footer->__construct()
#3 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/includes/global-header-footer.php(741): WBCOM_Elementor_Global_Header_Footer::instance()
#4 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/plugin.php(67): require('/home/lmsmysds/...')
#5 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/plugin.php(239): WbcomElementorAddons\Plugin->includes()
#6 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/plugin.php(59): WbcomElementorAddons\Plugin->__construct()
#7 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/plugin.php(245): WbcomElementorAddons\Plugin::instance()
#8 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/wbcom-essential.php(55): require('/home/lmsmysds/...')
#9 /home/lmsmysds/public_html/wp-includes/class-wp-hook.php(308): wbcom_elementor_addons_load_plugin('')
#10 /home/lmsmysds/public_html/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters(NULL, Array)
#11 /home/lmsmysds/public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
#12 /home/lmsmysds/public_html/wp-settings.php(480): do_action('plugins_loaded')
#13 /home/lmsmysds/public_html/wp-config.php(93): require_once('/home/lmsmysds/...')
#14 /home/lmsmysds/public_html/wp-load.php(50): require_once('/home/lmsmysds/...')
#15 /home/lmsmysds/public_html/xmlrpc.php(31): require_once('/home/lmsmysds/...')
#16 {main}
thrown [array (
'trace' => '
#0: Elementor\Core\Logger\Manager -> shutdown()
',
)]
PHP: 2023-02-28 11:25:43 [error X 2][/home/lmsmysds/public_html/wp-content/plugins/elementor_bak/includes/frontend.php::339] Uncaught Error: Call to a member function is_feature_active() on null in /home/lmsmysds/public_html/wp-content/plugins/elementor_bak/includes/frontend.php:339
Stack trace:
#0 /home/lmsmysds/public_html/wp-content/plugins/elementor_bak/includes/frontend.php(176): Elementor\Frontend->init_swiper_settings()
#1 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/includes/global-header-footer.php(41): Elementor\Frontend->__construct()
#2 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/includes/global-header-footer.php(33): WBCOM_Elementor_Global_Header_Footer->__construct()
#3 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/includes/global-header-footer.php(741): WBCOM_Elementor_Global_Header_Footer::instance()
#4 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/plugin.php(67): require('/home/lmsmysds/...')
#5 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/plugin.php(239): WbcomElementorAddons\Plugin->includes()
#6 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/plugin.php(59): WbcomElementorAddons\Plugin->__construct()
#7 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/plugin.php(245): WbcomElementorAddons\Plugin::instance()
#8 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/wbcom-essential.php(55): require('/home/lmsmysds/...')
#9 /home/lmsmysds/public_html/wp-includes/class-wp-hook.php(308): wbcom_elementor_addons_load_plugin('')
#10 /home/lmsmysds/public_html/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters(NULL, Array)
#11 /home/lmsmysds/public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
#12 /home/lmsmysds/public_html/wp-settings.php(480): do_action('plugins_loaded')
#13 /home/lmsmysds/public_html/wp-config.php(93): require_once('/home/lmsmysds/...')
#14 /home/lmsmysds/public_html/wp-load.php(50): require_once('/home/lmsmysds/...')
#15 /home/lmsmysds/public_html/wp-login.php(12): require('/home/lmsmysds/...')
#16 {main}
thrown [array (
'trace' => '
#0: Elementor\Core\Logger\Manager -> shutdown()
',
)]
== Elementor - Compatibility Tag ==
Contact Form DB - Elementor: Compatibility not specified
Elementor: Compatibility not specified
Elementor Pro: Compatibility not specified
== Elementor Pro - Compatibility Tag ==
| True | ⛔ 🐞 Bug Report: lementor gets affected with WooCommerence - ### Prerequisites
- [X] I have searched for similar issues in both open and closed tickets and cannot find a duplicate.
- [X] The issue still exists against the latest stable version of Elementor.
### Description
Whenever I activate any WooCommerce plugin Elementor gets affected.
### Steps to reproduce
I have updated Elementor and Elementor Pro Plugin. After updating that My website get down and got a email notification "[MySDS.ca LMS] Your Site is Experiencing a Technical Issue" and they provide me a recovery mode link. Whenever I activate any WooCommerce plugin Elementor gets affected.
### Isolating the problem
- [X] This bug happens with only Elementor plugin active (and Elementor Pro).
- [ ] This bug happens with a Blank WordPress theme active ([Hello theme](https://wordpress.org/themes/hello-elementor/)).
- [ ] I can reproduce this bug consistently following the steps above.
### System Info
== Server Environment ==
Operating System: Linux
Software: Apache
MySQL version: MariaDB Server v5.7.38
PHP Version: 7.4.33
PHP Memory Limit: 32M
PHP Max Input Vars: 1000
PHP Max Post Size: 600M
GD Installed: Yes
ZIP Installed: Yes
Write Permissions: All right
Elementor Library: Connected
== WordPress Environment ==
Version: 6.1.1
Site URL: https://lms.mysds.ca
Home URL: https://lms.mysds.ca
WP Multisite: No
Max Upload Size: 64 MB
Memory limit: 40M
Max Memory limit: 512M
Permalink Structure: /%year%/%monthnum%/%day%/%postname%/
Language: en-US
Timezone: America/Toronto
Admin Email: kamljeet@mysds.ca
Debug Mode: Inactive
== Theme ==
Name: REIGN
Version: 2.8.4
Author: Wbcom Designs
Child Theme: No
== User ==
Role: administrator
WP Profile lang: en_US
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/110.0.0.0 Safari/537.36
== Active Plugins ==
Admin Menu Editor
Version: 1.10.4
Author: Janis Elsts
Advanced Custom Fields
Version: 6.0.7
Author: WP Engine
Autocomplete WooCommerce Orders
Version: 3.0.3
Author: QuadLayers
Backup Duplicator & Migration - WP STAGING
Version: 2.12.0
Author: WP-STAGING, WPStagingBackup
Clean WP Dashboard
Version: 1.0
Author: Jerod Santo
Contact Form DB - Elementor
Version: 1.8.0
Author: Web Ace Tech Services
Course Scheduler for LearnDash
Version: 1.5.1
Author: WooNinjas
Custom Template for LearnDash
Version: 1.0.5
Author: Pratik Chaskar
Debug This
Version: 0.6.4
Author: WPChill
Design Upgrade for LearnDash
Version: 2.12
Author: Escape Creative
Disable Admin Notices Individually
Version: 1.3.2
Author: Creative Motion <info@cm-wp.com>
Elementor
Version: 3.11.2
Author: Elementor.com
Elementor Pro
Version: 3.11.3
Author: Elementor.com
Frontend Reset Password
Version: 1.2.1
Author: WP Enhanced
Increase Maximum Upload File Size
Version: 2.0.4
Author: Imagify
LearnDash - Exporter
Version: 1.0
Author: Manuel Costales
LearnDash GravityForms Addon
Version: 2.0.1
Author: LearnDash
LearnDash Licensing & Management
Version: 1.1.6
Author: LearnDash
LearnDash LMS
Version: 4.5.1.1
Author: LearnDash
LearnDash LMS - Course Grid
Version: 2.0.7
Author: LearnDash
LearnDash LMS - Notifications
Version: 1.6
Author: LearnDash
LearnDash LMS - ProPanel
Version: 2.1.4.2
Author: LearnDash
LearnDash Notes
Version: 1.4.3
Author: SnapOrbital
LoginWP (Formerly Peter's Login Redirect)
Version: 3.0.7.0
Author: LoginWP Team
Privileged Menu
Version: 1.8.4
Author: <a href="http://www.fuzzguard.com.au/"><strong>Benjamin Guy</strong></a>
Tin Canny LearnDash Reporting
Version: 3.3.3
Author: Uncanny Owl
Uncanny Codes
Version: 4.2.0.1
Author: Uncanny Owl
Uncanny Groups for LearnDash
Version: 4.2
Author: Uncanny Owl
Uncanny Toolkit for LearnDash
Version: 3.6.4.2
Author: Uncanny Owl
Uncanny Toolkit Pro for LearnDash
Version: 3.10
Author: Uncanny Owl
WP Htaccess Editor
Version: 1.71
Author: WebFactory Ltd
WP Rollback
Version: 1.7.3
Author: GiveWP.com
== Must-Use Plugins ==
LearnDash LMS Multisite
Version: 1.0.0
Author: LearnDash
WP STAGING Optimizer
Version: 1.5.1
Author: René Hermenau
== Features ==
Custom Fonts: 0
Custom Icons: 0
== Integrations ==
== Elementor Experiments ==
Optimized DOM Output: Inactive by default
Improved Asset Loading: Inactive by default
Improved CSS Loading: Inactive by default
Inline Font Icons: Inactive by default
Accessibility Improvements: Inactive by default
Additional Custom Breakpoints: Inactive by default
admin_menu_rearrangement: Inactive by default
Flexbox Container: Inactive by default
Upgrade Swiper Library: Inactive by default
Default to New Theme Builder: Active by default
Editor V2: Inactive by default
Landing Pages: Active by default
Nested Elements: Inactive by default
Lazy Load Background Images: Inactive by default
Save as Default: Active by default
Page Transitions: Active by default
Notes: Active by default
Loop: Active by default
Form Submissions: Active by default
Scroll Snap: Active by default
Mega Menu: Inactive by default
== Log ==
Log: showing 20 of 342021-06-21 12:14:36 [info] elementor-pro::elementor_pro_updater Started
2021-06-21 12:14:36 [info] Elementor Pro/Upgrades - _v_3_1_0_media_carousel Start
2021-06-21 12:14:36 [info] Elementor data updater process has been queued. [array (
'plugin' => 'Elementor Pro',
'from' => '3.0.6',
'to' => '3.3.1',
)]
2021-06-21 12:14:36 [info] Elementor Pro/Upgrades - _v_3_1_0_media_carousel Finished
2021-06-21 12:14:36 [info] Elementor Pro/Upgrades - _v_3_1_0_reviews Start
2021-06-21 12:14:36 [info] Elementor Pro/Upgrades - _v_3_1_0_reviews Finished
2021-06-21 12:14:36 [info] Elementor Pro/Upgrades - _v_3_1_0_testimonial_carousel Start
2021-06-21 12:14:37 [info] Elementor Pro/Upgrades - _v_3_1_0_testimonial_carousel Finished
2021-06-21 12:14:37 [info] Elementor Pro/Upgrades - _v_3_1_0_slides Start
2021-06-21 12:14:37 [info] Elementor Pro/Upgrades - _v_3_1_0_slides Finished
2021-06-21 12:14:37 [info] Elementor Pro/Upgrades - _v_3_3_0_nav_menu_icon Start
2021-06-21 12:14:37 [info] Elementor Pro/Upgrades - _v_3_3_0_nav_menu_icon Finished
2021-06-21 12:14:37 [info] Elementor Pro/Upgrades - _v_3_3_0_recalc_usage_data Start
2021-06-21 12:14:38 [info] Elementor Pro/Upgrades - _v_3_3_0_recalc_usage_data callback needs to run again
2021-06-21 12:14:38 [info] Elementor Pro/Upgrades - _v_3_3_0_recalc_usage_data Start (x2)
2021-06-21 12:14:38 [info] Elementor Pro/Upgrades - _v_3_3_0_recalc_usage_data Finished
2021-06-21 12:14:38 [info] Elementor data updater process has been completed. [array (
'plugin' => 'Elementor Pro',
'from' => '3.0.6',
'to' => '3.3.1',
)]
2023-02-23 10:17:33 [info] Elementor data updater process has been queued. [array (
'plugin' => 'Elementor',
'from' => '3.2.5',
'to' => '3.11.2',
)]
2023-02-23 10:17:33 [info] Elementor data updater process has been completed. [array (
'plugin' => 'Elementor Pro',
'from' => '3.3.1',
'to' => '3.4.2',
)]
2023-02-27 10:42:59 [info] Elementor data updater process has been queued. [array (
'plugin' => 'Elementor Pro',
'from' => '3.4.2',
'to' => '3.11.2',
)]
PHP: showing 8 of 8PHP: 2021-03-28 20:07:24 [error X 1][/home/lmsmysds/public_html/wp-content/plugins/elementor/includes/autoloader.php::269] Allowed memory size of 134217728 bytes exhausted (tried to allocate 73728 bytes) [array (
'trace' => '
#0: Elementor\Core\Logger\Manager -> shutdown()
',
)]
PHP: 2021-03-28 21:36:05 [error X 1][/home/lmsmysds/public_html/wp-content/plugins/elementor/includes/frontend.php::977] Allowed memory size of 134217728 bytes exhausted (tried to allocate 69632 bytes) [array (
'trace' => '
#0: Elementor\Core\Logger\Manager -> shutdown()
',
)]
PHP: 2023-02-23 10:02:34 [error X 185][/home/lmsmysds/public_html/wp-content/plugins/elementor/includes/frontend.php::339] Uncaught Error: Call to a member function is_feature_active() on null in /home/lmsmysds/public_html/wp-content/plugins/elementor/includes/frontend.php:339
Stack trace:
#0 /home/lmsmysds/public_html/wp-content/plugins/elementor/includes/frontend.php(176): Elementor\Frontend->init_swiper_settings()
#1 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/includes/global-header-footer.php(41): Elementor\Frontend->__construct()
#2 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/includes/global-header-footer.php(33): WBCOM_Elementor_Global_Header_Footer->__construct()
#3 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/includes/global-header-footer.php(741): WBCOM_Elementor_Global_Header_Footer::instance()
#4 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/plugin.php(67): require('/home/lmsmysds/...')
#5 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/plugin.php(239): WbcomElementorAddons\Plugin->includes()
#6 /home/lmsmysds/public_html/wp-content/plug [array (
'trace' => '
#0: Elementor\Core\Logger\Manager -> shutdown()
',
)]
PHP: 2023-02-27 10:42:33 [error X 611][/home/lmsmysds/public_html/wp-content/plugins/elementor_bak/includes/frontend.php::339] Uncaught Error: Call to a member function is_feature_active() on null in /home/lmsmysds/public_html/wp-content/plugins/elementor_bak/includes/frontend.php:339
Stack trace:
#0 /home/lmsmysds/public_html/wp-content/plugins/elementor_bak/includes/frontend.php(176): Elementor\Frontend->init_swiper_settings()
#1 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/includes/global-header-footer.php(41): Elementor\Frontend->__construct()
#2 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/includes/global-header-footer.php(33): WBCOM_Elementor_Global_Header_Footer->__construct()
#3 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/includes/global-header-footer.php(741): WBCOM_Elementor_Global_Header_Footer::instance()
#4 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/plugin.php(67): require('/home/lmsmysds/...')
#5 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/plugin.php(239): WbcomElementorAddons\Plugin->includes()
#6 /home/lmsmysds/public_html/wp-cont [array (
'trace' => '
#0: Elementor\Core\Logger\Manager -> shutdown()
',
)]
PHP: 2023-02-28 11:19:30 [error X 22][/home/lmsmysds/public_html/wp-content/plugins/elementor_bak/includes/frontend.php::339] Uncaught Error: Call to a member function is_feature_active() on null in /home/lmsmysds/public_html/wp-content/plugins/elementor_bak/includes/frontend.php:339
Stack trace:
#0 /home/lmsmysds/public_html/wp-content/plugins/elementor_bak/includes/frontend.php(176): Elementor\Frontend->init_swiper_settings()
#1 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/includes/global-header-footer.php(41): Elementor\Frontend->__construct()
#2 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/includes/global-header-footer.php(33): WBCOM_Elementor_Global_Header_Footer->__construct()
#3 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/includes/global-header-footer.php(741): WBCOM_Elementor_Global_Header_Footer::instance()
#4 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/plugin.php(67): require('/home/lmsmysds/...')
#5 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/plugin.php(239): WbcomElementorAddons\Plugin->includes()
#6 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/plugin.php(59): WbcomElementorAddons\Plugin->__construct()
#7 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/plugin.php(245): WbcomElementorAddons\Plugin::instance()
#8 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/wbcom-essential.php(55): require('/home/lmsmysds/...')
#9 /home/lmsmysds/public_html/wp-includes/class-wp-hook.php(308): wbcom_elementor_addons_load_plugin('')
#10 /home/lmsmysds/public_html/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters(NULL, Array)
#11 /home/lmsmysds/public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
#12 /home/lmsmysds/public_html/wp-settings.php(480): do_action('plugins_loaded')
#13 /home/lmsmysds/public_html/wp-config.php(93): require_once('/home/lmsmysds/...')
#14 /home/lmsmysds/public_html/wp-load.php(50): require_once('/home/lmsmysds/...')
#15 /home/lmsmysds/public_html/wp-blog-header.php(13): require_once('/home/lmsmysds/...')
#16 /home/lmsmysds/public_html/index.php(17): require('/home/lmsmysds/...')
#17 {main}
thrown [array (
'trace' => '
#0: Elementor\Core\Logger\Manager -> shutdown()
',
)]
PHP: 2023-02-28 11:19:48 [error X 10][/home/lmsmysds/public_html/wp-content/plugins/elementor_bak/includes/frontend.php::339] Uncaught Error: Call to a member function is_feature_active() on null in /home/lmsmysds/public_html/wp-content/plugins/elementor_bak/includes/frontend.php:339
Stack trace:
#0 /home/lmsmysds/public_html/wp-content/plugins/elementor_bak/includes/frontend.php(176): Elementor\Frontend->init_swiper_settings()
#1 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/includes/global-header-footer.php(41): Elementor\Frontend->__construct()
#2 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/includes/global-header-footer.php(33): WBCOM_Elementor_Global_Header_Footer->__construct()
#3 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/includes/global-header-footer.php(741): WBCOM_Elementor_Global_Header_Footer::instance()
#4 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/plugin.php(67): require('/home/lmsmysds/...')
#5 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/plugin.php(239): WbcomElementorAddons\Plugin->includes()
#6 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/plugin.php(59): WbcomElementorAddons\Plugin->__construct()
#7 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/plugin.php(245): WbcomElementorAddons\Plugin::instance()
#8 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/wbcom-essential.php(55): require('/home/lmsmysds/...')
#9 /home/lmsmysds/public_html/wp-includes/class-wp-hook.php(308): wbcom_elementor_addons_load_plugin('')
#10 /home/lmsmysds/public_html/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters(NULL, Array)
#11 /home/lmsmysds/public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
#12 /home/lmsmysds/public_html/wp-settings.php(480): do_action('plugins_loaded')
#13 /home/lmsmysds/public_html/wp-config.php(93): require_once('/home/lmsmysds/...')
#14 /home/lmsmysds/public_html/wp-load.php(50): require_once('/home/lmsmysds/...')
#15 /home/lmsmysds/public_html/wp-cron.php(46): require_once('/home/lmsmysds/...')
#16 {main}
thrown [array (
'trace' => '
#0: Elementor\Core\Logger\Manager -> shutdown()
',
)]
PHP: 2023-02-28 11:20:36 [error X 3][/home/lmsmysds/public_html/wp-content/plugins/elementor_bak/includes/frontend.php::339] Uncaught Error: Call to a member function is_feature_active() on null in /home/lmsmysds/public_html/wp-content/plugins/elementor_bak/includes/frontend.php:339
Stack trace:
#0 /home/lmsmysds/public_html/wp-content/plugins/elementor_bak/includes/frontend.php(176): Elementor\Frontend->init_swiper_settings()
#1 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/includes/global-header-footer.php(41): Elementor\Frontend->__construct()
#2 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/includes/global-header-footer.php(33): WBCOM_Elementor_Global_Header_Footer->__construct()
#3 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/includes/global-header-footer.php(741): WBCOM_Elementor_Global_Header_Footer::instance()
#4 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/plugin.php(67): require('/home/lmsmysds/...')
#5 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/plugin.php(239): WbcomElementorAddons\Plugin->includes()
#6 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/plugin.php(59): WbcomElementorAddons\Plugin->__construct()
#7 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/plugin.php(245): WbcomElementorAddons\Plugin::instance()
#8 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/wbcom-essential.php(55): require('/home/lmsmysds/...')
#9 /home/lmsmysds/public_html/wp-includes/class-wp-hook.php(308): wbcom_elementor_addons_load_plugin('')
#10 /home/lmsmysds/public_html/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters(NULL, Array)
#11 /home/lmsmysds/public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
#12 /home/lmsmysds/public_html/wp-settings.php(480): do_action('plugins_loaded')
#13 /home/lmsmysds/public_html/wp-config.php(93): require_once('/home/lmsmysds/...')
#14 /home/lmsmysds/public_html/wp-load.php(50): require_once('/home/lmsmysds/...')
#15 /home/lmsmysds/public_html/xmlrpc.php(31): require_once('/home/lmsmysds/...')
#16 {main}
thrown [array (
'trace' => '
#0: Elementor\Core\Logger\Manager -> shutdown()
',
)]
PHP: 2023-02-28 11:25:43 [error X 2][/home/lmsmysds/public_html/wp-content/plugins/elementor_bak/includes/frontend.php::339] Uncaught Error: Call to a member function is_feature_active() on null in /home/lmsmysds/public_html/wp-content/plugins/elementor_bak/includes/frontend.php:339
Stack trace:
#0 /home/lmsmysds/public_html/wp-content/plugins/elementor_bak/includes/frontend.php(176): Elementor\Frontend->init_swiper_settings()
#1 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/includes/global-header-footer.php(41): Elementor\Frontend->__construct()
#2 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/includes/global-header-footer.php(33): WBCOM_Elementor_Global_Header_Footer->__construct()
#3 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/includes/global-header-footer.php(741): WBCOM_Elementor_Global_Header_Footer::instance()
#4 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/plugin.php(67): require('/home/lmsmysds/...')
#5 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/plugin.php(239): WbcomElementorAddons\Plugin->includes()
#6 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/plugin.php(59): WbcomElementorAddons\Plugin->__construct()
#7 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/plugin.php(245): WbcomElementorAddons\Plugin::instance()
#8 /home/lmsmysds/public_html/wp-content/plugins/wbcom-essential/wbcom-essential.php(55): require('/home/lmsmysds/...')
#9 /home/lmsmysds/public_html/wp-includes/class-wp-hook.php(308): wbcom_elementor_addons_load_plugin('')
#10 /home/lmsmysds/public_html/wp-includes/class-wp-hook.php(332): WP_Hook->apply_filters(NULL, Array)
#11 /home/lmsmysds/public_html/wp-includes/plugin.php(517): WP_Hook->do_action(Array)
#12 /home/lmsmysds/public_html/wp-settings.php(480): do_action('plugins_loaded')
#13 /home/lmsmysds/public_html/wp-config.php(93): require_once('/home/lmsmysds/...')
#14 /home/lmsmysds/public_html/wp-load.php(50): require_once('/home/lmsmysds/...')
#15 /home/lmsmysds/public_html/wp-login.php(12): require('/home/lmsmysds/...')
#16 {main}
thrown [array (
'trace' => '
#0: Elementor\Core\Logger\Manager -> shutdown()
',
)]
== Elementor - Compatibility Tag ==
Contact Form DB - Elementor: Compatibility not specified
Elementor: Compatibility not specified
Elementor Pro: Compatibility not specified
== Elementor Pro - Compatibility Tag ==
| comp | ⛔ 🐞 bug report lementor gets affected with woocommerence prerequisites i have searched for similar issues in both open and closed tickets and cannot find a duplicate the issue still exists against the latest stable version of elementor description whenever i activate any woocommerce plugin elementor gets affected steps to reproduce i have updated elementor and elementor pro plugin after updating that my website get down and got a email notification your site is experiencing a technical issue and they provide me a recovery mode link whenever i activate any woocommerce plugin elementor gets affected isolating the problem this bug happens with only elementor plugin active and elementor pro this bug happens with a blank wordpress theme active i can reproduce this bug consistently following the steps above system info server environment operating system linux software apache mysql version mariadb server php version php memory limit php max input vars php max post size gd installed yes zip installed yes write permissions all right elementor library connected wordpress environment version site url home url wp multisite no max upload size mb memory limit max memory limit permalink structure year monthnum day postname language en us timezone america toronto admin email kamljeet mysds ca debug mode inactive theme name reign version author wbcom designs child theme no user role administrator wp profile lang en us user agent mozilla windows nt applewebkit khtml like gecko chrome safari active plugins admin menu editor version author janis elsts advanced custom fields version author wp engine autocomplete woocommerce orders version author quadlayers backup duplicator migration wp staging version author wp staging wpstagingbackup clean wp dashboard version author jerod santo contact form db elementor version author web ace tech services course scheduler for learndash version author wooninjas custom template for learndash version author pratik chaskar debug this version author wpchill design upgrade for learndash version author escape creative disable admin notices individually version author creative motion elementor version author elementor com elementor pro version author elementor com frontend reset password version author wp enhanced increase maximum upload file size version author imagify learndash exporter version author manuel costales learndash gravityforms addon version author learndash learndash licensing management version author learndash learndash lms version author learndash learndash lms course grid version author learndash learndash lms notifications version author learndash learndash lms propanel version author learndash learndash notes version author snaporbital loginwp formerly peter s login redirect version author loginwp team privileged menu version author tin canny learndash reporting version author uncanny owl uncanny codes version author uncanny owl uncanny groups for learndash version author uncanny owl uncanny toolkit for learndash version author uncanny owl uncanny toolkit pro for learndash version author uncanny owl wp htaccess editor version author webfactory ltd wp rollback version author givewp com must use plugins learndash lms multisite version author learndash wp staging optimizer version author rené hermenau features custom fonts custom icons integrations elementor experiments optimized dom output inactive by default improved asset loading inactive by default improved css loading inactive by default inline font icons inactive by default accessibility improvements inactive by default additional custom breakpoints inactive by default admin menu rearrangement inactive by default flexbox container inactive by default upgrade swiper library inactive by default default to new theme builder active by default editor inactive by default landing pages active by default nested elements inactive by default lazy load background images inactive by default save as default active by default page transitions active by default notes active by default loop active by default form submissions active by default scroll snap active by default mega menu inactive by default log log showing of elementor pro elementor pro updater started elementor pro upgrades v media carousel start elementor data updater process has been queued array plugin elementor pro from to elementor pro upgrades v media carousel finished elementor pro upgrades v reviews start elementor pro upgrades v reviews finished elementor pro upgrades v testimonial carousel start elementor pro upgrades v testimonial carousel finished elementor pro upgrades v slides start elementor pro upgrades v slides finished elementor pro upgrades v nav menu icon start elementor pro upgrades v nav menu icon finished elementor pro upgrades v recalc usage data start elementor pro upgrades v recalc usage data callback needs to run again elementor pro upgrades v recalc usage data start elementor pro upgrades v recalc usage data finished elementor data updater process has been completed array plugin elementor pro from to elementor data updater process has been queued array plugin elementor from to elementor data updater process has been completed array plugin elementor pro from to elementor data updater process has been queued array plugin elementor pro from to php showing of allowed memory size of bytes exhausted tried to allocate bytes array trace elementor core logger manager shutdown php allowed memory size of bytes exhausted tried to allocate bytes array trace elementor core logger manager shutdown php uncaught error call to a member function is feature active on null in home lmsmysds public html wp content plugins elementor includes frontend php stack trace home lmsmysds public html wp content plugins elementor includes frontend php elementor frontend init swiper settings home lmsmysds public html wp content plugins wbcom essential includes global header footer php elementor frontend construct home lmsmysds public html wp content plugins wbcom essential includes global header footer php wbcom elementor global header footer construct home lmsmysds public html wp content plugins wbcom essential includes global header footer php wbcom elementor global header footer instance home lmsmysds public html wp content plugins wbcom essential plugin php require home lmsmysds home lmsmysds public html wp content plugins wbcom essential plugin php wbcomelementoraddons plugin includes home lmsmysds public html wp content plug array trace elementor core logger manager shutdown php uncaught error call to a member function is feature active on null in home lmsmysds public html wp content plugins elementor bak includes frontend php stack trace home lmsmysds public html wp content plugins elementor bak includes frontend php elementor frontend init swiper settings home lmsmysds public html wp content plugins wbcom essential includes global header footer php elementor frontend construct home lmsmysds public html wp content plugins wbcom essential includes global header footer php wbcom elementor global header footer construct home lmsmysds public html wp content plugins wbcom essential includes global header footer php wbcom elementor global header footer instance home lmsmysds public html wp content plugins wbcom essential plugin php require home lmsmysds home lmsmysds public html wp content plugins wbcom essential plugin php wbcomelementoraddons plugin includes home lmsmysds public html wp cont array trace elementor core logger manager shutdown php uncaught error call to a member function is feature active on null in home lmsmysds public html wp content plugins elementor bak includes frontend php stack trace home lmsmysds public html wp content plugins elementor bak includes frontend php elementor frontend init swiper settings home lmsmysds public html wp content plugins wbcom essential includes global header footer php elementor frontend construct home lmsmysds public html wp content plugins wbcom essential includes global header footer php wbcom elementor global header footer construct home lmsmysds public html wp content plugins wbcom essential includes global header footer php wbcom elementor global header footer instance home lmsmysds public html wp content plugins wbcom essential plugin php require home lmsmysds home lmsmysds public html wp content plugins wbcom essential plugin php wbcomelementoraddons plugin includes home lmsmysds public html wp content plugins wbcom essential plugin php wbcomelementoraddons plugin construct home lmsmysds public html wp content plugins wbcom essential plugin php wbcomelementoraddons plugin instance home lmsmysds public html wp content plugins wbcom essential wbcom essential php require home lmsmysds home lmsmysds public html wp includes class wp hook php wbcom elementor addons load plugin home lmsmysds public html wp includes class wp hook php wp hook apply filters null array home lmsmysds public html wp includes plugin php wp hook do action array home lmsmysds public html wp settings php do action plugins loaded home lmsmysds public html wp config php require once home lmsmysds home lmsmysds public html wp load php require once home lmsmysds home lmsmysds public html wp blog header php require once home lmsmysds home lmsmysds public html index php require home lmsmysds main thrown array trace elementor core logger manager shutdown php uncaught error call to a member function is feature active on null in home lmsmysds public html wp content plugins elementor bak includes frontend php stack trace home lmsmysds public html wp content plugins elementor bak includes frontend php elementor frontend init swiper settings home lmsmysds public html wp content plugins wbcom essential includes global header footer php elementor frontend construct home lmsmysds public html wp content plugins wbcom essential includes global header footer php wbcom elementor global header footer construct home lmsmysds public html wp content plugins wbcom essential includes global header footer php wbcom elementor global header footer instance home lmsmysds public html wp content plugins wbcom essential plugin php require home lmsmysds home lmsmysds public html wp content plugins wbcom essential plugin php wbcomelementoraddons plugin includes home lmsmysds public html wp content plugins wbcom essential plugin php wbcomelementoraddons plugin construct home lmsmysds public html wp content plugins wbcom essential plugin php wbcomelementoraddons plugin instance home lmsmysds public html wp content plugins wbcom essential wbcom essential php require home lmsmysds home lmsmysds public html wp includes class wp hook php wbcom elementor addons load plugin home lmsmysds public html wp includes class wp hook php wp hook apply filters null array home lmsmysds public html wp includes plugin php wp hook do action array home lmsmysds public html wp settings php do action plugins loaded home lmsmysds public html wp config php require once home lmsmysds home lmsmysds public html wp load php require once home lmsmysds home lmsmysds public html wp cron php require once home lmsmysds main thrown array trace elementor core logger manager shutdown php uncaught error call to a member function is feature active on null in home lmsmysds public html wp content plugins elementor bak includes frontend php stack trace home lmsmysds public html wp content plugins elementor bak includes frontend php elementor frontend init swiper settings home lmsmysds public html wp content plugins wbcom essential includes global header footer php elementor frontend construct home lmsmysds public html wp content plugins wbcom essential includes global header footer php wbcom elementor global header footer construct home lmsmysds public html wp content plugins wbcom essential includes global header footer php wbcom elementor global header footer instance home lmsmysds public html wp content plugins wbcom essential plugin php require home lmsmysds home lmsmysds public html wp content plugins wbcom essential plugin php wbcomelementoraddons plugin includes home lmsmysds public html wp content plugins wbcom essential plugin php wbcomelementoraddons plugin construct home lmsmysds public html wp content plugins wbcom essential plugin php wbcomelementoraddons plugin instance home lmsmysds public html wp content plugins wbcom essential wbcom essential php require home lmsmysds home lmsmysds public html wp includes class wp hook php wbcom elementor addons load plugin home lmsmysds public html wp includes class wp hook php wp hook apply filters null array home lmsmysds public html wp includes plugin php wp hook do action array home lmsmysds public html wp settings php do action plugins loaded home lmsmysds public html wp config php require once home lmsmysds home lmsmysds public html wp load php require once home lmsmysds home lmsmysds public html xmlrpc php require once home lmsmysds main thrown array trace elementor core logger manager shutdown php uncaught error call to a member function is feature active on null in home lmsmysds public html wp content plugins elementor bak includes frontend php stack trace home lmsmysds public html wp content plugins elementor bak includes frontend php elementor frontend init swiper settings home lmsmysds public html wp content plugins wbcom essential includes global header footer php elementor frontend construct home lmsmysds public html wp content plugins wbcom essential includes global header footer php wbcom elementor global header footer construct home lmsmysds public html wp content plugins wbcom essential includes global header footer php wbcom elementor global header footer instance home lmsmysds public html wp content plugins wbcom essential plugin php require home lmsmysds home lmsmysds public html wp content plugins wbcom essential plugin php wbcomelementoraddons plugin includes home lmsmysds public html wp content plugins wbcom essential plugin php wbcomelementoraddons plugin construct home lmsmysds public html wp content plugins wbcom essential plugin php wbcomelementoraddons plugin instance home lmsmysds public html wp content plugins wbcom essential wbcom essential php require home lmsmysds home lmsmysds public html wp includes class wp hook php wbcom elementor addons load plugin home lmsmysds public html wp includes class wp hook php wp hook apply filters null array home lmsmysds public html wp includes plugin php wp hook do action array home lmsmysds public html wp settings php do action plugins loaded home lmsmysds public html wp config php require once home lmsmysds home lmsmysds public html wp load php require once home lmsmysds home lmsmysds public html wp login php require home lmsmysds main thrown array trace elementor core logger manager shutdown elementor compatibility tag contact form db elementor compatibility not specified elementor compatibility not specified elementor pro compatibility not specified elementor pro compatibility tag | 1 |
524,012 | 15,194,296,292 | IssuesEvent | 2021-02-16 03:13:56 | medic/medic-gateway | https://api.github.com/repos/medic/medic-gateway | closed | Document and solve upgrade path issues | Priority: 2 - Medium Type: Technical issue | Nepal MoH is using an older version of medic-gateway, as documented in [this project issue](https://github.com/medic/config-moh-nepal/issues/6). Work out what's needed to get them on to the latest so they can benefit from any improvements we make. | 1.0 | Document and solve upgrade path issues - Nepal MoH is using an older version of medic-gateway, as documented in [this project issue](https://github.com/medic/config-moh-nepal/issues/6). Work out what's needed to get them on to the latest so they can benefit from any improvements we make. | non_comp | document and solve upgrade path issues nepal moh is using an older version of medic gateway as documented in work out what s needed to get them on to the latest so they can benefit from any improvements we make | 0 |
366,896 | 10,831,907,057 | IssuesEvent | 2019-11-11 09:27:15 | webcompat/web-bugs | https://api.github.com/repos/webcompat/web-bugs | closed | www.ricardo.ch - site is not usable | browser-firefox engine-gecko priority-normal | <!-- @browser: Firefox 71.0 -->
<!-- @ua_header: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:71.0) Gecko/20100101 Firefox/71.0 -->
<!-- @reported_with: desktop-reporter -->
**URL**: https://www.ricardo.ch/de/s/21042/
**Browser / Version**: Firefox 71.0
**Operating System**: Windows 10
**Tested Another Browser**: Yes
**Problem type**: Site is not usable
**Description**: Coming from the mane page https://www.ricardo.ch/ , inserting a serach criteria, the result page appears blank
**Steps to Reproduce**:
Gone to page www.ricardo.ch. Search for number 10214 in the search bar on the page of Ricardo.ch, the result page then is compl. blank. The problem exists also searching anything else; the result page is even blank. The problem does not exists using other browsers like Chorme or MS IE (MS Edge).
[](https://webcompat.com/uploads/2019/11/5f09604e-02a3-4052-be8b-cb0117fe14e8.jpeg)
[](https://webcompat.com/uploads/2019/11/3095dfe1-45d3-4fe2-8bd8-8ab38bedb3c5.jpeg)
<details>
<summary>Browser Configuration</summary>
<ul>
<li>gfx.webrender.all: false</li><li>gfx.webrender.blob-images: true</li><li>gfx.webrender.enabled: false</li><li>image.mem.shared: true</li><li>buildID: 20191021164841</li><li>channel: beta</li><li>hasTouchScreen: false</li><li>mixed active content blocked: false</li><li>mixed passive content blocked: false</li><li>tracking content blocked: false</li>
</ul>
<p>Console Messages:</p>
<pre>
[{'level': 'error', 'log': ['Die Zeichenkodierung des Reintext-Dokuments wurde nicht deklariert. Das Dokument wird in manchen Browser-Konfigurationen mit verstmmeltem Text dargestellt, wenn das Dokument Zeichen auerhalb des US-ASCII-Bereichs enthlt. Die Zeichenkodierung der Seite muss im Transferprotokoll deklariert werden oder die Datei muss eine Byte-Order-Markierung als Kodierungssignatur verwenden.'], 'uri': 'https://www.ricardo.ch/de/s/21042/', 'pos': '0:0'}, {'level': 'warn', 'log': ['This page uses the non standard property zoom. Consider using calc() in the relevant property values, or using transform along with transform-origin: 0 0.'], 'uri': 'moz-extension://7866ac50-d1a7-41ff-874b-111a82a75200/frontend/notification/index.html?ref=https%3A%2F%2Fwww.ricardo.ch%2F', 'pos': '0:0'}]
</pre>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_ | 1.0 | www.ricardo.ch - site is not usable - <!-- @browser: Firefox 71.0 -->
<!-- @ua_header: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:71.0) Gecko/20100101 Firefox/71.0 -->
<!-- @reported_with: desktop-reporter -->
**URL**: https://www.ricardo.ch/de/s/21042/
**Browser / Version**: Firefox 71.0
**Operating System**: Windows 10
**Tested Another Browser**: Yes
**Problem type**: Site is not usable
**Description**: Coming from the mane page https://www.ricardo.ch/ , inserting a serach criteria, the result page appears blank
**Steps to Reproduce**:
Gone to page www.ricardo.ch. Search for number 10214 in the search bar on the page of Ricardo.ch, the result page then is compl. blank. The problem exists also searching anything else; the result page is even blank. The problem does not exists using other browsers like Chorme or MS IE (MS Edge).
[](https://webcompat.com/uploads/2019/11/5f09604e-02a3-4052-be8b-cb0117fe14e8.jpeg)
[](https://webcompat.com/uploads/2019/11/3095dfe1-45d3-4fe2-8bd8-8ab38bedb3c5.jpeg)
<details>
<summary>Browser Configuration</summary>
<ul>
<li>gfx.webrender.all: false</li><li>gfx.webrender.blob-images: true</li><li>gfx.webrender.enabled: false</li><li>image.mem.shared: true</li><li>buildID: 20191021164841</li><li>channel: beta</li><li>hasTouchScreen: false</li><li>mixed active content blocked: false</li><li>mixed passive content blocked: false</li><li>tracking content blocked: false</li>
</ul>
<p>Console Messages:</p>
<pre>
[{'level': 'error', 'log': ['Die Zeichenkodierung des Reintext-Dokuments wurde nicht deklariert. Das Dokument wird in manchen Browser-Konfigurationen mit verstmmeltem Text dargestellt, wenn das Dokument Zeichen auerhalb des US-ASCII-Bereichs enthlt. Die Zeichenkodierung der Seite muss im Transferprotokoll deklariert werden oder die Datei muss eine Byte-Order-Markierung als Kodierungssignatur verwenden.'], 'uri': 'https://www.ricardo.ch/de/s/21042/', 'pos': '0:0'}, {'level': 'warn', 'log': ['This page uses the non standard property zoom. Consider using calc() in the relevant property values, or using transform along with transform-origin: 0 0.'], 'uri': 'moz-extension://7866ac50-d1a7-41ff-874b-111a82a75200/frontend/notification/index.html?ref=https%3A%2F%2Fwww.ricardo.ch%2F', 'pos': '0:0'}]
</pre>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_ | non_comp | site is not usable url browser version firefox operating system windows tested another browser yes problem type site is not usable description coming from the mane page inserting a serach criteria the result page appears blank steps to reproduce gone to page search for number in the search bar on the page of ricardo ch the result page then is compl blank the problem exists also searching anything else the result page is even blank the problem does not exists using other browsers like chorme or ms ie ms edge browser configuration gfx webrender all false gfx webrender blob images true gfx webrender enabled false image mem shared true buildid channel beta hastouchscreen false mixed active content blocked false mixed passive content blocked false tracking content blocked false console messages uri pos level warn log uri moz extension frontend notification index html ref https pos from with ❤️ | 0 |
10,726 | 12,691,685,923 | IssuesEvent | 2020-06-21 18:19:41 | ClickHouse/ClickHouse | https://api.github.com/repos/ClickHouse/ClickHouse | closed | countDistinct returns null, instead of 0 for null types | bug sql-compatibility | Steps to reproduce:
**1. Create table with the following structure:**
```
xxxx :) CREATE TABLE nullableCountTest ( type UInt32, subType Nullable(String)) ENGINE=Log
CREATE TABLE nullableCountTest
(
type UInt32,
subType Nullable(String)
)
ENGINE = Log
Ok.
0 rows in set. Elapsed: 0.002 sec.
```
**2. Insert some data, similar to what I've inserted:**
```
xxxx :) INSERT INTO nullableCountTest VALUES (1, 'myType'), (2, 'myType2'), (3, 'myType3'), (4, 'myType'), (5, Null)
INSERT INTO default.nullableCountTest VALUES
Ok.
5 rows in set. Elapsed: 0.003 sec.
```
**3. Make a distinctCount query**
```
xxxx :) SELECT subType, countDistinct(subType) FROM nullableCountTest GROUP BY subType;
SELECT
subType,
countDistinct(subType)
FROM nullableCountTest
GROUP BY subType
┌─subType─┬─uniqExact(subType)─┐
│ myType3 │ 1 │
│ myType │ 1 │
│ myType2 │ 1 │
│ \N │ \N │
└─────────┴────────────────────┘
4 rows in set. Elapsed: 0.003 sec.
```
It might be a bug, or expected behaviour, but what if I want to process the result:
```
xxxx :) SELECT if(countDistinct(subType) IS NULL, '0 Items', concat(CAST(countDistinct(subType) AS Char), ' Items')) FROM default.nullableCountTest GROUP BY subType;
SELECT if(isNull(countDistinct(subType)), '0 Items', concat(CAST(countDistinct(subType) AS Char), ' Items'))
FROM nullableCountTest
GROUP BY subType
Received exception from server (version 1.1.54383):
Code: 349. DB::Exception: Received from localhost:9000, 127.0.0.1. DB::Exception: Cannot convert NULL value to non-Nullable type.
0 rows in set. Elapsed: 0.113 sec.
```
It doesn't allow conversion of null to another type. Also, it looks like both the expressions in the IF are evaluated regardless if the condition is met. Then the condition decides which one to use. I might be wrong, but the ifnull would be working then..
_the simple count function works as expected, though:_
```
xxxx :) SELECT subType, count(subType) FROM nullableCountTest GROUP BY subType;
SELECT
subType,
count(subType)
FROM nullableCountTest
GROUP BY subType
┌─subType─┬─count(subType)─┐
│ myType3 │ 1 │
│ myType │ 2 │
│ myType2 │ 1 │
│ \N │ 0 │
└─────────┴────────────────┘
4 rows in set. Elapsed: 0.003 sec.
```
| True | countDistinct returns null, instead of 0 for null types - Steps to reproduce:
**1. Create table with the following structure:**
```
xxxx :) CREATE TABLE nullableCountTest ( type UInt32, subType Nullable(String)) ENGINE=Log
CREATE TABLE nullableCountTest
(
type UInt32,
subType Nullable(String)
)
ENGINE = Log
Ok.
0 rows in set. Elapsed: 0.002 sec.
```
**2. Insert some data, similar to what I've inserted:**
```
xxxx :) INSERT INTO nullableCountTest VALUES (1, 'myType'), (2, 'myType2'), (3, 'myType3'), (4, 'myType'), (5, Null)
INSERT INTO default.nullableCountTest VALUES
Ok.
5 rows in set. Elapsed: 0.003 sec.
```
**3. Make a distinctCount query**
```
xxxx :) SELECT subType, countDistinct(subType) FROM nullableCountTest GROUP BY subType;
SELECT
subType,
countDistinct(subType)
FROM nullableCountTest
GROUP BY subType
┌─subType─┬─uniqExact(subType)─┐
│ myType3 │ 1 │
│ myType │ 1 │
│ myType2 │ 1 │
│ \N │ \N │
└─────────┴────────────────────┘
4 rows in set. Elapsed: 0.003 sec.
```
It might be a bug, or expected behaviour, but what if I want to process the result:
```
xxxx :) SELECT if(countDistinct(subType) IS NULL, '0 Items', concat(CAST(countDistinct(subType) AS Char), ' Items')) FROM default.nullableCountTest GROUP BY subType;
SELECT if(isNull(countDistinct(subType)), '0 Items', concat(CAST(countDistinct(subType) AS Char), ' Items'))
FROM nullableCountTest
GROUP BY subType
Received exception from server (version 1.1.54383):
Code: 349. DB::Exception: Received from localhost:9000, 127.0.0.1. DB::Exception: Cannot convert NULL value to non-Nullable type.
0 rows in set. Elapsed: 0.113 sec.
```
It doesn't allow conversion of null to another type. Also, it looks like both the expressions in the IF are evaluated regardless if the condition is met. Then the condition decides which one to use. I might be wrong, but the ifnull would be working then..
_the simple count function works as expected, though:_
```
xxxx :) SELECT subType, count(subType) FROM nullableCountTest GROUP BY subType;
SELECT
subType,
count(subType)
FROM nullableCountTest
GROUP BY subType
┌─subType─┬─count(subType)─┐
│ myType3 │ 1 │
│ myType │ 2 │
│ myType2 │ 1 │
│ \N │ 0 │
└─────────┴────────────────┘
4 rows in set. Elapsed: 0.003 sec.
```
| comp | countdistinct returns null instead of for null types steps to reproduce create table with the following structure xxxx create table nullablecounttest type subtype nullable string engine log create table nullablecounttest type subtype nullable string engine log ok rows in set elapsed sec insert some data similar to what i ve inserted xxxx insert into nullablecounttest values mytype mytype null insert into default nullablecounttest values ok rows in set elapsed sec make a distinctcount query xxxx select subtype countdistinct subtype from nullablecounttest group by subtype select subtype countdistinct subtype from nullablecounttest group by subtype ┌─subtype─┬─uniqexact subtype ─┐ │ │ │ │ mytype │ │ │ │ │ │ n │ n │ └─────────┴────────────────────┘ rows in set elapsed sec it might be a bug or expected behaviour but what if i want to process the result xxxx select if countdistinct subtype is null items concat cast countdistinct subtype as char items from default nullablecounttest group by subtype select if isnull countdistinct subtype items concat cast countdistinct subtype as char items from nullablecounttest group by subtype received exception from server version code db exception received from localhost db exception cannot convert null value to non nullable type rows in set elapsed sec it doesn t allow conversion of null to another type also it looks like both the expressions in the if are evaluated regardless if the condition is met then the condition decides which one to use i might be wrong but the ifnull would be working then the simple count function works as expected though xxxx select subtype count subtype from nullablecounttest group by subtype select subtype count subtype from nullablecounttest group by subtype ┌─subtype─┬─count subtype ─┐ │ │ │ │ mytype │ │ │ │ │ │ n │ │ └─────────┴────────────────┘ rows in set elapsed sec | 1 |
15,842 | 20,753,331,725 | IssuesEvent | 2022-03-15 09:50:25 | safing/portmaster | https://api.github.com/repos/safing/portmaster | closed | Issues running Urbackup with Portmaster | in/compatibility | **What worked?**
Nothing :(
**What did not work?**
I believe portmaster blocks all UDP probes heading to the local network server. I have a urbackup server within my local network and they usually auto-negotiate with my main pc urbackup-client but since portmaster it doesn't seem to communicate. Same problem with my laptop. I've tried allowing the program and the backend service but no dice 😢
| True | Issues running Urbackup with Portmaster - **What worked?**
Nothing :(
**What did not work?**
I believe portmaster blocks all UDP probes heading to the local network server. I have a urbackup server within my local network and they usually auto-negotiate with my main pc urbackup-client but since portmaster it doesn't seem to communicate. Same problem with my laptop. I've tried allowing the program and the backend service but no dice 😢
| comp | issues running urbackup with portmaster what worked nothing what did not work i believe portmaster blocks all udp probes heading to the local network server i have a urbackup server within my local network and they usually auto negotiate with my main pc urbackup client but since portmaster it doesn t seem to communicate same problem with my laptop i ve tried allowing the program and the backend service but no dice 😢 | 1 |
18,411 | 25,483,182,693 | IssuesEvent | 2022-11-26 02:51:18 | fildesh/fildesh | https://api.github.com/repos/fildesh/fildesh | opened | Deprecate `#include "fildesh.h"` way of including libfildesh header | incompatibility | ## Workaround
Use `#include <fildesh/fildesh.h>` instead.
## Timeline
* v0.1.6 will make the workaround possible.
* v0.1.6 will require the workaround in dependent CMake projects.
* v0.2.0 will require the workaround in dependent Bazel projects. | True | Deprecate `#include "fildesh.h"` way of including libfildesh header - ## Workaround
Use `#include <fildesh/fildesh.h>` instead.
## Timeline
* v0.1.6 will make the workaround possible.
* v0.1.6 will require the workaround in dependent CMake projects.
* v0.2.0 will require the workaround in dependent Bazel projects. | comp | deprecate include fildesh h way of including libfildesh header workaround use include instead timeline will make the workaround possible will require the workaround in dependent cmake projects will require the workaround in dependent bazel projects | 1 |
16,717 | 23,048,257,080 | IssuesEvent | 2022-07-24 08:23:37 | beauwilliams/focus.nvim | https://api.github.com/repos/beauwilliams/focus.nvim | closed | Vifm Problems while focus change | good first issue compatibility | Hi and sorry for a improper error reporting. Not sure exactly how to start.
So I use vifm (https://vifm.info) as my primary file manager in Neovim.
When i use ":VsplitVifm", a split window is opened with vifm as file manager within.
Using vifm works without problems, but as soon as focus to another buffer and then back to the vifmsplit, vifm stops working (no directory browsing, no command line etc.)
When I use :q to quit the vifm buffer, its not possible to reopen another vifm buffer (buffer is already existing).
In order to resume normal working for any vifm buffers, the (old vifm) buffer needs to be close via ":bd!" (just ":bd" does not seem to work somehow ..)
I tried some exclude_*:
```
excluded_filetypes = {"toggleterm","terminal","term", "VsplitVifm"},
excluded_buftypes = {"help", "vifm", "nofile", "prompt", "popup", "terminal","term","VsplitVifm"}
```
but nothing seems to help.
Any help or tips are greatly appreciated!
Bye the way: NICE Plugin!
| True | Vifm Problems while focus change - Hi and sorry for a improper error reporting. Not sure exactly how to start.
So I use vifm (https://vifm.info) as my primary file manager in Neovim.
When i use ":VsplitVifm", a split window is opened with vifm as file manager within.
Using vifm works without problems, but as soon as focus to another buffer and then back to the vifmsplit, vifm stops working (no directory browsing, no command line etc.)
When I use :q to quit the vifm buffer, its not possible to reopen another vifm buffer (buffer is already existing).
In order to resume normal working for any vifm buffers, the (old vifm) buffer needs to be close via ":bd!" (just ":bd" does not seem to work somehow ..)
I tried some exclude_*:
```
excluded_filetypes = {"toggleterm","terminal","term", "VsplitVifm"},
excluded_buftypes = {"help", "vifm", "nofile", "prompt", "popup", "terminal","term","VsplitVifm"}
```
but nothing seems to help.
Any help or tips are greatly appreciated!
Bye the way: NICE Plugin!
| comp | vifm problems while focus change hi and sorry for a improper error reporting not sure exactly how to start so i use vifm as my primary file manager in neovim when i use vsplitvifm a split window is opened with vifm as file manager within using vifm works without problems but as soon as focus to another buffer and then back to the vifmsplit vifm stops working no directory browsing no command line etc when i use q to quit the vifm buffer its not possible to reopen another vifm buffer buffer is already existing in order to resume normal working for any vifm buffers the old vifm buffer needs to be close via bd just bd does not seem to work somehow i tried some exclude excluded filetypes toggleterm terminal term vsplitvifm excluded buftypes help vifm nofile prompt popup terminal term vsplitvifm but nothing seems to help any help or tips are greatly appreciated bye the way nice plugin | 1 |
276,151 | 30,348,499,628 | IssuesEvent | 2023-07-11 17:06:03 | MatBenfield/news | https://api.github.com/repos/MatBenfield/news | closed | [SecurityWeek] TPG to Acquire Forcepoint’s Government Cybersecurity Business Unit | SecurityWeek Stale |
Private equity giant plans to buy Forcepoint’s Global Governments and Critical Infrastructure (G2CI) business unit for $2.5 billion.
The post [TPG to Acquire Forcepoint’s Government Cybersecurity Business Unit](https://www.securityweek.com/tpg-to-acquire-forcepoints-government-cybersecurity-business-unit/) appeared first on [SecurityWeek](https://www.securityweek.com).
<https://www.securityweek.com/tpg-to-acquire-forcepoints-government-cybersecurity-business-unit/>
| True | [SecurityWeek] TPG to Acquire Forcepoint’s Government Cybersecurity Business Unit -
Private equity giant plans to buy Forcepoint’s Global Governments and Critical Infrastructure (G2CI) business unit for $2.5 billion.
The post [TPG to Acquire Forcepoint’s Government Cybersecurity Business Unit](https://www.securityweek.com/tpg-to-acquire-forcepoints-government-cybersecurity-business-unit/) appeared first on [SecurityWeek](https://www.securityweek.com).
<https://www.securityweek.com/tpg-to-acquire-forcepoints-government-cybersecurity-business-unit/>
| non_comp | tpg to acquire forcepoint’s government cybersecurity business unit private equity giant plans to buy forcepoint’s global governments and critical infrastructure business unit for billion the post appeared first on | 0 |
3,571 | 6,494,424,394 | IssuesEvent | 2017-08-21 21:44:38 | csf-dev/CSF.Screenplay | https://api.github.com/repos/csf-dev/CSF.Screenplay | closed | Rename screenplay context to 'scenario' | breaks-compatibility enhancement | The class `ScreenplayContext` should be renamed `ScreenplayScenario`.
It should expose a context which is suitable for a single scenario only. | True | Rename screenplay context to 'scenario' - The class `ScreenplayContext` should be renamed `ScreenplayScenario`.
It should expose a context which is suitable for a single scenario only. | comp | rename screenplay context to scenario the class screenplaycontext should be renamed screenplayscenario it should expose a context which is suitable for a single scenario only | 1 |
2,724 | 5,459,829,585 | IssuesEvent | 2017-03-09 02:12:04 | Polymer/polymer | https://api.github.com/repos/Polymer/polymer | closed | 2.x class-based elements don't have behaviors defined in the constructor | 1.x-2.x compatibility 2.x | A legacy element (`Polymer({ is: 'my-el' })`) will have `behaviors` defined for each instance.
A class-based element (`class MyEl extends Polymer.Element`) will instead have `behaviors` defined in the constructor, so each instance must access via `this.constructor.behaviors`.
http://jsbin.com/fufikun/1/edit?html,console,output
How should hybrid element authors go about it? | True | 2.x class-based elements don't have behaviors defined in the constructor - A legacy element (`Polymer({ is: 'my-el' })`) will have `behaviors` defined for each instance.
A class-based element (`class MyEl extends Polymer.Element`) will instead have `behaviors` defined in the constructor, so each instance must access via `this.constructor.behaviors`.
http://jsbin.com/fufikun/1/edit?html,console,output
How should hybrid element authors go about it? | comp | x class based elements don t have behaviors defined in the constructor a legacy element polymer is my el will have behaviors defined for each instance a class based element class myel extends polymer element will instead have behaviors defined in the constructor so each instance must access via this constructor behaviors how should hybrid element authors go about it | 1 |
278,055 | 30,702,184,640 | IssuesEvent | 2023-07-27 01:09:36 | Satheesh575555/packages_apps_Settings_AOSP10_r33_CVE-2021-0333 | https://api.github.com/repos/Satheesh575555/packages_apps_Settings_AOSP10_r33_CVE-2021-0333 | reopened | CVE-2021-0434 (High) detected in Settingsandroid-10.0.0_r33 | Mend: dependency security vulnerability | ## CVE-2021-0434 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>Settingsandroid-10.0.0_r33</b></p></summary>
<p>
<p>Library home page: <a href=https://android.googlesource.com/platform/packages/apps/Settings>https://android.googlesource.com/platform/packages/apps/Settings</a></p>
<p>Found in HEAD commit: <a href="https://github.com/Satheesh575555/packages_apps_Settings_AOSP10_r33_CVE-2021-0333/commit/a353664da30a0b95adee9281a4af5c1d5cacc22e">a353664da30a0b95adee9281a4af5c1d5cacc22e</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/src/com/android/settings/bluetooth/BluetoothPermissionRequest.java</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> Vulnerability Details</summary>
<p>
In onReceive of BluetoothPermissionRequest.java, there is a possible phishing attack allowing a malicious Bluetooth device to acquire permissions based on insufficient information presented to the user in the consent dialog. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is needed for exploitation.Product: AndroidVersions: Android-10 Android-11 Android-9Android ID: A-167403112
<p>Publish Date: 2021-12-15
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-0434>CVE-2021-0434</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://source.android.com/security/bulletin/2021-11-01">https://source.android.com/security/bulletin/2021-11-01</a></p>
<p>Release Date: 2021-12-15</p>
<p>Fix Resolution: android-11.0.0_r43</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-0434 (High) detected in Settingsandroid-10.0.0_r33 - ## CVE-2021-0434 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>Settingsandroid-10.0.0_r33</b></p></summary>
<p>
<p>Library home page: <a href=https://android.googlesource.com/platform/packages/apps/Settings>https://android.googlesource.com/platform/packages/apps/Settings</a></p>
<p>Found in HEAD commit: <a href="https://github.com/Satheesh575555/packages_apps_Settings_AOSP10_r33_CVE-2021-0333/commit/a353664da30a0b95adee9281a4af5c1d5cacc22e">a353664da30a0b95adee9281a4af5c1d5cacc22e</a></p>
<p>Found in base branch: <b>master</b></p></p>
</details>
</p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Source Files (1)</summary>
<p></p>
<p>
<img src='https://s3.amazonaws.com/wss-public/bitbucketImages/xRedImage.png' width=19 height=20> <b>/src/com/android/settings/bluetooth/BluetoothPermissionRequest.java</b>
</p>
</details>
<p></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png?' width=19 height=20> Vulnerability Details</summary>
<p>
In onReceive of BluetoothPermissionRequest.java, there is a possible phishing attack allowing a malicious Bluetooth device to acquire permissions based on insufficient information presented to the user in the consent dialog. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is needed for exploitation.Product: AndroidVersions: Android-10 Android-11 Android-9Android ID: A-167403112
<p>Publish Date: 2021-12-15
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2021-0434>CVE-2021-0434</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.3</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Local
- Attack Complexity: Low
- Privileges Required: Low
- User Interaction: Required
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://source.android.com/security/bulletin/2021-11-01">https://source.android.com/security/bulletin/2021-11-01</a></p>
<p>Release Date: 2021-12-15</p>
<p>Fix Resolution: android-11.0.0_r43</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_comp | cve high detected in settingsandroid cve high severity vulnerability vulnerable library settingsandroid library home page a href found in head commit a href found in base branch master vulnerable source files src com android settings bluetooth bluetoothpermissionrequest java vulnerability details in onreceive of bluetoothpermissionrequest java there is a possible phishing attack allowing a malicious bluetooth device to acquire permissions based on insufficient information presented to the user in the consent dialog this could lead to local escalation of privilege with no additional execution privileges needed user interaction is needed for exploitation product androidversions android android android id a publish date url a href cvss score details base score metrics exploitability metrics attack vector local attack complexity low privileges required low user interaction required scope unchanged impact metrics confidentiality impact high integrity impact high availability impact high for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution android step up your open source security game with mend | 0 |
15,559 | 11,589,266,456 | IssuesEvent | 2020-02-24 01:15:48 | APSIMInitiative/ApsimX | https://api.github.com/repos/APSIMInitiative/ApsimX | closed | Property drop downs not working with dark theme | bug interface/infrastructure | When using the dark theme drop down boxes follow the theme, but the remaining properties are based on light theme such that the background of the grid is white and entries are black text and therefore the drop downs in their collapsed state do not show up and we can't see the drop down icon.
The value is there, but not showing up because the light text is the same colour as the grid background (which is incorrect)
This fault is present in windows and mac on the latest code for both @her123 and myself | 1.0 | Property drop downs not working with dark theme - When using the dark theme drop down boxes follow the theme, but the remaining properties are based on light theme such that the background of the grid is white and entries are black text and therefore the drop downs in their collapsed state do not show up and we can't see the drop down icon.
The value is there, but not showing up because the light text is the same colour as the grid background (which is incorrect)
This fault is present in windows and mac on the latest code for both @her123 and myself | non_comp | property drop downs not working with dark theme when using the dark theme drop down boxes follow the theme but the remaining properties are based on light theme such that the background of the grid is white and entries are black text and therefore the drop downs in their collapsed state do not show up and we can t see the drop down icon the value is there but not showing up because the light text is the same colour as the grid background which is incorrect this fault is present in windows and mac on the latest code for both and myself | 0 |
760 | 3,210,382,659 | IssuesEvent | 2015-10-06 02:18:25 | simeonradivoev/MatterOverdrive | https://api.github.com/repos/simeonradivoev/MatterOverdrive | closed | Server crash with KCauldron | mod compatibility bug | With KCauldron-1.7.10-1492.155, MatterOverdrive-1.7.10-0.4.0-RC4 Hotfix-1 there still seems to be a crash:
Crash:
http://pastebin.com/DZyn2fM5
Same issue was posted and closed already (#78), not sure if it was fixed though.
| True | Server crash with KCauldron - With KCauldron-1.7.10-1492.155, MatterOverdrive-1.7.10-0.4.0-RC4 Hotfix-1 there still seems to be a crash:
Crash:
http://pastebin.com/DZyn2fM5
Same issue was posted and closed already (#78), not sure if it was fixed though.
| comp | server crash with kcauldron with kcauldron matteroverdrive hotfix there still seems to be a crash crash same issue was posted and closed already not sure if it was fixed though | 1 |
6,873 | 9,182,146,245 | IssuesEvent | 2019-03-05 12:03:52 | Zrips/CMI | https://api.github.com/repos/Zrips/CMI | closed | Error Loadig 8.0.17 | Compatibility bug report | Ok. was putting together a new 1.13R2 server. got the newest version of playervaults and on load i got the following stacktrace.
```
Error occurred while enabling CMI v8.0.17.0 (Is it up to date?)
java.lang.NoClassDefFoundError: com/drtshock/playervaults/vaultmanagement/UUIDVaultManager
at com.Zrips.CMI.CMI.setupPlayerVaults(CMI.java:1692) ~[?:?]
at com.Zrips.CMI.CMI.onEnable(CMI.java:1536) ~[?:?]
at org.bukkit.plugin.java.JavaPlugin.setEnabled(JavaPlugin.java:264) ~[spigot-1.13.1.jar:git-Spigot-2440e18-4228a56]
at org.bukkit.plugin.java.JavaPluginLoader.enablePlugin(JavaPluginLoader.java:339) [spigot-1.13.1.jar:git-Spigot-2440e18-4228a56]
at org.bukkit.plugin.SimplePluginManager.enablePlugin(SimplePluginManager.java:403) [spigot-1.13.1.jar:git-Spigot-2440e18-4228a56]
at org.bukkit.craftbukkit.v1_13_R2.CraftServer.enablePlugin(CraftServer.java:427) [spigot-1.13.1.jar:git-Spigot-2440e18-4228a56]
at org.bukkit.craftbukkit.v1_13_R2.CraftServer.enablePlugins(CraftServer.java:341) [spigot-1.13.1.jar:git-Spigot-2440e18-4228a56]
at net.minecraft.server.v1_13_R2.MinecraftServer.l(MinecraftServer.java:582) [spigot-1.13.1.jar:git-Spigot-2440e18-4228a56]
at net.minecraft.server.v1_13_R2.MinecraftServer.a(MinecraftServer.java:545) [spigot-1.13.1.jar:git-Spigot-2440e18-4228a56]
at net.minecraft.server.v1_13_R2.MinecraftServer.a(MinecraftServer.java:423) [spigot-1.13.1.jar:git-Spigot-2440e18-4228a56]
at net.minecraft.server.v1_13_R2.DedicatedServer.init(DedicatedServer.java:288) [spigot-1.13.1.jar:git-Spigot-2440e18-4228a56]
at net.minecraft.server.v1_13_R2.MinecraftServer.run(MinecraftServer.java:698) [spigot-1.13.1.jar:git-Spigot-2440e18-4228a56]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_181]
Caused by: java.lang.ClassNotFoundException: com.drtshock.playervaults.vaultmanagement.UUIDVaultManager
at java.net.URLClassLoader.findClass(Unknown Source) ~[?:1.8.0_181]
at org.bukkit.plugin.java.PluginClassLoader.findClass(PluginClassLoader.java:154) ~[spigot-1.13.1.jar:git-Spigot-2440e18-4228a56]
at org.bukkit.plugin.java.PluginClassLoader.findClass(PluginClassLoader.java:100) ~[spigot-1.13.1.jar:git-Spigot-2440e18-4228a56]
at java.lang.ClassLoader.loadClass(Unknown Source) ~[?:1.8.0_181]
at java.lang.ClassLoader.loadClass(Unknown Source) ~[?:1.8.0_181]
... 13 more
```
**Cmi Version (using`/cmi version`):**
8.0.17
**Server Type (Spigot/Paperspigot/etc):**
Spigot
**Server Version (using `/ver`):**
1.13 R2 | True | Error Loadig 8.0.17 - Ok. was putting together a new 1.13R2 server. got the newest version of playervaults and on load i got the following stacktrace.
```
Error occurred while enabling CMI v8.0.17.0 (Is it up to date?)
java.lang.NoClassDefFoundError: com/drtshock/playervaults/vaultmanagement/UUIDVaultManager
at com.Zrips.CMI.CMI.setupPlayerVaults(CMI.java:1692) ~[?:?]
at com.Zrips.CMI.CMI.onEnable(CMI.java:1536) ~[?:?]
at org.bukkit.plugin.java.JavaPlugin.setEnabled(JavaPlugin.java:264) ~[spigot-1.13.1.jar:git-Spigot-2440e18-4228a56]
at org.bukkit.plugin.java.JavaPluginLoader.enablePlugin(JavaPluginLoader.java:339) [spigot-1.13.1.jar:git-Spigot-2440e18-4228a56]
at org.bukkit.plugin.SimplePluginManager.enablePlugin(SimplePluginManager.java:403) [spigot-1.13.1.jar:git-Spigot-2440e18-4228a56]
at org.bukkit.craftbukkit.v1_13_R2.CraftServer.enablePlugin(CraftServer.java:427) [spigot-1.13.1.jar:git-Spigot-2440e18-4228a56]
at org.bukkit.craftbukkit.v1_13_R2.CraftServer.enablePlugins(CraftServer.java:341) [spigot-1.13.1.jar:git-Spigot-2440e18-4228a56]
at net.minecraft.server.v1_13_R2.MinecraftServer.l(MinecraftServer.java:582) [spigot-1.13.1.jar:git-Spigot-2440e18-4228a56]
at net.minecraft.server.v1_13_R2.MinecraftServer.a(MinecraftServer.java:545) [spigot-1.13.1.jar:git-Spigot-2440e18-4228a56]
at net.minecraft.server.v1_13_R2.MinecraftServer.a(MinecraftServer.java:423) [spigot-1.13.1.jar:git-Spigot-2440e18-4228a56]
at net.minecraft.server.v1_13_R2.DedicatedServer.init(DedicatedServer.java:288) [spigot-1.13.1.jar:git-Spigot-2440e18-4228a56]
at net.minecraft.server.v1_13_R2.MinecraftServer.run(MinecraftServer.java:698) [spigot-1.13.1.jar:git-Spigot-2440e18-4228a56]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_181]
Caused by: java.lang.ClassNotFoundException: com.drtshock.playervaults.vaultmanagement.UUIDVaultManager
at java.net.URLClassLoader.findClass(Unknown Source) ~[?:1.8.0_181]
at org.bukkit.plugin.java.PluginClassLoader.findClass(PluginClassLoader.java:154) ~[spigot-1.13.1.jar:git-Spigot-2440e18-4228a56]
at org.bukkit.plugin.java.PluginClassLoader.findClass(PluginClassLoader.java:100) ~[spigot-1.13.1.jar:git-Spigot-2440e18-4228a56]
at java.lang.ClassLoader.loadClass(Unknown Source) ~[?:1.8.0_181]
at java.lang.ClassLoader.loadClass(Unknown Source) ~[?:1.8.0_181]
... 13 more
```
**Cmi Version (using`/cmi version`):**
8.0.17
**Server Type (Spigot/Paperspigot/etc):**
Spigot
**Server Version (using `/ver`):**
1.13 R2 | comp | error loadig ok was putting together a new server got the newest version of playervaults and on load i got the following stacktrace error occurred while enabling cmi is it up to date java lang noclassdeffounderror com drtshock playervaults vaultmanagement uuidvaultmanager at com zrips cmi cmi setupplayervaults cmi java at com zrips cmi cmi onenable cmi java at org bukkit plugin java javaplugin setenabled javaplugin java at org bukkit plugin java javapluginloader enableplugin javapluginloader java at org bukkit plugin simplepluginmanager enableplugin simplepluginmanager java at org bukkit craftbukkit craftserver enableplugin craftserver java at org bukkit craftbukkit craftserver enableplugins craftserver java at net minecraft server minecraftserver l minecraftserver java at net minecraft server minecraftserver a minecraftserver java at net minecraft server minecraftserver a minecraftserver java at net minecraft server dedicatedserver init dedicatedserver java at net minecraft server minecraftserver run minecraftserver java at java lang thread run unknown source caused by java lang classnotfoundexception com drtshock playervaults vaultmanagement uuidvaultmanager at java net urlclassloader findclass unknown source at org bukkit plugin java pluginclassloader findclass pluginclassloader java at org bukkit plugin java pluginclassloader findclass pluginclassloader java at java lang classloader loadclass unknown source at java lang classloader loadclass unknown source more cmi version using cmi version server type spigot paperspigot etc spigot server version using ver | 1 |
20,597 | 30,602,954,793 | IssuesEvent | 2023-07-22 16:23:18 | MrKacafirekCZ/doggo-mod-overhauled | https://api.github.com/repos/MrKacafirekCZ/doggo-mod-overhauled | opened | [COMPATIBILITY] with texture pack | compatibility | **Is your compatibility request related to a problem? Please describe.**
yes patrix does not work with doggo overhauled mod
**Describe the solution you'd like**
to make them compatible
**Describe alternatives you've considered**
create a texture pack that uses patrix dog to put ontop of patrix texture pack
**The mod you'd like a compatibility with**
patrix and fresh animations
**Additional context**
patrix uses fresh animations but if you cant make it compatible with fresh animations how would i make patrix compatible with doggo mod overhauled? i could do it myself if you help me on what to change since ive never made a texture pack before
| True | [COMPATIBILITY] with texture pack - **Is your compatibility request related to a problem? Please describe.**
yes patrix does not work with doggo overhauled mod
**Describe the solution you'd like**
to make them compatible
**Describe alternatives you've considered**
create a texture pack that uses patrix dog to put ontop of patrix texture pack
**The mod you'd like a compatibility with**
patrix and fresh animations
**Additional context**
patrix uses fresh animations but if you cant make it compatible with fresh animations how would i make patrix compatible with doggo mod overhauled? i could do it myself if you help me on what to change since ive never made a texture pack before
| comp | with texture pack is your compatibility request related to a problem please describe yes patrix does not work with doggo overhauled mod describe the solution you d like to make them compatible describe alternatives you ve considered create a texture pack that uses patrix dog to put ontop of patrix texture pack the mod you d like a compatibility with patrix and fresh animations additional context patrix uses fresh animations but if you cant make it compatible with fresh animations how would i make patrix compatible with doggo mod overhauled i could do it myself if you help me on what to change since ive never made a texture pack before | 1 |
4,634 | 7,268,316,135 | IssuesEvent | 2018-02-20 09:40:52 | sebastianbergmann/phpunit-mock-objects | https://api.github.com/repos/sebastianbergmann/phpunit-mock-objects | opened | Remove PHPUnit_Framework_MockObject_MockObject | backward-compatibility-break | In time for the release of PHPUnit 8:
- [ ] Rename `PHPUnit_Framework_MockObject_MockObject` to `PHPUnit\Framework\MockObject\MockObject`
- [ ] Remove `src/ForwardCompatibility/MockObject.php`
This is a BC break (that should have happened together with PHPUnit 7) because many developers use annotations such as
```php
/** @var Foo|PHPUnit_Framework_MockObject_MockObject $foo*/
$foo = $this->createMock(Foo::class);
```
in their code. | True | Remove PHPUnit_Framework_MockObject_MockObject - In time for the release of PHPUnit 8:
- [ ] Rename `PHPUnit_Framework_MockObject_MockObject` to `PHPUnit\Framework\MockObject\MockObject`
- [ ] Remove `src/ForwardCompatibility/MockObject.php`
This is a BC break (that should have happened together with PHPUnit 7) because many developers use annotations such as
```php
/** @var Foo|PHPUnit_Framework_MockObject_MockObject $foo*/
$foo = $this->createMock(Foo::class);
```
in their code. | comp | remove phpunit framework mockobject mockobject in time for the release of phpunit rename phpunit framework mockobject mockobject to phpunit framework mockobject mockobject remove src forwardcompatibility mockobject php this is a bc break that should have happened together with phpunit because many developers use annotations such as php var foo phpunit framework mockobject mockobject foo foo this createmock foo class in their code | 1 |
587,721 | 17,630,070,682 | IssuesEvent | 2021-08-19 06:41:06 | francheska-vicente/cssweng | https://api.github.com/repos/francheska-vicente/cssweng | closed | Reservation's acceptance error for end date that is more than 5 years | bug priority: medium front-end severity: high | ### Summary:
End date that is more than 5 years from today’s date should not be accepted as input. However, the software allows such reservations to be made.
### Steps to Reproduce:
1. Login
2. Go to calendar
3. Click on any date
4. Press create reservation button
5. Fill out the fields with proper information except for end date
6. Select an end date that is more than 5 years from today
### Visual Proof:
### Expected Results:
Error Message should be shown after confirming
### Actual Results:
Reservation is made
| Additional Information | |
| ----------- | ----------- |
| Defect ID | 15-0002 |
| Platform | V8 engine (Google)|
| Operating System | Windows 10 | | 1.0 | Reservation's acceptance error for end date that is more than 5 years - ### Summary:
End date that is more than 5 years from today’s date should not be accepted as input. However, the software allows such reservations to be made.
### Steps to Reproduce:
1. Login
2. Go to calendar
3. Click on any date
4. Press create reservation button
5. Fill out the fields with proper information except for end date
6. Select an end date that is more than 5 years from today
### Visual Proof:
### Expected Results:
Error Message should be shown after confirming
### Actual Results:
Reservation is made
| Additional Information | |
| ----------- | ----------- |
| Defect ID | 15-0002 |
| Platform | V8 engine (Google)|
| Operating System | Windows 10 | | non_comp | reservation s acceptance error for end date that is more than years summary end date that is more than years from today’s date should not be accepted as input however the software allows such reservations to be made steps to reproduce login go to calendar click on any date press create reservation button fill out the fields with proper information except for end date select an end date that is more than years from today visual proof expected results error message should be shown after confirming actual results reservation is made additional information defect id platform engine google operating system windows | 0 |
16,853 | 23,198,714,289 | IssuesEvent | 2022-08-01 19:05:27 | avalanche-org/Gen_Assoc | https://api.github.com/repos/avalanche-org/Gen_Assoc | closed | Linux 64 bit Appimage. The SUID sandbox helper binary was found, but is not configured correctly | compatibilty behavior | to resolve this problem please
> sudo sysctl kernel.unprivileged_userns_clone=1 | True | Linux 64 bit Appimage. The SUID sandbox helper binary was found, but is not configured correctly - to resolve this problem please
> sudo sysctl kernel.unprivileged_userns_clone=1 | comp | linux bit appimage the suid sandbox helper binary was found but is not configured correctly to resolve this problem please sudo sysctl kernel unprivileged userns clone | 1 |
41,027 | 5,291,881,057 | IssuesEvent | 2017-02-08 23:54:10 | elastic/kibana | https://api.github.com/repos/elastic/kibana | closed | [UI Framework] Hollow button text hidden on focus | :Design bug | Any button with `kuiButton kuiButton--hollow` looks broken when focused.
*unfocused text*
*focused text*
As you can see, the text is white, and given that all of the backgrounds are now white, you can't read the text. | 1.0 | [UI Framework] Hollow button text hidden on focus - Any button with `kuiButton kuiButton--hollow` looks broken when focused.
*unfocused text*
*focused text*
As you can see, the text is white, and given that all of the backgrounds are now white, you can't read the text. | non_comp | hollow button text hidden on focus any button with kuibutton kuibutton hollow looks broken when focused unfocused text focused text as you can see the text is white and given that all of the backgrounds are now white you can t read the text | 0 |
535,110 | 15,682,372,215 | IssuesEvent | 2021-03-25 07:12:01 | wso2/product-apim-tooling | https://api.github.com/repos/wso2/product-apim-tooling | closed | Support endpoint security separately for Production and Sandbox endpoints via params file | 4.0.0 Priority/Highest Type/Improvement | **Description:**
Currently, we cannot specify the endpoint security for **Production** or **Sandbox** endpoint wise separately. We need to support this model.
A sample params file of an API with the new modified **security** field should be like below. It should support both **Production** and **Sandbox** endpoints security separately so that user can specify both or one of them as his/her wish.
```
environments:
- name: production
configs:
endpoints:
production:
url: 'https://localhost:9443/am/sample/prod/pizzashack/v1/api/'
sandbox:
url: 'https://localhost:9443/am/sample/sand/pizzashack/v1/api/'
security:
production:
enabled: true
type: basic
username: admin
password: admin
sandbox:
enabled: true
type: digest
username: admin
password: admin
```
**Affected Product Version:**
APICTL 4.0.0-Alpha2
**Note:-** Documentation should be updated as well after implementing this. | 1.0 | Support endpoint security separately for Production and Sandbox endpoints via params file - **Description:**
Currently, we cannot specify the endpoint security for **Production** or **Sandbox** endpoint wise separately. We need to support this model.
A sample params file of an API with the new modified **security** field should be like below. It should support both **Production** and **Sandbox** endpoints security separately so that user can specify both or one of them as his/her wish.
```
environments:
- name: production
configs:
endpoints:
production:
url: 'https://localhost:9443/am/sample/prod/pizzashack/v1/api/'
sandbox:
url: 'https://localhost:9443/am/sample/sand/pizzashack/v1/api/'
security:
production:
enabled: true
type: basic
username: admin
password: admin
sandbox:
enabled: true
type: digest
username: admin
password: admin
```
**Affected Product Version:**
APICTL 4.0.0-Alpha2
**Note:-** Documentation should be updated as well after implementing this. | non_comp | support endpoint security separately for production and sandbox endpoints via params file description currently we cannot specify the endpoint security for production or sandbox endpoint wise separately we need to support this model a sample params file of an api with the new modified security field should be like below it should support both production and sandbox endpoints security separately so that user can specify both or one of them as his her wish environments name production configs endpoints production url sandbox url security production enabled true type basic username admin password admin sandbox enabled true type digest username admin password admin affected product version apictl note documentation should be updated as well after implementing this | 0 |
184,298 | 21,784,850,439 | IssuesEvent | 2022-05-14 01:32:57 | MidnightBSD/midnightbsd-app-store | https://api.github.com/repos/MidnightBSD/midnightbsd-app-store | opened | CVE-2022-22970 (Medium) detected in spring-beans-5.3.18.jar, spring-core-5.3.18.jar | security vulnerability | ## CVE-2022-22970 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>spring-beans-5.3.18.jar</b>, <b>spring-core-5.3.18.jar</b></p></summary>
<p>
<details><summary><b>spring-beans-5.3.18.jar</b></p></summary>
<p>Spring Beans</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/springframework/spring-beans/5.3.18/spring-beans-5.3.18.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-hateoas-2.5.12.jar (Root Library)
- spring-hateoas-1.3.7.jar
- :x: **spring-beans-5.3.18.jar** (Vulnerable Library)
</details>
<details><summary><b>spring-core-5.3.18.jar</b></p></summary>
<p>Spring Core</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/springframework/spring-core/5.3.18/spring-core-5.3.18.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-2.5.12.jar (Root Library)
- :x: **spring-core-5.3.18.jar** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/MidnightBSD/midnightbsd-app-store/commit/f98a7663cd4534d7282b786a5f475d4e4b48c1c7">f98a7663cd4534d7282b786a5f475d4e4b48c1c7</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>
In spring framework versions prior to 5.3.20+ , 5.2.22+ and old unsupported versions, applications that handle file uploads are vulnerable to DoS attack if they rely on data binding to set a MultipartFile or javax.servlet.Part to a field in a model object.
<p>Publish Date: 2022-05-12
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-22970>CVE-2022-22970</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://tanzu.vmware.com/security/cve-2022-22970">https://tanzu.vmware.com/security/cve-2022-22970</a></p>
<p>Release Date: 2022-05-12</p>
<p>Fix Resolution: org.springframework:spring-beans:5.2.22,5.3.20;org.springframework:spring-core:5.2.22,5.3.20</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2022-22970 (Medium) detected in spring-beans-5.3.18.jar, spring-core-5.3.18.jar - ## CVE-2022-22970 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>spring-beans-5.3.18.jar</b>, <b>spring-core-5.3.18.jar</b></p></summary>
<p>
<details><summary><b>spring-beans-5.3.18.jar</b></p></summary>
<p>Spring Beans</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/springframework/spring-beans/5.3.18/spring-beans-5.3.18.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-hateoas-2.5.12.jar (Root Library)
- spring-hateoas-1.3.7.jar
- :x: **spring-beans-5.3.18.jar** (Vulnerable Library)
</details>
<details><summary><b>spring-core-5.3.18.jar</b></p></summary>
<p>Spring Core</p>
<p>Path to dependency file: /pom.xml</p>
<p>Path to vulnerable library: /home/wss-scanner/.m2/repository/org/springframework/spring-core/5.3.18/spring-core-5.3.18.jar</p>
<p>
Dependency Hierarchy:
- spring-boot-starter-2.5.12.jar (Root Library)
- :x: **spring-core-5.3.18.jar** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/MidnightBSD/midnightbsd-app-store/commit/f98a7663cd4534d7282b786a5f475d4e4b48c1c7">f98a7663cd4534d7282b786a5f475d4e4b48c1c7</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>
In spring framework versions prior to 5.3.20+ , 5.2.22+ and old unsupported versions, applications that handle file uploads are vulnerable to DoS attack if they rely on data binding to set a MultipartFile or javax.servlet.Part to a field in a model object.
<p>Publish Date: 2022-05-12
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2022-22970>CVE-2022-22970</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://tanzu.vmware.com/security/cve-2022-22970">https://tanzu.vmware.com/security/cve-2022-22970</a></p>
<p>Release Date: 2022-05-12</p>
<p>Fix Resolution: org.springframework:spring-beans:5.2.22,5.3.20;org.springframework:spring-core:5.2.22,5.3.20</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_comp | cve medium detected in spring beans jar spring core jar cve medium severity vulnerability vulnerable libraries spring beans jar spring core jar spring beans jar spring beans path to dependency file pom xml path to vulnerable library home wss scanner repository org springframework spring beans spring beans jar dependency hierarchy spring boot starter hateoas jar root library spring hateoas jar x spring beans jar vulnerable library spring core jar spring core path to dependency file pom xml path to vulnerable library home wss scanner repository org springframework spring core spring core jar dependency hierarchy spring boot starter jar root library x spring core jar vulnerable library found in head commit a href found in base branch master vulnerability details in spring framework versions prior to and old unsupported versions applications that handle file uploads are vulnerable to dos attack if they rely on data binding to set a multipartfile or javax servlet part to a field in a model object 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 org springframework spring beans org springframework spring core step up your open source security game with whitesource | 0 |
226,232 | 24,946,756,707 | IssuesEvent | 2022-11-01 01:24:17 | snykiotcubedev/react-17.0.2 | https://api.github.com/repos/snykiotcubedev/react-17.0.2 | opened | CVE-2022-37620 (Medium) detected in multiple libraries | security vulnerability | ## CVE-2022-37620 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>html-minifier-3.5.8.tgz</b>, <b>html-minifier-3.2.3.tgz</b>, <b>html-minifier-3.4.2.tgz</b>, <b>html-minifier-3.5.3.tgz</b>, <b>html-minifier-3.5.21.tgz</b>, <b>html-minifier-3.5.6.tgz</b></p></summary>
<p>
<details><summary><b>html-minifier-3.5.8.tgz</b></p></summary>
<p>Highly configurable, well-tested, JavaScript-based HTML minifier.</p>
<p>Library home page: <a href="https://registry.npmjs.org/html-minifier/-/html-minifier-3.5.8.tgz">https://registry.npmjs.org/html-minifier/-/html-minifier-3.5.8.tgz</a></p>
<p>
Dependency Hierarchy:
- react-scripts-1.1.4.tgz (Root Library)
- html-webpack-plugin-2.29.0.tgz
- :x: **html-minifier-3.5.8.tgz** (Vulnerable Library)
</details>
<details><summary><b>html-minifier-3.2.3.tgz</b></p></summary>
<p>Highly configurable, well-tested, JavaScript-based HTML minifier.</p>
<p>Library home page: <a href="https://registry.npmjs.org/html-minifier/-/html-minifier-3.2.3.tgz">https://registry.npmjs.org/html-minifier/-/html-minifier-3.2.3.tgz</a></p>
<p>
Dependency Hierarchy:
- react-scripts-0.9.5.tgz (Root Library)
- html-webpack-plugin-2.24.0.tgz
- :x: **html-minifier-3.2.3.tgz** (Vulnerable Library)
</details>
<details><summary><b>html-minifier-3.4.2.tgz</b></p></summary>
<p>Highly configurable, well-tested, JavaScript-based HTML minifier.</p>
<p>Library home page: <a href="https://registry.npmjs.org/html-minifier/-/html-minifier-3.4.2.tgz">https://registry.npmjs.org/html-minifier/-/html-minifier-3.4.2.tgz</a></p>
<p>
Dependency Hierarchy:
- react-scripts-0.9.5.tgz (Root Library)
- html-webpack-plugin-2.24.0.tgz
- :x: **html-minifier-3.4.2.tgz** (Vulnerable Library)
</details>
<details><summary><b>html-minifier-3.5.3.tgz</b></p></summary>
<p>Highly configurable, well-tested, JavaScript-based HTML minifier.</p>
<p>Library home page: <a href="https://registry.npmjs.org/html-minifier/-/html-minifier-3.5.3.tgz">https://registry.npmjs.org/html-minifier/-/html-minifier-3.5.3.tgz</a></p>
<p>
Dependency Hierarchy:
- react-scripts-1.0.11.tgz (Root Library)
- html-webpack-plugin-2.29.0.tgz
- :x: **html-minifier-3.5.3.tgz** (Vulnerable Library)
</details>
<details><summary><b>html-minifier-3.5.21.tgz</b></p></summary>
<p>Highly configurable, well-tested, JavaScript-based HTML minifier.</p>
<p>Library home page: <a href="https://registry.npmjs.org/html-minifier/-/html-minifier-3.5.21.tgz">https://registry.npmjs.org/html-minifier/-/html-minifier-3.5.21.tgz</a></p>
<p>
Dependency Hierarchy:
- html-webpack-plugin-4.0.0-beta.5.tgz (Root Library)
- :x: **html-minifier-3.5.21.tgz** (Vulnerable Library)
</details>
<details><summary><b>html-minifier-3.5.6.tgz</b></p></summary>
<p>Highly configurable, well-tested, JavaScript-based HTML minifier.</p>
<p>Library home page: <a href="https://registry.npmjs.org/html-minifier/-/html-minifier-3.5.6.tgz">https://registry.npmjs.org/html-minifier/-/html-minifier-3.5.6.tgz</a></p>
<p>
Dependency Hierarchy:
- react-scripts-1.0.17.tgz (Root Library)
- html-webpack-plugin-2.29.0.tgz
- :x: **html-minifier-3.5.6.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/snykiotcubedev/react-17.0.2/commit/c546697344431dcd6c04b4fea877c488ef3a6ad5">c546697344431dcd6c04b4fea877c488ef3a6ad5</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A Regular Expression Denial of Service (ReDoS) flaw was found in kangax html-minifier 4.0.0 via the candidate variable in htmlminifier.js.
<p>Publish Date: 2022-10-31
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-37620>CVE-2022-37620</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>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2022-37620 (Medium) detected in multiple libraries - ## CVE-2022-37620 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Libraries - <b>html-minifier-3.5.8.tgz</b>, <b>html-minifier-3.2.3.tgz</b>, <b>html-minifier-3.4.2.tgz</b>, <b>html-minifier-3.5.3.tgz</b>, <b>html-minifier-3.5.21.tgz</b>, <b>html-minifier-3.5.6.tgz</b></p></summary>
<p>
<details><summary><b>html-minifier-3.5.8.tgz</b></p></summary>
<p>Highly configurable, well-tested, JavaScript-based HTML minifier.</p>
<p>Library home page: <a href="https://registry.npmjs.org/html-minifier/-/html-minifier-3.5.8.tgz">https://registry.npmjs.org/html-minifier/-/html-minifier-3.5.8.tgz</a></p>
<p>
Dependency Hierarchy:
- react-scripts-1.1.4.tgz (Root Library)
- html-webpack-plugin-2.29.0.tgz
- :x: **html-minifier-3.5.8.tgz** (Vulnerable Library)
</details>
<details><summary><b>html-minifier-3.2.3.tgz</b></p></summary>
<p>Highly configurable, well-tested, JavaScript-based HTML minifier.</p>
<p>Library home page: <a href="https://registry.npmjs.org/html-minifier/-/html-minifier-3.2.3.tgz">https://registry.npmjs.org/html-minifier/-/html-minifier-3.2.3.tgz</a></p>
<p>
Dependency Hierarchy:
- react-scripts-0.9.5.tgz (Root Library)
- html-webpack-plugin-2.24.0.tgz
- :x: **html-minifier-3.2.3.tgz** (Vulnerable Library)
</details>
<details><summary><b>html-minifier-3.4.2.tgz</b></p></summary>
<p>Highly configurable, well-tested, JavaScript-based HTML minifier.</p>
<p>Library home page: <a href="https://registry.npmjs.org/html-minifier/-/html-minifier-3.4.2.tgz">https://registry.npmjs.org/html-minifier/-/html-minifier-3.4.2.tgz</a></p>
<p>
Dependency Hierarchy:
- react-scripts-0.9.5.tgz (Root Library)
- html-webpack-plugin-2.24.0.tgz
- :x: **html-minifier-3.4.2.tgz** (Vulnerable Library)
</details>
<details><summary><b>html-minifier-3.5.3.tgz</b></p></summary>
<p>Highly configurable, well-tested, JavaScript-based HTML minifier.</p>
<p>Library home page: <a href="https://registry.npmjs.org/html-minifier/-/html-minifier-3.5.3.tgz">https://registry.npmjs.org/html-minifier/-/html-minifier-3.5.3.tgz</a></p>
<p>
Dependency Hierarchy:
- react-scripts-1.0.11.tgz (Root Library)
- html-webpack-plugin-2.29.0.tgz
- :x: **html-minifier-3.5.3.tgz** (Vulnerable Library)
</details>
<details><summary><b>html-minifier-3.5.21.tgz</b></p></summary>
<p>Highly configurable, well-tested, JavaScript-based HTML minifier.</p>
<p>Library home page: <a href="https://registry.npmjs.org/html-minifier/-/html-minifier-3.5.21.tgz">https://registry.npmjs.org/html-minifier/-/html-minifier-3.5.21.tgz</a></p>
<p>
Dependency Hierarchy:
- html-webpack-plugin-4.0.0-beta.5.tgz (Root Library)
- :x: **html-minifier-3.5.21.tgz** (Vulnerable Library)
</details>
<details><summary><b>html-minifier-3.5.6.tgz</b></p></summary>
<p>Highly configurable, well-tested, JavaScript-based HTML minifier.</p>
<p>Library home page: <a href="https://registry.npmjs.org/html-minifier/-/html-minifier-3.5.6.tgz">https://registry.npmjs.org/html-minifier/-/html-minifier-3.5.6.tgz</a></p>
<p>
Dependency Hierarchy:
- react-scripts-1.0.17.tgz (Root Library)
- html-webpack-plugin-2.29.0.tgz
- :x: **html-minifier-3.5.6.tgz** (Vulnerable Library)
</details>
<p>Found in HEAD commit: <a href="https://github.com/snykiotcubedev/react-17.0.2/commit/c546697344431dcd6c04b4fea877c488ef3a6ad5">c546697344431dcd6c04b4fea877c488ef3a6ad5</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
A Regular Expression Denial of Service (ReDoS) flaw was found in kangax html-minifier 4.0.0 via the candidate variable in htmlminifier.js.
<p>Publish Date: 2022-10-31
<p>URL: <a href=https://www.mend.io/vulnerability-database/CVE-2022-37620>CVE-2022-37620</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>
***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_comp | cve medium detected in multiple libraries cve medium severity vulnerability vulnerable libraries html minifier tgz html minifier tgz html minifier tgz html minifier tgz html minifier tgz html minifier tgz html minifier tgz highly configurable well tested javascript based html minifier library home page a href dependency hierarchy react scripts tgz root library html webpack plugin tgz x html minifier tgz vulnerable library html minifier tgz highly configurable well tested javascript based html minifier library home page a href dependency hierarchy react scripts tgz root library html webpack plugin tgz x html minifier tgz vulnerable library html minifier tgz highly configurable well tested javascript based html minifier library home page a href dependency hierarchy react scripts tgz root library html webpack plugin tgz x html minifier tgz vulnerable library html minifier tgz highly configurable well tested javascript based html minifier library home page a href dependency hierarchy react scripts tgz root library html webpack plugin tgz x html minifier tgz vulnerable library html minifier tgz highly configurable well tested javascript based html minifier library home page a href dependency hierarchy html webpack plugin beta tgz root library x html minifier tgz vulnerable library html minifier tgz highly configurable well tested javascript based html minifier library home page a href dependency hierarchy react scripts tgz root library html webpack plugin tgz x html minifier tgz vulnerable library found in head commit a href found in base branch main vulnerability details a regular expression denial of service redos flaw was found in kangax html minifier via the candidate variable in htmlminifier js 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 step up your open source security game with mend | 0 |
3,553 | 6,493,163,807 | IssuesEvent | 2017-08-21 15:55:28 | Cxbx-Reloaded/Cxbx-Reloaded | https://api.github.com/repos/Cxbx-Reloaded/Cxbx-Reloaded | closed | Marvel vs. Capcom 2 - Missing HLE Patch | game-compatibility HLE | `[0x1C74] EmuWarn: EmuX86_Write32(0xFD714178, 0x0F39F518) Unexpected NV2A access, missing a HLE patch. Please notify https://github.com/Cxbx-Reloaded/Cxbx-Reloaded which title raised this!`
This line gets spammed in the console, albeit with varying addresses.
[KrnlDebug.txt](https://github.com/Cxbx-Reloaded/Cxbx-Reloaded/files/846120/KrnlDebug.txt)
| True | Marvel vs. Capcom 2 - Missing HLE Patch - `[0x1C74] EmuWarn: EmuX86_Write32(0xFD714178, 0x0F39F518) Unexpected NV2A access, missing a HLE patch. Please notify https://github.com/Cxbx-Reloaded/Cxbx-Reloaded which title raised this!`
This line gets spammed in the console, albeit with varying addresses.
[KrnlDebug.txt](https://github.com/Cxbx-Reloaded/Cxbx-Reloaded/files/846120/KrnlDebug.txt)
| comp | marvel vs capcom missing hle patch emuwarn unexpected access missing a hle patch please notify which title raised this this line gets spammed in the console albeit with varying addresses | 1 |
17,403 | 23,989,915,827 | IssuesEvent | 2022-09-13 23:23:24 | Yesssssman/epicfightmod | https://api.github.com/repos/Yesssssman/epicfightmod | closed | Compatibility Issue with Mowzie's Mobs | mod incompatibility work-in-progress 1.16.5 | 
Rendering issue when placing the gauntlet on the player's off hand | True | Compatibility Issue with Mowzie's Mobs - 
Rendering issue when placing the gauntlet on the player's off hand | comp | compatibility issue with mowzie s mobs rendering issue when placing the gauntlet on the player s off hand | 1 |
60,966 | 6,719,535,962 | IssuesEvent | 2017-10-16 01:22:55 | lazyengineering/gobase | https://api.github.com/repos/lazyengineering/gobase | closed | testing for main command | testing | write tests for main command, or at least benchmarks for a clear idea what we're doing.
| 1.0 | testing for main command - write tests for main command, or at least benchmarks for a clear idea what we're doing.
| non_comp | testing for main command write tests for main command or at least benchmarks for a clear idea what we re doing | 0 |
50,820 | 10,561,781,256 | IssuesEvent | 2019-10-04 16:40:32 | education/classroom | https://api.github.com/repos/education/classroom | closed | Starter Code Takes Forever | slow code import | Likes issues #1759, my starter code takes forever (10 hours and counting) to import too. The classroom is: https://github.com/EECS388-Classroom
To Reproduce Steps to reproduce the behavior:
Go to https://classroom.github.com/a/80TPAyLe
wait
Expected behavior The starter code should import, and I should see the starter code in the repository.
screenshot:
| 1.0 | Starter Code Takes Forever - Likes issues #1759, my starter code takes forever (10 hours and counting) to import too. The classroom is: https://github.com/EECS388-Classroom
To Reproduce Steps to reproduce the behavior:
Go to https://classroom.github.com/a/80TPAyLe
wait
Expected behavior The starter code should import, and I should see the starter code in the repository.
screenshot:
| non_comp | starter code takes forever likes issues my starter code takes forever hours and counting to import too the classroom is to reproduce steps to reproduce the behavior go to wait expected behavior the starter code should import and i should see the starter code in the repository screenshot | 0 |
10,390 | 12,345,565,891 | IssuesEvent | 2020-05-15 09:10:49 | JuliaStats/MixedModels.jl | https://api.github.com/repos/JuliaStats/MixedModels.jl | closed | Conflict with the latest version of NLopt v0.6.0 #master | compatibility | Hello!
I have difficulty to add the current master branch of MixedModels.jl due to the conflict with the working version of NLOpt v0.6.0 #master. Currently, that version of NLopt is the only version that works. Previous versions, e.g., v0.5.0 and v0.5.1 do not work under Julia 1.4. So, I added this master branch of NLopt first. Then, I tried to add the MixedModels.jl, but got the following error:
```
(@v1.4) pkg> add MixedModels#master
Cloning git-repo `https://github.com/JuliaStats/MixedModels.jl.git`
Updating git-repo `https://github.com/JuliaStats/MixedModels.jl.git`
Resolving package versions...
ERROR: Unsatisfiable requirements detected for package NLopt [76087f3c]:
NLopt [76087f3c] log:
├─possible versions are: 0.6.0 or uninstalled
├─restricted to versions 0.5 by MixedModels [ff71e718] — no versions left
│ └─MixedModels [ff71e718] log:
│ ├─possible versions are: 2.2.0 or uninstalled
│ └─MixedModels [ff71e718] is fixed to version 2.2.0
└─NLopt [76087f3c] is fixed to version 0.6.0
```
Would things work if `Project.toml` of the MixedModels.jl is updated to the NLopt v0.6.0? Currently, it is set as v0.5.0. Thanks for your help! | True | Conflict with the latest version of NLopt v0.6.0 #master - Hello!
I have difficulty to add the current master branch of MixedModels.jl due to the conflict with the working version of NLOpt v0.6.0 #master. Currently, that version of NLopt is the only version that works. Previous versions, e.g., v0.5.0 and v0.5.1 do not work under Julia 1.4. So, I added this master branch of NLopt first. Then, I tried to add the MixedModels.jl, but got the following error:
```
(@v1.4) pkg> add MixedModels#master
Cloning git-repo `https://github.com/JuliaStats/MixedModels.jl.git`
Updating git-repo `https://github.com/JuliaStats/MixedModels.jl.git`
Resolving package versions...
ERROR: Unsatisfiable requirements detected for package NLopt [76087f3c]:
NLopt [76087f3c] log:
├─possible versions are: 0.6.0 or uninstalled
├─restricted to versions 0.5 by MixedModels [ff71e718] — no versions left
│ └─MixedModels [ff71e718] log:
│ ├─possible versions are: 2.2.0 or uninstalled
│ └─MixedModels [ff71e718] is fixed to version 2.2.0
└─NLopt [76087f3c] is fixed to version 0.6.0
```
Would things work if `Project.toml` of the MixedModels.jl is updated to the NLopt v0.6.0? Currently, it is set as v0.5.0. Thanks for your help! | comp | conflict with the latest version of nlopt master hello i have difficulty to add the current master branch of mixedmodels jl due to the conflict with the working version of nlopt master currently that version of nlopt is the only version that works previous versions e g and do not work under julia so i added this master branch of nlopt first then i tried to add the mixedmodels jl but got the following error pkg add mixedmodels master cloning git repo updating git repo resolving package versions error unsatisfiable requirements detected for package nlopt nlopt log ├─possible versions are or uninstalled ├─restricted to versions by mixedmodels — no versions left │ └─mixedmodels log │ ├─possible versions are or uninstalled │ └─mixedmodels is fixed to version └─nlopt is fixed to version would things work if project toml of the mixedmodels jl is updated to the nlopt currently it is set as thanks for your help | 1 |
4,619 | 7,260,648,050 | IssuesEvent | 2018-02-18 12:37:16 | vyskoczilova/Simple-Admin-Language-Change | https://api.github.com/repos/vyskoczilova/Simple-Admin-Language-Change | closed | Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; | compatibility | **Reported by:** Tina Hammar (by email)
**Reported:**
I would like to report to you that your plugin "Simple Adming Language Change" reports an error if you turn on wp debugging.
error:
Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; admin_language_new_general_setting has a deprecated constructor in /home/bokamark/public_html/wp-content/plugins/simple-admin-language-change/simple-admin-language-change.php on line 55
I am a happy user of your, very helpful plugin and I hope that It will not stop working in the future.
Thank You for your giving your time in keeping your plugin free for others to user.
Best regards
Tina Hammar | True | Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; - **Reported by:** Tina Hammar (by email)
**Reported:**
I would like to report to you that your plugin "Simple Adming Language Change" reports an error if you turn on wp debugging.
error:
Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; admin_language_new_general_setting has a deprecated constructor in /home/bokamark/public_html/wp-content/plugins/simple-admin-language-change/simple-admin-language-change.php on line 55
I am a happy user of your, very helpful plugin and I hope that It will not stop working in the future.
Thank You for your giving your time in keeping your plugin free for others to user.
Best regards
Tina Hammar | comp | deprecated methods with the same name as their class will not be constructors in a future version of php reported by tina hammar by email reported i would like to report to you that your plugin simple adming language change reports an error if you turn on wp debugging error deprecated methods with the same name as their class will not be constructors in a future version of php admin language new general setting has a deprecated constructor in home bokamark public html wp content plugins simple admin language change simple admin language change php on line i am a happy user of your very helpful plugin and i hope that it will not stop working in the future thank you for your giving your time in keeping your plugin free for others to user best regards tina hammar | 1 |
6,555 | 8,820,637,916 | IssuesEvent | 2019-01-01 15:10:06 | RogueException/Discord.Net | https://api.github.com/repos/RogueException/Discord.Net | closed | Deprecation Warning: User Accounts (2.x) | compatibility | This is an early warning that **user tokens will no longer be supported** under the primary library distribution starting in Discord.Net 2.0.
As we approach the development cycle for the next major version, 3.0, an alternative for users that wish to continue using user tokens may be provided - but this will not be a first-class feature of Discord.Net moving forward.
---
Starting in Discord.Net 2.0, user tokens will be marked as deprecated, and we will formally stop providing support for user logins. As a side-effect of this, we would like to warn users **against using user tokens, including selfbots**.
~~Discord's official stance against selfbots is vague, but there are certain methods that we would advise against using from your selfbot, if you must use a selfbot:~~
As of November 2017, **selfbots are not allowed, at all.** See [Discord Support](https://support.discordapp.com/hc/en-us/articles/115002192352-Automated-user-accounts-self-bots-) for the official stance. As such, you **should not** use selfbots or userbots. The following methods are known to trigger red-flags on your account if you use them from a userbot or selfbot:
- `IUser.SendMessageAsync`
- `IInvite.AcceptAsync`
Using these methods may result in your account being unverified, flagged as spam, or deleted for violating Discord's Terms of Service. | True | Deprecation Warning: User Accounts (2.x) - This is an early warning that **user tokens will no longer be supported** under the primary library distribution starting in Discord.Net 2.0.
As we approach the development cycle for the next major version, 3.0, an alternative for users that wish to continue using user tokens may be provided - but this will not be a first-class feature of Discord.Net moving forward.
---
Starting in Discord.Net 2.0, user tokens will be marked as deprecated, and we will formally stop providing support for user logins. As a side-effect of this, we would like to warn users **against using user tokens, including selfbots**.
~~Discord's official stance against selfbots is vague, but there are certain methods that we would advise against using from your selfbot, if you must use a selfbot:~~
As of November 2017, **selfbots are not allowed, at all.** See [Discord Support](https://support.discordapp.com/hc/en-us/articles/115002192352-Automated-user-accounts-self-bots-) for the official stance. As such, you **should not** use selfbots or userbots. The following methods are known to trigger red-flags on your account if you use them from a userbot or selfbot:
- `IUser.SendMessageAsync`
- `IInvite.AcceptAsync`
Using these methods may result in your account being unverified, flagged as spam, or deleted for violating Discord's Terms of Service. | comp | deprecation warning user accounts x this is an early warning that user tokens will no longer be supported under the primary library distribution starting in discord net as we approach the development cycle for the next major version an alternative for users that wish to continue using user tokens may be provided but this will not be a first class feature of discord net moving forward starting in discord net user tokens will be marked as deprecated and we will formally stop providing support for user logins as a side effect of this we would like to warn users against using user tokens including selfbots discord s official stance against selfbots is vague but there are certain methods that we would advise against using from your selfbot if you must use a selfbot as of november selfbots are not allowed at all see for the official stance as such you should not use selfbots or userbots the following methods are known to trigger red flags on your account if you use them from a userbot or selfbot iuser sendmessageasync iinvite acceptasync using these methods may result in your account being unverified flagged as spam or deleted for violating discord s terms of service | 1 |
76,371 | 26,395,205,548 | IssuesEvent | 2023-01-12 18:45:29 | vector-im/element-call | https://api.github.com/repos/vector-im/element-call | opened | Releasing camera on video mute is unreliable | T-Defect | ### Steps to reproduce
1. Enter call
2. Mute video
### Outcome
#### What did you expect?
Camera light goes off
#### What happened instead?
Camera light stays on sometimes, although it does work other times. Haven't yet found a correlation - I'd assume we must have a stray stream kicking around. It still fails sometimes when I'm the the only person in the call.
### Operating system
_No response_
### Browser information
_No response_
### URL for webapp
_No response_
### Will you send logs?
Yes | 1.0 | Releasing camera on video mute is unreliable - ### Steps to reproduce
1. Enter call
2. Mute video
### Outcome
#### What did you expect?
Camera light goes off
#### What happened instead?
Camera light stays on sometimes, although it does work other times. Haven't yet found a correlation - I'd assume we must have a stray stream kicking around. It still fails sometimes when I'm the the only person in the call.
### Operating system
_No response_
### Browser information
_No response_
### URL for webapp
_No response_
### Will you send logs?
Yes | non_comp | releasing camera on video mute is unreliable steps to reproduce enter call mute video outcome what did you expect camera light goes off what happened instead camera light stays on sometimes although it does work other times haven t yet found a correlation i d assume we must have a stray stream kicking around it still fails sometimes when i m the the only person in the call operating system no response browser information no response url for webapp no response will you send logs yes | 0 |
1,039 | 3,497,730,935 | IssuesEvent | 2016-01-06 03:27:09 | blay09/CraftingTweaks | https://api.github.com/repos/blay09/CraftingTweaks | closed | Transfer-to-grid crash [1.0.57] | compatibility | Description: When attempting the recently added 'transfer-to-grid' (W + Shift Click) feature in a portable crafting table from CraftingCraft, I crash out of my world and into the main menu.
I didn't receive an actual crash report as my game was only exited to the main menu. Here is the relevant area of the client log:
https://gist.github.com/dirtyfargo/e46727378a6953876dee
Version: 1.0.57
Forge Version: 10.13.4.1614
CraftingCraft Version: 1.0.7 | True | Transfer-to-grid crash [1.0.57] - Description: When attempting the recently added 'transfer-to-grid' (W + Shift Click) feature in a portable crafting table from CraftingCraft, I crash out of my world and into the main menu.
I didn't receive an actual crash report as my game was only exited to the main menu. Here is the relevant area of the client log:
https://gist.github.com/dirtyfargo/e46727378a6953876dee
Version: 1.0.57
Forge Version: 10.13.4.1614
CraftingCraft Version: 1.0.7 | comp | transfer to grid crash description when attempting the recently added transfer to grid w shift click feature in a portable crafting table from craftingcraft i crash out of my world and into the main menu i didn t receive an actual crash report as my game was only exited to the main menu here is the relevant area of the client log version forge version craftingcraft version | 1 |
366,833 | 25,604,028,914 | IssuesEvent | 2022-12-01 23:11:02 | googleforgames/agones | https://api.github.com/repos/googleforgames/agones | closed | `agones.allocator.allocationBatchWaitTime` missing in Helm Configuration documentation | kind/bug kind/documentation | **What happened**:
The `agones.allocator.allocationBatchWaitTime` helm chart configuration value is not present in https://agones.dev/site/docs/installation/install-agones/helm/#configuration but is in the chart's `values.yaml` file [agones.allocator.allocationBatchWaitTime](https://github.com/googleforgames/agones/blob/main/install/helm/agones/values.yaml#L212).
The `agones.controller.allocationBatchWaitTime` value on the other hand is present in both.
**What you expected to happen**:
`agones.allocator.allocationBatchWaitTime` should be present in [Configuratioon
](https://agones.dev/site/docs/installation/install-agones/helm/#configuration) to reflect the Helm chart value https://github.com/googleforgames/agones/blob/main/install/helm/agones/values.yaml#L212
**How to reproduce it (as minimally and precisely as possible)**:
Visit https://agones.dev/site/docs/installation/install-agones/helm/#configuration
**Anything else we need to know?**:
**Environment**:
- Agones version:
- Kubernetes version (use `kubectl version`):
- Cloud provider or hardware configuration:
- Install method (yaml/helm):
- Troubleshooting guide log(s):
- Others:
| 1.0 | `agones.allocator.allocationBatchWaitTime` missing in Helm Configuration documentation - **What happened**:
The `agones.allocator.allocationBatchWaitTime` helm chart configuration value is not present in https://agones.dev/site/docs/installation/install-agones/helm/#configuration but is in the chart's `values.yaml` file [agones.allocator.allocationBatchWaitTime](https://github.com/googleforgames/agones/blob/main/install/helm/agones/values.yaml#L212).
The `agones.controller.allocationBatchWaitTime` value on the other hand is present in both.
**What you expected to happen**:
`agones.allocator.allocationBatchWaitTime` should be present in [Configuratioon
](https://agones.dev/site/docs/installation/install-agones/helm/#configuration) to reflect the Helm chart value https://github.com/googleforgames/agones/blob/main/install/helm/agones/values.yaml#L212
**How to reproduce it (as minimally and precisely as possible)**:
Visit https://agones.dev/site/docs/installation/install-agones/helm/#configuration
**Anything else we need to know?**:
**Environment**:
- Agones version:
- Kubernetes version (use `kubectl version`):
- Cloud provider or hardware configuration:
- Install method (yaml/helm):
- Troubleshooting guide log(s):
- Others:
| non_comp | agones allocator allocationbatchwaittime missing in helm configuration documentation what happened the agones allocator allocationbatchwaittime helm chart configuration value is not present in but is in the chart s values yaml file the agones controller allocationbatchwaittime value on the other hand is present in both what you expected to happen agones allocator allocationbatchwaittime should be present in configuratioon to reflect the helm chart value how to reproduce it as minimally and precisely as possible visit anything else we need to know environment agones version kubernetes version use kubectl version cloud provider or hardware configuration install method yaml helm troubleshooting guide log s others | 0 |
521,297 | 15,107,262,503 | IssuesEvent | 2021-02-08 15:14:16 | epam/ketcher | https://api.github.com/repos/epam/ketcher | closed | Add error handling to indigo worker | enhancement high priority | It is necessary to extend current post messages by error messages that are getting from indigo wasm module. | 1.0 | Add error handling to indigo worker - It is necessary to extend current post messages by error messages that are getting from indigo wasm module. | non_comp | add error handling to indigo worker it is necessary to extend current post messages by error messages that are getting from indigo wasm module | 0 |
42,050 | 5,412,647,282 | IssuesEvent | 2017-03-01 15:02:21 | jupyterlab/jupyterlab | https://api.github.com/repos/jupyterlab/jupyterlab | closed | Selected cell "moves out of sight" when adding a new cell below | cat:Design and UX component:Notebook type:Bug | The title is maybe not the best description, but a gif is probably clearer. What I do here in the gif, is simply pressing a few times 'b' to add new cells below the existing one (and scrolling down at the end):
As you can see, the selected cell (the new cell that is added below) moves out of sight, as the view does not update and does not scroll down automatically with the selected cell.
In the classic notebook, the selected cell keeps being focused and the view is updated on each 'b' stroke.
Reported with latest jupyterlab from conda-forge (0.16.0), using Firefox on Ubuntu 16.04.
| 1.0 | Selected cell "moves out of sight" when adding a new cell below - The title is maybe not the best description, but a gif is probably clearer. What I do here in the gif, is simply pressing a few times 'b' to add new cells below the existing one (and scrolling down at the end):
As you can see, the selected cell (the new cell that is added below) moves out of sight, as the view does not update and does not scroll down automatically with the selected cell.
In the classic notebook, the selected cell keeps being focused and the view is updated on each 'b' stroke.
Reported with latest jupyterlab from conda-forge (0.16.0), using Firefox on Ubuntu 16.04.
| non_comp | selected cell moves out of sight when adding a new cell below the title is maybe not the best description but a gif is probably clearer what i do here in the gif is simply pressing a few times b to add new cells below the existing one and scrolling down at the end as you can see the selected cell the new cell that is added below moves out of sight as the view does not update and does not scroll down automatically with the selected cell in the classic notebook the selected cell keeps being focused and the view is updated on each b stroke reported with latest jupyterlab from conda forge using firefox on ubuntu | 0 |
143,294 | 19,177,912,329 | IssuesEvent | 2021-12-04 00:04:38 | samq-ghdemo/js-monorepo | https://api.github.com/repos/samq-ghdemo/js-monorepo | opened | CVE-2017-16114 (High) detected in marked-0.3.5.tgz | security vulnerability | ## CVE-2017-16114 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>marked-0.3.5.tgz</b></p></summary>
<p>A markdown parser built for speed</p>
<p>Library home page: <a href="https://registry.npmjs.org/marked/-/marked-0.3.5.tgz">https://registry.npmjs.org/marked/-/marked-0.3.5.tgz</a></p>
<p>Path to dependency file: js-monorepo/nodejs-goof/package.json</p>
<p>Path to vulnerable library: /nodejs-goof/node_modules/marked/package.json</p>
<p>
Dependency Hierarchy:
- :x: **marked-0.3.5.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/samq-ghdemo/js-monorepo/commit/f3701923c18333c1e4e49bf595dd36b3f186812f">f3701923c18333c1e4e49bf595dd36b3f186812f</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The marked module is vulnerable to a regular expression denial of service. Based on the information published in the public issue, 1k characters can block for around 6 seconds.
<p>Publish Date: 2018-06-07
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-16114>CVE-2017-16114</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.npmjs.com/advisories/531/versions">https://www.npmjs.com/advisories/531/versions</a></p>
<p>Release Date: 2018-06-07</p>
<p>Fix Resolution: 0.3.9</p>
</p>
</details>
<p></p>
***
:rescue_worker_helmet: Automatic Remediation is available for this issue
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"marked","packageVersion":"0.3.5","packageFilePaths":["/nodejs-goof/package.json"],"isTransitiveDependency":false,"dependencyTree":"marked:0.3.5","isMinimumFixVersionAvailable":true,"minimumFixVersion":"0.3.9","isBinary":false}],"baseBranches":["main"],"vulnerabilityIdentifier":"CVE-2017-16114","vulnerabilityDetails":"The marked module is vulnerable to a regular expression denial of service. Based on the information published in the public issue, 1k characters can block for around 6 seconds.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-16114","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> --> | True | CVE-2017-16114 (High) detected in marked-0.3.5.tgz - ## CVE-2017-16114 - High Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>marked-0.3.5.tgz</b></p></summary>
<p>A markdown parser built for speed</p>
<p>Library home page: <a href="https://registry.npmjs.org/marked/-/marked-0.3.5.tgz">https://registry.npmjs.org/marked/-/marked-0.3.5.tgz</a></p>
<p>Path to dependency file: js-monorepo/nodejs-goof/package.json</p>
<p>Path to vulnerable library: /nodejs-goof/node_modules/marked/package.json</p>
<p>
Dependency Hierarchy:
- :x: **marked-0.3.5.tgz** (Vulnerable Library)
<p>Found in HEAD commit: <a href="https://github.com/samq-ghdemo/js-monorepo/commit/f3701923c18333c1e4e49bf595dd36b3f186812f">f3701923c18333c1e4e49bf595dd36b3f186812f</a></p>
<p>Found in base branch: <b>main</b></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/high_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
The marked module is vulnerable to a regular expression denial of service. Based on the information published in the public issue, 1k characters can block for around 6 seconds.
<p>Publish Date: 2018-06-07
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-16114>CVE-2017-16114</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>7.5</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: High
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://www.npmjs.com/advisories/531/versions">https://www.npmjs.com/advisories/531/versions</a></p>
<p>Release Date: 2018-06-07</p>
<p>Fix Resolution: 0.3.9</p>
</p>
</details>
<p></p>
***
:rescue_worker_helmet: Automatic Remediation is available for this issue
<!-- <REMEDIATE>{"isOpenPROnVulnerability":true,"isPackageBased":true,"isDefaultBranch":true,"packages":[{"packageType":"javascript/Node.js","packageName":"marked","packageVersion":"0.3.5","packageFilePaths":["/nodejs-goof/package.json"],"isTransitiveDependency":false,"dependencyTree":"marked:0.3.5","isMinimumFixVersionAvailable":true,"minimumFixVersion":"0.3.9","isBinary":false}],"baseBranches":["main"],"vulnerabilityIdentifier":"CVE-2017-16114","vulnerabilityDetails":"The marked module is vulnerable to a regular expression denial of service. Based on the information published in the public issue, 1k characters can block for around 6 seconds.","vulnerabilityUrl":"https://vuln.whitesourcesoftware.com/vulnerability/CVE-2017-16114","cvss3Severity":"high","cvss3Score":"7.5","cvss3Metrics":{"A":"High","AC":"Low","PR":"None","S":"Unchanged","C":"None","UI":"None","AV":"Network","I":"None"},"extraData":{}}</REMEDIATE> --> | non_comp | cve high detected in marked tgz cve high severity vulnerability vulnerable library marked tgz a markdown parser built for speed library home page a href path to dependency file js monorepo nodejs goof package json path to vulnerable library nodejs goof node modules marked package json dependency hierarchy x marked tgz vulnerable library found in head commit a href found in base branch main vulnerability details the marked module is vulnerable to a regular expression denial of service based on the information published in the public issue characters can block for around seconds 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 rescue worker helmet automatic remediation is available for this issue isopenpronvulnerability true ispackagebased true isdefaultbranch true packages istransitivedependency false dependencytree marked isminimumfixversionavailable true minimumfixversion isbinary false basebranches vulnerabilityidentifier cve vulnerabilitydetails the marked module is vulnerable to a regular expression denial of service based on the information published in the public issue characters can block for around seconds vulnerabilityurl | 0 |
91,850 | 15,856,663,593 | IssuesEvent | 2021-04-08 02:53:09 | Check-den-Fakt/WebScraper | https://api.github.com/repos/Check-den-Fakt/WebScraper | opened | CVE-2020-28168 (Medium) detected in axios-0.19.2.tgz | security vulnerability | ## CVE-2020-28168 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>axios-0.19.2.tgz</b></p></summary>
<p>Promise based HTTP client for the browser and node.js</p>
<p>Library home page: <a href="https://registry.npmjs.org/axios/-/axios-0.19.2.tgz">https://registry.npmjs.org/axios/-/axios-0.19.2.tgz</a></p>
<p>Path to dependency file: WebScraper/package.json</p>
<p>Path to vulnerable library: WebScraper/node_modules/axios/package.json</p>
<p>
Dependency Hierarchy:
- :x: **axios-0.19.2.tgz** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Axios NPM package 0.21.0 contains a Server-Side Request Forgery (SSRF) vulnerability where an attacker is able to bypass a proxy by providing a URL that responds with a redirect to a restricted host or IP address.
<p>Publish Date: 2020-11-06
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-28168>CVE-2020-28168</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.9</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/axios/axios/commit/c7329fefc890050edd51e40e469a154d0117fc55">https://github.com/axios/axios/commit/c7329fefc890050edd51e40e469a154d0117fc55</a></p>
<p>Release Date: 2020-11-06</p>
<p>Fix Resolution: axios - 0.21.1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | True | CVE-2020-28168 (Medium) detected in axios-0.19.2.tgz - ## CVE-2020-28168 - Medium Severity Vulnerability
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/vulnerability_details.png' width=19 height=20> Vulnerable Library - <b>axios-0.19.2.tgz</b></p></summary>
<p>Promise based HTTP client for the browser and node.js</p>
<p>Library home page: <a href="https://registry.npmjs.org/axios/-/axios-0.19.2.tgz">https://registry.npmjs.org/axios/-/axios-0.19.2.tgz</a></p>
<p>Path to dependency file: WebScraper/package.json</p>
<p>Path to vulnerable library: WebScraper/node_modules/axios/package.json</p>
<p>
Dependency Hierarchy:
- :x: **axios-0.19.2.tgz** (Vulnerable Library)
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/medium_vul.png' width=19 height=20> Vulnerability Details</summary>
<p>
Axios NPM package 0.21.0 contains a Server-Side Request Forgery (SSRF) vulnerability where an attacker is able to bypass a proxy by providing a URL that responds with a redirect to a restricted host or IP address.
<p>Publish Date: 2020-11-06
<p>URL: <a href=https://vuln.whitesourcesoftware.com/vulnerability/CVE-2020-28168>CVE-2020-28168</a></p>
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/cvss3.png' width=19 height=20> CVSS 3 Score Details (<b>5.9</b>)</summary>
<p>
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: None
- Availability Impact: None
</p>
For more information on CVSS3 Scores, click <a href="https://www.first.org/cvss/calculator/3.0">here</a>.
</p>
</details>
<p></p>
<details><summary><img src='https://whitesource-resources.whitesourcesoftware.com/suggested_fix.png' width=19 height=20> Suggested Fix</summary>
<p>
<p>Type: Upgrade version</p>
<p>Origin: <a href="https://github.com/axios/axios/commit/c7329fefc890050edd51e40e469a154d0117fc55">https://github.com/axios/axios/commit/c7329fefc890050edd51e40e469a154d0117fc55</a></p>
<p>Release Date: 2020-11-06</p>
<p>Fix Resolution: axios - 0.21.1</p>
</p>
</details>
<p></p>
***
Step up your Open Source Security Game with WhiteSource [here](https://www.whitesourcesoftware.com/full_solution_bolt_github) | non_comp | cve medium detected in axios tgz cve medium severity vulnerability vulnerable library axios tgz promise based http client for the browser and node js library home page a href path to dependency file webscraper package json path to vulnerable library webscraper node modules axios package json dependency hierarchy x axios tgz vulnerable library vulnerability details axios npm package contains a server side request forgery ssrf vulnerability where an attacker is able to bypass a proxy by providing a url that responds with a redirect to a restricted host or ip address publish date url a href cvss score details base score metrics exploitability metrics attack vector network attack complexity high privileges required none user interaction none scope unchanged impact metrics confidentiality impact high integrity impact none availability impact none for more information on scores click a href suggested fix type upgrade version origin a href release date fix resolution axios step up your open source security game with whitesource | 0 |
134,021 | 12,560,049,067 | IssuesEvent | 2020-06-07 20:52:26 | Enough-Software/enough_mail | https://api.github.com/repos/Enough-Software/enough_mail | closed | how to count unseen without use client.selectMailbox? | documentation imap | how to count unseen without use select client.selectMailbox? | 1.0 | how to count unseen without use client.selectMailbox? - how to count unseen without use select client.selectMailbox? | non_comp | how to count unseen without use client selectmailbox how to count unseen without use select client selectmailbox | 0 |
374,856 | 11,096,346,087 | IssuesEvent | 2019-12-16 10:57:21 | webcompat/web-bugs | https://api.github.com/repos/webcompat/web-bugs | closed | www.myntra.com - see bug description | browser-chrome ml-needsdiagnosis-false ml-probability-high priority-important | <!-- @browser: Chrome 78.0.3904 -->
<!-- @ua_header: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.108 Safari/537.36 -->
<!-- @reported_with: -->
**URL**: https://www.myntra.com
**Browser / Version**: Chrome 78.0.3904
**Operating System**: Windows 10
**Tested Another Browser**: Unknown
**Problem type**: Something else
**Description**: the search method is not elastic
**Steps to Reproduce**:
i tried to search for shirts by typing 'SIRT'. the website returned nothing.
[](https://webcompat.com/uploads/2019/12/25862f99-f387-4f15-a092-b297b5e1faf8.jpg)
<details>
<summary>Browser Configuration</summary>
<ul>
<li>None</li>
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_ | 1.0 | www.myntra.com - see bug description - <!-- @browser: Chrome 78.0.3904 -->
<!-- @ua_header: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.108 Safari/537.36 -->
<!-- @reported_with: -->
**URL**: https://www.myntra.com
**Browser / Version**: Chrome 78.0.3904
**Operating System**: Windows 10
**Tested Another Browser**: Unknown
**Problem type**: Something else
**Description**: the search method is not elastic
**Steps to Reproduce**:
i tried to search for shirts by typing 'SIRT'. the website returned nothing.
[](https://webcompat.com/uploads/2019/12/25862f99-f387-4f15-a092-b297b5e1faf8.jpg)
<details>
<summary>Browser Configuration</summary>
<ul>
<li>None</li>
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_ | non_comp | see bug description url browser version chrome operating system windows tested another browser unknown problem type something else description the search method is not elastic steps to reproduce i tried to search for shirts by typing sirt the website returned nothing browser configuration none from with ❤️ | 0 |
5,432 | 7,892,923,023 | IssuesEvent | 2018-06-28 16:21:01 | jupyterlab/jupyterlab | https://api.github.com/repos/jupyterlab/jupyterlab | closed | cannot paste a code in the cell?? | tag:Browser Compatibility type:Bug | So lets say i wanna copy and paste some lines of code to a cell?
I can use ctr+c and ctr+v, but I cannot right click and do this stuff. in other words, we dont have copy and paste option?
I just copy a line of code from somewhere and I need to do ctr+v to paste in inside jupyterlab's cell.
is it a bug or there is some reasons behind it.... | True | cannot paste a code in the cell?? - So lets say i wanna copy and paste some lines of code to a cell?
I can use ctr+c and ctr+v, but I cannot right click and do this stuff. in other words, we dont have copy and paste option?
I just copy a line of code from somewhere and I need to do ctr+v to paste in inside jupyterlab's cell.
is it a bug or there is some reasons behind it.... | comp | cannot paste a code in the cell so lets say i wanna copy and paste some lines of code to a cell i can use ctr c and ctr v but i cannot right click and do this stuff in other words we dont have copy and paste option i just copy a line of code from somewhere and i need to do ctr v to paste in inside jupyterlab s cell is it a bug or there is some reasons behind it | 1 |
5,773 | 8,215,772,766 | IssuesEvent | 2018-09-05 07:05:54 | rootsongjc/kubernetes-vagrant-centos-cluster | https://api.github.com/repos/rootsongjc/kubernetes-vagrant-centos-cluster | closed | node1 machine bug | compatibility | windows 10-hyper-v,系统：ubuntu 18.04新装的，软件都更新了。,其他的都是按照教程装的。
--------------------------------------------------------------
```
==> node1: An error occurred. The error will be shown after all tasks complete.
==> node3: Removing domain...
==> node3: An error occurred. The error will be shown after all tasks complete.
==> node2: Removing domain...
==> node2: An error occurred. The error will be shown after all tasks complete.
An error occurred while executing multiple actions in parallel.
Any errors that occurred are shown below.
An unexpected error occurred when executing the action on the
'node1' machine. Please report this as a bug:
The specified wait_for timeout (2 seconds) was exceeded
/usr/lib/ruby/vendor_ruby/fog/core/wait_for.rb:9:in `block in wait_for'
/usr/lib/ruby/vendor_ruby/fog/core/wait_for.rb:6:in `loop'
/usr/lib/ruby/vendor_ruby/fog/core/wait_for.rb:6:in `wait_for'
/usr/lib/ruby/vendor_ruby/fog/core/model.rb:74:in `wait_for'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/wait_till_up.rb:42:in `block (2 levels) in call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/util/retryable.rb:17:in `retryable'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/wait_till_up.rb:37:in `block in call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/util/timer.rb:9:in `time'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/wait_till_up.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/start_domain.rb:302:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/set_boot_order.rb:78:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/create_network_interfaces.rb:182:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/create_networks.rb:84:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/share_folders.rb:20:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/prepare_nfs_settings.rb:18:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builtin/synced_folders.rb:87:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builtin/synced_folder_cleanup.rb:28:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/plugins/synced_folders/nfs/action_cleanup.rb:25:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/prepare_nfs_valid_ids.rb:12:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builtin/provision.rb:80:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/create_domain.rb:317:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/create_domain_volume.rb:82:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/handle_box_image.rb:113:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builtin/handle_box.rb:56:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/handle_storage_pool.rb:52:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/set_name_of_domain.rb:35:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builder.rb:116:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/runner.rb:66:in `block in run'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/util/busy.rb:19:in `busy'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/runner.rb:66:in `run'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builtin/call.rb:53:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builtin/box_check_outdated.rb:23:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builder.rb:116:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/runner.rb:66:in `block in run'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/util/busy.rb:19:in `busy'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/runner.rb:66:in `run'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/machine.rb:227:in `action_raw'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/machine.rb:202:in `block in action'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/environment.rb:592:in `lock'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/machine.rb:188:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/machine.rb:188:in `action'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/batch_action.rb:82:in `block (2 levels) in run'
An unexpected error occurred when executing the action on the
'node2' machine. Please report this as a bug:
The specified wait_for timeout (2 seconds) was exceeded
/usr/lib/ruby/vendor_ruby/fog/core/wait_for.rb:9:in `block in wait_for'
/usr/lib/ruby/vendor_ruby/fog/core/wait_for.rb:6:in `loop'
/usr/lib/ruby/vendor_ruby/fog/core/wait_for.rb:6:in `wait_for'
/usr/lib/ruby/vendor_ruby/fog/core/model.rb:74:in `wait_for'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/wait_till_up.rb:42:in `block (2 levels) in call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/util/retryable.rb:17:in `retryable'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/wait_till_up.rb:37:in `block in call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/util/timer.rb:9:in `time'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/wait_till_up.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/start_domain.rb:302:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/set_boot_order.rb:78:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/create_network_interfaces.rb:182:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/create_networks.rb:84:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/share_folders.rb:20:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/prepare_nfs_settings.rb:18:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builtin/synced_folders.rb:87:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builtin/synced_folder_cleanup.rb:28:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/plugins/synced_folders/nfs/action_cleanup.rb:25:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/prepare_nfs_valid_ids.rb:12:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builtin/provision.rb:80:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/create_domain.rb:317:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/create_domain_volume.rb:82:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/handle_box_image.rb:113:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builtin/handle_box.rb:56:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/handle_storage_pool.rb:52:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/set_name_of_domain.rb:35:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builder.rb:116:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/runner.rb:66:in `block in run'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/util/busy.rb:19:in `busy'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/runner.rb:66:in `run'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builtin/call.rb:53:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builtin/box_check_outdated.rb:23:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builder.rb:116:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/runner.rb:66:in `block in run'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/util/busy.rb:19:in `busy'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/runner.rb:66:in `run'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/machine.rb:227:in `action_raw'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/machine.rb:202:in `block in action'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/environment.rb:592:in `lock'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/machine.rb:188:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/machine.rb:188:in `action'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/batch_action.rb:82:in `block (2 levels) in run'
An unexpected error occurred when executing the action on the
'node3' machine. Please report this as a bug:
The specified wait_for timeout (2 seconds) was exceeded
/usr/lib/ruby/vendor_ruby/fog/core/wait_for.rb:9:in `block in wait_for'
/usr/lib/ruby/vendor_ruby/fog/core/wait_for.rb:6:in `loop'
/usr/lib/ruby/vendor_ruby/fog/core/wait_for.rb:6:in `wait_for'
/usr/lib/ruby/vendor_ruby/fog/core/model.rb:74:in `wait_for'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/wait_till_up.rb:42:in `block (2 levels) in call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/util/retryable.rb:17:in `retryable'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/wait_till_up.rb:37:in `block in call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/util/timer.rb:9:in `time'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/wait_till_up.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/start_domain.rb:302:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/set_boot_order.rb:78:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/create_network_interfaces.rb:182:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/create_networks.rb:84:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/share_folders.rb:20:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/prepare_nfs_settings.rb:18:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builtin/synced_folders.rb:87:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builtin/synced_folder_cleanup.rb:28:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/plugins/synced_folders/nfs/action_cleanup.rb:25:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/prepare_nfs_valid_ids.rb:12:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builtin/provision.rb:80:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/create_domain.rb:317:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/create_domain_volume.rb:82:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/handle_box_image.rb:113:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builtin/handle_box.rb:56:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/handle_storage_pool.rb:52:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/set_name_of_domain.rb:35:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builder.rb:116:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/runner.rb:66:in `block in run'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/util/busy.rb:19:in `busy'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/runner.rb:66:in `run'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builtin/call.rb:53:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builtin/box_check_outdated.rb:23:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builder.rb:116:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/runner.rb:66:in `block in run'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/util/busy.rb:19:in `busy'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/runner.rb:66:in `run'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/machine.rb:227:in `action_raw'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/machine.rb:202:in `block in action'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/environment.rb:592:in `lock'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/machine.rb:188:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/machine.rb:188:in `action'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/batch_action.rb:82:in `block (2 levels) in run'
``` | True | node1 machine bug - windows 10-hyper-v,系统：ubuntu 18.04新装的，软件都更新了。,其他的都是按照教程装的。
--------------------------------------------------------------
```
==> node1: An error occurred. The error will be shown after all tasks complete.
==> node3: Removing domain...
==> node3: An error occurred. The error will be shown after all tasks complete.
==> node2: Removing domain...
==> node2: An error occurred. The error will be shown after all tasks complete.
An error occurred while executing multiple actions in parallel.
Any errors that occurred are shown below.
An unexpected error occurred when executing the action on the
'node1' machine. Please report this as a bug:
The specified wait_for timeout (2 seconds) was exceeded
/usr/lib/ruby/vendor_ruby/fog/core/wait_for.rb:9:in `block in wait_for'
/usr/lib/ruby/vendor_ruby/fog/core/wait_for.rb:6:in `loop'
/usr/lib/ruby/vendor_ruby/fog/core/wait_for.rb:6:in `wait_for'
/usr/lib/ruby/vendor_ruby/fog/core/model.rb:74:in `wait_for'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/wait_till_up.rb:42:in `block (2 levels) in call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/util/retryable.rb:17:in `retryable'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/wait_till_up.rb:37:in `block in call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/util/timer.rb:9:in `time'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/wait_till_up.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/start_domain.rb:302:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/set_boot_order.rb:78:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/create_network_interfaces.rb:182:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/create_networks.rb:84:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/share_folders.rb:20:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/prepare_nfs_settings.rb:18:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builtin/synced_folders.rb:87:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builtin/synced_folder_cleanup.rb:28:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/plugins/synced_folders/nfs/action_cleanup.rb:25:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/prepare_nfs_valid_ids.rb:12:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builtin/provision.rb:80:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/create_domain.rb:317:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/create_domain_volume.rb:82:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/handle_box_image.rb:113:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builtin/handle_box.rb:56:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/handle_storage_pool.rb:52:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/set_name_of_domain.rb:35:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builder.rb:116:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/runner.rb:66:in `block in run'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/util/busy.rb:19:in `busy'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/runner.rb:66:in `run'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builtin/call.rb:53:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builtin/box_check_outdated.rb:23:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builder.rb:116:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/runner.rb:66:in `block in run'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/util/busy.rb:19:in `busy'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/runner.rb:66:in `run'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/machine.rb:227:in `action_raw'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/machine.rb:202:in `block in action'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/environment.rb:592:in `lock'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/machine.rb:188:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/machine.rb:188:in `action'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/batch_action.rb:82:in `block (2 levels) in run'
An unexpected error occurred when executing the action on the
'node2' machine. Please report this as a bug:
The specified wait_for timeout (2 seconds) was exceeded
/usr/lib/ruby/vendor_ruby/fog/core/wait_for.rb:9:in `block in wait_for'
/usr/lib/ruby/vendor_ruby/fog/core/wait_for.rb:6:in `loop'
/usr/lib/ruby/vendor_ruby/fog/core/wait_for.rb:6:in `wait_for'
/usr/lib/ruby/vendor_ruby/fog/core/model.rb:74:in `wait_for'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/wait_till_up.rb:42:in `block (2 levels) in call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/util/retryable.rb:17:in `retryable'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/wait_till_up.rb:37:in `block in call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/util/timer.rb:9:in `time'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/wait_till_up.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/start_domain.rb:302:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/set_boot_order.rb:78:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/create_network_interfaces.rb:182:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/create_networks.rb:84:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/share_folders.rb:20:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/prepare_nfs_settings.rb:18:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builtin/synced_folders.rb:87:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builtin/synced_folder_cleanup.rb:28:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/plugins/synced_folders/nfs/action_cleanup.rb:25:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/prepare_nfs_valid_ids.rb:12:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builtin/provision.rb:80:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/create_domain.rb:317:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/create_domain_volume.rb:82:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/handle_box_image.rb:113:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builtin/handle_box.rb:56:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/handle_storage_pool.rb:52:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/set_name_of_domain.rb:35:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builder.rb:116:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/runner.rb:66:in `block in run'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/util/busy.rb:19:in `busy'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/runner.rb:66:in `run'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builtin/call.rb:53:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builtin/box_check_outdated.rb:23:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builder.rb:116:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/runner.rb:66:in `block in run'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/util/busy.rb:19:in `busy'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/runner.rb:66:in `run'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/machine.rb:227:in `action_raw'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/machine.rb:202:in `block in action'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/environment.rb:592:in `lock'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/machine.rb:188:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/machine.rb:188:in `action'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/batch_action.rb:82:in `block (2 levels) in run'
An unexpected error occurred when executing the action on the
'node3' machine. Please report this as a bug:
The specified wait_for timeout (2 seconds) was exceeded
/usr/lib/ruby/vendor_ruby/fog/core/wait_for.rb:9:in `block in wait_for'
/usr/lib/ruby/vendor_ruby/fog/core/wait_for.rb:6:in `loop'
/usr/lib/ruby/vendor_ruby/fog/core/wait_for.rb:6:in `wait_for'
/usr/lib/ruby/vendor_ruby/fog/core/model.rb:74:in `wait_for'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/wait_till_up.rb:42:in `block (2 levels) in call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/util/retryable.rb:17:in `retryable'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/wait_till_up.rb:37:in `block in call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/util/timer.rb:9:in `time'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/wait_till_up.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/start_domain.rb:302:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/set_boot_order.rb:78:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/create_network_interfaces.rb:182:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/create_networks.rb:84:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/share_folders.rb:20:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/prepare_nfs_settings.rb:18:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builtin/synced_folders.rb:87:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builtin/synced_folder_cleanup.rb:28:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/plugins/synced_folders/nfs/action_cleanup.rb:25:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/prepare_nfs_valid_ids.rb:12:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builtin/provision.rb:80:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/create_domain.rb:317:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/create_domain_volume.rb:82:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/handle_box_image.rb:113:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builtin/handle_box.rb:56:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/handle_storage_pool.rb:52:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-libvirt-0.0.43/lib/vagrant-libvirt/action/set_name_of_domain.rb:35:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builder.rb:116:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/runner.rb:66:in `block in run'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/util/busy.rb:19:in `busy'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/runner.rb:66:in `run'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builtin/call.rb:53:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builtin/box_check_outdated.rb:23:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/warden.rb:34:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/builder.rb:116:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/runner.rb:66:in `block in run'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/util/busy.rb:19:in `busy'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/action/runner.rb:66:in `run'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/machine.rb:227:in `action_raw'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/machine.rb:202:in `block in action'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/environment.rb:592:in `lock'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/machine.rb:188:in `call'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/machine.rb:188:in `action'
/usr/share/rubygems-integration/all/gems/vagrant-2.0.2/lib/vagrant/batch_action.rb:82:in `block (2 levels) in run'
``` | comp | machine bug windows hyper v 系统：ubuntu ，软件都更新了。 其他的都是按照教程装的。 an error occurred the error will be shown after all tasks complete removing domain an error occurred the error will be shown after all tasks complete removing domain an error occurred the error will be shown after all tasks complete an error occurred while executing multiple actions in parallel any errors that occurred are shown below an unexpected error occurred when executing the action on the machine please report this as a bug the specified wait for timeout seconds was exceeded usr lib ruby vendor ruby fog core wait for rb in block in wait for usr lib ruby vendor ruby fog core wait for rb in loop usr lib ruby vendor ruby fog core wait for rb in wait for usr lib ruby vendor ruby fog core model rb in wait for usr share rubygems integration all gems vagrant libvirt lib vagrant libvirt action wait till up rb in block levels in call usr share rubygems integration all gems vagrant lib vagrant util retryable rb in retryable usr share rubygems integration all gems vagrant libvirt lib vagrant libvirt action wait till up rb in block in call usr share rubygems integration all gems vagrant libvirt lib vagrant libvirt util timer rb in time usr share rubygems integration all gems vagrant libvirt lib vagrant libvirt action wait till up rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant libvirt lib vagrant libvirt action start domain rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant libvirt lib vagrant libvirt action set boot order rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant libvirt lib vagrant libvirt action create network interfaces rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant libvirt lib vagrant libvirt action create networks rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant libvirt lib vagrant libvirt action share folders rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant libvirt lib vagrant libvirt action prepare nfs settings rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant lib vagrant action builtin synced folders rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant lib vagrant action builtin synced folder cleanup rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant plugins synced folders nfs action cleanup rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant libvirt lib vagrant libvirt action prepare nfs valid ids rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant lib vagrant action builtin provision rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant libvirt lib vagrant libvirt action create domain rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant libvirt lib vagrant libvirt action create domain volume rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant libvirt lib vagrant libvirt action handle box image rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant lib vagrant action builtin handle box rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant libvirt lib vagrant libvirt action handle storage pool rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant libvirt lib vagrant libvirt action set name of domain rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in block in finalize action usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant lib vagrant action builder rb in call usr share rubygems integration all gems vagrant lib vagrant action runner rb in block in run usr share rubygems integration all gems vagrant lib vagrant util busy rb in busy usr share rubygems integration all gems vagrant lib vagrant action runner rb in run usr share rubygems integration all gems vagrant lib vagrant action builtin call rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant lib vagrant action builtin box check outdated rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant lib vagrant action builtin config validate rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant lib vagrant action builder rb in call usr share rubygems integration all gems vagrant lib vagrant action runner rb in block in run usr share rubygems integration all gems vagrant lib vagrant util busy rb in busy usr share rubygems integration all gems vagrant lib vagrant action runner rb in run usr share rubygems integration all gems vagrant lib vagrant machine rb in action raw usr share rubygems integration all gems vagrant lib vagrant machine rb in block in action usr share rubygems integration all gems vagrant lib vagrant environment rb in lock usr share rubygems integration all gems vagrant lib vagrant machine rb in call usr share rubygems integration all gems vagrant lib vagrant machine rb in action usr share rubygems integration all gems vagrant lib vagrant batch action rb in block levels in run an unexpected error occurred when executing the action on the machine please report this as a bug the specified wait for timeout seconds was exceeded usr lib ruby vendor ruby fog core wait for rb in block in wait for usr lib ruby vendor ruby fog core wait for rb in loop usr lib ruby vendor ruby fog core wait for rb in wait for usr lib ruby vendor ruby fog core model rb in wait for usr share rubygems integration all gems vagrant libvirt lib vagrant libvirt action wait till up rb in block levels in call usr share rubygems integration all gems vagrant lib vagrant util retryable rb in retryable usr share rubygems integration all gems vagrant libvirt lib vagrant libvirt action wait till up rb in block in call usr share rubygems integration all gems vagrant libvirt lib vagrant libvirt util timer rb in time usr share rubygems integration all gems vagrant libvirt lib vagrant libvirt action wait till up rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant libvirt lib vagrant libvirt action start domain rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant libvirt lib vagrant libvirt action set boot order rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant libvirt lib vagrant libvirt action create network interfaces rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant libvirt lib vagrant libvirt action create networks rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant libvirt lib vagrant libvirt action share folders rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant libvirt lib vagrant libvirt action prepare nfs settings rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant lib vagrant action builtin synced folders rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant lib vagrant action builtin synced folder cleanup rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant plugins synced folders nfs action cleanup rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant libvirt lib vagrant libvirt action prepare nfs valid ids rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant lib vagrant action builtin provision rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant libvirt lib vagrant libvirt action create domain rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant libvirt lib vagrant libvirt action create domain volume rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant libvirt lib vagrant libvirt action handle box image rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant lib vagrant action builtin handle box rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant libvirt lib vagrant libvirt action handle storage pool rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant libvirt lib vagrant libvirt action set name of domain rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in block in finalize action usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant lib vagrant action builder rb in call usr share rubygems integration all gems vagrant lib vagrant action runner rb in block in run usr share rubygems integration all gems vagrant lib vagrant util busy rb in busy usr share rubygems integration all gems vagrant lib vagrant action runner rb in run usr share rubygems integration all gems vagrant lib vagrant action builtin call rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant lib vagrant action builtin box check outdated rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant lib vagrant action builtin config validate rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant lib vagrant action builder rb in call usr share rubygems integration all gems vagrant lib vagrant action runner rb in block in run usr share rubygems integration all gems vagrant lib vagrant util busy rb in busy usr share rubygems integration all gems vagrant lib vagrant action runner rb in run usr share rubygems integration all gems vagrant lib vagrant machine rb in action raw usr share rubygems integration all gems vagrant lib vagrant machine rb in block in action usr share rubygems integration all gems vagrant lib vagrant environment rb in lock usr share rubygems integration all gems vagrant lib vagrant machine rb in call usr share rubygems integration all gems vagrant lib vagrant machine rb in action usr share rubygems integration all gems vagrant lib vagrant batch action rb in block levels in run an unexpected error occurred when executing the action on the machine please report this as a bug the specified wait for timeout seconds was exceeded usr lib ruby vendor ruby fog core wait for rb in block in wait for usr lib ruby vendor ruby fog core wait for rb in loop usr lib ruby vendor ruby fog core wait for rb in wait for usr lib ruby vendor ruby fog core model rb in wait for usr share rubygems integration all gems vagrant libvirt lib vagrant libvirt action wait till up rb in block levels in call usr share rubygems integration all gems vagrant lib vagrant util retryable rb in retryable usr share rubygems integration all gems vagrant libvirt lib vagrant libvirt action wait till up rb in block in call usr share rubygems integration all gems vagrant libvirt lib vagrant libvirt util timer rb in time usr share rubygems integration all gems vagrant libvirt lib vagrant libvirt action wait till up rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant libvirt lib vagrant libvirt action start domain rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant libvirt lib vagrant libvirt action set boot order rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant libvirt lib vagrant libvirt action create network interfaces rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant libvirt lib vagrant libvirt action create networks rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant libvirt lib vagrant libvirt action share folders rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant libvirt lib vagrant libvirt action prepare nfs settings rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant lib vagrant action builtin synced folders rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant lib vagrant action builtin synced folder cleanup rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant plugins synced folders nfs action cleanup rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant libvirt lib vagrant libvirt action prepare nfs valid ids rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant lib vagrant action builtin provision rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant libvirt lib vagrant libvirt action create domain rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant libvirt lib vagrant libvirt action create domain volume rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant libvirt lib vagrant libvirt action handle box image rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant lib vagrant action builtin handle box rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant libvirt lib vagrant libvirt action handle storage pool rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant libvirt lib vagrant libvirt action set name of domain rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in block in finalize action usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant lib vagrant action builder rb in call usr share rubygems integration all gems vagrant lib vagrant action runner rb in block in run usr share rubygems integration all gems vagrant lib vagrant util busy rb in busy usr share rubygems integration all gems vagrant lib vagrant action runner rb in run usr share rubygems integration all gems vagrant lib vagrant action builtin call rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant lib vagrant action builtin box check outdated rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant lib vagrant action builtin config validate rb in call usr share rubygems integration all gems vagrant lib vagrant action warden rb in call usr share rubygems integration all gems vagrant lib vagrant action builder rb in call usr share rubygems integration all gems vagrant lib vagrant action runner rb in block in run usr share rubygems integration all gems vagrant lib vagrant util busy rb in busy usr share rubygems integration all gems vagrant lib vagrant action runner rb in run usr share rubygems integration all gems vagrant lib vagrant machine rb in action raw usr share rubygems integration all gems vagrant lib vagrant machine rb in block in action usr share rubygems integration all gems vagrant lib vagrant environment rb in lock usr share rubygems integration all gems vagrant lib vagrant machine rb in call usr share rubygems integration all gems vagrant lib vagrant machine rb in action usr share rubygems integration all gems vagrant lib vagrant batch action rb in block levels in run | 1 |
160,162 | 6,077,708,125 | IssuesEvent | 2017-06-16 05:29:13 | geoffreyyip/mta-dashboard | https://api.github.com/repos/geoffreyyip/mta-dashboard | closed | Users should have the option to filter subway advisories by route. | priority | Currently, the user must load information for all train routes, even if they only want information for a handful of routes. | 1.0 | Users should have the option to filter subway advisories by route. - Currently, the user must load information for all train routes, even if they only want information for a handful of routes. | non_comp | users should have the option to filter subway advisories by route currently the user must load information for all train routes even if they only want information for a handful of routes | 0 |
16,576 | 9,834,347,419 | IssuesEvent | 2019-06-17 09:28:44 | automium/reactor | https://api.github.com/repos/automium/reactor | closed | Run consul with a valid ACL Token | security | In order to join a Consul cluster with ACL enabled, the agent configuration must be changed as in the following example:
```
{
"acl": {
"enabled": true,
"default_policy": "deny",
"down_policy": "extend-cache",
"tokens": {
"agent": "edb20702-9e16-1171-b0e1-6c1d95afcc51"
}
}
}
```
The api client needs to manage the Consul catalog, so the token provided needs the right policy, like:
```
service_prefix "" {
policy = "read"
}
service "example" {
policy = "write"
}
``` | True | Run consul with a valid ACL Token - In order to join a Consul cluster with ACL enabled, the agent configuration must be changed as in the following example:
```
{
"acl": {
"enabled": true,
"default_policy": "deny",
"down_policy": "extend-cache",
"tokens": {
"agent": "edb20702-9e16-1171-b0e1-6c1d95afcc51"
}
}
}
```
The api client needs to manage the Consul catalog, so the token provided needs the right policy, like:
```
service_prefix "" {
policy = "read"
}
service "example" {
policy = "write"
}
``` | non_comp | run consul with a valid acl token in order to join a consul cluster with acl enabled the agent configuration must be changed as in the following example acl enabled true default policy deny down policy extend cache tokens agent the api client needs to manage the consul catalog so the token provided needs the right policy like service prefix policy read service example policy write | 0 |
13,586 | 16,100,707,773 | IssuesEvent | 2021-04-27 08:56:06 | spatie/laravel-activitylog | https://api.github.com/repos/spatie/laravel-activitylog | closed | Deep Diff checking is not working | enhancement help wanted package-compatibility revisit for next major version | When using a package like spatie's own schemaless-attributes, the extra attributes are logged as being different every touch of the model, which not only generates useless logs even when using `$logOnlyDirty` but just creates confusion in the activity log itself. While specifying specific json attributes is supported, that functionality isn't carried over into the dirty checks to confirm that what's going into the activity log is only specifically changed json attributes. Additionally, the reverse filtering that normally works isn't applied either (being able to set logAttributes = *, and then exclude attributes from ever being logged).
It seems that there was quite a bit more that needed to be done to add json attribute logging that what's currently there. On top of that, in enabling that functionality or really handling any deep diffing is completely unsupported. | True | Deep Diff checking is not working - When using a package like spatie's own schemaless-attributes, the extra attributes are logged as being different every touch of the model, which not only generates useless logs even when using `$logOnlyDirty` but just creates confusion in the activity log itself. While specifying specific json attributes is supported, that functionality isn't carried over into the dirty checks to confirm that what's going into the activity log is only specifically changed json attributes. Additionally, the reverse filtering that normally works isn't applied either (being able to set logAttributes = *, and then exclude attributes from ever being logged).
It seems that there was quite a bit more that needed to be done to add json attribute logging that what's currently there. On top of that, in enabling that functionality or really handling any deep diffing is completely unsupported. | comp | deep diff checking is not working when using a package like spatie s own schemaless attributes the extra attributes are logged as being different every touch of the model which not only generates useless logs even when using logonlydirty but just creates confusion in the activity log itself while specifying specific json attributes is supported that functionality isn t carried over into the dirty checks to confirm that what s going into the activity log is only specifically changed json attributes additionally the reverse filtering that normally works isn t applied either being able to set logattributes and then exclude attributes from ever being logged it seems that there was quite a bit more that needed to be done to add json attribute logging that what s currently there on top of that in enabling that functionality or really handling any deep diffing is completely unsupported | 1 |
115,148 | 11,866,285,769 | IssuesEvent | 2020-03-26 03:11:51 | AY1920S2-CS2113T-M16-2/tp | https://api.github.com/repos/AY1920S2-CS2113T-M16-2/tp | closed | User Guide for Recipe-commands | priority.High type.Documentation | Reopen #94
This is for the reformatting of the user guide and reopening of the merged PR is not feasible without undoing commits | 1.0 | User Guide for Recipe-commands - Reopen #94
This is for the reformatting of the user guide and reopening of the merged PR is not feasible without undoing commits | non_comp | user guide for recipe commands reopen this is for the reformatting of the user guide and reopening of the merged pr is not feasible without undoing commits | 0 |
27,414 | 7,961,757,963 | IssuesEvent | 2018-07-13 12:02:32 | coredns/coredns | https://api.github.com/repos/coredns/coredns | closed | travis build stops for a reason | build | Def. seeing this a lot more:
~~~
=== RUN TestNameFromRight
--- PASS: TestNameFromRight (0.00s)
PASS
2018/04/24 06:49:11 [ERROR] plugin/file: Failed to open zone "miek.nl." in "go-test-tmpfile739461045": open go-test-tmpfile739461045: no such file or directory
2018/04/24 06:49:11 [ERROR] plugin/file: Failed to open zone "miek.nl." in "go-test-tmpfile739461045": open go-test-tmpfile739461045: no such file or directory
ok github.com/coredns/coredns/plugin/file 3.400s
=== RUN TestLess
--- PASS: TestLess (0.00s)
PASS
ok github.com/coredns/coredns/plugin/file/tree 1.012s
No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.
Check the details on how to adjust your build configuration on: https://docs.travis-ci.com/user/common-build-problems/#Build-times-out-because-no-output-was-received
The build has been terminated
=== RUN TestNameFromRight
--- PASS: TestNameFromRight (0.00s)
PASS
2018/04/24 06:49:11 [ERROR] plugin/file: Failed to open zone "miek.nl." in "go-test-tmpfile739461045": open go-test-tmpfile739461045: no such file or directory
2018/04/24 06:49:11 [ERROR] plugin/file: Failed to open zone "miek.nl." in "go-test-tmpfile739461045": open go-test-tmpfile739461045: no such file or directory
ok github.com/coredns/coredns/plugin/file 3.400s
=== RUN TestLess
--- PASS: TestLess (0.00s)
PASS
ok github.com/coredns/coredns/plugin/file/tree 1.012s
No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.
Check the details on how to adjust your build configuration on: https://docs.travis-ci.com/user/common-build-problems/#Build-times-out-because-no-output-was-received
The build has been terminated
~~~
Haven't look in detail, gut feeling says it started with the merge of #1709 | 1.0 | travis build stops for a reason - Def. seeing this a lot more:
~~~
=== RUN TestNameFromRight
--- PASS: TestNameFromRight (0.00s)
PASS
2018/04/24 06:49:11 [ERROR] plugin/file: Failed to open zone "miek.nl." in "go-test-tmpfile739461045": open go-test-tmpfile739461045: no such file or directory
2018/04/24 06:49:11 [ERROR] plugin/file: Failed to open zone "miek.nl." in "go-test-tmpfile739461045": open go-test-tmpfile739461045: no such file or directory
ok github.com/coredns/coredns/plugin/file 3.400s
=== RUN TestLess
--- PASS: TestLess (0.00s)
PASS
ok github.com/coredns/coredns/plugin/file/tree 1.012s
No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.
Check the details on how to adjust your build configuration on: https://docs.travis-ci.com/user/common-build-problems/#Build-times-out-because-no-output-was-received
The build has been terminated
=== RUN TestNameFromRight
--- PASS: TestNameFromRight (0.00s)
PASS
2018/04/24 06:49:11 [ERROR] plugin/file: Failed to open zone "miek.nl." in "go-test-tmpfile739461045": open go-test-tmpfile739461045: no such file or directory
2018/04/24 06:49:11 [ERROR] plugin/file: Failed to open zone "miek.nl." in "go-test-tmpfile739461045": open go-test-tmpfile739461045: no such file or directory
ok github.com/coredns/coredns/plugin/file 3.400s
=== RUN TestLess
--- PASS: TestLess (0.00s)
PASS
ok github.com/coredns/coredns/plugin/file/tree 1.012s
No output has been received in the last 10m0s, this potentially indicates a stalled build or something wrong with the build itself.
Check the details on how to adjust your build configuration on: https://docs.travis-ci.com/user/common-build-problems/#Build-times-out-because-no-output-was-received
The build has been terminated
~~~
Haven't look in detail, gut feeling says it started with the merge of #1709 | non_comp | travis build stops for a reason def seeing this a lot more run testnamefromright pass testnamefromright pass plugin file failed to open zone miek nl in go test open go test no such file or directory plugin file failed to open zone miek nl in go test open go test no such file or directory ok github com coredns coredns plugin file run testless pass testless pass ok github com coredns coredns plugin file tree no output has been received in the last this potentially indicates a stalled build or something wrong with the build itself check the details on how to adjust your build configuration on the build has been terminated run testnamefromright pass testnamefromright pass plugin file failed to open zone miek nl in go test open go test no such file or directory plugin file failed to open zone miek nl in go test open go test no such file or directory ok github com coredns coredns plugin file run testless pass testless pass ok github com coredns coredns plugin file tree no output has been received in the last this potentially indicates a stalled build or something wrong with the build itself check the details on how to adjust your build configuration on the build has been terminated haven t look in detail gut feeling says it started with the merge of | 0 |
13,545 | 3,152,762,474 | IssuesEvent | 2015-09-16 15:11:54 | CartoDB/docs | https://api.github.com/repos/CartoDB/docs | closed | Create a script for generating a printable version of the docs | Design | I need a printable version of the docs. For example, I have some work-in-progress branches that I need my team to review.
Ideally, I can generate and save a local PDF, or something similar, so that they can view my changes and questions.
| 1.0 | Create a script for generating a printable version of the docs - I need a printable version of the docs. For example, I have some work-in-progress branches that I need my team to review.
Ideally, I can generate and save a local PDF, or something similar, so that they can view my changes and questions.
| non_comp | create a script for generating a printable version of the docs i need a printable version of the docs for example i have some work in progress branches that i need my team to review ideally i can generate and save a local pdf or something similar so that they can view my changes and questions | 0 |
16,464 | 21,390,659,125 | IssuesEvent | 2022-04-21 06:42:36 | zammad/zammad | https://api.github.com/repos/zammad/zammad | closed | parsing incoming mails breaks on this line "Reply-To: <>" | enhancement verified prioritised by payment mail processing | <!--
Hi there - thanks for filing an issue. Please ensure the following things before creating an issue - thank you! 🤓
Since november 15th we handle all requests, except real bugs, at our community board.
Full explanation: https://community.zammad.org/t/major-change-regarding-github-issues-community-board/21
Please post:
- Feature requests
- Development questions
- Technical questions
on the board -> https://community.zammad.org !
If you think you hit a bug, please continue:
- Search existing issues and the CHANGELOG.md for your issue - there might be a solution already
- Make sure to use the latest version of Zammad if possible
- Add the `log/production.log` file from your system. Attention: Make sure no confidential data is in it!
- Please write the issue in english
- Don't remove the template - otherwise we will close the issue without further comments
- Ask questions about Zammad configuration and usage at our mailinglist. See: https://zammad.org/participate
Note: We always do our best. Unfortunately, sometimes there are too many requests and we can't handle everything at once. If you want to prioritize/escalate your issue, you can do so by means of a support contract (see https://zammad.com/pricing#selfhosted).
* The upper textblock will be removed automatically when you submit your issue *
-->
### Infos:
* Used Zammad version: 4.1.x
* Installation method (source, package, ..): package
* Operating system: CentOS 7
* Database + version:
* Elasticsearch version:
* Browser + version: none, it's an cli issue
### Expected behavior:
* parsing incoming mails should not break if the mail contains this line: "Reply-To: <>"
### Actual behavior:
* it breaks with this error message
```
zammad run rails r 'Channel::EmailParser.process_unprocessable_mails'
"ERROR: Can't process email, you will find it for bug reporting under /opt/zammad/tmp/unprocessable_mail/83e5bf7c5a1a640f057cbf0b668f40e0.eml, please create an issue at https://github.com/zammad/zammad/issues"
"ERROR: #<Exceptions::UnprocessableEntity: Invalid email '@local'>"
/opt/zammad/app/models/channel/email_parser.rb:135:in `rescue in process': #<Exceptions::UnprocessableEntity: Invalid email '@local'> (RuntimeError)
/opt/zammad/app/models/user.rb:927:in `check_email'
...
```
Once I removed the Reply-To line it works.
Yes I'm sure this is a bug and no feature request or a general question.
| 1.0 | parsing incoming mails breaks on this line "Reply-To: <>" - <!--
Hi there - thanks for filing an issue. Please ensure the following things before creating an issue - thank you! 🤓
Since november 15th we handle all requests, except real bugs, at our community board.
Full explanation: https://community.zammad.org/t/major-change-regarding-github-issues-community-board/21
Please post:
- Feature requests
- Development questions
- Technical questions
on the board -> https://community.zammad.org !
If you think you hit a bug, please continue:
- Search existing issues and the CHANGELOG.md for your issue - there might be a solution already
- Make sure to use the latest version of Zammad if possible
- Add the `log/production.log` file from your system. Attention: Make sure no confidential data is in it!
- Please write the issue in english
- Don't remove the template - otherwise we will close the issue without further comments
- Ask questions about Zammad configuration and usage at our mailinglist. See: https://zammad.org/participate
Note: We always do our best. Unfortunately, sometimes there are too many requests and we can't handle everything at once. If you want to prioritize/escalate your issue, you can do so by means of a support contract (see https://zammad.com/pricing#selfhosted).
* The upper textblock will be removed automatically when you submit your issue *
-->
### Infos:
* Used Zammad version: 4.1.x
* Installation method (source, package, ..): package
* Operating system: CentOS 7
* Database + version:
* Elasticsearch version:
* Browser + version: none, it's an cli issue
### Expected behavior:
* parsing incoming mails should not break if the mail contains this line: "Reply-To: <>"
### Actual behavior:
* it breaks with this error message
```
zammad run rails r 'Channel::EmailParser.process_unprocessable_mails'
"ERROR: Can't process email, you will find it for bug reporting under /opt/zammad/tmp/unprocessable_mail/83e5bf7c5a1a640f057cbf0b668f40e0.eml, please create an issue at https://github.com/zammad/zammad/issues"
"ERROR: #<Exceptions::UnprocessableEntity: Invalid email '@local'>"
/opt/zammad/app/models/channel/email_parser.rb:135:in `rescue in process': #<Exceptions::UnprocessableEntity: Invalid email '@local'> (RuntimeError)
/opt/zammad/app/models/user.rb:927:in `check_email'
...
```
Once I removed the Reply-To line it works.
Yes I'm sure this is a bug and no feature request or a general question.
| non_comp | parsing incoming mails breaks on this line reply to hi there thanks for filing an issue please ensure the following things before creating an issue thank you 🤓 since november we handle all requests except real bugs at our community board full explanation please post feature requests development questions technical questions on the board if you think you hit a bug please continue search existing issues and the changelog md for your issue there might be a solution already make sure to use the latest version of zammad if possible add the log production log file from your system attention make sure no confidential data is in it please write the issue in english don t remove the template otherwise we will close the issue without further comments ask questions about zammad configuration and usage at our mailinglist see note we always do our best unfortunately sometimes there are too many requests and we can t handle everything at once if you want to prioritize escalate your issue you can do so by means of a support contract see the upper textblock will be removed automatically when you submit your issue infos used zammad version x installation method source package package operating system centos database version elasticsearch version browser version none it s an cli issue expected behavior parsing incoming mails should not break if the mail contains this line reply to actual behavior it breaks with this error message zammad run rails r channel emailparser process unprocessable mails error can t process email you will find it for bug reporting under opt zammad tmp unprocessable mail eml please create an issue at error opt zammad app models channel email parser rb in rescue in process runtimeerror opt zammad app models user rb in check email once i removed the reply to line it works yes i m sure this is a bug and no feature request or a general question | 0 |
4,729 | 3,438,565,096 | IssuesEvent | 2015-12-14 01:32:56 | jeff1evesque/machine-learning | https://api.github.com/repos/jeff1evesque/machine-learning | closed | Ensure only js files minify with uglifyjs | build enhancement | We need to ensure that uglifyjs only minifies files with `.js` file extensions. Specifically, we need to adjust `/puppet/script/uglifyjs`, similar to [`/puppet/script/browserify`](https://github.com/jeff1evesque/machine-learning/blob/18d1b4a9abb3fffd6e86cf5e3e62097f53cb0eb7/puppet/scripts/browserify#L23). | 1.0 | Ensure only js files minify with uglifyjs - We need to ensure that uglifyjs only minifies files with `.js` file extensions. Specifically, we need to adjust `/puppet/script/uglifyjs`, similar to [`/puppet/script/browserify`](https://github.com/jeff1evesque/machine-learning/blob/18d1b4a9abb3fffd6e86cf5e3e62097f53cb0eb7/puppet/scripts/browserify#L23). | non_comp | ensure only js files minify with uglifyjs we need to ensure that uglifyjs only minifies files with js file extensions specifically we need to adjust puppet script uglifyjs similar to | 0 |
216,657 | 16,794,400,216 | IssuesEvent | 2021-06-16 00:04:22 | microsoft/appcenter | https://api.github.com/repos/microsoft/appcenter | closed | Xamarin.UITest 3.0.14 - Android SDK not found - Missing: apksigner | reviewed-DRI support test | Getting this error after upgrading to Xamarin.UITest 3.0.14 on Windows 10:
```
System.Exception : Android SDK not found. Please install it and if it is still not located, please set the ANDROID_HOME environment variable to point to the directory.
Searched locations:
Windows Registry
F:\Android\VS-SDK - Partial match. Found: zipalign, aapt, adb, android.jar Missing: apksigner [ Source: ANDROID_HOME ]
C:\Program Files (x86)\Android\android-sdk - Partial match. Found: zipalign, aapt, adb, android.jar Missing: apksigner [ Source: Registry ]
C:\Program Files (x86)\Android\android-sdk - Partial match. Found: zipalign, aapt, adb, android.jar Missing: apksigner [ Source: Registry ]
```
Found https://stackoverflow.com/questions/66031511/xamarin-uitest-3-0-14-apksigner-not-found which notes:
> Yeah I noticed the same error : Xamarin.UITest 3.0.14 doesn't accept the apksigner.bat file. I tried to create a file named "apksigner" (without any extension, just like Linux and MacOS files for Android SDK) and the error disappeared. But this workaround will raise another error and the problem will remain.
>
> The only solution I found is to downgrade your Xamarin.UITest to 3.0.13, because (in my opinion) 3.0.14 will only work with Linux and MacOS.
>
> The next version should solve this problem, so we just have to wait ^^
Downgrading to 3.0.13 resolves the issue. | 1.0 | Xamarin.UITest 3.0.14 - Android SDK not found - Missing: apksigner - Getting this error after upgrading to Xamarin.UITest 3.0.14 on Windows 10:
```
System.Exception : Android SDK not found. Please install it and if it is still not located, please set the ANDROID_HOME environment variable to point to the directory.
Searched locations:
Windows Registry
F:\Android\VS-SDK - Partial match. Found: zipalign, aapt, adb, android.jar Missing: apksigner [ Source: ANDROID_HOME ]
C:\Program Files (x86)\Android\android-sdk - Partial match. Found: zipalign, aapt, adb, android.jar Missing: apksigner [ Source: Registry ]
C:\Program Files (x86)\Android\android-sdk - Partial match. Found: zipalign, aapt, adb, android.jar Missing: apksigner [ Source: Registry ]
```
Found https://stackoverflow.com/questions/66031511/xamarin-uitest-3-0-14-apksigner-not-found which notes:
> Yeah I noticed the same error : Xamarin.UITest 3.0.14 doesn't accept the apksigner.bat file. I tried to create a file named "apksigner" (without any extension, just like Linux and MacOS files for Android SDK) and the error disappeared. But this workaround will raise another error and the problem will remain.
>
> The only solution I found is to downgrade your Xamarin.UITest to 3.0.13, because (in my opinion) 3.0.14 will only work with Linux and MacOS.
>
> The next version should solve this problem, so we just have to wait ^^
Downgrading to 3.0.13 resolves the issue. | non_comp | xamarin uitest android sdk not found missing apksigner getting this error after upgrading to xamarin uitest on windows system exception android sdk not found please install it and if it is still not located please set the android home environment variable to point to the directory searched locations windows registry f android vs sdk partial match found zipalign aapt adb android jar missing apksigner c program files android android sdk partial match found zipalign aapt adb android jar missing apksigner c program files android android sdk partial match found zipalign aapt adb android jar missing apksigner found which notes yeah i noticed the same error xamarin uitest doesn t accept the apksigner bat file i tried to create a file named apksigner without any extension just like linux and macos files for android sdk and the error disappeared but this workaround will raise another error and the problem will remain the only solution i found is to downgrade your xamarin uitest to because in my opinion will only work with linux and macos the next version should solve this problem so we just have to wait downgrading to resolves the issue | 0 |
5,415 | 7,888,208,763 | IssuesEvent | 2018-06-27 21:11:20 | bitwalker/distillery | https://api.github.com/repos/bitwalker/distillery | closed | Custom tasks fail with Erlang/OTP 21 (nonexistent `no_dot_erlang.boot` file) | bug:compatibility deployment:scripts | ### Steps to reproduce
After building a release with the new Elixir 1.6.6 and Erlang/OTP 21, I'm unable to run custom release tasks.
N.B: this didn't happened with the previous Erlang/OTP 20.1. The application still runs OK (e.g. `console`, `foreground`, etc.)
I get the following error:
```
root@3411ff09020c:~/my_app/_build/prod/rel/my_app/bin# ./my_app command Elixir.MyApp.ReleaseTasks migrate_up
init terminating in do_boot ({cannot get bootfile,no_dot_erlang.boot})
Crash dump is being written to: erl_crash.dump...done
```
This is the `bin` folder content:
```
root@3411ff09020c:~/my_app/_build/prod/rel/my_app/bin# ll
total 112
drwxr-xr-x 2 root root 4096 Jun 21 12:41 .
drwxr-xr-x 7 root root 4096 Jun 21 11:13 ..
-rwxrwxrwx 1 root root 794 Jun 21 11:13 my_app
-rwxrwxrwx 1 root root 334 Jun 21 11:13 my_app.bat
-rwxrwxrwx 1 root root 2049 Jun 21 11:13 my_app_loader.sh
-rw-r--r-- 1 root root 6906 Jun 21 11:13 nodetool
-rw-r--r-- 1 root root 10835 Jun 21 11:13 release_utils.escript
-rw-r--r-- 1 root root 20794 Jun 21 11:13 start_clean.boot
```
If I copy the `start_clean.boot` to `no_dot_erlang.boot`, everything works as expected.
Maybe Erlang/OTP 21 changed the name of the `.boot` file it generates?
### Verbose Logs
<details>
```
==> Loading configuration..
==> Assembling release..
==> Building release my_app:0.0.1 using environment prod
==> One or more direct or transitive dependencies are missing from
:applications or :included_applications, they will not be included
in the release:
:parse_trans
This can cause your application to fail at runtime. If you are sure
that this is not an issue, you may ignore this warning.
==> Discovered applications:
poolboy-1.5.1
from: _build/prod/lib/poolboy
applications:
:kernel
:stdlib
includes: none
ecto-2.2.10
from: _build/prod/lib/ecto
applications:
:kernel
:stdlib
:elixir
:logger
:decimal
:poolboy
:crypto
includes: none
phoenix_ecto-3.3.0
from: _build/prod/lib/phoenix_ecto
applications:
:kernel
:stdlib
:elixir
:logger
:ecto
:plug
includes: none
distillery-1.5.2
from: _build/prod/lib/distillery
applications:
:kernel
:stdlib
:elixir
includes: none
decimal-1.5.0
from: _build/prod/lib/decimal
applications:
:kernel
:stdlib
:elixir
includes: none
connection-1.0.4
from: _build/prod/lib/connection
applications:
:kernel
:stdlib
:elixir
includes: none
db_connection-1.1.3
from: _build/prod/lib/db_connection
applications:
:kernel
:stdlib
:elixir
:logger
:connection
includes: none
postgrex-0.13.5
from: _build/prod/lib/postgrex
applications:
:kernel
:stdlib
:elixir
:logger
:db_connection
:decimal
:crypto
includes: none
eex-1.6.6
from: /elixir/bin/../lib/eex
applications:
:kernel
:stdlib
:elixir
includes: none
mime-1.2.0
from: _build/prod/lib/mime
applications:
:kernel
:stdlib
:elixir
includes: none
plug-1.5.1
from: _build/prod/lib/plug
applications:
:kernel
:stdlib
:elixir
:crypto
:logger
:mime
includes: none
phoenix-1.3.2
from: _build/prod/lib/phoenix
applications:
:kernel
:stdlib
:elixir
:plug
:poison
:logger
:eex
:phoenix_pubsub
:crypto
includes: none
ex_statsd-0.5.3
from: _build/prod/lib/ex_statsd
applications:
:kernel
:stdlib
:elixir
includes: none
cowlib-1.0.2
from: _build/prod/lib/cowlib
applications:
:kernel
:stdlib
:crypto
includes: none
ranch-1.3.2
from: _build/prod/lib/ranch
applications:
:kernel
:stdlib
:ssl
includes: none
cowboy-1.1.2
from: _build/prod/lib/cowboy
applications:
:kernel
:stdlib
:ranch
:cowlib
:crypto
includes: none
phoenix_pubsub-1.0.2
from: _build/prod/lib/phoenix_pubsub
applications:
:kernel
:stdlib
:elixir
:logger
:crypto
includes: none
ex_aws_kms-2.0.0
from: _build/prod/lib/ex_aws_kms
applications:
:kernel
:stdlib
:elixir
:logger
:ex_aws
includes: none
ex_aws_s3-2.0.0
from: _build/prod/lib/ex_aws_s3
applications:
:kernel
:stdlib
:elixir
:logger
:ex_aws
includes: none
ex_aws-2.0.2
from: _build/prod/lib/ex_aws
applications:
:kernel
:stdlib
:elixir
:logger
:crypto
includes: none
metrics-1.0.1
from: _build/prod/lib/metrics
applications:
:kernel
:stdlib
includes: none
ssl_verify_fun-1.1.1
from: _build/prod/lib/ssl_verify_fun
applications:
:kernel
:stdlib
:ssl
includes: none
certifi-2.3.1
from: _build/prod/lib/certifi
applications:
:kernel
:stdlib
includes: none
mimerl-1.0.2
from: _build/prod/lib/mimerl
applications:
:kernel
:stdlib
includes: none
unicode_util_compat-0.3.1
from: _build/prod/lib/unicode_util_compat
applications:
:kernel
:stdlib
includes: none
idna-5.1.1
from: _build/prod/lib/idna
applications:
:kernel
:stdlib
:unicode_util_compat
includes: none
ssl-9.0
from: /usr/local/lib/erlang/lib/ssl-9.0
applications:
:crypto
:public_key
:kernel
:stdlib
includes: none
public_key-1.6
from: /usr/local/lib/erlang/lib/public_key-1.6
applications:
:asn1
:crypto
:kernel
:stdlib
includes: none
asn1-5.0.6
from: /usr/local/lib/erlang/lib/asn1-5.0.6
applications:
:kernel
:stdlib
includes: none
crypto-4.3
from: /usr/local/lib/erlang/lib/crypto-4.3
applications:
:kernel
:stdlib
includes: none
hackney-1.12.1
from: _build/prod/lib/hackney
applications:
:kernel
:stdlib
:crypto
:asn1
:public_key
:ssl
:idna
:mimerl
:certifi
:ssl_verify_fun
:metrics
includes: none
poison-3.1.0
from: _build/prod/lib/poison
applications:
:kernel
:stdlib
:elixir
includes: none
gettext-0.15.0
from: _build/prod/lib/gettext
applications:
:kernel
:stdlib
:elixir
:logger
includes: none
runtime_tools-1.13
from: /usr/local/lib/erlang/lib/runtime_tools-1.13
applications:
:kernel
:stdlib
includes: none
logger-1.6.6
from: /elixir/bin/../lib/logger
applications:
:kernel
:stdlib
:elixir
includes: none
compiler-7.2
from: /usr/local/lib/erlang/lib/compiler-7.2
applications:
:kernel
:stdlib
includes: none
elixir-1.6.6
from: /elixir/bin/../lib/elixir
applications:
:kernel
:stdlib
:compiler
includes: none
stdlib-3.5
from: /usr/local/lib/erlang/lib/stdlib-3.5
applications:
:kernel
includes: none
kernel-6.0
from: /usr/local/lib/erlang/lib/kernel-6.0
applications: none
includes: none
my_app-0.0.1
from: _build/prod/lib/my_app
applications:
:kernel
:stdlib
:elixir
:logger
:runtime_tools
:gettext
:poison
:hackney
:ex_aws
:ex_aws_s3
:ex_aws_kms
:phoenix_pubsub
:cowboy
:ex_statsd
:phoenix
:postgrex
:distillery
:phoenix_ecto
includes: none
iex-1.6.6
from: /elixir/bin/../lib/iex
applications:
:kernel
:stdlib
:elixir
includes: none
sasl-3.2
from: /usr/local/lib/erlang/lib/sasl-3.2
applications:
:kernel
:stdlib
includes: none
==> Generated overlay vars:
release_name=:my_app
release_version="0.0.1"
is_upgrade=false
upgrade_from=:latest
dev_mode=false
include_erts=true
include_src=false
include_system_libs=true
erl_opts=""
run_erl_env=""
erts_vsn="10.0"
output_dir="_build/prod/rel/my_app"
==> Copying applications to _build/prod/rel/my_app
==> Generating nodetool
==> Generating start_erl.data
==> Generating vm.args from rel/custom.vm.args
==> Generating sys.config from config/config.exs
==> Including ERTS 10.0 from /usr/local/lib/erlang/erts-10.0
==> Generating boot script
==> Generating RELEASES
==> Generating start_clean.boot
==> Applying overlays
==> Applying mkdir overlay
dst: releases/0.0.1/hooks
==> Applying mkdir overlay
dst: releases/0.0.1/hooks/pre_configure.d
==> Applying mkdir overlay
dst: releases/0.0.1/hooks/post_configure.d
==> Applying mkdir overlay
dst: releases/0.0.1/hooks/pre_start.d
==> Applying mkdir overlay
dst: releases/0.0.1/hooks/post_start.d
==> Applying mkdir overlay
dst: releases/0.0.1/hooks/pre_stop.d
==> Applying mkdir overlay
dst: releases/0.0.1/hooks/post_stop.d
==> Applying mkdir overlay
dst: releases/0.0.1/hooks/pre_upgrade.d
==> Applying mkdir overlay
dst: releases/0.0.1/hooks/post_upgrade.d
==> Applying copy overlay
src: _build/prod/lib/distillery/priv/libexec
dst: releases/0.0.1/libexec
==> Applying mkdir overlay
dst: releases/0.0.1/commands
==> Applying copy overlay
src: rel/commands/migrate_up.sh
dst: releases/0.0.1/commands/migrate_up.sh
==> Applying copy overlay
src: rel/commands/migrate_down.sh
dst: releases/0.0.1/commands/migrate_down.sh
==> Packaging release..
==> Archiving my_app-0.0.1
==> Writing tarball to _build/prod/rel/my_app/releases/0.0.1/my_app.tar.gz
==> Updating tarball
==> Tarball updated!
==> Release successfully built!
You can run it in one of the following ways:
Interactive: _build/prod/rel/my_app/bin/my_app console
Foreground: _build/prod/rel/my_app/bin/my_app foreground
Daemon: _build/prod/rel/my_app/bin/my_app start
```
</details>
### Description of issue
- What are the expected results?
I should be able to run my custom task.
- What OS, Erlang/Elixir versions are you seeing this issue on?
Linux (Debian container), Elixir 1.6.6, Erlang/OTP 21.
- If possible, also provide your `rel/config.exs`, as it is often
my first troubleshooting question, and you'll save us both time :)
```
Path.join(["rel", "plugins", "*.exs"])
|> Path.wildcard()
|> Enum.map(&Code.eval_file(&1))
use Mix.Releases.Config,
default_release: :default,
default_environment: Mix.env()
environment :dev do
set dev_mode: true
set include_erts: false
set cookie: :"REDACTED"
end
environment :prod do
set include_erts: true
set include_src: false
set cookie: :"won't be used, we set it via a custom vm.args file (rel/custom.vm.args)"
end
release :media_provider do
set vm_args: "rel/custom.vm.args"
set version: current_version(:media_provider)
set applications: [
:runtime_tools
]
set commands: [
"migrate_up": "rel/commands/migrate_up.sh",
"migrate_down": "rel/commands/migrate_down.sh"
]
end
```
```
$ cat rel/custom.vm.args
-name <%= release_name %>@${POD_IP}
-setcookie ${ERLANG_COOKIE}
-smp auto
``` | True | Custom tasks fail with Erlang/OTP 21 (nonexistent `no_dot_erlang.boot` file) - ### Steps to reproduce
After building a release with the new Elixir 1.6.6 and Erlang/OTP 21, I'm unable to run custom release tasks.
N.B: this didn't happened with the previous Erlang/OTP 20.1. The application still runs OK (e.g. `console`, `foreground`, etc.)
I get the following error:
```
root@3411ff09020c:~/my_app/_build/prod/rel/my_app/bin# ./my_app command Elixir.MyApp.ReleaseTasks migrate_up
init terminating in do_boot ({cannot get bootfile,no_dot_erlang.boot})
Crash dump is being written to: erl_crash.dump...done
```
This is the `bin` folder content:
```
root@3411ff09020c:~/my_app/_build/prod/rel/my_app/bin# ll
total 112
drwxr-xr-x 2 root root 4096 Jun 21 12:41 .
drwxr-xr-x 7 root root 4096 Jun 21 11:13 ..
-rwxrwxrwx 1 root root 794 Jun 21 11:13 my_app
-rwxrwxrwx 1 root root 334 Jun 21 11:13 my_app.bat
-rwxrwxrwx 1 root root 2049 Jun 21 11:13 my_app_loader.sh
-rw-r--r-- 1 root root 6906 Jun 21 11:13 nodetool
-rw-r--r-- 1 root root 10835 Jun 21 11:13 release_utils.escript
-rw-r--r-- 1 root root 20794 Jun 21 11:13 start_clean.boot
```
If I copy the `start_clean.boot` to `no_dot_erlang.boot`, everything works as expected.
Maybe Erlang/OTP 21 changed the name of the `.boot` file it generates?
### Verbose Logs
<details>
```
==> Loading configuration..
==> Assembling release..
==> Building release my_app:0.0.1 using environment prod
==> One or more direct or transitive dependencies are missing from
:applications or :included_applications, they will not be included
in the release:
:parse_trans
This can cause your application to fail at runtime. If you are sure
that this is not an issue, you may ignore this warning.
==> Discovered applications:
poolboy-1.5.1
from: _build/prod/lib/poolboy
applications:
:kernel
:stdlib
includes: none
ecto-2.2.10
from: _build/prod/lib/ecto
applications:
:kernel
:stdlib
:elixir
:logger
:decimal
:poolboy
:crypto
includes: none
phoenix_ecto-3.3.0
from: _build/prod/lib/phoenix_ecto
applications:
:kernel
:stdlib
:elixir
:logger
:ecto
:plug
includes: none
distillery-1.5.2
from: _build/prod/lib/distillery
applications:
:kernel
:stdlib
:elixir
includes: none
decimal-1.5.0
from: _build/prod/lib/decimal
applications:
:kernel
:stdlib
:elixir
includes: none
connection-1.0.4
from: _build/prod/lib/connection
applications:
:kernel
:stdlib
:elixir
includes: none
db_connection-1.1.3
from: _build/prod/lib/db_connection
applications:
:kernel
:stdlib
:elixir
:logger
:connection
includes: none
postgrex-0.13.5
from: _build/prod/lib/postgrex
applications:
:kernel
:stdlib
:elixir
:logger
:db_connection
:decimal
:crypto
includes: none
eex-1.6.6
from: /elixir/bin/../lib/eex
applications:
:kernel
:stdlib
:elixir
includes: none
mime-1.2.0
from: _build/prod/lib/mime
applications:
:kernel
:stdlib
:elixir
includes: none
plug-1.5.1
from: _build/prod/lib/plug
applications:
:kernel
:stdlib
:elixir
:crypto
:logger
:mime
includes: none
phoenix-1.3.2
from: _build/prod/lib/phoenix
applications:
:kernel
:stdlib
:elixir
:plug
:poison
:logger
:eex
:phoenix_pubsub
:crypto
includes: none
ex_statsd-0.5.3
from: _build/prod/lib/ex_statsd
applications:
:kernel
:stdlib
:elixir
includes: none
cowlib-1.0.2
from: _build/prod/lib/cowlib
applications:
:kernel
:stdlib
:crypto
includes: none
ranch-1.3.2
from: _build/prod/lib/ranch
applications:
:kernel
:stdlib
:ssl
includes: none
cowboy-1.1.2
from: _build/prod/lib/cowboy
applications:
:kernel
:stdlib
:ranch
:cowlib
:crypto
includes: none
phoenix_pubsub-1.0.2
from: _build/prod/lib/phoenix_pubsub
applications:
:kernel
:stdlib
:elixir
:logger
:crypto
includes: none
ex_aws_kms-2.0.0
from: _build/prod/lib/ex_aws_kms
applications:
:kernel
:stdlib
:elixir
:logger
:ex_aws
includes: none
ex_aws_s3-2.0.0
from: _build/prod/lib/ex_aws_s3
applications:
:kernel
:stdlib
:elixir
:logger
:ex_aws
includes: none
ex_aws-2.0.2
from: _build/prod/lib/ex_aws
applications:
:kernel
:stdlib
:elixir
:logger
:crypto
includes: none
metrics-1.0.1
from: _build/prod/lib/metrics
applications:
:kernel
:stdlib
includes: none
ssl_verify_fun-1.1.1
from: _build/prod/lib/ssl_verify_fun
applications:
:kernel
:stdlib
:ssl
includes: none
certifi-2.3.1
from: _build/prod/lib/certifi
applications:
:kernel
:stdlib
includes: none
mimerl-1.0.2
from: _build/prod/lib/mimerl
applications:
:kernel
:stdlib
includes: none
unicode_util_compat-0.3.1
from: _build/prod/lib/unicode_util_compat
applications:
:kernel
:stdlib
includes: none
idna-5.1.1
from: _build/prod/lib/idna
applications:
:kernel
:stdlib
:unicode_util_compat
includes: none
ssl-9.0
from: /usr/local/lib/erlang/lib/ssl-9.0
applications:
:crypto
:public_key
:kernel
:stdlib
includes: none
public_key-1.6
from: /usr/local/lib/erlang/lib/public_key-1.6
applications:
:asn1
:crypto
:kernel
:stdlib
includes: none
asn1-5.0.6
from: /usr/local/lib/erlang/lib/asn1-5.0.6
applications:
:kernel
:stdlib
includes: none
crypto-4.3
from: /usr/local/lib/erlang/lib/crypto-4.3
applications:
:kernel
:stdlib
includes: none
hackney-1.12.1
from: _build/prod/lib/hackney
applications:
:kernel
:stdlib
:crypto
:asn1
:public_key
:ssl
:idna
:mimerl
:certifi
:ssl_verify_fun
:metrics
includes: none
poison-3.1.0
from: _build/prod/lib/poison
applications:
:kernel
:stdlib
:elixir
includes: none
gettext-0.15.0
from: _build/prod/lib/gettext
applications:
:kernel
:stdlib
:elixir
:logger
includes: none
runtime_tools-1.13
from: /usr/local/lib/erlang/lib/runtime_tools-1.13
applications:
:kernel
:stdlib
includes: none
logger-1.6.6
from: /elixir/bin/../lib/logger
applications:
:kernel
:stdlib
:elixir
includes: none
compiler-7.2
from: /usr/local/lib/erlang/lib/compiler-7.2
applications:
:kernel
:stdlib
includes: none
elixir-1.6.6
from: /elixir/bin/../lib/elixir
applications:
:kernel
:stdlib
:compiler
includes: none
stdlib-3.5
from: /usr/local/lib/erlang/lib/stdlib-3.5
applications:
:kernel
includes: none
kernel-6.0
from: /usr/local/lib/erlang/lib/kernel-6.0
applications: none
includes: none
my_app-0.0.1
from: _build/prod/lib/my_app
applications:
:kernel
:stdlib
:elixir
:logger
:runtime_tools
:gettext
:poison
:hackney
:ex_aws
:ex_aws_s3
:ex_aws_kms
:phoenix_pubsub
:cowboy
:ex_statsd
:phoenix
:postgrex
:distillery
:phoenix_ecto
includes: none
iex-1.6.6
from: /elixir/bin/../lib/iex
applications:
:kernel
:stdlib
:elixir
includes: none
sasl-3.2
from: /usr/local/lib/erlang/lib/sasl-3.2
applications:
:kernel
:stdlib
includes: none
==> Generated overlay vars:
release_name=:my_app
release_version="0.0.1"
is_upgrade=false
upgrade_from=:latest
dev_mode=false
include_erts=true
include_src=false
include_system_libs=true
erl_opts=""
run_erl_env=""
erts_vsn="10.0"
output_dir="_build/prod/rel/my_app"
==> Copying applications to _build/prod/rel/my_app
==> Generating nodetool
==> Generating start_erl.data
==> Generating vm.args from rel/custom.vm.args
==> Generating sys.config from config/config.exs
==> Including ERTS 10.0 from /usr/local/lib/erlang/erts-10.0
==> Generating boot script
==> Generating RELEASES
==> Generating start_clean.boot
==> Applying overlays
==> Applying mkdir overlay
dst: releases/0.0.1/hooks
==> Applying mkdir overlay
dst: releases/0.0.1/hooks/pre_configure.d
==> Applying mkdir overlay
dst: releases/0.0.1/hooks/post_configure.d
==> Applying mkdir overlay
dst: releases/0.0.1/hooks/pre_start.d
==> Applying mkdir overlay
dst: releases/0.0.1/hooks/post_start.d
==> Applying mkdir overlay
dst: releases/0.0.1/hooks/pre_stop.d
==> Applying mkdir overlay
dst: releases/0.0.1/hooks/post_stop.d
==> Applying mkdir overlay
dst: releases/0.0.1/hooks/pre_upgrade.d
==> Applying mkdir overlay
dst: releases/0.0.1/hooks/post_upgrade.d
==> Applying copy overlay
src: _build/prod/lib/distillery/priv/libexec
dst: releases/0.0.1/libexec
==> Applying mkdir overlay
dst: releases/0.0.1/commands
==> Applying copy overlay
src: rel/commands/migrate_up.sh
dst: releases/0.0.1/commands/migrate_up.sh
==> Applying copy overlay
src: rel/commands/migrate_down.sh
dst: releases/0.0.1/commands/migrate_down.sh
==> Packaging release..
==> Archiving my_app-0.0.1
==> Writing tarball to _build/prod/rel/my_app/releases/0.0.1/my_app.tar.gz
==> Updating tarball
==> Tarball updated!
==> Release successfully built!
You can run it in one of the following ways:
Interactive: _build/prod/rel/my_app/bin/my_app console
Foreground: _build/prod/rel/my_app/bin/my_app foreground
Daemon: _build/prod/rel/my_app/bin/my_app start
```
</details>
### Description of issue
- What are the expected results?
I should be able to run my custom task.
- What OS, Erlang/Elixir versions are you seeing this issue on?
Linux (Debian container), Elixir 1.6.6, Erlang/OTP 21.
- If possible, also provide your `rel/config.exs`, as it is often
my first troubleshooting question, and you'll save us both time :)
```
Path.join(["rel", "plugins", "*.exs"])
|> Path.wildcard()
|> Enum.map(&Code.eval_file(&1))
use Mix.Releases.Config,
default_release: :default,
default_environment: Mix.env()
environment :dev do
set dev_mode: true
set include_erts: false
set cookie: :"REDACTED"
end
environment :prod do
set include_erts: true
set include_src: false
set cookie: :"won't be used, we set it via a custom vm.args file (rel/custom.vm.args)"
end
release :media_provider do
set vm_args: "rel/custom.vm.args"
set version: current_version(:media_provider)
set applications: [
:runtime_tools
]
set commands: [
"migrate_up": "rel/commands/migrate_up.sh",
"migrate_down": "rel/commands/migrate_down.sh"
]
end
```
```
$ cat rel/custom.vm.args
-name <%= release_name %>@${POD_IP}
-setcookie ${ERLANG_COOKIE}
-smp auto
``` | comp | custom tasks fail with erlang otp nonexistent no dot erlang boot file steps to reproduce after building a release with the new elixir and erlang otp i m unable to run custom release tasks n b this didn t happened with the previous erlang otp the application still runs ok e g console foreground etc i get the following error root my app build prod rel my app bin my app command elixir myapp releasetasks migrate up init terminating in do boot cannot get bootfile no dot erlang boot crash dump is being written to erl crash dump done this is the bin folder content root my app build prod rel my app bin ll total drwxr xr x root root jun drwxr xr x root root jun rwxrwxrwx root root jun my app rwxrwxrwx root root jun my app bat rwxrwxrwx root root jun my app loader sh rw r r root root jun nodetool rw r r root root jun release utils escript rw r r root root jun start clean boot if i copy the start clean boot to no dot erlang boot everything works as expected maybe erlang otp changed the name of the boot file it generates verbose logs loading configuration assembling release building release my app using environment prod one or more direct or transitive dependencies are missing from applications or included applications they will not be included in the release parse trans this can cause your application to fail at runtime if you are sure that this is not an issue you may ignore this warning discovered applications poolboy from build prod lib poolboy applications kernel stdlib includes none ecto from build prod lib ecto applications kernel stdlib elixir logger decimal poolboy crypto includes none phoenix ecto from build prod lib phoenix ecto applications kernel stdlib elixir logger ecto plug includes none distillery from build prod lib distillery applications kernel stdlib elixir includes none decimal from build prod lib decimal applications kernel stdlib elixir includes none connection from build prod lib connection applications kernel stdlib elixir includes none db connection from build prod lib db connection applications kernel stdlib elixir logger connection includes none postgrex from build prod lib postgrex applications kernel stdlib elixir logger db connection decimal crypto includes none eex from elixir bin lib eex applications kernel stdlib elixir includes none mime from build prod lib mime applications kernel stdlib elixir includes none plug from build prod lib plug applications kernel stdlib elixir crypto logger mime includes none phoenix from build prod lib phoenix applications kernel stdlib elixir plug poison logger eex phoenix pubsub crypto includes none ex statsd from build prod lib ex statsd applications kernel stdlib elixir includes none cowlib from build prod lib cowlib applications kernel stdlib crypto includes none ranch from build prod lib ranch applications kernel stdlib ssl includes none cowboy from build prod lib cowboy applications kernel stdlib ranch cowlib crypto includes none phoenix pubsub from build prod lib phoenix pubsub applications kernel stdlib elixir logger crypto includes none ex aws kms from build prod lib ex aws kms applications kernel stdlib elixir logger ex aws includes none ex aws from build prod lib ex aws applications kernel stdlib elixir logger ex aws includes none ex aws from build prod lib ex aws applications kernel stdlib elixir logger crypto includes none metrics from build prod lib metrics applications kernel stdlib includes none ssl verify fun from build prod lib ssl verify fun applications kernel stdlib ssl includes none certifi from build prod lib certifi applications kernel stdlib includes none mimerl from build prod lib mimerl applications kernel stdlib includes none unicode util compat from build prod lib unicode util compat applications kernel stdlib includes none idna from build prod lib idna applications kernel stdlib unicode util compat includes none ssl from usr local lib erlang lib ssl applications crypto public key kernel stdlib includes none public key from usr local lib erlang lib public key applications crypto kernel stdlib includes none from usr local lib erlang lib applications kernel stdlib includes none crypto from usr local lib erlang lib crypto applications kernel stdlib includes none hackney from build prod lib hackney applications kernel stdlib crypto public key ssl idna mimerl certifi ssl verify fun metrics includes none poison from build prod lib poison applications kernel stdlib elixir includes none gettext from build prod lib gettext applications kernel stdlib elixir logger includes none runtime tools from usr local lib erlang lib runtime tools applications kernel stdlib includes none logger from elixir bin lib logger applications kernel stdlib elixir includes none compiler from usr local lib erlang lib compiler applications kernel stdlib includes none elixir from elixir bin lib elixir applications kernel stdlib compiler includes none stdlib from usr local lib erlang lib stdlib applications kernel includes none kernel from usr local lib erlang lib kernel applications none includes none my app from build prod lib my app applications kernel stdlib elixir logger runtime tools gettext poison hackney ex aws ex aws ex aws kms phoenix pubsub cowboy ex statsd phoenix postgrex distillery phoenix ecto includes none iex from elixir bin lib iex applications kernel stdlib elixir includes none sasl from usr local lib erlang lib sasl applications kernel stdlib includes none generated overlay vars release name my app release version is upgrade false upgrade from latest dev mode false include erts true include src false include system libs true erl opts run erl env erts vsn output dir build prod rel my app copying applications to build prod rel my app generating nodetool generating start erl data generating vm args from rel custom vm args generating sys config from config config exs including erts from usr local lib erlang erts generating boot script generating releases generating start clean boot applying overlays applying mkdir overlay dst releases hooks applying mkdir overlay dst releases hooks pre configure d applying mkdir overlay dst releases hooks post configure d applying mkdir overlay dst releases hooks pre start d applying mkdir overlay dst releases hooks post start d applying mkdir overlay dst releases hooks pre stop d applying mkdir overlay dst releases hooks post stop d applying mkdir overlay dst releases hooks pre upgrade d applying mkdir overlay dst releases hooks post upgrade d applying copy overlay src build prod lib distillery priv libexec dst releases libexec applying mkdir overlay dst releases commands applying copy overlay src rel commands migrate up sh dst releases commands migrate up sh applying copy overlay src rel commands migrate down sh dst releases commands migrate down sh packaging release archiving my app writing tarball to build prod rel my app releases my app tar gz updating tarball tarball updated release successfully built you can run it in one of the following ways interactive build prod rel my app bin my app console foreground build prod rel my app bin my app foreground daemon build prod rel my app bin my app start description of issue what are the expected results i should be able to run my custom task what os erlang elixir versions are you seeing this issue on linux debian container elixir erlang otp if possible also provide your rel config exs as it is often my first troubleshooting question and you ll save us both time path join path wildcard enum map code eval file use mix releases config default release default default environment mix env environment dev do set dev mode true set include erts false set cookie redacted end environment prod do set include erts true set include src false set cookie won t be used we set it via a custom vm args file rel custom vm args end release media provider do set vm args rel custom vm args set version current version media provider set applications runtime tools set commands migrate up rel commands migrate up sh migrate down rel commands migrate down sh end cat rel custom vm args name pod ip setcookie erlang cookie smp auto | 1 |
10,605 | 12,512,748,733 | IssuesEvent | 2020-06-02 23:44:21 | svenhjol/Charm | https://api.github.com/repos/svenhjol/Charm | closed | Leather Armor doesn't become Invisible. | bug compatibility | When using a potion of invisibility, mobs can still detect the player. Leather armor does not become invisible as well. I am using the latest 1.14.4 version. | True | Leather Armor doesn't become Invisible. - When using a potion of invisibility, mobs can still detect the player. Leather armor does not become invisible as well. I am using the latest 1.14.4 version. | comp | leather armor doesn t become invisible when using a potion of invisibility mobs can still detect the player leather armor does not become invisible as well i am using the latest version | 1 |
683,625 | 23,389,183,601 | IssuesEvent | 2022-08-11 16:08:33 | insightsengineering/tern.mmrm | https://api.github.com/repos/insightsengineering/tern.mmrm | closed | [UAT] Test fitting of rank-deficient models | sme high priority | UAT the option `accept_singular` in `fit_mmrm()` which allows to estimate rank-deficient models (similar as `lm()` and `gls()` do) by omitting singular coefficients.
To do:
- [x] Use pre-release branch on enableR (see Dinakar's instructions)
- [x] See `?fit_mmrm` for description of the `accept_singular` and check if that is clear
- [ ] Play around with the argument and results and see if that works - will need very small data sets, or artificially introduced collinear columns in the formula, to see the effect. | 1.0 | [UAT] Test fitting of rank-deficient models - UAT the option `accept_singular` in `fit_mmrm()` which allows to estimate rank-deficient models (similar as `lm()` and `gls()` do) by omitting singular coefficients.
To do:
- [x] Use pre-release branch on enableR (see Dinakar's instructions)
- [x] See `?fit_mmrm` for description of the `accept_singular` and check if that is clear
- [ ] Play around with the argument and results and see if that works - will need very small data sets, or artificially introduced collinear columns in the formula, to see the effect. | non_comp | test fitting of rank deficient models uat the option accept singular in fit mmrm which allows to estimate rank deficient models similar as lm and gls do by omitting singular coefficients to do use pre release branch on enabler see dinakar s instructions see fit mmrm for description of the accept singular and check if that is clear play around with the argument and results and see if that works will need very small data sets or artificially introduced collinear columns in the formula to see the effect | 0 |
65,911 | 6,978,332,766 | IssuesEvent | 2017-12-12 17:11:17 | restrictcontentpro/restrict-content-pro | https://api.github.com/repos/restrictcontentpro/restrict-content-pro | closed | Undefined index | bug has PR needs testing | While using shortcodes, I have got undefined index `free_message` message. #1541 | 1.0 | Undefined index - While using shortcodes, I have got undefined index `free_message` message. #1541 | non_comp | undefined index while using shortcodes i have got undefined index free message message | 0 |
6,372 | 8,683,752,754 | IssuesEvent | 2018-12-02 20:51:09 | metarhia/impress | https://api.github.com/repos/metarhia/impress | opened | Optimize stack logging | compatibility optimization performance | See `lib/stacj.js` to rewrite `impress.shortenStack` without `RegExp` (it's used to remove long names to the current folder and paths to the modules in `node_modules`) | True | Optimize stack logging - See `lib/stacj.js` to rewrite `impress.shortenStack` without `RegExp` (it's used to remove long names to the current folder and paths to the modules in `node_modules`) | comp | optimize stack logging see lib stacj js to rewrite impress shortenstack without regexp it s used to remove long names to the current folder and paths to the modules in node modules | 1 |
5,044 | 7,633,690,599 | IssuesEvent | 2018-05-06 08:55:55 | MeGysssTaa/ReflexIssueTracker | https://api.github.com/repos/MeGysssTaa/ReflexIssueTracker | closed | Reflex bot pushing because it cant go below your y level | Bug Compatibility Fixed | By creating this issue on the Reflex Issue Tracker, I agree that I have fully and accurately read and understood everything stated in it's [Guide on this page](https://goo.gl/Sjdqvb). I understand and agree that this issue can be ignored, closed or labeled "Invalid" without any further comments from Reflex maintainers if this issue doesn't match [the Guide](https://goo.gl/Sjdqvb) entirely and properly.
I know and understand which cheats does Reflex check for, and which it doesn't. I clearly understand that there are no any movement checks and similar at the moment. I confirm that I am not running any possibly incompatible plugins or mods and my server core is either Spigot or PaperSpigot. I confirm that I will actively cooperate with Reflex maintainers in order to solve this issue as soon as possible.
By erasing this text I understand that this issue will most likely be deleted or ignored.
## General
**ISSUE TYPE**
Bypass／false positive／bug／console error／feature request／question
＞ bug
https://www.youtube.com/watch?v=EaTTKfqa3go&feature=youtu.be
This video shows 3 minutes of me getting harassed by bots, for the simple reason that the bot is unable to go below your y level, meaning that if you look straight up the bot will be shaking inside your body, constantly randomly pushing you. All that has it be changed is to allow the bot to go below the players y level, and then it will never be able to push you since when you look up it will be under you instead of being in your body. | True | Reflex bot pushing because it cant go below your y level - By creating this issue on the Reflex Issue Tracker, I agree that I have fully and accurately read and understood everything stated in it's [Guide on this page](https://goo.gl/Sjdqvb). I understand and agree that this issue can be ignored, closed or labeled "Invalid" without any further comments from Reflex maintainers if this issue doesn't match [the Guide](https://goo.gl/Sjdqvb) entirely and properly.
I know and understand which cheats does Reflex check for, and which it doesn't. I clearly understand that there are no any movement checks and similar at the moment. I confirm that I am not running any possibly incompatible plugins or mods and my server core is either Spigot or PaperSpigot. I confirm that I will actively cooperate with Reflex maintainers in order to solve this issue as soon as possible.
By erasing this text I understand that this issue will most likely be deleted or ignored.
## General
**ISSUE TYPE**
Bypass／false positive／bug／console error／feature request／question
＞ bug
https://www.youtube.com/watch?v=EaTTKfqa3go&feature=youtu.be
This video shows 3 minutes of me getting harassed by bots, for the simple reason that the bot is unable to go below your y level, meaning that if you look straight up the bot will be shaking inside your body, constantly randomly pushing you. All that has it be changed is to allow the bot to go below the players y level, and then it will never be able to push you since when you look up it will be under you instead of being in your body. | comp | reflex bot pushing because it cant go below your y level by creating this issue on the reflex issue tracker i agree that i have fully and accurately read and understood everything stated in it s i understand and agree that this issue can be ignored closed or labeled invalid without any further comments from reflex maintainers if this issue doesn t match entirely and properly i know and understand which cheats does reflex check for and which it doesn t i clearly understand that there are no any movement checks and similar at the moment i confirm that i am not running any possibly incompatible plugins or mods and my server core is either spigot or paperspigot i confirm that i will actively cooperate with reflex maintainers in order to solve this issue as soon as possible by erasing this text i understand that this issue will most likely be deleted or ignored general issue type bypass／false positive／bug／console error／feature request／question ＞ bug this video shows minutes of me getting harassed by bots for the simple reason that the bot is unable to go below your y level meaning that if you look straight up the bot will be shaking inside your body constantly randomly pushing you all that has it be changed is to allow the bot to go below the players y level and then it will never be able to push you since when you look up it will be under you instead of being in your body | 1 |
17,724 | 24,462,761,023 | IssuesEvent | 2022-10-07 12:39:55 | jOOQ/jOOQ | https://api.github.com/repos/jOOQ/jOOQ | closed | WindowSpecification::$partitionBy should return UnmodifiableList<? extends GroupField> | T: Enhancement C: Functionality P: Medium R: Fixed T: Incompatible change E: All Editions | The `QOM` API and `DSL` API should support `GroupField` whenever a `PARTITION BY` clause is supported, allowing for using `Table<?>` expressions, which can be used as `GroupField` since jOOQ 3.16: https://github.com/jOOQ/jOOQ/issues/11834
An example:
```java
ctx.select(count().over(partitionBy(T_BOOK_STORE)))
.from(T_BOOK_TO_BOOK_STORE)
.join(T_BOOK_STORE).on(...)
.orderBy(1)
.fetch();
```
Instead of:
```java
ctx.select(count().over(partitionBy(T_BOOK_STORE.COL1, T_BOOK_STORE.COL2, ...)))
.from(T_BOOK_TO_BOOK_STORE)
.join(T_BOOK_STORE).on(...)
.orderBy(1)
.fetch();
```
This is a backwards incompatible change in the experimental `QOM` API. The DSL API change is source compatible. | True | WindowSpecification::$partitionBy should return UnmodifiableList<? extends GroupField> - The `QOM` API and `DSL` API should support `GroupField` whenever a `PARTITION BY` clause is supported, allowing for using `Table<?>` expressions, which can be used as `GroupField` since jOOQ 3.16: https://github.com/jOOQ/jOOQ/issues/11834
An example:
```java
ctx.select(count().over(partitionBy(T_BOOK_STORE)))
.from(T_BOOK_TO_BOOK_STORE)
.join(T_BOOK_STORE).on(...)
.orderBy(1)
.fetch();
```
Instead of:
```java
ctx.select(count().over(partitionBy(T_BOOK_STORE.COL1, T_BOOK_STORE.COL2, ...)))
.from(T_BOOK_TO_BOOK_STORE)
.join(T_BOOK_STORE).on(...)
.orderBy(1)
.fetch();
```
This is a backwards incompatible change in the experimental `QOM` API. The DSL API change is source compatible. | comp | windowspecification partitionby should return unmodifiablelist the qom api and dsl api should support groupfield whenever a partition by clause is supported allowing for using table expressions which can be used as groupfield since jooq an example java ctx select count over partitionby t book store from t book to book store join t book store on orderby fetch instead of java ctx select count over partitionby t book store t book store from t book to book store join t book store on orderby fetch this is a backwards incompatible change in the experimental qom api the dsl api change is source compatible | 1 |
86,506 | 10,508,552,729 | IssuesEvent | 2019-09-27 08:55:09 | bounswe/bounswe2019group5 | https://api.github.com/repos/bounswe/bounswe2019group5 | closed | API: Brief description of software (Wiki) | Effort: Medium Priority: Medium Status: Available Type: Documentation | Creating a wiki page called API Description and typing the functionalities etc. | 1.0 | API: Brief description of software (Wiki) - Creating a wiki page called API Description and typing the functionalities etc. | non_comp | api brief description of software wiki creating a wiki page called api description and typing the functionalities etc | 0 |
434,629 | 30,459,142,459 | IssuesEvent | 2023-07-17 04:44:57 | XtensibleBinaryFormat/XBF | https://api.github.com/repos/XtensibleBinaryFormat/XBF | closed | Should structs be allowed to have duplicate field names? | bug documentation | My assumption here is no, however it is not explicitly defined that way in the specification. We need to define how collisions should be handled, if at all, as it will determine how #53 gets implemented. | 1.0 | Should structs be allowed to have duplicate field names? - My assumption here is no, however it is not explicitly defined that way in the specification. We need to define how collisions should be handled, if at all, as it will determine how #53 gets implemented. | non_comp | should structs be allowed to have duplicate field names my assumption here is no however it is not explicitly defined that way in the specification we need to define how collisions should be handled if at all as it will determine how gets implemented | 0 |
5,502 | 7,959,717,784 | IssuesEvent | 2018-07-13 02:41:13 | sass/sass | https://api.github.com/repos/sass/sass | closed | wrong number of arguments (1 for 2) for `mix' | CSS Compatibility | I cannot compile (bundle exec rake assets:precompile) this code
``` scss
.reveal.tileflip .slides section.present {
-webkit-filter: custom( url(shaders/tile-flip.vs) mix(url(shaders/tile-flip.fs) multiply source-atop), 10 10 border-box detached, transform perspective(1000) scale(1) rotateX(0deg) rotateY(0deg) rotateZ(0deg), amount 0, randomness 0, flipAxis 0 1 0, tileOutline 1 );
}
```
The code is part of reveal.js
| True | wrong number of arguments (1 for 2) for `mix' - I cannot compile (bundle exec rake assets:precompile) this code
``` scss
.reveal.tileflip .slides section.present {
-webkit-filter: custom( url(shaders/tile-flip.vs) mix(url(shaders/tile-flip.fs) multiply source-atop), 10 10 border-box detached, transform perspective(1000) scale(1) rotateX(0deg) rotateY(0deg) rotateZ(0deg), amount 0, randomness 0, flipAxis 0 1 0, tileOutline 1 );
}
```
The code is part of reveal.js
| comp | wrong number of arguments for for mix i cannot compile bundle exec rake assets precompile this code scss reveal tileflip slides section present webkit filter custom url shaders tile flip vs mix url shaders tile flip fs multiply source atop border box detached transform perspective scale rotatex rotatey rotatez amount randomness flipaxis tileoutline the code is part of reveal js | 1 |
8,163 | 10,256,273,190 | IssuesEvent | 2019-08-21 17:16:17 | Johni0702/BetterPortals | https://api.github.com/repos/Johni0702/BetterPortals | closed | Player Model is Invisible in 3rd Person when Both Pixelmon and BetterPortals are Installed | bug compatibility | When both Better Portals and Pixelmon Reforged are installed, the player is invisible in the 3rd person views. | True | Player Model is Invisible in 3rd Person when Both Pixelmon and BetterPortals are Installed - When both Better Portals and Pixelmon Reforged are installed, the player is invisible in the 3rd person views. | comp | player model is invisible in person when both pixelmon and betterportals are installed when both better portals and pixelmon reforged are installed the player is invisible in the person views | 1 |
14,361 | 17,330,060,703 | IssuesEvent | 2021-07-28 00:02:35 | OroArmor/Netherite-Plus-Mod | https://api.github.com/repos/OroArmor/Netherite-Plus-Mod | closed | Add compatibility for Gilded Netherite | Compatibility | The mod is Gilded Netherite, created by Azriel_Taylor.
When I have both of these mods installed, I get a crash on startup. I don't have this issue when only one of the two mods is installed, so I assume that it's a compatibility issue. I think that these two mods would go together really nicely, so compatibility would be awesome if at all possible!
Thank you for your time and hard work on the mod so far, have a great day :)
| True | Add compatibility for Gilded Netherite - The mod is Gilded Netherite, created by Azriel_Taylor.
When I have both of these mods installed, I get a crash on startup. I don't have this issue when only one of the two mods is installed, so I assume that it's a compatibility issue. I think that these two mods would go together really nicely, so compatibility would be awesome if at all possible!
Thank you for your time and hard work on the mod so far, have a great day :)
| comp | add compatibility for gilded netherite the mod is gilded netherite created by azriel taylor when i have both of these mods installed i get a crash on startup i don t have this issue when only one of the two mods is installed so i assume that it s a compatibility issue i think that these two mods would go together really nicely so compatibility would be awesome if at all possible thank you for your time and hard work on the mod so far have a great day | 1 |
235,934 | 18,065,550,319 | IssuesEvent | 2021-09-20 18:41:37 | airbytehq/airbyte | https://api.github.com/repos/airbytehq/airbyte | opened | Connector Development: add storybook into docs | area/documentation type/enhancement | ### Tell us about the documentation you'd like us to add or update.
Transfer this [doc](https://github.com/airbytehq/airbyte/blob/master/airbyte-webapp/docs/HowTo-ConnectionSpecification.md) to the connector development section.
### If applicable, add links to the relevant docs that should be updated
- [Link to relevant docs page](https://docs.airbyte.io) | 1.0 | Connector Development: add storybook into docs - ### Tell us about the documentation you'd like us to add or update.
Transfer this [doc](https://github.com/airbytehq/airbyte/blob/master/airbyte-webapp/docs/HowTo-ConnectionSpecification.md) to the connector development section.
### If applicable, add links to the relevant docs that should be updated
- [Link to relevant docs page](https://docs.airbyte.io) | non_comp | connector development add storybook into docs tell us about the documentation you d like us to add or update transfer this to the connector development section if applicable add links to the relevant docs that should be updated | 0 |
14,329 | 17,244,118,834 | IssuesEvent | 2021-07-21 05:49:02 | spoorn/sodium-forge | https://api.github.com/repos/spoorn/sodium-forge | closed | Sodium + Malum Crash | compatibility crash | ### Reproduction Steps
Install malum and sodium
equip crude scythe
kill mob
crystal drops
client crash
Disabling "Use Vertex Array Objects" and "Use Compact Vertex Format" seems to solve the issue though the original crystals which caused the client crash still seem to be there and unable to be picked up but client no longer crashes.
a 3rd player crashed even with these options disabled. requiring them to outright remove sodium
https://pastebin.com/nbyF7vqa
| True | Sodium + Malum Crash - ### Reproduction Steps
Install malum and sodium
equip crude scythe
kill mob
crystal drops
client crash
Disabling "Use Vertex Array Objects" and "Use Compact Vertex Format" seems to solve the issue though the original crystals which caused the client crash still seem to be there and unable to be picked up but client no longer crashes.
a 3rd player crashed even with these options disabled. requiring them to outright remove sodium
https://pastebin.com/nbyF7vqa
| comp | sodium malum crash reproduction steps install malum and sodium equip crude scythe kill mob crystal drops client crash disabling use vertex array objects and use compact vertex format seems to solve the issue though the original crystals which caused the client crash still seem to be there and unable to be picked up but client no longer crashes a player crashed even with these options disabled requiring them to outright remove sodium | 1 |
14,225 | 17,104,438,422 | IssuesEvent | 2021-07-09 15:34:15 | rust-lang/rust | https://api.github.com/repos/rust-lang/rust | closed | illegal_floating_point_literal_pattern warns twice | A-lint C-bug C-future-compatibility | With the following code [(playground)](https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=3d8d20c7f65bc6699b47419f26e8095f):
```rust
fn main() {
let x = 42.0;
match x {
5.0 => {}
_ => {}
}
}
```
I expected to see one warning.
Instead, this happened:
```
warning: floating-point types cannot be used in patterns
--> src/main.rs:5:9
|
5 | 5.0 => {}
| ^^^
|
= note: `#[warn(illegal_floating_point_literal_pattern)]` on by default
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #41620 <https://github.com/rust-lang/rust/issues/41620>
warning: floating-point types cannot be used in patterns
--> src/main.rs:5:9
|
5 | 5.0 => {}
| ^^^
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #41620 <https://github.com/rust-lang/rust/issues/41620>
warning: 2 warnings emitted
```
### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->
```
1.55.0-nightly
(2021-06-23 5a7834050f3a0ebcd117)
```
| True | illegal_floating_point_literal_pattern warns twice - With the following code [(playground)](https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=3d8d20c7f65bc6699b47419f26e8095f):
```rust
fn main() {
let x = 42.0;
match x {
5.0 => {}
_ => {}
}
}
```
I expected to see one warning.
Instead, this happened:
```
warning: floating-point types cannot be used in patterns
--> src/main.rs:5:9
|
5 | 5.0 => {}
| ^^^
|
= note: `#[warn(illegal_floating_point_literal_pattern)]` on by default
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #41620 <https://github.com/rust-lang/rust/issues/41620>
warning: floating-point types cannot be used in patterns
--> src/main.rs:5:9
|
5 | 5.0 => {}
| ^^^
|
= warning: this was previously accepted by the compiler but is being phased out; it will become a hard error in a future release!
= note: for more information, see issue #41620 <https://github.com/rust-lang/rust/issues/41620>
warning: 2 warnings emitted
```
### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->
```
1.55.0-nightly
(2021-06-23 5a7834050f3a0ebcd117)
```
| comp | illegal floating point literal pattern warns twice with the following code rust fn main let x match x i expected to see one warning instead this happened warning floating point types cannot be used in patterns src main rs note on by default warning this was previously accepted by the compiler but is being phased out it will become a hard error in a future release note for more information see issue warning floating point types cannot be used in patterns src main rs warning this was previously accepted by the compiler but is being phased out it will become a hard error in a future release note for more information see issue warning warnings emitted meta if you re using the stable version of the compiler you should also check if the bug also exists in the beta or nightly versions nightly | 1 |
286,111 | 8,784,031,960 | IssuesEvent | 2018-12-20 08:35:27 | webcompat/web-bugs | https://api.github.com/repos/webcompat/web-bugs | closed | www.mundijuegos.com - video or audio doesn't play | browser-firefox priority-normal | <!-- @browser: Firefox 66.0 -->
<!-- @ua_header: Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:66.0) Gecko/20100101 Firefox/66.0 -->
<!-- @reported_with: desktop-reporter -->
**URL**: https://www.mundijuegos.com/juegos/juego.php?juego=21&sala=1
**Browser / Version**: Firefox 66.0
**Operating System**: Windows 8.1
**Tested Another Browser**: Yes
**Problem type**: Video or audio doesn't play
**Description**: BILAR
**Steps to Reproduce**:
[](https://webcompat.com/uploads/2018/12/2f426fb4-3986-45a0-8c5d-722087bf6844.jpeg)
<details>
<summary>Browser Configuration</summary>
<ul>
<li>mixed active content blocked: false</li><li>image.mem.shared: true</li><li>buildID: 20181218095120</li><li>tracking content blocked: false</li><li>gfx.webrender.blob-images: true</li><li>hasTouchScreen: false</li><li>mixed passive content blocked: false</li><li>gfx.webrender.enabled: false</li><li>gfx.webrender.all: false</li><li>channel: nightly</li>
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_ | 1.0 | www.mundijuegos.com - video or audio doesn't play - <!-- @browser: Firefox 66.0 -->
<!-- @ua_header: Mozilla/5.0 (Windows NT 6.3; Win64; x64; rv:66.0) Gecko/20100101 Firefox/66.0 -->
<!-- @reported_with: desktop-reporter -->
**URL**: https://www.mundijuegos.com/juegos/juego.php?juego=21&sala=1
**Browser / Version**: Firefox 66.0
**Operating System**: Windows 8.1
**Tested Another Browser**: Yes
**Problem type**: Video or audio doesn't play
**Description**: BILAR
**Steps to Reproduce**:
[](https://webcompat.com/uploads/2018/12/2f426fb4-3986-45a0-8c5d-722087bf6844.jpeg)
<details>
<summary>Browser Configuration</summary>
<ul>
<li>mixed active content blocked: false</li><li>image.mem.shared: true</li><li>buildID: 20181218095120</li><li>tracking content blocked: false</li><li>gfx.webrender.blob-images: true</li><li>hasTouchScreen: false</li><li>mixed passive content blocked: false</li><li>gfx.webrender.enabled: false</li><li>gfx.webrender.all: false</li><li>channel: nightly</li>
</ul>
</details>
_From [webcompat.com](https://webcompat.com/) with ❤️_ | non_comp | video or audio doesn t play url browser version firefox operating system windows tested another browser yes problem type video or audio doesn t play description bilar steps to reproduce browser configuration mixed active content blocked false image mem shared true buildid tracking content blocked false gfx webrender blob images true hastouchscreen false mixed passive content blocked false gfx webrender enabled false gfx webrender all false channel nightly from with ❤️ | 0 |
281,945 | 24,439,478,738 | IssuesEvent | 2022-10-06 13:44:02 | eclipse/sumo | https://api.github.com/repos/eclipse/sumo | closed | crash in addBidiEdge | a:netconvert bug test needed | It may happen that the new edge e2 to add gets filtered away on ec.insert which deletes the edge object. Maybe we should change the code of ec.insert such that it either has a tri-state return value (added, ignored and filtered) and/or always (or never) deletes the edge it could not add. | 1.0 | crash in addBidiEdge - It may happen that the new edge e2 to add gets filtered away on ec.insert which deletes the edge object. Maybe we should change the code of ec.insert such that it either has a tri-state return value (added, ignored and filtered) and/or always (or never) deletes the edge it could not add. | non_comp | crash in addbidiedge it may happen that the new edge to add gets filtered away on ec insert which deletes the edge object maybe we should change the code of ec insert such that it either has a tri state return value added ignored and filtered and or always or never deletes the edge it could not add | 0 |
931 | 3,398,987,880 | IssuesEvent | 2015-12-02 08:32:19 | amazeui/amazeui | https://api.github.com/repos/amazeui/amazeui | closed | Bug：安卓手机手机QQ或者微信打开页面，文字溢出点点拦不住文字 | compatibility os-Android ua-wechat | 安卓手机手机QQ或者微信打开页面的时候，
有文字溢出... 但是多出的文字没有被隐藏住，还是展示出来了，栏目列表展示时，左文字 右日期时最明显 | True | Bug：安卓手机手机QQ或者微信打开页面，文字溢出点点拦不住文字 - 安卓手机手机QQ或者微信打开页面的时候，
有文字溢出... 但是多出的文字没有被隐藏住，还是展示出来了，栏目列表展示时，左文字 右日期时最明显 | comp | bug：安卓手机手机qq或者微信打开页面，文字溢出点点拦不住文字 安卓手机手机qq或者微信打开页面的时候， 有文字溢出 但是多出的文字没有被隐藏住，还是展示出来了，栏目列表展示时，左文字 右日期时最明显 | 1 |
11,354 | 13,300,407,978 | IssuesEvent | 2020-08-25 11:18:34 | dotnet/runtime | https://api.github.com/repos/dotnet/runtime | closed | After migration to .Net Core 3.1 for a given Cancellation Request test case ReadAsStringAsync() throws System.IO.IOException with message 'Error while copying content to a stream' | area-System.Net.Http needs more info tenet-compatibility | After migrating my solution from 2.2 to 3.1 I ended with a single test failing.
Test:
```C#
[Fact]
public async Task RequestCancellation_Test()
{
// Setup
...
var cancellationSource = new CancellationTokenSource();
var requestTask = Client.PostItemAsync(uri, data, cancellationSource.Token)
.EnsureSuccessStatusCodeWithMessage();
await Task.Delay(TimeSpan.FromMilliseconds(10));
cancellationSource.Cancel();
var exception = await Assert.ThrowsAsync<HttpRequestException> (() => requestTask);
Assert.Equal("StatusCode: BadRequest", exception.Message);
}
```
`EnsureSuccessStatusCodeWithMessage` is extension method where I use `ReadAsStringAsync`:
``` C#
public static async ValueTask<HttpResponseMessage> EnsureSuccessStatusCodeWithMessage(this HttpResponseMessage response)
{
if (!response.IsSuccessStatusCode)
{
var errorMessage = response.Content == null ? null : await
response.Content.ReadAsStringAsync();
if (string.IsNullOrEmpty(errorMessage))
{
errorMessage = $"StatusCode: {response.StatusCode}";
}
// Make sure to actually dispose the response.T
response.Dispose();
throw new HttpRequestException(errorMessage);
}
return response;
}
```
the `response.Content.ReadAsStringAsync();` throws `System.IO.IOException` with message `Error while copying content to a stream`
Btw, if I leave the request to finish (remove the cancellation part), I don't have issues with `ReadAsStringAsync()`
In the test I expect the error message to be empty and end up with `"StatusCode: BadRequest"`,
`ReadAsStringAsync` was returning empty string while I was at .Net Core 2.2
`ReadAsStringAsync` was coming from:
`Assembly netstandard, Version=2.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51`
now on Net Core 3.1 it comes from:
`Assembly System.Net.Http, Version=4.2.2.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a` | True | After migration to .Net Core 3.1 for a given Cancellation Request test case ReadAsStringAsync() throws System.IO.IOException with message 'Error while copying content to a stream' - After migrating my solution from 2.2 to 3.1 I ended with a single test failing.
Test:
```C#
[Fact]
public async Task RequestCancellation_Test()
{
// Setup
...
var cancellationSource = new CancellationTokenSource();
var requestTask = Client.PostItemAsync(uri, data, cancellationSource.Token)
.EnsureSuccessStatusCodeWithMessage();
await Task.Delay(TimeSpan.FromMilliseconds(10));
cancellationSource.Cancel();
var exception = await Assert.ThrowsAsync<HttpRequestException> (() => requestTask);
Assert.Equal("StatusCode: BadRequest", exception.Message);
}
```
`EnsureSuccessStatusCodeWithMessage` is extension method where I use `ReadAsStringAsync`:
``` C#
public static async ValueTask<HttpResponseMessage> EnsureSuccessStatusCodeWithMessage(this HttpResponseMessage response)
{
if (!response.IsSuccessStatusCode)
{
var errorMessage = response.Content == null ? null : await
response.Content.ReadAsStringAsync();
if (string.IsNullOrEmpty(errorMessage))
{
errorMessage = $"StatusCode: {response.StatusCode}";
}
// Make sure to actually dispose the response.T
response.Dispose();
throw new HttpRequestException(errorMessage);
}
return response;
}
```
the `response.Content.ReadAsStringAsync();` throws `System.IO.IOException` with message `Error while copying content to a stream`
Btw, if I leave the request to finish (remove the cancellation part), I don't have issues with `ReadAsStringAsync()`
In the test I expect the error message to be empty and end up with `"StatusCode: BadRequest"`,
`ReadAsStringAsync` was returning empty string while I was at .Net Core 2.2
`ReadAsStringAsync` was coming from:
`Assembly netstandard, Version=2.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51`
now on Net Core 3.1 it comes from:
`Assembly System.Net.Http, Version=4.2.2.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a` | comp | after migration to net core for a given cancellation request test case readasstringasync throws system io ioexception with message error while copying content to a stream after migrating my solution from to i ended with a single test failing test c public async task requestcancellation test setup var cancellationsource new cancellationtokensource var requesttask client postitemasync uri data cancellationsource token ensuresuccessstatuscodewithmessage await task delay timespan frommilliseconds cancellationsource cancel var exception await assert throwsasync requesttask assert equal statuscode badrequest exception message ensuresuccessstatuscodewithmessage is extension method where i use readasstringasync c public static async valuetask ensuresuccessstatuscodewithmessage this httpresponsemessage response if response issuccessstatuscode var errormessage response content null null await response content readasstringasync if string isnullorempty errormessage errormessage statuscode response statuscode make sure to actually dispose the response t response dispose throw new httprequestexception errormessage return response the response content readasstringasync throws system io ioexception with message error while copying content to a stream btw if i leave the request to finish remove the cancellation part i don t have issues with readasstringasync in the test i expect the error message to be empty and end up with statuscode badrequest readasstringasync was returning empty string while i was at net core readasstringasync was coming from assembly netstandard version culture neutral publickeytoken now on net core it comes from assembly system net http version culture neutral publickeytoken | 1 |
12,596 | 14,906,478,420 | IssuesEvent | 2021-01-22 00:41:38 | Foundry376/Mailspring | https://api.github.com/repos/Foundry376/Mailspring | closed | Can't get oauth token for gmail accounts | mailserver-incompatibility needs-reproduction | #### What is the behavior you're seeing?
Lost connection to all Gmail accounts
##### What email provider (Gmail, Exchange, etc.) are you trying to use?
gmail
##### What operating system are you using?
ubuntu
##### What version of Mailspring are you using?
1.7.6
tried authenticating, but the auth window also gets stuck
also can't add a new Gmail account
```
3203 [2020-05-01 12:20:31.082] [metadata] [info] Encountered error: {"debuginfo":"https://id.getmailspring.com/deltas/c8bfb684/head","key":"Timeout was reached","retryable":true,"what":"std::exception"}. Will retry in 300 sec.
3203 [2020-05-01 12:21:51.118] [background] [info] Fetching XOAuth2 access token from Gmail for c8bfb684
3203 [2020-05-01 12:22:11.170] [background] [info] Sleeping after exception: {"debuginfo":"https://www.googleapis.com/oauth2/v4/token","key":"Timeout was reached","retryable":true,"what":"std::exception"}
3203 [2020-05-01 12:24:11.170] [background] [info] Fetching XOAuth2 access token from Gmail for c8bfb684
3203 [2020-05-01 12:24:31.224] [background] [info] Sleeping after exception: {"debuginfo":"https://www.googleapis.com/oauth2/v4/token","key":"Timeout was reached","retryable":true,"what":"std::exception"}
3203 [2020-05-01 12:25:51.111] [metadata] [info] Encountered error: {"debuginfo":"https://id.getmailspring.com/deltas/c8bfb684/head","key":"Timeout was reached","retryable":true,"what":"std::exception"}. Will retry in 300 sec.
3203 [2020-05-01 12:26:31.224] [background] [info] Fetching XOAuth2 access token from Gmail for c8bfb684
3203 [2020-05-01 12:26:51.278] [background] [info] Sleeping after exception: {"debuginfo":"https://www.googleapis.com/oauth2/v4/token","key":"Timeout was reached","retryable":true,"what":"std::exception"}
``` | True | Can't get oauth token for gmail accounts - #### What is the behavior you're seeing?
Lost connection to all Gmail accounts
##### What email provider (Gmail, Exchange, etc.) are you trying to use?
gmail
##### What operating system are you using?
ubuntu
##### What version of Mailspring are you using?
1.7.6
tried authenticating, but the auth window also gets stuck
also can't add a new Gmail account
```
3203 [2020-05-01 12:20:31.082] [metadata] [info] Encountered error: {"debuginfo":"https://id.getmailspring.com/deltas/c8bfb684/head","key":"Timeout was reached","retryable":true,"what":"std::exception"}. Will retry in 300 sec.
3203 [2020-05-01 12:21:51.118] [background] [info] Fetching XOAuth2 access token from Gmail for c8bfb684
3203 [2020-05-01 12:22:11.170] [background] [info] Sleeping after exception: {"debuginfo":"https://www.googleapis.com/oauth2/v4/token","key":"Timeout was reached","retryable":true,"what":"std::exception"}
3203 [2020-05-01 12:24:11.170] [background] [info] Fetching XOAuth2 access token from Gmail for c8bfb684
3203 [2020-05-01 12:24:31.224] [background] [info] Sleeping after exception: {"debuginfo":"https://www.googleapis.com/oauth2/v4/token","key":"Timeout was reached","retryable":true,"what":"std::exception"}
3203 [2020-05-01 12:25:51.111] [metadata] [info] Encountered error: {"debuginfo":"https://id.getmailspring.com/deltas/c8bfb684/head","key":"Timeout was reached","retryable":true,"what":"std::exception"}. Will retry in 300 sec.
3203 [2020-05-01 12:26:31.224] [background] [info] Fetching XOAuth2 access token from Gmail for c8bfb684
3203 [2020-05-01 12:26:51.278] [background] [info] Sleeping after exception: {"debuginfo":"https://www.googleapis.com/oauth2/v4/token","key":"Timeout was reached","retryable":true,"what":"std::exception"}
``` | comp | can t get oauth token for gmail accounts what is the behavior you re seeing lost connection to all gmail accounts what email provider gmail exchange etc are you trying to use gmail what operating system are you using ubuntu what version of mailspring are you using tried authenticating but the auth window also gets stuck also can t add a new gmail account encountered error debuginfo was reached retryable true what std exception will retry in sec fetching access token from gmail for sleeping after exception debuginfo was reached retryable true what std exception fetching access token from gmail for sleeping after exception debuginfo was reached retryable true what std exception encountered error debuginfo was reached retryable true what std exception will retry in sec fetching access token from gmail for sleeping after exception debuginfo was reached retryable true what std exception | 1 |
17,459 | 24,068,953,501 | IssuesEvent | 2022-09-17 22:42:32 | Shockah/Stardew-Valley-Mods | https://api.github.com/repos/Shockah/Stardew-Valley-Mods | closed | Animal Husbandry Mod - Syringe | -Don't Stop Me Now T:compatibility C2 !!!!4 | Using an Animal Husbandry syringe with no valid target while Don't Stop Me Now is installed causes a soft-lock. | True | Animal Husbandry Mod - Syringe - Using an Animal Husbandry syringe with no valid target while Don't Stop Me Now is installed causes a soft-lock. | comp | animal husbandry mod syringe using an animal husbandry syringe with no valid target while don t stop me now is installed causes a soft lock | 1 |
7,331 | 9,577,136,858 | IssuesEvent | 2019-05-07 10:49:27 | invoiceninja/invoiceninja | https://api.github.com/repos/invoiceninja/invoiceninja | closed | Error in artisan ninja:send-reminders with php7.3 | compatibility | With php7.3, the cron job for send-reminders task gives the following error:
Sun, 05 May 2019 15:30:02 +0000 Running SendReminders...
Sun, 05 May 2019 15:30:02 +0000 0 due recurring invoice instance(s) found
In Builder.php line 1229:
compact(): Undefined variable: operator
This does not happen with older versions of php. Maybe this is related to https://github.com/laravel/framework/issues/26936 ? (which basically calls out upgrading laravel version)
Here is the complete stacktrace:
`
2019-05-05 03:30:02 compact(): Undefined variable: operator: #0 [internal function]: Illuminate\Foundation\Bootstrap\HandleExceptions->handleError(8, 'compact(): Unde...', '/home/billing/p...', 1229, Array)
#1 /home/billing/public_html/vendor/laravel/framework/src/Illuminate/Database/Query/Builder.php(1229): compact('type', 'operator', 'query', 'boolean')
#2 /home/billing/public_html/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Builder.php(1254): Illuminate\Database\Query\Builder->addWhereExistsQuery(Object(Illuminate\Database\Query\Builder), 'and', false)
#3 /home/billing/public_html/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Concerns/QueriesRelationships.php(242): Illuminate\Database\Eloquent\Builder->__call('addWhereExistsQ...', Array)
#4 /home/billing/public_html/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Concerns/QueriesRelationships.php(52): Illuminate\Database\Eloquent\Build
er->addHasWhere(Object(Illuminate\Database\Eloquent\Builder), Object(Illuminate\Database\Eloquent\Relations\HasOne), '>=', 1, 'and')
#5 /home/billing/public_html/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Concerns/QueriesRelationships.php(132): Illuminate\Database\Eloquent\Builder->has(Object(Illuminate\Database\Eloquent\Relations\HasOne), '>=', 1, 'and',
Object(Closure))
#6 /home/billing/public_html/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Model.php(1374): Illuminate\Database\Eloquent\Builder->whereHas('account_email_s...', Object(Closure))
#7 /home/billing/public_html/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Model.php(1386): Illuminate\Database\Eloquent\Model->__call('whereHas', Array)
#8 /home/billing/public_html/app/Ninja/Repositories/AccountRepository.php(769): Illuminate\Database\Eloquent\Model::__callStatic('whereHas', Array)
#9 /home/billing/public_html/app/Console/Commands/SendReminders.php(127): App\Ninja\Repositories\AccountRepository->findWithFees()
#10 /home/billing/public_html/app/Console/Commands/SendReminders.php(82): App\Co
nsole\Commands\SendReminders->chargeLateFees()
#11 [internal function]: App\Console\Commands\SendReminders->fire()
#12 /home/billing/public_html/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(29): call_user_func_array(Array, Array)
#13 /home/billing/public_html/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(87): Illuminate\Container\BoundMethod::Illuminate\Container\{closure}()
#14 /home/billing/public_html/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(31): Illuminate\Container\BoundMethod::callBoundMethod(Object(Illuminate\Foundation\Application), Array, Object(Closure))
#15 /home/billing/public_html/vendor/laravel/framework/src/Illuminate/Container/Container.php(539): Illuminate\Container\BoundMethod::call(Object(Illuminate\Foundation\Application), Array, Array, NULL)
#16 /home/billing/public_html/vendor/laravel/framework/src/Illuminate/Console/Command.php(182): Illuminate\Container\Container->call(Array)
#17 /home/billing/public_html/vendor/symfony/console/Command/Command.php(252): Illuminate\Console\Command->execute(Object(Symfony\Component\Console\Input\ArgvInput), Object(Illuminate\Console\OutputStyle))
#18 /home/billing/public_html/vendor/laravel/framework/src/Illuminate/Console/Command.php(167): Symfony\Component\Console\Command\Command->run(Object(Symfony\Component\Console\Input\ArgvInput), Object(Illuminate\Console\OutputStyle))
#19 /home/billing/public_html/vendor/symfony/console/Application.php(946): Illuminate\Console\Command->run(Object(Symfony\Component\Console\Input\ArgvInput), Ob
ject(Symfony\Component\Console\Output\ConsoleOutput))
#20 /home/billing/public_html/vendor/symfony/console/Application.php(248): Symfony\Component\Console\Application->doRunCommand(Object(App\Console\Commands\SendReminders), Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#21 /home/billing/public_html/vendor/symfony/console/Application.php(148): Symfony\Component\Console\Application->doRun(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#22 /home/billing/public_html/vendor/laravel/framework/src/Illuminate/Foundation/Console/Kernel.php(122): Symfony\Component\Console\Application->run(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\
ConsoleOutput))
#23 /home/billing/public_html/artisan(35): Illuminate\Foundation\Console\Kernel->handle(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Compon
ent\Console\Output\ConsoleOutput))
#24 {main}
`
| True | Error in artisan ninja:send-reminders with php7.3 - With php7.3, the cron job for send-reminders task gives the following error:
Sun, 05 May 2019 15:30:02 +0000 Running SendReminders...
Sun, 05 May 2019 15:30:02 +0000 0 due recurring invoice instance(s) found
In Builder.php line 1229:
compact(): Undefined variable: operator
This does not happen with older versions of php. Maybe this is related to https://github.com/laravel/framework/issues/26936 ? (which basically calls out upgrading laravel version)
Here is the complete stacktrace:
`
2019-05-05 03:30:02 compact(): Undefined variable: operator: #0 [internal function]: Illuminate\Foundation\Bootstrap\HandleExceptions->handleError(8, 'compact(): Unde...', '/home/billing/p...', 1229, Array)
#1 /home/billing/public_html/vendor/laravel/framework/src/Illuminate/Database/Query/Builder.php(1229): compact('type', 'operator', 'query', 'boolean')
#2 /home/billing/public_html/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Builder.php(1254): Illuminate\Database\Query\Builder->addWhereExistsQuery(Object(Illuminate\Database\Query\Builder), 'and', false)
#3 /home/billing/public_html/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Concerns/QueriesRelationships.php(242): Illuminate\Database\Eloquent\Builder->__call('addWhereExistsQ...', Array)
#4 /home/billing/public_html/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Concerns/QueriesRelationships.php(52): Illuminate\Database\Eloquent\Build
er->addHasWhere(Object(Illuminate\Database\Eloquent\Builder), Object(Illuminate\Database\Eloquent\Relations\HasOne), '>=', 1, 'and')
#5 /home/billing/public_html/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Concerns/QueriesRelationships.php(132): Illuminate\Database\Eloquent\Builder->has(Object(Illuminate\Database\Eloquent\Relations\HasOne), '>=', 1, 'and',
Object(Closure))
#6 /home/billing/public_html/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Model.php(1374): Illuminate\Database\Eloquent\Builder->whereHas('account_email_s...', Object(Closure))
#7 /home/billing/public_html/vendor/laravel/framework/src/Illuminate/Database/Eloquent/Model.php(1386): Illuminate\Database\Eloquent\Model->__call('whereHas', Array)
#8 /home/billing/public_html/app/Ninja/Repositories/AccountRepository.php(769): Illuminate\Database\Eloquent\Model::__callStatic('whereHas', Array)
#9 /home/billing/public_html/app/Console/Commands/SendReminders.php(127): App\Ninja\Repositories\AccountRepository->findWithFees()
#10 /home/billing/public_html/app/Console/Commands/SendReminders.php(82): App\Co
nsole\Commands\SendReminders->chargeLateFees()
#11 [internal function]: App\Console\Commands\SendReminders->fire()
#12 /home/billing/public_html/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(29): call_user_func_array(Array, Array)
#13 /home/billing/public_html/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(87): Illuminate\Container\BoundMethod::Illuminate\Container\{closure}()
#14 /home/billing/public_html/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php(31): Illuminate\Container\BoundMethod::callBoundMethod(Object(Illuminate\Foundation\Application), Array, Object(Closure))
#15 /home/billing/public_html/vendor/laravel/framework/src/Illuminate/Container/Container.php(539): Illuminate\Container\BoundMethod::call(Object(Illuminate\Foundation\Application), Array, Array, NULL)
#16 /home/billing/public_html/vendor/laravel/framework/src/Illuminate/Console/Command.php(182): Illuminate\Container\Container->call(Array)
#17 /home/billing/public_html/vendor/symfony/console/Command/Command.php(252): Illuminate\Console\Command->execute(Object(Symfony\Component\Console\Input\ArgvInput), Object(Illuminate\Console\OutputStyle))
#18 /home/billing/public_html/vendor/laravel/framework/src/Illuminate/Console/Command.php(167): Symfony\Component\Console\Command\Command->run(Object(Symfony\Component\Console\Input\ArgvInput), Object(Illuminate\Console\OutputStyle))
#19 /home/billing/public_html/vendor/symfony/console/Application.php(946): Illuminate\Console\Command->run(Object(Symfony\Component\Console\Input\ArgvInput), Ob
ject(Symfony\Component\Console\Output\ConsoleOutput))
#20 /home/billing/public_html/vendor/symfony/console/Application.php(248): Symfony\Component\Console\Application->doRunCommand(Object(App\Console\Commands\SendReminders), Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#21 /home/billing/public_html/vendor/symfony/console/Application.php(148): Symfony\Component\Console\Application->doRun(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#22 /home/billing/public_html/vendor/laravel/framework/src/Illuminate/Foundation/Console/Kernel.php(122): Symfony\Component\Console\Application->run(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Component\Console\Output\
ConsoleOutput))
#23 /home/billing/public_html/artisan(35): Illuminate\Foundation\Console\Kernel->handle(Object(Symfony\Component\Console\Input\ArgvInput), Object(Symfony\Compon
ent\Console\Output\ConsoleOutput))
#24 {main}
`
| comp | error in artisan ninja send reminders with with the cron job for send reminders task gives the following error sun may running sendreminders sun may due recurring invoice instance s found in builder php line compact undefined variable operator this does not happen with older versions of php maybe this is related to which basically calls out upgrading laravel version here is the complete stacktrace compact undefined variable operator illuminate foundation bootstrap handleexceptions handleerror compact unde home billing p array home billing public html vendor laravel framework src illuminate database query builder php compact type operator query boolean home billing public html vendor laravel framework src illuminate database eloquent builder php illuminate database query builder addwhereexistsquery object illuminate database query builder and false home billing public html vendor laravel framework src illuminate database eloquent concerns queriesrelationships php illuminate database eloquent builder call addwhereexistsq array home billing public html vendor laravel framework src illuminate database eloquent concerns queriesrelationships php illuminate database eloquent build er addhaswhere object illuminate database eloquent builder object illuminate database eloquent relations hasone and home billing public html vendor laravel framework src illuminate database eloquent concerns queriesrelationships php illuminate database eloquent builder has object illuminate database eloquent relations hasone and object closure home billing public html vendor laravel framework src illuminate database eloquent model php illuminate database eloquent builder wherehas account email s object closure home billing public html vendor laravel framework src illuminate database eloquent model php illuminate database eloquent model call wherehas array home billing public html app ninja repositories accountrepository php illuminate database eloquent model callstatic wherehas array home billing public html app console commands sendreminders php app ninja repositories accountrepository findwithfees home billing public html app console commands sendreminders php app co nsole commands sendreminders chargelatefees app console commands sendreminders fire home billing public html vendor laravel framework src illuminate container boundmethod php call user func array array array home billing public html vendor laravel framework src illuminate container boundmethod php illuminate container boundmethod illuminate container closure home billing public html vendor laravel framework src illuminate container boundmethod php illuminate container boundmethod callboundmethod object illuminate foundation application array object closure home billing public html vendor laravel framework src illuminate container container php illuminate container boundmethod call object illuminate foundation application array array null home billing public html vendor laravel framework src illuminate console command php illuminate container container call array home billing public html vendor symfony console command command php illuminate console command execute object symfony component console input argvinput object illuminate console outputstyle home billing public html vendor laravel framework src illuminate console command php symfony component console command command run object symfony component console input argvinput object illuminate console outputstyle home billing public html vendor symfony console application php illuminate console command run object symfony component console input argvinput ob ject symfony component console output consoleoutput home billing public html vendor symfony console application php symfony component console application doruncommand object app console commands sendreminders object symfony component console input argvinput object symfony component console output consoleoutput home billing public html vendor symfony console application php symfony component console application dorun object symfony component console input argvinput object symfony component console output consoleoutput home billing public html vendor laravel framework src illuminate foundation console kernel php symfony component console application run object symfony component console input argvinput object symfony component console output consoleoutput home billing public html artisan illuminate foundation console kernel handle object symfony component console input argvinput object symfony compon ent console output consoleoutput main | 1 |
483 | 2,900,138,221 | IssuesEvent | 2015-06-17 15:04:14 | OpenBEL/bel.rb | https://api.github.com/repos/OpenBEL/bel.rb | opened | Improve support for JGF format | compatibility enhancement | *Reading JGF*
- Merge JGF metadata into evidence metadata.
- Read `evidences` in `edge.metadata`, conforming to [BEL JGF](http://jsongraphformat.info/child-schemas/bel-json-graph.schema.json)
- Support extracting edge as evidence, edge.evidences, or both. This control would determine which assertions are read.
*Write JGF*
- Merge evidence metadata into JGF.
- Collect evidences by BEL statement (e.g. strict equaliity of subject, rel, object) as a JGF edge. Store one or more evidences in JGF edge's metadata. | True | Improve support for JGF format - *Reading JGF*
- Merge JGF metadata into evidence metadata.
- Read `evidences` in `edge.metadata`, conforming to [BEL JGF](http://jsongraphformat.info/child-schemas/bel-json-graph.schema.json)
- Support extracting edge as evidence, edge.evidences, or both. This control would determine which assertions are read.
*Write JGF*
- Merge evidence metadata into JGF.
- Collect evidences by BEL statement (e.g. strict equaliity of subject, rel, object) as a JGF edge. Store one or more evidences in JGF edge's metadata. | comp | improve support for jgf format reading jgf merge jgf metadata into evidence metadata read evidences in edge metadata conforming to support extracting edge as evidence edge evidences or both this control would determine which assertions are read write jgf merge evidence metadata into jgf collect evidences by bel statement e g strict equaliity of subject rel object as a jgf edge store one or more evidences in jgf edge s metadata | 1 |
130,614 | 18,098,913,087 | IssuesEvent | 2021-09-22 12:17:03 | hzi-braunschweig/SORMAS-Project | https://api.github.com/repos/hzi-braunschweig/SORMAS-Project | closed | Handling of special characters / country specific characters / Umlauts in search | design & usability change general | ### Problem Description
When searching for a name in the case view, only exact matches are found.
So when searching for Müller, neither Muller nor Mueller would be found, Grossmann does not match with Großmann, Rene does not match with René, Yağmur Çelik does not match Yagmur Celik and some Vietnamese names such as Thường can be irretrievable once entered into the system.
With Demis this problem becomes more salient, as Demis messages often contain names with special characters that have to be described to Latin characters manually.
Also, this has led to situations where our database contained duplicates that were not easily discernible.
### Proposed Change
Country specific characters should be mapped in the search to their Latin character equivalent (As in e.g. https://docs.oracle.com/cd/E29584_01/webhelp/mdex_basicDev/src/rbdv_chars_mapping.html ), with the exceptions of ä, ö, ü, ß being mapped to ae, oe, ue add ss.
### Possible Alternatives
Handling of special characters as wildcards during search might be acceptable (Müller would find Mueller but also Möller).
| 1.0 | Handling of special characters / country specific characters / Umlauts in search - ### Problem Description
When searching for a name in the case view, only exact matches are found.
So when searching for Müller, neither Muller nor Mueller would be found, Grossmann does not match with Großmann, Rene does not match with René, Yağmur Çelik does not match Yagmur Celik and some Vietnamese names such as Thường can be irretrievable once entered into the system.
With Demis this problem becomes more salient, as Demis messages often contain names with special characters that have to be described to Latin characters manually.
Also, this has led to situations where our database contained duplicates that were not easily discernible.
### Proposed Change
Country specific characters should be mapped in the search to their Latin character equivalent (As in e.g. https://docs.oracle.com/cd/E29584_01/webhelp/mdex_basicDev/src/rbdv_chars_mapping.html ), with the exceptions of ä, ö, ü, ß being mapped to ae, oe, ue add ss.
### Possible Alternatives
Handling of special characters as wildcards during search might be acceptable (Müller would find Mueller but also Möller).
| non_comp | handling of special characters country specific characters umlauts in search problem description when searching for a name in the case view only exact matches are found so when searching for müller neither muller nor mueller would be found grossmann does not match with großmann rene does not match with rené yağmur çelik does not match yagmur celik and some vietnamese names such as thường can be irretrievable once entered into the system with demis this problem becomes more salient as demis messages often contain names with special characters that have to be described to latin characters manually also this has led to situations where our database contained duplicates that were not easily discernible proposed change country specific characters should be mapped in the search to their latin character equivalent as in e g with the exceptions of ä ö ü ß being mapped to ae oe ue add ss possible alternatives handling of special characters as wildcards during search might be acceptable müller would find mueller but also möller | 0 |
10,180 | 12,194,680,474 | IssuesEvent | 2020-04-29 16:09:46 | wordpress-mobile/WordPress-iOS | https://api.github.com/repos/wordpress-mobile/WordPress-iOS | closed | Notifications: Gutenberg comments don't show up in notifications about likes or replies to comments | Beta Request Gutenberg compatibility Mobile Request Notifications [Type] Bug | ### Expected behavior
When some likes or replies to a comment I made, I expect to see the beginning of my comment at the top of the notification about it.
### Actual behavior
When my comment was made using Gutenberg, the area in the notification where I expect to see the beginning of my comment is blank.
This issue is specific to WPiOS — it works as expected on the web and in WPAndroid.
### Steps to reproduce the behavior
1. On a site, enable Gutenberg for the site comments.
2. Leave a comment using Gutenberg.
3. From another account, like or reply to that comment.
4. In the app, check your notifications on the account you used to leave the Gutenberg comment.
5. Select the notification about the like/reply to your comment to view the notification detail.
Result: The notification is received, but the text of your comment isn't visible in the notification detail.
WPiOS (bug)|WPAndroid (expected)
-|-
<img src="https://user-images.githubusercontent.com/8658164/78901767-b7650c00-7a70-11ea-9976-f6edec9641b7.PNG" width="300px">|<img src="https://user-images.githubusercontent.com/8658164/78901551-62c19100-7a70-11ea-8deb-e04a5535207c.png" width="300px">
##### Tested on [iPhone XS], iOS [13.4], WPiOS [14.6.0.20200406]
| True | Notifications: Gutenberg comments don't show up in notifications about likes or replies to comments - ### Expected behavior
When some likes or replies to a comment I made, I expect to see the beginning of my comment at the top of the notification about it.
### Actual behavior
When my comment was made using Gutenberg, the area in the notification where I expect to see the beginning of my comment is blank.
This issue is specific to WPiOS — it works as expected on the web and in WPAndroid.
### Steps to reproduce the behavior
1. On a site, enable Gutenberg for the site comments.
2. Leave a comment using Gutenberg.
3. From another account, like or reply to that comment.
4. In the app, check your notifications on the account you used to leave the Gutenberg comment.
5. Select the notification about the like/reply to your comment to view the notification detail.
Result: The notification is received, but the text of your comment isn't visible in the notification detail.
WPiOS (bug)|WPAndroid (expected)
-|-
<img src="https://user-images.githubusercontent.com/8658164/78901767-b7650c00-7a70-11ea-9976-f6edec9641b7.PNG" width="300px">|<img src="https://user-images.githubusercontent.com/8658164/78901551-62c19100-7a70-11ea-8deb-e04a5535207c.png" width="300px">
##### Tested on [iPhone XS], iOS [13.4], WPiOS [14.6.0.20200406]
| comp | notifications gutenberg comments don t show up in notifications about likes or replies to comments expected behavior when some likes or replies to a comment i made i expect to see the beginning of my comment at the top of the notification about it actual behavior when my comment was made using gutenberg the area in the notification where i expect to see the beginning of my comment is blank this issue is specific to wpios — it works as expected on the web and in wpandroid steps to reproduce the behavior on a site enable gutenberg for the site comments leave a comment using gutenberg from another account like or reply to that comment in the app check your notifications on the account you used to leave the gutenberg comment select the notification about the like reply to your comment to view the notification detail result the notification is received but the text of your comment isn t visible in the notification detail wpios bug wpandroid expected tested on ios wpios | 1 |
34,558 | 9,411,962,855 | IssuesEvent | 2019-04-10 01:53:46 | opencv/opencv | https://api.github.com/repos/opencv/opencv | closed | Error compiling 4.1.0 source code with mingw-w64: 'D3D11_TEXTURE2D_DESC' was not declared in this scope | category: build/install |
##### System information (version)
- OpenCV => 4.1.0
- Operating System / Platform => Windows 10 64bit
- Compiler => mingw-w64 8.1.0-posix-seh-rt_v6-rev0
##### Detailed description
When I compiled the 4.1.0 version with mingw-w64, there was an error
```
E:\opencv-4.1.0\opencv-4.1.0\modules\core\src\directx.cpp:1035:5: error: 'D3D11_TEXTURE2D_DESC' was not declared in this scope
D3D11_TEXTURE2D_DESC desc = { 0 };
^~~~~~~~~~~~~~~~~~~~
```
I can solve it like this
```
cmake -DWITH_OPENCL_D3D11_NV=OFF
```
But I don't know if this is the right solution, and whether this will affect the compiled dll.
| 1.0 | Error compiling 4.1.0 source code with mingw-w64: 'D3D11_TEXTURE2D_DESC' was not declared in this scope -
##### System information (version)
- OpenCV => 4.1.0
- Operating System / Platform => Windows 10 64bit
- Compiler => mingw-w64 8.1.0-posix-seh-rt_v6-rev0
##### Detailed description
When I compiled the 4.1.0 version with mingw-w64, there was an error
```
E:\opencv-4.1.0\opencv-4.1.0\modules\core\src\directx.cpp:1035:5: error: 'D3D11_TEXTURE2D_DESC' was not declared in this scope
D3D11_TEXTURE2D_DESC desc = { 0 };
^~~~~~~~~~~~~~~~~~~~
```
I can solve it like this
```
cmake -DWITH_OPENCL_D3D11_NV=OFF
```
But I don't know if this is the right solution, and whether this will affect the compiled dll.
| non_comp | error compiling source code with mingw desc was not declared in this scope system information version opencv operating system platform windows compiler mingw posix seh rt detailed description when i compiled the version with mingw there was an error e opencv opencv modules core src directx cpp error desc was not declared in this scope desc desc i can solve it like this cmake dwith opencl nv off but i don t know if this is the right solution and whether this will affect the compiled dll | 0 |
81,643 | 31,167,348,014 | IssuesEvent | 2023-08-16 20:52:31 | department-of-veterans-affairs/va.gov-cms | https://api.github.com/repos/department-of-veterans-affairs/va.gov-cms | closed | 508-defect-4 [COGNITION]: Breadcrumbs should match `h1` | Defect VA.gov frontend Public Websites accessibility a11y-defect-4 Still Applicable wcag2.0 | ### Update from Laura 3/31/23: Please see the [last comment](https://github.com/department-of-veterans-affairs/va.gov-cms/issues/13147) for most recent review/update for what still remains to be done on this ticket
## Details
We recently updated a couple of the search page's `h1`s from "Search results" to "Search" in order to communicate to screen reader users that they can both search and browse search results. However, we did not update the breadcrumbs to match those changes which may be confusing or inconsistent to users.
## Acceptance Criteria
- [x] department-of-veterans-affairs/va.gov-team#29733 is closed
- [x] Breadcrumbs for VA.gov Search matches respective `h1`
- [ ] Breadcrumbs for Resources and support matches respective `h1`
## Proposed Solution
### Before
<img width="784" alt="Screen Shot 2021-09-08 at 2 28 44 PM" src="https://user-images.githubusercontent.com/14154792/132566179-1024cb97-0f83-4140-af98-8da7338ab976.png">
<img width="800" alt="Screen Shot 2021-09-08 at 2 38 23 PM" src="https://user-images.githubusercontent.com/14154792/132566229-88452e9e-1de2-430a-8116-ccee3a3d1799.png">
### After
<img width="787" alt="Screen Shot 2021-09-08 at 2 28 37 PM" src="https://user-images.githubusercontent.com/14154792/132566193-a383e7f3-818d-4707-95f6-b1bbc5e136f0.png">
<img width="791" alt="Screen Shot 2021-09-08 at 2 30 42 PM" src="https://user-images.githubusercontent.com/14154792/132566157-9e5635b4-864e-4898-b043-b0b3bd3c08e0.png">
| 2.0 | 508-defect-4 [COGNITION]: Breadcrumbs should match `h1` - ### Update from Laura 3/31/23: Please see the [last comment](https://github.com/department-of-veterans-affairs/va.gov-cms/issues/13147) for most recent review/update for what still remains to be done on this ticket
## Details
We recently updated a couple of the search page's `h1`s from "Search results" to "Search" in order to communicate to screen reader users that they can both search and browse search results. However, we did not update the breadcrumbs to match those changes which may be confusing or inconsistent to users.
## Acceptance Criteria
- [x] department-of-veterans-affairs/va.gov-team#29733 is closed
- [x] Breadcrumbs for VA.gov Search matches respective `h1`
- [ ] Breadcrumbs for Resources and support matches respective `h1`
## Proposed Solution
### Before
<img width="784" alt="Screen Shot 2021-09-08 at 2 28 44 PM" src="https://user-images.githubusercontent.com/14154792/132566179-1024cb97-0f83-4140-af98-8da7338ab976.png">
<img width="800" alt="Screen Shot 2021-09-08 at 2 38 23 PM" src="https://user-images.githubusercontent.com/14154792/132566229-88452e9e-1de2-430a-8116-ccee3a3d1799.png">
### After
<img width="787" alt="Screen Shot 2021-09-08 at 2 28 37 PM" src="https://user-images.githubusercontent.com/14154792/132566193-a383e7f3-818d-4707-95f6-b1bbc5e136f0.png">
<img width="791" alt="Screen Shot 2021-09-08 at 2 30 42 PM" src="https://user-images.githubusercontent.com/14154792/132566157-9e5635b4-864e-4898-b043-b0b3bd3c08e0.png">
| non_comp | defect breadcrumbs should match update from laura please see the for most recent review update for what still remains to be done on this ticket details we recently updated a couple of the search page s s from search results to search in order to communicate to screen reader users that they can both search and browse search results however we did not update the breadcrumbs to match those changes which may be confusing or inconsistent to users acceptance criteria department of veterans affairs va gov team is closed breadcrumbs for va gov search matches respective breadcrumbs for resources and support matches respective proposed solution before img width alt screen shot at pm src img width alt screen shot at pm src after img width alt screen shot at pm src img width alt screen shot at pm src | 0 |
20,685 | 30,764,753,673 | IssuesEvent | 2023-07-30 06:27:54 | acemod/ACE3 | https://api.github.com/repos/acemod/ACE3 | closed | Handling of custom FirstAidKits and MedKits | kind/bug area/compatibility | **Arma 3 Version:** `1.92` (stable / rc / dev)
**CBA Version:** `3.10.1` (stable / dev + commit hash)
**ACE3 Version:** `3.12.6` (stable / dev + commit hash)
**Mods:**
```
- Global Mobilization
- CBA_A3
- ace
```
**Description:**
- GM has two new FAK's, gm_ge_army_burnBandage & gm_ge_army_gauzeBandage. These need to be changed into medical supplies
**Steps to reproduce:**
- Load GM, go into campaign or play as a unit with vanilla loadout.
**Where did the issue occur?**
- Dedicated / Self-Hosted Multiplayer / Singleplayer / Editor (Singleplayer) / Editor (Multiplayer) / Virtual Arsenal
**Additional information:**
`while {({_x == "gm_ge_army_burnBandage"} count items _unit) > 0} do {
_unit removeItem "gm_ge_army_burnBandage";
if (GVAR(convertItems) == 0) then {
if (GVAR(level) >= 2) then {
_unit addItem "ACE_fieldDressing";
_unit addItem "ACE_packingBandage";
_unit addItem "ACE_morphine";
_unit addItem "ACE_tourniquet";
} else {
_unit addItem "ACE_fieldDressing";
_unit addItem "ACE_fieldDressing";
_unit addItem "ACE_morphine";
};
};
};`
`while {({_x == "gm_ge_army_gauzeBandage"} count items _unit) > 0} do {
_unit removeItem "gm_ge_army_gauzeBandage";
if (GVAR(convertItems) == 0) then {
if (GVAR(level) >= 2) then {
_unit addItem "ACE_fieldDressing";
_unit addItem "ACE_packingBandage";
_unit addItem "ACE_morphine";
_unit addItem "ACE_tourniquet";
} else {
_unit addItem "ACE_fieldDressing";
_unit addItem "ACE_fieldDressing";
_unit addItem "ACE_morphine";
};
};
};` https://github.com/acemod/ACE3/blob/v3.12.6/addons/medical/functions/fnc_itemCheck.sqf
| True | Handling of custom FirstAidKits and MedKits - **Arma 3 Version:** `1.92` (stable / rc / dev)
**CBA Version:** `3.10.1` (stable / dev + commit hash)
**ACE3 Version:** `3.12.6` (stable / dev + commit hash)
**Mods:**
```
- Global Mobilization
- CBA_A3
- ace
```
**Description:**
- GM has two new FAK's, gm_ge_army_burnBandage & gm_ge_army_gauzeBandage. These need to be changed into medical supplies
**Steps to reproduce:**
- Load GM, go into campaign or play as a unit with vanilla loadout.
**Where did the issue occur?**
- Dedicated / Self-Hosted Multiplayer / Singleplayer / Editor (Singleplayer) / Editor (Multiplayer) / Virtual Arsenal
**Additional information:**
`while {({_x == "gm_ge_army_burnBandage"} count items _unit) > 0} do {
_unit removeItem "gm_ge_army_burnBandage";
if (GVAR(convertItems) == 0) then {
if (GVAR(level) >= 2) then {
_unit addItem "ACE_fieldDressing";
_unit addItem "ACE_packingBandage";
_unit addItem "ACE_morphine";
_unit addItem "ACE_tourniquet";
} else {
_unit addItem "ACE_fieldDressing";
_unit addItem "ACE_fieldDressing";
_unit addItem "ACE_morphine";
};
};
};`
`while {({_x == "gm_ge_army_gauzeBandage"} count items _unit) > 0} do {
_unit removeItem "gm_ge_army_gauzeBandage";
if (GVAR(convertItems) == 0) then {
if (GVAR(level) >= 2) then {
_unit addItem "ACE_fieldDressing";
_unit addItem "ACE_packingBandage";
_unit addItem "ACE_morphine";
_unit addItem "ACE_tourniquet";
} else {
_unit addItem "ACE_fieldDressing";
_unit addItem "ACE_fieldDressing";
_unit addItem "ACE_morphine";
};
};
};` https://github.com/acemod/ACE3/blob/v3.12.6/addons/medical/functions/fnc_itemCheck.sqf
| comp | handling of custom firstaidkits and medkits arma version stable rc dev cba version stable dev commit hash version stable dev commit hash mods global mobilization cba ace description gm has two new fak s gm ge army burnbandage gm ge army gauzebandage these need to be changed into medical supplies steps to reproduce load gm go into campaign or play as a unit with vanilla loadout where did the issue occur dedicated self hosted multiplayer singleplayer editor singleplayer editor multiplayer virtual arsenal additional information while x gm ge army burnbandage count items unit do unit removeitem gm ge army burnbandage if gvar convertitems then if gvar level then unit additem ace fielddressing unit additem ace packingbandage unit additem ace morphine unit additem ace tourniquet else unit additem ace fielddressing unit additem ace fielddressing unit additem ace morphine while x gm ge army gauzebandage count items unit do unit removeitem gm ge army gauzebandage if gvar convertitems then if gvar level then unit additem ace fielddressing unit additem ace packingbandage unit additem ace morphine unit additem ace tourniquet else unit additem ace fielddressing unit additem ace fielddressing unit additem ace morphine | 1 |
19,653 | 27,293,414,625 | IssuesEvent | 2023-02-23 18:16:16 | elementor/elementor | https://api.github.com/repos/elementor/elementor | closed | ⛔ 🐞 Bug Report: Elementor-created shop page defaults back to WooCommerce standard shop page after assigning it in the Settings. After the page is assigned, I’m unable to edit the page using Elementor | bug compatibility/3rd_party product/pro component/woocommerce type/dynamic-content type/templates | ### Prerequisites
- [X] I have searched for similar issues in both open and closed tickets and cannot find a duplicate.
- [X] The issue still exists against the latest stable version of Elementor.
### Description
When exactly did you first notice the problem?
- I noticed this problem today when I finished modifying the Shop All page and navigated to the WooCommerce Settings to assign this page as a WooCommerce Shop Page
Have any updates been applied to your website recently?
- Updated the woocommerce templates that required an update
Have you changed themes or made design changes?
- No theme changes
Have you installed any new plugins?
- Yes, but I disabled and uninstalled it. (Royal Addons)
Can the issue be replicated on multiple devices?
- Yes, shop page shows incorrectly all devices
Is your problem happening in one browser or all of them?
- all of them
Do you see a specific error message? Take a screenshot.
- yes, when I attempt to edit the page after assigning it to WooCommerce I get the message: The Preview could not be loaded.
### Steps to reproduce
1. Created a Shop Page with Elementor
2. Navigate to the WooCommerce Settings to assign this page as a WooCommerce Shop Page
3. Navigate back to the page from the Pages menu
4. Click the Edit with Elementor link
5. Get an error The Preview Could Not Be Loaded
<img width="1393" alt="Screen Shot 2023-02-21 at 10 59 35 PM" src="https://user-images.githubusercontent.com/57504763/220518797-e13f501b-4ffa-44ec-aaa9-7fa1b5fe463d.png">
<img width="1299" alt="Screen Shot 2023-02-21 at 11 00 11 PM" src="https://user-images.githubusercontent.com/57504763/220518801-ff8d9985-b888-43ec-bc5b-b46bc04ec662.png">
<img width="587" alt="Screen Shot 2023-02-21 at 11 00 51 PM" src="https://user-images.githubusercontent.com/57504763/220518803-e31a3ada-b3dc-4b16-b5e3-3fa38db7a01c.png">
### Isolating the problem
- [ ] This bug happens with only Elementor plugin active (and Elementor Pro).
- [ ] This bug happens with a Blank WordPress theme active ([Hello theme](https://wordpress.org/themes/hello-elementor/)).
- [ ] I can reproduce this bug consistently following the steps above.
### System Info
<details>
<summary>System Info</summary>
````txt
== Server Environment ==
Operating System: Linux
Software: LiteSpeed
MySQL version: MariaDB Server v10.3.34
PHP Version: 7.4.29
PHP Memory Limit: 256M
PHP Max Input Vars: 5000
PHP Max Post Size: 1024M
GD Installed: Yes
ZIP Installed: Yes
Write Permissions: All right
Elementor Library: Connected
== WordPress Environment ==
Version: 6.1.1
Site URL: https://www.silkresse.com
Home URL: https://www.silkresse.com
WP Multisite: No
Max Upload Size: 512 MB
Memory limit: 40M
Max Memory limit: 256M
Permalink Structure: /blog/%postname%/
Language: en-US
Timezone: 0
Admin Email: silkresse@gmail.com
Debug Mode: Inactive
== Theme ==
Name: Blocksy Child
Version:
Author: Creative Themes
Child Theme: Yes
Parent Theme Name: Blocksy
Parent Theme Version: 1.8.42
Parent Theme Author: CreativeThemes
== User ==
Role: administrator
WP Profile lang: en_US
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36
== Active Plugins ==
Advanced Product Fields for WooCommerce
Version: 1.5.9
Author: StudioWombat
Blocksy Companion
Version: 1.8.75
Author: CreativeThemes
CoDesigner
Version: 3.9
Author: Codexpert
Elementor
Version: 3.12.0-dev4
Author: Elementor.com
Elementor Beta (Developer Edition)
Version: 1.1.1
Author: Elementor.com
ElementsKit Lite
Version: 2.8.1
Author: Wpmet
Essential Addons for Elementor
Version: 5.5.4
Author: WPDeveloper
Spotlight - Social Media Feeds
Version: 1.4.4
Author: RebelCode
WooCommerce
Version: 7.4.0
Author: Automattic
WPForms Lite
Version: 1.8.0.1
Author: WPForms
== Elementor Experiments ==
Optimized DOM Output: Active by default
Improved Asset Loading: Active by default
Improved CSS Loading: Active by default
Inline Font Icons: Active by default
Accessibility Improvements: Active by default
Additional Custom Breakpoints: Active by default
admin_menu_rearrangement: Inactive by default
Flexbox Container: Active
Upgrade Swiper Library: Active by default
Editor V2: Inactive by default
Landing Pages: Active by default
Nested Elements: Active by default
Lazy Load Background Images: Inactive by default
Save as Default: Active by default
== Log ==
JS: showing 17 of 17JS: 2022-07-12 18:06:59 [error X 75][https://www.silkresse.com/wp-content/plugins/elementor/assets/js/editor.min.js?ver=3.6.7:3:475108] Cannot read properties of undefined (reading \'parent\')
JS: 2022-07-16 15:21:36 [error X 28][https://www.silkresse.com/wp-content/plugins/elementor/assets/js/editor.min.js?ver=3.7.0-dev10:2:185947] Cannot read properties of undefined (reading \'data\')
JS: 2022-07-20 16:33:37 [error X 6][https://www.silkresse.com/wp-content/plugins/elementor/assets/js/editor.min.js?ver=3.7.0-dev10:2:610510] Cannot read properties of null (reading \'getBoundingClientRect\')
JS: 2022-08-12 21:59:03 [error X 8][https://www.silkresse.com/wp-content/plugins/elementor/assets/js/editor.min.js?ver=3.7.0-dev10:2:614960] Cannot read properties of undefined (reading \'toLowerCase\')
JS: 2022-08-16 02:01:16 [error X 34][https://www.silkresse.com/wp-content/plugins/elementor/assets/js/editor.min.js?ver=3.7.0-dev10:2:615467] Cannot read properties of undefined (reading \'localized\')
JS: 2022-09-12 01:10:55 [error X 1][https://www.silkresse.com/wp-content/plugins/elementor/assets/js/container-converter.min.js?ver=3.7.0-dev10:2:10719] elementor is not defined
JS: 2022-11-09 01:26:51 [error X 13][https://www.silkresse.com/wp-admin/load-scripts.php?c=1&loadchunk_0=jquery-core,jquery-migrate,regenerator-runtime,wp-polyfill,underscore,shortcode,utils,backbone,wp-util,wp-backbone,media-models,&loadchunk_1=moxiejs,plupload,wp-plupload,jquery-ui-core,jquery-ui-mouse,jquery-ui-sortable&ver=6.1:2:51824] Cannot read properties of undefined (reading \'replace\')
JS: 2022-11-09 02:35:21 [error X 36][https://www.silkresse.com/wp-content/plugins/elementor/assets/js/frontend.min.js?ver=3.10.0-dev1:2:32848] elementorFrontendConfig is not defined
JS: 2022-11-09 03:20:43 [error X 2][https://www.silkresse.com/wp-content/plugins/elementor/assets/js/editor.min.js?ver=3.10.0-dev1:3:811312] Cannot convert undefined or null to object
JS: 2022-11-17 22:00:07 [error X 4][https://www.silkresse.com/wp-content/plugins/elementor/assets/js/frontend.min.js?ver=3.10.0-dev1:2:32871] Can\'t find variable: elementorFrontendConfig
JS: 2023-01-10 04:51:46 [error X 69][https://www.silkresse.com/wp-admin/load-scripts.php?c=1&loadchunk_0=jquery-core,jquery-migrate,regenerator-runtime,wp-polyfill,jquery-ui-core,jquery-ui-mouse,underscore,backbone,wp-api-request,wp-&loadchunk_1=hooks&ver=6.1.1:2:51824] Cannot read properties of undefined (reading 'replace')
JS: 2023-01-11 15:19:35 [error X 1][https://www.silkresse.com/wp-content/plugins/elementor/assets/js/editor.min.js?ver=3.11.0-dev3:3:583495] Cannot read properties of null (reading 'id')
JS: 2023-01-11 17:27:40 [error X 3][https://www.silkresse.com/wp-content/plugins/elementor/assets/js/editor.min.js?ver=3.11.0-dev3:3:782318] Cannot read properties of undefined (reading 'toLowerCase')
JS: 2023-01-18 02:51:41 [error X 1][https://www.silkresse.com/wp-content/plugins/elementor/assets/js/web-cli.min.js?ver=3.11.0-dev3:3:105230] Routes: `library/templates` not found.
JS: 2023-01-19 04:31:23 [error X 1][https://www.silkresse.com/wp-content/plugins/elementor/assets/js/web-cli.min.js?ver=3.11.0-dev3:3:105230] Routes: `library/blocks` not found.
JS: 2023-01-19 04:31:26 [error X 1][https://www.silkresse.com/wp-content/plugins/elementor/assets/js/web-cli.min.js?ver=3.11.0-dev3:3:105230] Routes: `library/pages` not found.
JS: 2023-02-20 16:19:44 [error X 14][https://www.silkresse.com/wp-content/plugins/elementor/assets/js/editor.min.js?ver=3.12.0-dev4:3:794636] Cannot read properties of undefined (reading 'localized')
PHP: showing 5 of 5PHP: 2022-07-12 20:02:17 [notice X 120][/home/silkress/public_html/wp-content/plugins/elementor/modules/dev-tools/deprecation.php::301] The $finder_category_name argument is deprecated since version 3.5.0! [array (
'trace' => '
#0: Elementor\Core\Logger\Manager -> shutdown()
',
)]
PHP: 2022-07-12 20:05:38 [notice X 5][/home/silkress/public_html/wp-content/plugins/elementor/includes/widgets/traits/button-trait.php::553] Undefined index: icon [array (
'trace' => '
#0: Elementor\Core\Logger\Manager -> shutdown()
',
)]
PHP: 2022-09-12 19:12:19 [notice X 1][/home/silkress/public_html/wp-content/plugins/elementor/core/common/modules/ajax/module.php::171] Undefined index: data [array (
'trace' => '
#0: Elementor\Core\Logger\Manager -> shutdown()
',
)]
PHP: 2023-01-18 02:53:19 [notice X 2][/home/silkress/public_html/wp-content/plugins/elementor/core/page-assets/data-managers/font-icon-svg/font-awesome.php::50] Trying to access array offset on value of type null [array (
'trace' => '
#0: Elementor\Core\Logger\Manager -> shutdown()
',
)]
PHP: 2023-02-20 04:56:40 [notice X 21][/home/silkress/public_html/wp-content/plugins/elementor/includes/managers/image.php::108] Trying to access array offset on value of type bool [array (
'trace' => '
#0: Elementor\Core\Logger\Manager -> shutdown()
',
)]
Log: showing 20 of 202022-07-16 14:45:12 [info] elementor::elementor_updater Started
2022-07-16 14:45:12 [info] Elementor/Upgrades - _on_each_version Start
2022-07-16 14:45:12 [info] Elementor/Upgrades - _on_each_version Finished
2022-07-16 14:45:12 [info] Elementor/Upgrades - _v_3_7_0_remove_old_elements_usage Start
2022-07-16 14:45:12 [info] Elementor/Upgrades - _v_3_7_0_remove_old_elements_usage Finished
2022-07-16 14:45:12 [info] Elementor data updater process has been completed. [array (
'plugin' => 'Elementor',
'from' => '3.6.7',
'to' => '3.7.0-dev10',
)]
2022-07-16 14:45:12 [info] Elementor data updater process has been queued. [array (
'plugin' => 'Elementor',
'from' => '3.6.7',
'to' => '3.7.0-dev10',
)]
2022-11-09 02:20:27 [info] Elementor data updater process has been queued. [array (
'plugin' => 'Elementor',
'from' => '3.7.0-dev10',
'to' => '3.10.0-dev1',
)]
2022-11-09 02:20:27 [info] elementor::elementor_updater Started
2022-11-09 02:20:27 [info] Elementor/Upgrades - _on_each_version Start
2022-11-09 02:20:27 [info] Elementor/Upgrades - _on_each_version Finished
2022-11-09 02:20:27 [info] Elementor/Upgrades - _v_3_8_0_fix_php8_image_custom_size Start
2022-11-09 02:20:27 [info] Elementor/Upgrades - _v_3_8_0_fix_php8_image_custom_size Finished
2022-11-09 02:20:27 [info] Elementor data updater process has been completed. [array (
'plugin' => 'Elementor',
'from' => '3.7.0-dev10',
'to' => '3.10.0-dev1',
)]
2022-12-14 01:22:22 [info] Elementor data updater process has been queued. [array (
'plugin' => 'Elementor',
'from' => '3.10.0-dev1',
'to' => '3.11.0-dev1',
)]
2022-12-14 01:22:22 [info] elementor::elementor_updater Started
2022-12-14 01:22:22 [info] Elementor/Upgrades - _on_each_version Start
2022-12-14 01:22:22 [info] Elementor/Upgrades - _on_each_version Finished
2022-12-14 01:22:22 [info] Elementor data updater process has been completed. [array (
'plugin' => 'Elementor',
'from' => '3.10.0-dev1',
'to' => '3.11.0-dev1',
)]
2022-12-14 01:22:23 [info] Elementor data updater process has been queued. [array (
'plugin' => 'Elementor',
'from' => '3.10.0-dev1',
'to' => '3.11.0-dev1',
)]
== Elementor - Compatibility Tag ==
Essential Addons for Elementor: Incompatible
````
</details> | True | ⛔ 🐞 Bug Report: Elementor-created shop page defaults back to WooCommerce standard shop page after assigning it in the Settings. After the page is assigned, I’m unable to edit the page using Elementor - ### Prerequisites
- [X] I have searched for similar issues in both open and closed tickets and cannot find a duplicate.
- [X] The issue still exists against the latest stable version of Elementor.
### Description
When exactly did you first notice the problem?
- I noticed this problem today when I finished modifying the Shop All page and navigated to the WooCommerce Settings to assign this page as a WooCommerce Shop Page
Have any updates been applied to your website recently?
- Updated the woocommerce templates that required an update
Have you changed themes or made design changes?
- No theme changes
Have you installed any new plugins?
- Yes, but I disabled and uninstalled it. (Royal Addons)
Can the issue be replicated on multiple devices?
- Yes, shop page shows incorrectly all devices
Is your problem happening in one browser or all of them?
- all of them
Do you see a specific error message? Take a screenshot.
- yes, when I attempt to edit the page after assigning it to WooCommerce I get the message: The Preview could not be loaded.
### Steps to reproduce
1. Created a Shop Page with Elementor
2. Navigate to the WooCommerce Settings to assign this page as a WooCommerce Shop Page
3. Navigate back to the page from the Pages menu
4. Click the Edit with Elementor link
5. Get an error The Preview Could Not Be Loaded
<img width="1393" alt="Screen Shot 2023-02-21 at 10 59 35 PM" src="https://user-images.githubusercontent.com/57504763/220518797-e13f501b-4ffa-44ec-aaa9-7fa1b5fe463d.png">
<img width="1299" alt="Screen Shot 2023-02-21 at 11 00 11 PM" src="https://user-images.githubusercontent.com/57504763/220518801-ff8d9985-b888-43ec-bc5b-b46bc04ec662.png">
<img width="587" alt="Screen Shot 2023-02-21 at 11 00 51 PM" src="https://user-images.githubusercontent.com/57504763/220518803-e31a3ada-b3dc-4b16-b5e3-3fa38db7a01c.png">
### Isolating the problem
- [ ] This bug happens with only Elementor plugin active (and Elementor Pro).
- [ ] This bug happens with a Blank WordPress theme active ([Hello theme](https://wordpress.org/themes/hello-elementor/)).
- [ ] I can reproduce this bug consistently following the steps above.
### System Info
<details>
<summary>System Info</summary>
````txt
== Server Environment ==
Operating System: Linux
Software: LiteSpeed
MySQL version: MariaDB Server v10.3.34
PHP Version: 7.4.29
PHP Memory Limit: 256M
PHP Max Input Vars: 5000
PHP Max Post Size: 1024M
GD Installed: Yes
ZIP Installed: Yes
Write Permissions: All right
Elementor Library: Connected
== WordPress Environment ==
Version: 6.1.1
Site URL: https://www.silkresse.com
Home URL: https://www.silkresse.com
WP Multisite: No
Max Upload Size: 512 MB
Memory limit: 40M
Max Memory limit: 256M
Permalink Structure: /blog/%postname%/
Language: en-US
Timezone: 0
Admin Email: silkresse@gmail.com
Debug Mode: Inactive
== Theme ==
Name: Blocksy Child
Version:
Author: Creative Themes
Child Theme: Yes
Parent Theme Name: Blocksy
Parent Theme Version: 1.8.42
Parent Theme Author: CreativeThemes
== User ==
Role: administrator
WP Profile lang: en_US
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/103.0.0.0 Safari/537.36
== Active Plugins ==
Advanced Product Fields for WooCommerce
Version: 1.5.9
Author: StudioWombat
Blocksy Companion
Version: 1.8.75
Author: CreativeThemes
CoDesigner
Version: 3.9
Author: Codexpert
Elementor
Version: 3.12.0-dev4
Author: Elementor.com
Elementor Beta (Developer Edition)
Version: 1.1.1
Author: Elementor.com
ElementsKit Lite
Version: 2.8.1
Author: Wpmet
Essential Addons for Elementor
Version: 5.5.4
Author: WPDeveloper
Spotlight - Social Media Feeds
Version: 1.4.4
Author: RebelCode
WooCommerce
Version: 7.4.0
Author: Automattic
WPForms Lite
Version: 1.8.0.1
Author: WPForms
== Elementor Experiments ==
Optimized DOM Output: Active by default
Improved Asset Loading: Active by default
Improved CSS Loading: Active by default
Inline Font Icons: Active by default
Accessibility Improvements: Active by default
Additional Custom Breakpoints: Active by default
admin_menu_rearrangement: Inactive by default
Flexbox Container: Active
Upgrade Swiper Library: Active by default
Editor V2: Inactive by default
Landing Pages: Active by default
Nested Elements: Active by default
Lazy Load Background Images: Inactive by default
Save as Default: Active by default
== Log ==
JS: showing 17 of 17JS: 2022-07-12 18:06:59 [error X 75][https://www.silkresse.com/wp-content/plugins/elementor/assets/js/editor.min.js?ver=3.6.7:3:475108] Cannot read properties of undefined (reading \'parent\')
JS: 2022-07-16 15:21:36 [error X 28][https://www.silkresse.com/wp-content/plugins/elementor/assets/js/editor.min.js?ver=3.7.0-dev10:2:185947] Cannot read properties of undefined (reading \'data\')
JS: 2022-07-20 16:33:37 [error X 6][https://www.silkresse.com/wp-content/plugins/elementor/assets/js/editor.min.js?ver=3.7.0-dev10:2:610510] Cannot read properties of null (reading \'getBoundingClientRect\')
JS: 2022-08-12 21:59:03 [error X 8][https://www.silkresse.com/wp-content/plugins/elementor/assets/js/editor.min.js?ver=3.7.0-dev10:2:614960] Cannot read properties of undefined (reading \'toLowerCase\')
JS: 2022-08-16 02:01:16 [error X 34][https://www.silkresse.com/wp-content/plugins/elementor/assets/js/editor.min.js?ver=3.7.0-dev10:2:615467] Cannot read properties of undefined (reading \'localized\')
JS: 2022-09-12 01:10:55 [error X 1][https://www.silkresse.com/wp-content/plugins/elementor/assets/js/container-converter.min.js?ver=3.7.0-dev10:2:10719] elementor is not defined
JS: 2022-11-09 01:26:51 [error X 13][https://www.silkresse.com/wp-admin/load-scripts.php?c=1&loadchunk_0=jquery-core,jquery-migrate,regenerator-runtime,wp-polyfill,underscore,shortcode,utils,backbone,wp-util,wp-backbone,media-models,&loadchunk_1=moxiejs,plupload,wp-plupload,jquery-ui-core,jquery-ui-mouse,jquery-ui-sortable&ver=6.1:2:51824] Cannot read properties of undefined (reading \'replace\')
JS: 2022-11-09 02:35:21 [error X 36][https://www.silkresse.com/wp-content/plugins/elementor/assets/js/frontend.min.js?ver=3.10.0-dev1:2:32848] elementorFrontendConfig is not defined
JS: 2022-11-09 03:20:43 [error X 2][https://www.silkresse.com/wp-content/plugins/elementor/assets/js/editor.min.js?ver=3.10.0-dev1:3:811312] Cannot convert undefined or null to object
JS: 2022-11-17 22:00:07 [error X 4][https://www.silkresse.com/wp-content/plugins/elementor/assets/js/frontend.min.js?ver=3.10.0-dev1:2:32871] Can\'t find variable: elementorFrontendConfig
JS: 2023-01-10 04:51:46 [error X 69][https://www.silkresse.com/wp-admin/load-scripts.php?c=1&loadchunk_0=jquery-core,jquery-migrate,regenerator-runtime,wp-polyfill,jquery-ui-core,jquery-ui-mouse,underscore,backbone,wp-api-request,wp-&loadchunk_1=hooks&ver=6.1.1:2:51824] Cannot read properties of undefined (reading 'replace')
JS: 2023-01-11 15:19:35 [error X 1][https://www.silkresse.com/wp-content/plugins/elementor/assets/js/editor.min.js?ver=3.11.0-dev3:3:583495] Cannot read properties of null (reading 'id')
JS: 2023-01-11 17:27:40 [error X 3][https://www.silkresse.com/wp-content/plugins/elementor/assets/js/editor.min.js?ver=3.11.0-dev3:3:782318] Cannot read properties of undefined (reading 'toLowerCase')
JS: 2023-01-18 02:51:41 [error X 1][https://www.silkresse.com/wp-content/plugins/elementor/assets/js/web-cli.min.js?ver=3.11.0-dev3:3:105230] Routes: `library/templates` not found.
JS: 2023-01-19 04:31:23 [error X 1][https://www.silkresse.com/wp-content/plugins/elementor/assets/js/web-cli.min.js?ver=3.11.0-dev3:3:105230] Routes: `library/blocks` not found.
JS: 2023-01-19 04:31:26 [error X 1][https://www.silkresse.com/wp-content/plugins/elementor/assets/js/web-cli.min.js?ver=3.11.0-dev3:3:105230] Routes: `library/pages` not found.
JS: 2023-02-20 16:19:44 [error X 14][https://www.silkresse.com/wp-content/plugins/elementor/assets/js/editor.min.js?ver=3.12.0-dev4:3:794636] Cannot read properties of undefined (reading 'localized')
PHP: showing 5 of 5PHP: 2022-07-12 20:02:17 [notice X 120][/home/silkress/public_html/wp-content/plugins/elementor/modules/dev-tools/deprecation.php::301] The $finder_category_name argument is deprecated since version 3.5.0! [array (
'trace' => '
#0: Elementor\Core\Logger\Manager -> shutdown()
',
)]
PHP: 2022-07-12 20:05:38 [notice X 5][/home/silkress/public_html/wp-content/plugins/elementor/includes/widgets/traits/button-trait.php::553] Undefined index: icon [array (
'trace' => '
#0: Elementor\Core\Logger\Manager -> shutdown()
',
)]
PHP: 2022-09-12 19:12:19 [notice X 1][/home/silkress/public_html/wp-content/plugins/elementor/core/common/modules/ajax/module.php::171] Undefined index: data [array (
'trace' => '
#0: Elementor\Core\Logger\Manager -> shutdown()
',
)]
PHP: 2023-01-18 02:53:19 [notice X 2][/home/silkress/public_html/wp-content/plugins/elementor/core/page-assets/data-managers/font-icon-svg/font-awesome.php::50] Trying to access array offset on value of type null [array (
'trace' => '
#0: Elementor\Core\Logger\Manager -> shutdown()
',
)]
PHP: 2023-02-20 04:56:40 [notice X 21][/home/silkress/public_html/wp-content/plugins/elementor/includes/managers/image.php::108] Trying to access array offset on value of type bool [array (
'trace' => '
#0: Elementor\Core\Logger\Manager -> shutdown()
',
)]
Log: showing 20 of 202022-07-16 14:45:12 [info] elementor::elementor_updater Started
2022-07-16 14:45:12 [info] Elementor/Upgrades - _on_each_version Start
2022-07-16 14:45:12 [info] Elementor/Upgrades - _on_each_version Finished
2022-07-16 14:45:12 [info] Elementor/Upgrades - _v_3_7_0_remove_old_elements_usage Start
2022-07-16 14:45:12 [info] Elementor/Upgrades - _v_3_7_0_remove_old_elements_usage Finished
2022-07-16 14:45:12 [info] Elementor data updater process has been completed. [array (
'plugin' => 'Elementor',
'from' => '3.6.7',
'to' => '3.7.0-dev10',
)]
2022-07-16 14:45:12 [info] Elementor data updater process has been queued. [array (
'plugin' => 'Elementor',
'from' => '3.6.7',
'to' => '3.7.0-dev10',
)]
2022-11-09 02:20:27 [info] Elementor data updater process has been queued. [array (
'plugin' => 'Elementor',
'from' => '3.7.0-dev10',
'to' => '3.10.0-dev1',
)]
2022-11-09 02:20:27 [info] elementor::elementor_updater Started
2022-11-09 02:20:27 [info] Elementor/Upgrades - _on_each_version Start
2022-11-09 02:20:27 [info] Elementor/Upgrades - _on_each_version Finished
2022-11-09 02:20:27 [info] Elementor/Upgrades - _v_3_8_0_fix_php8_image_custom_size Start
2022-11-09 02:20:27 [info] Elementor/Upgrades - _v_3_8_0_fix_php8_image_custom_size Finished
2022-11-09 02:20:27 [info] Elementor data updater process has been completed. [array (
'plugin' => 'Elementor',
'from' => '3.7.0-dev10',
'to' => '3.10.0-dev1',
)]
2022-12-14 01:22:22 [info] Elementor data updater process has been queued. [array (
'plugin' => 'Elementor',
'from' => '3.10.0-dev1',
'to' => '3.11.0-dev1',
)]
2022-12-14 01:22:22 [info] elementor::elementor_updater Started
2022-12-14 01:22:22 [info] Elementor/Upgrades - _on_each_version Start
2022-12-14 01:22:22 [info] Elementor/Upgrades - _on_each_version Finished
2022-12-14 01:22:22 [info] Elementor data updater process has been completed. [array (
'plugin' => 'Elementor',
'from' => '3.10.0-dev1',
'to' => '3.11.0-dev1',
)]
2022-12-14 01:22:23 [info] Elementor data updater process has been queued. [array (
'plugin' => 'Elementor',
'from' => '3.10.0-dev1',
'to' => '3.11.0-dev1',
)]
== Elementor - Compatibility Tag ==
Essential Addons for Elementor: Incompatible
````
</details> | comp | ⛔ 🐞 bug report elementor created shop page defaults back to woocommerce standard shop page after assigning it in the settings after the page is assigned i’m unable to edit the page using elementor prerequisites i have searched for similar issues in both open and closed tickets and cannot find a duplicate the issue still exists against the latest stable version of elementor description when exactly did you first notice the problem i noticed this problem today when i finished modifying the shop all page and navigated to the woocommerce settings to assign this page as a woocommerce shop page have any updates been applied to your website recently updated the woocommerce templates that required an update have you changed themes or made design changes no theme changes have you installed any new plugins yes but i disabled and uninstalled it royal addons can the issue be replicated on multiple devices yes shop page shows incorrectly all devices is your problem happening in one browser or all of them all of them do you see a specific error message take a screenshot yes when i attempt to edit the page after assigning it to woocommerce i get the message the preview could not be loaded steps to reproduce created a shop page with elementor navigate to the woocommerce settings to assign this page as a woocommerce shop page navigate back to the page from the pages menu click the edit with elementor link get an error the preview could not be loaded img width alt screen shot at pm src img width alt screen shot at pm src img width alt screen shot at pm src isolating the problem this bug happens with only elementor plugin active and elementor pro this bug happens with a blank wordpress theme active i can reproduce this bug consistently following the steps above system info system info txt server environment operating system linux software litespeed mysql version mariadb server php version php memory limit php max input vars php max post size gd installed yes zip installed yes write permissions all right elementor library connected wordpress environment version site url home url wp multisite no max upload size mb memory limit max memory limit permalink structure blog postname language en us timezone admin email silkresse gmail com debug mode inactive theme name blocksy child version author creative themes child theme yes parent theme name blocksy parent theme version parent theme author creativethemes user role administrator wp profile lang en us user agent mozilla macintosh intel mac os x applewebkit khtml like gecko chrome safari active plugins advanced product fields for woocommerce version author studiowombat blocksy companion version author creativethemes codesigner version author codexpert elementor version author elementor com elementor beta developer edition version author elementor com elementskit lite version author wpmet essential addons for elementor version author wpdeveloper spotlight social media feeds version author rebelcode woocommerce version author automattic wpforms lite version author wpforms elementor experiments optimized dom output active by default improved asset loading active by default improved css loading active by default inline font icons active by default accessibility improvements active by default additional custom breakpoints active by default admin menu rearrangement inactive by default flexbox container active upgrade swiper library active by default editor inactive by default landing pages active by default nested elements active by default lazy load background images inactive by default save as default active by default log js showing of cannot read properties of undefined reading parent js cannot read properties of undefined reading data js cannot read properties of null reading getboundingclientrect js cannot read properties of undefined reading tolowercase js cannot read properties of undefined reading localized js elementor is not defined js cannot read properties of undefined reading replace js elementorfrontendconfig is not defined js cannot convert undefined or null to object js can t find variable elementorfrontendconfig js cannot read properties of undefined reading replace js cannot read properties of null reading id js cannot read properties of undefined reading tolowercase js routes library templates not found js routes library blocks not found js routes library pages not found js cannot read properties of undefined reading localized php showing of the finder category name argument is deprecated since version array trace elementor core logger manager shutdown php undefined index icon array trace elementor core logger manager shutdown php undefined index data array trace elementor core logger manager shutdown php trying to access array offset on value of type null array trace elementor core logger manager shutdown php trying to access array offset on value of type bool array trace elementor core logger manager shutdown log showing of elementor elementor updater started elementor upgrades on each version start elementor upgrades on each version finished elementor upgrades v remove old elements usage start elementor upgrades v remove old elements usage finished elementor data updater process has been completed array plugin elementor from to elementor data updater process has been queued array plugin elementor from to elementor data updater process has been queued array plugin elementor from to elementor elementor updater started elementor upgrades on each version start elementor upgrades on each version finished elementor upgrades v fix image custom size start elementor upgrades v fix image custom size finished elementor data updater process has been completed array plugin elementor from to elementor data updater process has been queued array plugin elementor from to elementor elementor updater started elementor upgrades on each version start elementor upgrades on each version finished elementor data updater process has been completed array plugin elementor from to elementor data updater process has been queued array plugin elementor from to elementor compatibility tag essential addons for elementor incompatible | 1 |
74,104 | 3,428,427,845 | IssuesEvent | 2015-12-10 09:30:34 | Itseez/opencv | https://api.github.com/repos/Itseez/opencv | closed | memory leak with videocapture, memory goes up with the function of read(image) | affected: master bug category: highgui-video priority: low | Hello! I am using opencv 3.0 beta with visual studio 2013 under windows 7 and 64bit. I downloaded opencv3.0 beta for windows from http://opencv.org/downloads.html.
The following is the code I am using to capture the video from rtsp stream and then save some frames every several minutes. It has no problem to capture and read the stream. But I found, the function "read(InputArrray Image)" cause the memory leak. The memory goes up slowly, about one MB for two or three hours. But it keep going up. I am using it for severy months continually. so it is seriouly problem for me. The following is my code for test. Please help me find out where is my problem with these code. Thanks a lot!
int main()
{
string fileNameSave;
string URLName;
BOOL stop = FALSE;
BOOL saveFrame = TRUE;
BOOL got_frame = FALSE;
string fileSave = "saveFrame.jpg";
URLName = "rtsp://username:password@IP adress:554/h264/ch1/main/av_stream";
VideoCapture capture;
Mat frame;
capture.open(URLName);
if (!capture.isOpened()){
cout << " channel 1st has error " << endl;
}
while (!stop){
got_frame = capture.read(frame); //here the memory keep goes up
//save the frame every minute locally
if (saveFrame == TRUE){
if (got_frame){
imwrite(fileSave, frame);
}
}
}
capture.release();
return 0;
}
| 1.0 | memory leak with videocapture, memory goes up with the function of read(image) - Hello! I am using opencv 3.0 beta with visual studio 2013 under windows 7 and 64bit. I downloaded opencv3.0 beta for windows from http://opencv.org/downloads.html.
The following is the code I am using to capture the video from rtsp stream and then save some frames every several minutes. It has no problem to capture and read the stream. But I found, the function "read(InputArrray Image)" cause the memory leak. The memory goes up slowly, about one MB for two or three hours. But it keep going up. I am using it for severy months continually. so it is seriouly problem for me. The following is my code for test. Please help me find out where is my problem with these code. Thanks a lot!
int main()
{
string fileNameSave;
string URLName;
BOOL stop = FALSE;
BOOL saveFrame = TRUE;
BOOL got_frame = FALSE;
string fileSave = "saveFrame.jpg";
URLName = "rtsp://username:password@IP adress:554/h264/ch1/main/av_stream";
VideoCapture capture;
Mat frame;
capture.open(URLName);
if (!capture.isOpened()){
cout << " channel 1st has error " << endl;
}
while (!stop){
got_frame = capture.read(frame); //here the memory keep goes up
//save the frame every minute locally
if (saveFrame == TRUE){
if (got_frame){
imwrite(fileSave, frame);
}
}
}
capture.release();
return 0;
}
| non_comp | memory leak with videocapture memory goes up with the function of read image hello i am using opencv beta with visual studio under windows and i downloaded beta for windows from the following is the code i am using to capture the video from rtsp stream and then save some frames every several minutes it has no problem to capture and read the stream but i found the function read inputarrray image cause the memory leak the memory goes up slowly about one mb for two or three hours but it keep going up i am using it for severy months continually so it is seriouly problem for me the following is my code for test please help me find out where is my problem with these code thanks a lot int main string filenamesave string urlname bool stop false bool saveframe true bool got frame false string filesave saveframe jpg urlname rtsp username password ip adress main av stream videocapture capture mat frame capture open urlname if capture isopened cout channel has error endl while stop got frame capture read frame here the memory keep goes up save the frame every minute locally if saveframe true if got frame imwrite filesave frame capture release return | 0 |
541,380 | 15,826,125,686 | IssuesEvent | 2021-04-06 06:59:11 | zephyrproject-rtos/zephyr | https://api.github.com/repos/zephyrproject-rtos/zephyr | closed | tests should not be silently skipped due to insufficient RAM | Stale area: Twister bug priority: low | **Describe the bug**
We have a problem in that if a testcase doesn't fit in target RAM, which would normally produce a build error, instead it just gets skipped:
```
INFO - 12/18 hifive1_revb tests/kernel/mem_protect/mem_protect/kernel.memory_protection SKIPPED (RAM overflow)
```
This is actually a serious problem. It can result in a particular test case being skipped on ALL platforms for a particular arch, and nobody will have any idea or visibility on this without careful inspection of the logs.
**To Reproduce**
See https://github.com/zephyrproject-rtos/zephyr/issues/30066 for an example.
This mem_protect test is uncovered completely on RiscV.
**Expected behavior**
At an absolute bare minimum, some way of ensuring that we don't completely lose code coverage for tests on at least a sub-architecture basis (examples of sub-architectures: x86 64 and 32-bit, ARM cortex-A, -R, -M)
One possibility is a flag in board.yaml indicating that skipping tests for memory reasons is forbidden. This could then be applied to all emulator targets.
**Impact**
Certain kernel features could end up with no code coverage and nobody aware that this is happening. | 1.0 | tests should not be silently skipped due to insufficient RAM - **Describe the bug**
We have a problem in that if a testcase doesn't fit in target RAM, which would normally produce a build error, instead it just gets skipped:
```
INFO - 12/18 hifive1_revb tests/kernel/mem_protect/mem_protect/kernel.memory_protection SKIPPED (RAM overflow)
```
This is actually a serious problem. It can result in a particular test case being skipped on ALL platforms for a particular arch, and nobody will have any idea or visibility on this without careful inspection of the logs.
**To Reproduce**
See https://github.com/zephyrproject-rtos/zephyr/issues/30066 for an example.
This mem_protect test is uncovered completely on RiscV.
**Expected behavior**
At an absolute bare minimum, some way of ensuring that we don't completely lose code coverage for tests on at least a sub-architecture basis (examples of sub-architectures: x86 64 and 32-bit, ARM cortex-A, -R, -M)
One possibility is a flag in board.yaml indicating that skipping tests for memory reasons is forbidden. This could then be applied to all emulator targets.
**Impact**
Certain kernel features could end up with no code coverage and nobody aware that this is happening. | non_comp | tests should not be silently skipped due to insufficient ram describe the bug we have a problem in that if a testcase doesn t fit in target ram which would normally produce a build error instead it just gets skipped info revb tests kernel mem protect mem protect kernel memory protection skipped ram overflow this is actually a serious problem it can result in a particular test case being skipped on all platforms for a particular arch and nobody will have any idea or visibility on this without careful inspection of the logs to reproduce see for an example this mem protect test is uncovered completely on riscv expected behavior at an absolute bare minimum some way of ensuring that we don t completely lose code coverage for tests on at least a sub architecture basis examples of sub architectures and bit arm cortex a r m one possibility is a flag in board yaml indicating that skipping tests for memory reasons is forbidden this could then be applied to all emulator targets impact certain kernel features could end up with no code coverage and nobody aware that this is happening | 0 |
31,516 | 6,543,845,578 | IssuesEvent | 2017-09-03 07:10:29 | sparkartgroup/gulp-markdown-to-json | https://api.github.com/repos/sparkartgroup/gulp-markdown-to-json | closed | frontmatter error handling | Defect | @pushred so today i tested new version and it has pretty much same errors as before
especially if i have error in front matter there is no file path shown
also if i don't put any `.on('error',` listeners then there is no error reporting at all and it's not noted in readme
| 1.0 | frontmatter error handling - @pushred so today i tested new version and it has pretty much same errors as before
especially if i have error in front matter there is no file path shown
also if i don't put any `.on('error',` listeners then there is no error reporting at all and it's not noted in readme
| non_comp | frontmatter error handling pushred so today i tested new version and it has pretty much same errors as before especially if i have error in front matter there is no file path shown also if i don t put any on error listeners then there is no error reporting at all and it s not noted in readme | 0 |
13,270 | 15,624,758,839 | IssuesEvent | 2021-03-21 04:22:39 | wpcache/wpcache | https://api.github.com/repos/wpcache/wpcache | opened | Polylang Compatibility | stat:awaiting type:compatibility | Please make sure that this compatibility has not been reported before.
**Compatibility Type:**
- [ ] WordPress Hosting Platforms
- [ ] Themes & Page Builders
- [ ] Plugins
- [ ] eCommerce
- [x] Multilingual
**Compatibility Info:**
- Name: Polylang
- Web: https://polylang.pro/
**Compatibility Tests:**
- [ ] Cache reads/writes expectedly
- [ ] Cache deletes/expires expectedly
**Additional Info:**
| True | Polylang Compatibility - Please make sure that this compatibility has not been reported before.
**Compatibility Type:**
- [ ] WordPress Hosting Platforms
- [ ] Themes & Page Builders
- [ ] Plugins
- [ ] eCommerce
- [x] Multilingual
**Compatibility Info:**
- Name: Polylang
- Web: https://polylang.pro/
**Compatibility Tests:**
- [ ] Cache reads/writes expectedly
- [ ] Cache deletes/expires expectedly
**Additional Info:**
| comp | polylang compatibility please make sure that this compatibility has not been reported before compatibility type wordpress hosting platforms themes page builders plugins ecommerce multilingual compatibility info name polylang web compatibility tests cache reads writes expectedly cache deletes expires expectedly additional info | 1 |
19,264 | 26,758,924,250 | IssuesEvent | 2023-01-31 04:13:34 | hammertater/treechop | https://api.github.com/repos/hammertater/treechop | closed | Crash while playing Triforge | bug compatibility | I was getting into a modpack I found called Triforge (v1.5.2) and I went to cut down a tree that had some branches after it got to the second log up, where the branches were, it crashed. The modpack uses 1.18.2-0.15.7 If anymore information is needed I would be glad to provide it. | True | Crash while playing Triforge - I was getting into a modpack I found called Triforge (v1.5.2) and I went to cut down a tree that had some branches after it got to the second log up, where the branches were, it crashed. The modpack uses 1.18.2-0.15.7 If anymore information is needed I would be glad to provide it. | comp | crash while playing triforge i was getting into a modpack i found called triforge and i went to cut down a tree that had some branches after it got to the second log up where the branches were it crashed the modpack uses if anymore information is needed i would be glad to provide it | 1 |
7,070 | 9,358,367,223 | IssuesEvent | 2019-04-02 02:06:24 | dotnet/winforms | https://api.github.com/repos/dotnet/winforms | closed | UAC shield icon no longer shows in preview 1 | bug tenet-compatibility up-for-grabs | The shield button is required to indicate a task requires elevation.
On .NET Framework it is possible to use Windows message to manipulate a button, for example
```c#
[DllImport("user32")]
public static extern uint SendMessage(IntPtr hWnd, uint msg, IntPtr wParam, IntPtr lParam);
internal const int BCM_SETSHIELD = (0x1600 + 0x000C); //Elevated button
private static void AddShieldToButton(Button b)
{
b.FlatStyle = FlatStyle.System;
SendMessage(b.Handle, BCM_SETSHIELD, IntPtr.Zero, (IntPtr)1);
}
```
This does not work on Preview 1, and no shield icon is displayed. | True | UAC shield icon no longer shows in preview 1 - The shield button is required to indicate a task requires elevation.
On .NET Framework it is possible to use Windows message to manipulate a button, for example
```c#
[DllImport("user32")]
public static extern uint SendMessage(IntPtr hWnd, uint msg, IntPtr wParam, IntPtr lParam);
internal const int BCM_SETSHIELD = (0x1600 + 0x000C); //Elevated button
private static void AddShieldToButton(Button b)
{
b.FlatStyle = FlatStyle.System;
SendMessage(b.Handle, BCM_SETSHIELD, IntPtr.Zero, (IntPtr)1);
}
```
This does not work on Preview 1, and no shield icon is displayed. | comp | uac shield icon no longer shows in preview the shield button is required to indicate a task requires elevation on net framework it is possible to use windows message to manipulate a button for example c public static extern uint sendmessage intptr hwnd uint msg intptr wparam intptr lparam internal const int bcm setshield elevated button private static void addshieldtobutton button b b flatstyle flatstyle system sendmessage b handle bcm setshield intptr zero intptr this does not work on preview and no shield icon is displayed | 1 |
216,637 | 16,778,163,268 | IssuesEvent | 2021-06-15 01:56:03 | cockroachdb/cockroach | https://api.github.com/repos/cockroachdb/cockroach | closed | roachtest: workload fails to connect to a node - connection timed out | A-testing C-bug O-robot X-stale no-issue-activity | SHA: https://github.com/cockroachdb/cockroach/commits/a22a3780ebb5482be04b6f31344c764b2fb5f765
Parameters:
To repro, try:
```
# Don't forget to check out a clean suitable branch and experiment with the
# stress invocation until the desired results present themselves. For example,
# using stress instead of stressrace and passing the '-p' stressflag which
# controls concurrency.
./scripts/gceworker.sh start && ./scripts/gceworker.sh mosh
cd ~/go/src/github.com/cockroachdb/cockroach && \
stdbuf -oL -eL \
make stressrace TESTS=kv0/enc=false/nodes=3/cpu=96 PKG=roachtest TESTTIMEOUT=5m STRESSFLAGS='-maxtime 20m -timeout 10m' 2>&1 | tee /tmp/stress.log
```
Failed test: https://teamcity.cockroachdb.com/viewLog.html?buildId=1257365&tab=buildLog
```
The test failed on release-19.1:
cluster.go:1423,kv.go:69,cluster.go:1761,errgroup.go:57: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/bin/roachprod run teamcity-1257365-kv0-enc-false-nodes-3-cpu-96:4 -- ./workload run kv --init --splits=1000 --histograms=logs/stats.json --concurrency=192 --duration=10m --read-percent=0 {pgurl:1-3} returned:
stderr:
stdout:
Error: dial tcp 10.12.41.6:26257: connect: connection timed out
Error: exit status 1
: exit status 1
cluster.go:1782,kv.go:72,kv.go:137,test.go:1245: Goexit() was called
``` | 1.0 | roachtest: workload fails to connect to a node - connection timed out - SHA: https://github.com/cockroachdb/cockroach/commits/a22a3780ebb5482be04b6f31344c764b2fb5f765
Parameters:
To repro, try:
```
# Don't forget to check out a clean suitable branch and experiment with the
# stress invocation until the desired results present themselves. For example,
# using stress instead of stressrace and passing the '-p' stressflag which
# controls concurrency.
./scripts/gceworker.sh start && ./scripts/gceworker.sh mosh
cd ~/go/src/github.com/cockroachdb/cockroach && \
stdbuf -oL -eL \
make stressrace TESTS=kv0/enc=false/nodes=3/cpu=96 PKG=roachtest TESTTIMEOUT=5m STRESSFLAGS='-maxtime 20m -timeout 10m' 2>&1 | tee /tmp/stress.log
```
Failed test: https://teamcity.cockroachdb.com/viewLog.html?buildId=1257365&tab=buildLog
```
The test failed on release-19.1:
cluster.go:1423,kv.go:69,cluster.go:1761,errgroup.go:57: /home/agent/work/.go/src/github.com/cockroachdb/cockroach/bin/roachprod run teamcity-1257365-kv0-enc-false-nodes-3-cpu-96:4 -- ./workload run kv --init --splits=1000 --histograms=logs/stats.json --concurrency=192 --duration=10m --read-percent=0 {pgurl:1-3} returned:
stderr:
stdout:
Error: dial tcp 10.12.41.6:26257: connect: connection timed out
Error: exit status 1
: exit status 1
cluster.go:1782,kv.go:72,kv.go:137,test.go:1245: Goexit() was called
``` | non_comp | roachtest workload fails to connect to a node connection timed out sha parameters to repro try don t forget to check out a clean suitable branch and experiment with the stress invocation until the desired results present themselves for example using stress instead of stressrace and passing the p stressflag which controls concurrency scripts gceworker sh start scripts gceworker sh mosh cd go src github com cockroachdb cockroach stdbuf ol el make stressrace tests enc false nodes cpu pkg roachtest testtimeout stressflags maxtime timeout tee tmp stress log failed test the test failed on release cluster go kv go cluster go errgroup go home agent work go src github com cockroachdb cockroach bin roachprod run teamcity enc false nodes cpu workload run kv init splits histograms logs stats json concurrency duration read percent pgurl returned stderr stdout error dial tcp connect connection timed out error exit status exit status cluster go kv go kv go test go goexit was called | 0 |
32,144 | 7,495,978,459 | IssuesEvent | 2018-04-08 03:44:38 | Microsoft/devkit-sdk | https://api.github.com/repos/Microsoft/devkit-sdk | closed | Error infomation contains build machine's path information | Bug Code Ready P2 | Package version: 1.3.2.44
Platform: Windows and Mac
when running examples, (such as getstarted), the following error message displays.
----------Error Message-----------------
201.\features\mbedtls\src\ssl_tls.c (3789): mbedtls_ssl_fetch_input() returned -27648 (-0x6c00)
.\features\mbedtls\src\ssl_tls.c (3734): mbedtls_ssl_read_record_layer() returned -27648 (-0x6c00)
.\features\mbedtls\src\ssl_tls.c (6577): mbedtls_ssl_read_record() returned -27648 (-0x6c00)
8-02-07 02:55:12 ERROR: File:C:\Users\v-fional\AppData\Local\Arduino15\packages\AZ3166\hardware\stm32f4\1.3.0\cores\arduino\az_iot\c-utility\adapters\socketio_mbed_os5.c Func:retrieve_data Line:172, Socketio_Failure: underlying IO error -3004.
2018-02-07 02:55:13 INFO: >>>Re-connect.
2018-02-07 02:55:13 ERROR: File:C:\Users\v-fional\AppData\Local\Arduino15\packages\AZ3166\hardware\stm32f4\1.3.0\cores\arduino\az_iot\umqtt\src\mqtt_client.c Func:sendPacketItem Line:332, 620: Failure sending control packet data
2018-02-07 02:55:13 ERROR: File:C:\Users\v-fional\AppData\Local\Arduino15\packages\AZ3166\hardware\stm32f4\1.3.0\cores\arduino\az_iot\umqtt\src\mqtt_client.c Func:mqtt_client_disconnect Line:1176, Error: mqtt_client_disconnect send failed
| 1.0 | Error infomation contains build machine's path information - Package version: 1.3.2.44
Platform: Windows and Mac
when running examples, (such as getstarted), the following error message displays.
----------Error Message-----------------
201.\features\mbedtls\src\ssl_tls.c (3789): mbedtls_ssl_fetch_input() returned -27648 (-0x6c00)
.\features\mbedtls\src\ssl_tls.c (3734): mbedtls_ssl_read_record_layer() returned -27648 (-0x6c00)
.\features\mbedtls\src\ssl_tls.c (6577): mbedtls_ssl_read_record() returned -27648 (-0x6c00)
8-02-07 02:55:12 ERROR: File:C:\Users\v-fional\AppData\Local\Arduino15\packages\AZ3166\hardware\stm32f4\1.3.0\cores\arduino\az_iot\c-utility\adapters\socketio_mbed_os5.c Func:retrieve_data Line:172, Socketio_Failure: underlying IO error -3004.
2018-02-07 02:55:13 INFO: >>>Re-connect.
2018-02-07 02:55:13 ERROR: File:C:\Users\v-fional\AppData\Local\Arduino15\packages\AZ3166\hardware\stm32f4\1.3.0\cores\arduino\az_iot\umqtt\src\mqtt_client.c Func:sendPacketItem Line:332, 620: Failure sending control packet data
2018-02-07 02:55:13 ERROR: File:C:\Users\v-fional\AppData\Local\Arduino15\packages\AZ3166\hardware\stm32f4\1.3.0\cores\arduino\az_iot\umqtt\src\mqtt_client.c Func:mqtt_client_disconnect Line:1176, Error: mqtt_client_disconnect send failed
| non_comp | error infomation contains build machine s path information package version platform windows and mac when running examples such as getstarted the following error message displays error message features mbedtls src ssl tls c mbedtls ssl fetch input returned features mbedtls src ssl tls c mbedtls ssl read record layer returned features mbedtls src ssl tls c mbedtls ssl read record returned error file c users v fional appdata local packages hardware cores arduino az iot c utility adapters socketio mbed c func retrieve data line socketio failure underlying io error info re connect error file c users v fional appdata local packages hardware cores arduino az iot umqtt src mqtt client c func sendpacketitem line failure sending control packet data error file c users v fional appdata local packages hardware cores arduino az iot umqtt src mqtt client c func mqtt client disconnect line error mqtt client disconnect send failed | 0 |
121,204 | 10,153,114,314 | IssuesEvent | 2019-08-06 02:58:30 | mozilla/iris_firefox | https://api.github.com/repos/mozilla/iris_firefox | closed | Fix search_suggestions_are_displayed_in_search_bar test case | regression test case | Fails on non-retina and retina osx line 46, duckduck go search engine icon pattern | 1.0 | Fix search_suggestions_are_displayed_in_search_bar test case - Fails on non-retina and retina osx line 46, duckduck go search engine icon pattern | non_comp | fix search suggestions are displayed in search bar test case fails on non retina and retina osx line duckduck go search engine icon pattern | 0 |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.