Investigate the accessibility rules configured in the jest-axe library.

Investigate the accessibility rules configured in the jest-axe library in fluent repo https://github.com/microsoft/fluentui/blob/d8321c5e8191f94e9413aee0e800f96d3de8e311/package.json#L251.
Our baseline is the accessibility insights web tool which keeps on adding more rules and checks in their releases.
Refer<EMAIL_ADDRESS>Are the rules in jest-axe dependency upto date.
If not, then how to update these rules to represent the current standard.
Assigned to @Shubhabrata08

The repo is at 6.0.1 whereas the latest is at 8.0.0.
axe-core has been updated from 4.4.1 to 4.7.2

Here are a list of changes as referred from axe-core's changelog at master branch
4.7.2 (2023-05-25)
Bug Fixes

aria-allowed-attr: Add 'aria-required' to switch role (#4029) (cb51be4), closes #4027
aria-allowed-attr: allow aria-required on role=slider (#4035) (bb2bf60)
aria-required-children: set related nodes for invalid children (#4033) (377f72b)
tags: Add / correct several TTv5 tags (#4031) (25859dd)

4.7.1 (2023-05-15)
Bug Fixes

aria-allowed-attr: no inconsistent aria-checked on HTML checkboxes (#3895) (704043e)
aria-allowed-attrs: add aria-expanded to allowed attrs for menuitemcheckbox and menuitemradio (#3994) (0f405c6)
aria-required-children: trigger reviewEmpty with hidden children (#4012) (a19b6cb)
color-contrast: support CSS 4 color spaces (#4020) (65621c3)
link-in-text-block: set links with pseudo-content for review (#4005) (949f4f8)

4.7.0 (2023-04-17)
Features

aria-roledescription: deprecate rule (#3948) (1913a9e)
aria-roles: deprecate the ARIA directory role (#3952) (893fdd0)
d.ts: setup/teardown, reporters & metadata definitions (#3966) (78264ee)
deprecate bower (#3889) (651d811)
deprecate color.filteredRectStack, color.getRectStack, and dom.visuallyContains (#3859) (3be2bad)
dom.focusDisabled,dom.isVisibleForScreenreader: support the inert attribute (#3857) (273c971)
metadata: add Trusted Tester tag (#3986) (1f6a2a6)
support the dialog element (#3902) (d4522cd)

Bug Fixes

aria-allowed-attrs: allow aria-description and aria-braille* attrs (#3956) (2842395)
aria-input-field-name: skip combobox popups (#3886) (3dcdd42)
aria-required-children: allow separator in menu(bar) (#3868) (ec9f507)
aria-required-children: do not fail for children with aria-hidden (#3949) (8714d6b)
aria-required-children: list elements that are not allowed (#3951) (cce7586)
autocomplete-valid: allow webauthn token (#3866) (fd3010f)
color-contrast: correcly apply opacity to foreground color (#3973) (d7db279)
color-contrast: correctly calculate contrast of flex/grid items with z-index (#3884) (cef96be)
color-contrast: correctly compute background color for elements with opacity (#3944) (c051fe8), closes #3932
color-contrast: correctly compute color contrast of  elements (#3847) (4c3a00c)
color-contrast: do not check contrast on elemets that are inerted (#3894) (da19946)
color-contrast: skip ligature icons (#3867) (9486288)
create-grid: correctly compute stack order for non-positioned stacking contexts (#3930) (8db2c24), closes #3932
css-orientation-lock: support the css rotate property (#3958) (c51f8bf)
focus-order-semantics: Add ARIA role article to list of valid roles for scrollable regions (#3927) (f029271)
is-icon-ligature: prevent canvas2d warning willReadFrequently (#3931) (b3c52bb)
link-in-text-block: allow links with identical colors (#3861) (5f90040)
respondable: work with CDP Page.setDocumentContent (#3921) (66f23e5)
scrollable-region-focusable: change impact to serious (#3959) (e3a5c21)
scrollable-region-focusable: skip native controls (#3862) (b0bdefa)

4.6.3 (2023-01-23)
Bug Fixes

aria-required-children: allow separator in menu(bar) (#3868) (46c9499)
autocomplete-valid: allow webauthn token (#3866) (a3d1b9d)
color-contrast: correctly compute color contrast of  elements (#3847) (844cea1)
color-contrast: skip ligature icons (#3867) (7dfbd9a)
link-in-text-block: allow links with identical colors (#3861) (6761f36)
scrollable-region-focusable: skip native controls (#3862) (aaf44e9)

4.6.2 (2022-12-23)
Bug Fixes

color-contrast: fix color-contrast check when running in an extension (#3838) (31a3e01)

4.6.1 (2022-12-14)
Bug Fixes

d.ts: add optional include to ContextObject (#3830) (36ed242)

4.6.0 (2022-12-12)
Features

aria-required-attr: require aria-controls on combobox and aria-valuenow on focusable separator (#3786) (5259e88)
checks/label-content-name-mismatch: deprecate occuranceThreshold option in favor of occurrenceThreshold to fix typo (#3782) (5026d65)
commons: deprecate flattenShadowColors in favor of flattenColors (#3792) (af49daf)
context: allow selecting shadow DOM nodes (#3798) (9e1e31b)
list,listitem: do not allow group as allowed parent or child (#3784) (d1cbf6f)
required-attr: require aria-checked for checkbox-like and radio-like roles (#3785) (563e4e9)
utils: new shadowSelectAll utility (#3796) (5865462)

Bug Fixes

aria-allowed-role: allow combobox on button, checkbox and combobox on input[type=button] (#3354) (ac688c0), closes #3353
aria-required-children: allow menu as child of menu (#3820) (a6569e5)
color-contrast: consider -webkit-text-stroke & -webkit-text-fill-color (#3791) (228daf1)
color-contrast: correctly calculate background color of text nodes with different size than their container (#3703) (123b83c)
get-role: handle presentation role inheritance for vnodes with no parent (#3801) (b971caf)
html-lang-valid: only run rule when attribute has value (#3663) (1a7eecb), closes #3624
metadata: Map aria-required-children to ACT rule bc4a75 (#3790) (a33a523)

4.5.2 (2022-11-14)
Bug Fixes

aria-required-children: allow menu and menubar to be empty (#3770) (d11aed8)
create-grid: include elements scrolled out of view in the grid (#3773) (a563263)
do not warn when using webpack (#3777) (d6cef9a)
link-in-text-block: don't match style or script text (#3775) (ab877f9)
prevent undefined relatedNodes from halting axe (#3778) (efefb18)

4.5.1 (2022-11-01)
Bug Fixes

allow axe to run in certain configurations of jsdom (#3755) (b74c5d4)
prevent crash on jsdom when preloading CSSOM (#3754) (b1f0c6b)

4.5.0 (2022-10-17)
Features
Highlights

new rule: Add WCAG 2.2 target-size rule (off by default) (#3616) (691f1b6)
new rule: Add meta-refresh-no-exceptions (off by default, wcag2aaa) (#3530) (27031a8)
identical-links-same-purpose: Disable by default (wcag2aaa rule) (#3615) (a2c2d2f)
link-in-text-block: Remove experimental and enable by default (#3706) (37b6e7a)
i18n: Add Norwegian Bokmål locale (#3375) (2886d33)
i18n: Add Hebrew translation (#3438) (b4162ed)

Tags and Metadata Updates
Various changes of tags, for greater consistency with ACT Rules.

area-alt: Remove the wcag111 tag (#3479) (1c3cc51)
aria-hidden-focus: Remove the wcag131 tag (#3477) (36ace76)
empty-table-headers: Rule is now best-practice and fails instead of incompletes (#3427) (0a4397d), closes #3404
frame-title: Remove wcag241 tag (#3519) (9c6b828)
input-image-alt: Add the wcag412 tag (#3478) (34272c6)
label,select-name: Remove the sc131 tag (#3476) (7caef89)
meta-viewport: Report as violation of wcag 1.4.4 (#3704) (6f7e4a9)
metadata: Update ACT tags & actIds (#3498) (571722b)

Deprecations

Deprecate Internet Explorer support (#3644) (11f5163)
Deprecate sri-history.json file (#3646) (6f6a89e)
Deprecate and replace dom.isVisible, utils.isHidden, and dom.isHiddenWithCss (#3351) (1ae2ac0)
Deprecate only-dlitems-evaluate & only-listitems-evaluate methods (#3724) (322e9ed)
Deprecate presentation-role-conflict-matchess (#3638) (0f02a15)
Deprecate is-visible-matches, use is-visible-on-screen-matches (#3679) (738dd8f)
Deprecate not-html-matches, use :not(html) instead (#3540) (e0010d9)

Others

aria-roles: Permit fallback roles (#3683) (5665260)
aria-required-children: Allow aria-busy on children (#3569) (3618f50)
aria-required-children: Fail for children which are not listed as required (#3597) (b5ceabc)
getRules: Return actIds when set (#3470) (a3d5cef)
is-in-tab-order: Add isInTabOrder to commons (#3619) (77afe90), closes #3500
list/definition-list: Only allow required owned roles (#3707) (a920d35)
presentation-role-conflict: Test img elements with empty alt (#3717) (ea32fa7)

Bug Fixes

utils: greatly improve the speed of querySelectorAll (#3423) (1cae5ea)
aria-hidden-focus: Do not fail for focus trap bumper elements (#3667) (46b6658)
aria-required-attr: aria-valuenow is no longer required for spinbutton (#3552) (a22cf56)
aria-required-parent: Allow nested group and presentational roles (#3492) (4685270)
aria-valid-attr-value: Report empty values as incomplete (#3635) (fff39db)
avoid-inline-spacing: Add spacing threshold (#3533) (92add05)
checks/no-focusable-disable: Don't count non-disableable elements as disabled (#3393) (bb8b5ca), closes #2466 #2934 #2934 #3315
checks/unsupportedrole: Support unsupported dpub and fallback roles, add role to message (#3395) (3c0f10f), closes #2466 #2934 #2934 #3282
color-contrast-enhanced: Avoid duplicates between color-contrast and color-contrast-enhanced (#3714) (2811f77)
color-contrast: Correctly determine color contrast for element that exactly overlaps midpoint of node (#3565) (90de9aa)
frame-focusable-content: don't fail for elements with negative tabindex (#3493) (94e75ac)
frame-title-unique: Make frame-title-unique reviewOnly and WCAG412 (#3610) (8401b8e), closes #3487
frame-title: ignore frames with negative tabindex (f61f825)
frame-title: return incomplete for presentational iframe with empty title (#3594) (c2cfd84)
is-hidden-for-everyone: count elements inside closed details as hidden (#3726) (e65e962)
is-hidden-for-everyone: support content-visibility: hidden (#3690) (95cf6e7)
is-visible-on-screen: ignore elements hidden by overflow:hidden (#3676) (2935950)
label: avoid passing labels because of an input[value] (#3688) (54a8116)
link-in-text-block: Update rule to match current guidance, revise tests (#3575) (edb88ed)
meta-refresh: Add WCAG's 20-hour exception (#3525) (5beb6c3)
no-autoplay-audio: add reviewOnFail and update tests (#3557) (60ec997)
object-alt: ignore unloaded objects (#3680) (8e03e2c)
page-has-heading-one,landmark-one-main: do not fail if modal is open (#3501) (c6af316)
td-headers-attr: ignore hidden cells with headers attr (#3684) (e0403f4)
td-headers-attr: ignore table elements with their role changed (#3687) (902d07c)
utils.matches: fix attribute exists selector to match empty attributes (#3669) (4b768ea)
valid-lang: ignore lang on elements with no text (#3523) (fd85f39)
valid-lang: run on aria-hidden text (#3634) (a0860bd)
video-caption: remove excludeHidden: false (#3554) (a3e4bbe)

4.4.3 (2022-07-13)
Bug Fixes

axe.d.ts: updates type definition for Rule to add reviewOnFail (#3521) (afb2478)
Continue supporting Node >=4 (#3538) (da7923b), closes #3537

4.4.2 (2022-05-12)
Bug Fixes

aria-hidden-focusable: report incomplete with onfocus (#3407) (6755e89)
aria-hidden-focus: Update rule help & description (#3422) (7cfb4b1)
aria-valid-attr-value: add note about element id being in a different shadow DOM tree (#3421) (24f74df)
color-contrast: consistently return color contrast information in the data object for pseudo elements (#3453) (1a9d95e)
deprecatedrole,color-contrast: fix message to properly include deprecated role, improve color-contrast pass messages (#3387) (650e503)
html-elms: update role allowances for nav element (#3402) (8aa816a), closes #3401
standards: fix address typo in html-elms.js (#3418) (f235cc7), closes #3417

Here are a list of changes to axe-core from v4.4.1 to v4.7.2
4.7.2 (2023-05-25)
Bug Fixes

aria-allowed-attr: Add 'aria-required' to switch role (#4029) (cb51be4), closes #4027
aria-allowed-attr: allow aria-required on role=slider (#4035) (bb2bf60)
aria-required-children: set related nodes for invalid children (#4033) (377f72b)
tags: Add / correct several TTv5 tags (#4031) (25859dd)

4.7.1 (2023-05-15)
Bug Fixes

aria-allowed-attr: no inconsistent aria-checked on HTML checkboxes (#3895) (704043e)
aria-allowed-attrs: add aria-expanded to allowed attrs for menuitemcheckbox and menuitemradio (#3994) (0f405c6)
aria-required-children: trigger reviewEmpty with hidden children (#4012) (a19b6cb)
color-contrast: support CSS 4 color spaces (#4020) (65621c3)
link-in-text-block: set links with pseudo-content for review (#4005) (949f4f8)

4.7.0 (2023-04-17)
Features

aria-roledescription: deprecate rule (#3948) (1913a9e)
aria-roles: deprecate the ARIA directory role (#3952) (893fdd0)
d.ts: setup/teardown, reporters & metadata definitions (#3966) (78264ee)
deprecate bower (#3889) (651d811)
deprecate color.filteredRectStack, color.getRectStack, and dom.visuallyContains (#3859) (3be2bad)
dom.focusDisabled,dom.isVisibleForScreenreader: support the inert attribute (#3857) (273c971)
metadata: add Trusted Tester tag (#3986) (1f6a2a6)
support the dialog element (#3902) (d4522cd)

Bug Fixes

aria-allowed-attrs: allow aria-description and aria-braille* attrs (#3956) (2842395)
aria-input-field-name: skip combobox popups (#3886) (3dcdd42)
aria-required-children: allow separator in menu(bar) (#3868) (ec9f507)
aria-required-children: do not fail for children with aria-hidden (#3949) (8714d6b)
aria-required-children: list elements that are not allowed (#3951) (cce7586)
autocomplete-valid: allow webauthn token (#3866) (fd3010f)
color-contrast: correcly apply opacity to foreground color (#3973) (d7db279)
color-contrast: correctly calculate contrast of flex/grid items with z-index (#3884) (cef96be)
color-contrast: correctly compute background color for elements with opacity (#3944) (c051fe8), closes #3932
color-contrast: correctly compute color contrast of  elements (#3847) (4c3a00c)
color-contrast: do not check contrast on elemets that are inerted (#3894) (da19946)
color-contrast: skip ligature icons (#3867) (9486288)
create-grid: correctly compute stack order for non-positioned stacking contexts (#3930) (8db2c24), closes #3932
css-orientation-lock: support the css rotate property (#3958) (c51f8bf)
focus-order-semantics: Add ARIA role article to list of valid roles for scrollable regions (#3927) (f029271)
is-icon-ligature: prevent canvas2d warning willReadFrequently (#3931) (b3c52bb)
link-in-text-block: allow links with identical colors (#3861) (5f90040)
respondable: work with CDP Page.setDocumentContent (#3921) (66f23e5)
scrollable-region-focusable: change impact to serious (#3959) (e3a5c21)
scrollable-region-focusable: skip native controls (#3862) (b0bdefa)

4.6.3 (2023-01-23)
Bug Fixes

aria-required-children: allow separator in menu(bar) (#3868) (46c9499)
autocomplete-valid: allow webauthn token (#3866) (a3d1b9d)
color-contrast: correctly compute color contrast of  elements (#3847) (844cea1)
color-contrast: skip ligature icons (#3867) (7dfbd9a)
link-in-text-block: allow links with identical colors (#3861) (6761f36)
scrollable-region-focusable: skip native controls (#3862) (aaf44e9)

4.6.2 (2022-12-23)
Bug Fixes

color-contrast: fix color-contrast check when running in an extension (#3838) (31a3e01)

4.6.1 (2022-12-14)
Bug Fixes

d.ts: add optional include to ContextObject (#3830) (36ed242)

4.6.0 (2022-12-12)
Features

aria-required-attr: require aria-controls on combobox and aria-valuenow on focusable separator (#3786) (5259e88)
checks/label-content-name-mismatch: deprecate occuranceThreshold option in favor of occurrenceThreshold to fix typo (#3782) (5026d65)
commons: deprecate flattenShadowColors in favor of flattenColors (#3792) (af49daf)
context: allow selecting shadow DOM nodes (#3798) (9e1e31b)
list,listitem: do not allow group as allowed parent or child (#3784) (d1cbf6f)
required-attr: require aria-checked for checkbox-like and radio-like roles (#3785) (563e4e9)
utils: new shadowSelectAll utility (#3796) (5865462)

Bug Fixes

aria-allowed-role: allow combobox on button, checkbox and combobox on input[type=button] (#3354) (ac688c0), closes #3353
aria-required-children: allow menu as child of menu (#3820) (a6569e5)
color-contrast: consider -webkit-text-stroke & -webkit-text-fill-color (#3791) (228daf1)
color-contrast: correctly calculate background color of text nodes with different size than their container (#3703) (123b83c)
get-role: handle presentation role inheritance for vnodes with no parent (#3801) (b971caf)
html-lang-valid: only run rule when attribute has value (#3663) (1a7eecb), closes #3624
metadata: Map aria-required-children to ACT rule bc4a75 (#3790) (a33a523)

4.5.2 (2022-11-14)
Bug Fixes

aria-required-children: allow menu and menubar to be empty (#3770) (d11aed8)
create-grid: include elements scrolled out of view in the grid (#3773) (a563263)
do not warn when using webpack (#3777) (d6cef9a)
link-in-text-block: don't match style or script text (#3775) (ab877f9)
prevent undefined relatedNodes from halting axe (#3778) (efefb18)

4.5.1 (2022-11-01)
Bug Fixes

allow axe to run in certain configurations of jsdom (#3755) (b74c5d4)
prevent crash on jsdom when preloading CSSOM (#3754) (b1f0c6b)

4.5.0 (2022-10-17)
Features
Highlights

new rule: Add WCAG 2.2 target-size rule (off by default) (#3616) (691f1b6)
new rule: Add meta-refresh-no-exceptions (off by default, wcag2aaa) (#3530) (27031a8)
identical-links-same-purpose: Disable by default (wcag2aaa rule) (#3615) (a2c2d2f)
link-in-text-block: Remove experimental and enable by default (#3706) (37b6e7a)
i18n: Add Norwegian Bokmål locale (#3375) (2886d33)
i18n: Add Hebrew translation (#3438) (b4162ed)

Tags and Metadata Updates
Various changes of tags, for greater consistency with ACT Rules.

area-alt: Remove the wcag111 tag (#3479) (1c3cc51)
aria-hidden-focus: Remove the wcag131 tag (#3477) (36ace76)
empty-table-headers: Rule is now best-practice and fails instead of incompletes (#3427) (0a4397d), closes #3404
frame-title: Remove wcag241 tag (#3519) (9c6b828)
input-image-alt: Add the wcag412 tag (#3478) (34272c6)
label,select-name: Remove the sc131 tag (#3476) (7caef89)
meta-viewport: Report as violation of wcag 1.4.4 (#3704) (6f7e4a9)
metadata: Update ACT tags & actIds (#3498) (571722b)

Deprecations

Deprecate Internet Explorer support (#3644) (11f5163)
Deprecate sri-history.json file (#3646) (6f6a89e)
Deprecate and replace dom.isVisible, utils.isHidden, and dom.isHiddenWithCss (#3351) (1ae2ac0)
Deprecate only-dlitems-evaluate & only-listitems-evaluate methods (#3724) (322e9ed)
Deprecate presentation-role-conflict-matchess (#3638) (0f02a15)
Deprecate is-visible-matches, use is-visible-on-screen-matches (#3679) (738dd8f)
Deprecate not-html-matches, use :not(html) instead (#3540) (e0010d9)

Others

aria-roles: Permit fallback roles (#3683) (5665260)
aria-required-children: Allow aria-busy on children (#3569) (3618f50)
aria-required-children: Fail for children which are not listed as required (#3597) (b5ceabc)
getRules: Return actIds when set (#3470) (a3d5cef)
is-in-tab-order: Add isInTabOrder to commons (#3619) (77afe90), closes #3500
list/definition-list: Only allow required owned roles (#3707) (a920d35)
presentation-role-conflict: Test img elements with empty alt (#3717) (ea32fa7)

Bug Fixes

utils: greatly improve the speed of querySelectorAll (#3423) (1cae5ea)
aria-hidden-focus: Do not fail for focus trap bumper elements (#3667) (46b6658)
aria-required-attr: aria-valuenow is no longer required for spinbutton (#3552) (a22cf56)
aria-required-parent: Allow nested group and presentational roles (#3492) (4685270)
aria-valid-attr-value: Report empty values as incomplete (#3635) (fff39db)
avoid-inline-spacing: Add spacing threshold (#3533) (92add05)
checks/no-focusable-disable: Don't count non-disableable elements as disabled (#3393) (bb8b5ca), closes #2466 #2934 #2934 #3315
checks/unsupportedrole: Support unsupported dpub and fallback roles, add role to message (#3395) (3c0f10f), closes #2466 #2934 #2934 #3282
color-contrast-enhanced: Avoid duplicates between color-contrast and color-contrast-enhanced (#3714) (2811f77)
color-contrast: Correctly determine color contrast for element that exactly overlaps midpoint of node (#3565) (90de9aa)
frame-focusable-content: don't fail for elements with negative tabindex (#3493) (94e75ac)
frame-title-unique: Make frame-title-unique reviewOnly and WCAG412 (#3610) (8401b8e), closes #3487
frame-title: ignore frames with negative tabindex (f61f825)
frame-title: return incomplete for presentational iframe with empty title (#3594) (c2cfd84)
is-hidden-for-everyone: count elements inside closed details as hidden (#3726) (e65e962)
is-hidden-for-everyone: support content-visibility: hidden (#3690) (95cf6e7)
is-visible-on-screen: ignore elements hidden by overflow:hidden (#3676) (2935950)
label: avoid passing labels because of an input[value] (#3688) (54a8116)
link-in-text-block: Update rule to match current guidance, revise tests (#3575) (edb88ed)
meta-refresh: Add WCAG's 20-hour exception (#3525) (5beb6c3)
no-autoplay-audio: add reviewOnFail and update tests (#3557) (60ec997)
object-alt: ignore unloaded objects (#3680) (8e03e2c)
page-has-heading-one,landmark-one-main: do not fail if modal is open (#3501) (c6af316)
td-headers-attr: ignore hidden cells with headers attr (#3684) (e0403f4)
td-headers-attr: ignore table elements with their role changed (#3687) (902d07c)
utils.matches: fix attribute exists selector to match empty attributes (#3669) (4b768ea)
valid-lang: ignore lang on elements with no text (#3523) (fd85f39)
valid-lang: run on aria-hidden text (#3634) (a0860bd)
video-caption: remove excludeHidden: false (#3554) (a3e4bbe)

4.4.3 (2022-07-13)
Bug Fixes

axe.d.ts: updates type definition for Rule to add reviewOnFail (#3521) (afb2478)
Continue supporting Node >=4 (#3538) (da7923b), closes #3537

4.4.2 (2022-05-12)
Bug Fixes

aria-hidden-focusable: report incomplete with onfocus (#3407) (6755e89)
aria-hidden-focus: Update rule help & description (#3422) (7cfb4b1)
aria-valid-attr-value: add note about element id being in a different shadow DOM tree (#3421) (24f74df)
color-contrast: consistently return color contrast information in the data object for pseudo elements (#3453) (1a9d95e)
deprecatedrole,color-contrast: fix message to properly include deprecated role, improve color-contrast pass messages (#3387) (650e503)
html-elms: update role allowances for nav element (#3402) (8aa816a), closes #3401
standards: fix address typo in html-elms.js (#3418) (f235cc7), closes #3417

Issue fixed with PR# https://github.com/microsoft/fluentui/pull/30309


No callback to handle database_error event

I've just been trying to get Firestack set up on a brand new project using the FirestackModule and have found an issue when a database permission error is thrown on iOS.
In database.js, a native success and error listener are added for "database_event" and "database_error".  However, in FirestackDatabase.m, both the database events and errors are sent with the "database_event" identifier.
This means that an error is subsequently thrown in database.js as there is no callback registered against a "database_error" type.
I'm happy to submit a PR to make sure that FirestackDatabase.m sends the event as "database_error" but wanted to check there wasn't a reason they're currently sent with the same type before I did?
I'm assuming it's an oversight as the Java code appears to emit the two events separately.

Added PR https://github.com/fullstackreact/react-native-firestack/pull/58 as one way of fixing this issue

Awesome! Thanks for the PR. Good spot.


Theme and Category Name not showing

Current state :
The current eos-icons-figma plugin does not contains the titles like theme and category which makes it harder for a user to differentiate between the two select components

Expected state :
Proper titles should be added to avoid confusion between the two select components.

I am working on this issue


Standart HTTP component

taking a look at the docs it seems that sub-classing "Component" is the only way to add a custom component (and registering it here which requires modifying the project source code, I was wondering if its possible to just add a generic HTTP component. The HTTP component would then be able to communicate with any back-end for integrating any pre-existing pipelines, in this case users would just need to add a simple REST interface which RASA can send incoming messages to.

if you think that's a good idea, I would be willing to make a pull request.

Thanks for raising this issue, @tmbo  will get back to you about it soon.

You do not need to change the code, you can also reference the component without putting it into the registry (referencing it by full class path) - should be stated like that in the docs.
But I think the http component might still be useful. What would be your use case for that?

We had a pre-existing pipeline that does some preprocessing specific to our use case, I was just thinking about making a simple REST that RASA could send messages to for preprocessing. what I ended up doing is that I retrofitted our pre-existing code to be in the form of RASA components, on the same note I was wondering what would be the idiomatic why to feed an audio input into RASA?
I can work on implementation, if you decide to add this component.

@abdelrahman-t is this something you're still working on?

no, I am happy to work on it though If you decide to add this feature to RASA.

hm actually wait, does the REST channel not cover this? https://rasa.com/docs/core/connectors/#rest-channels

I think this is only used to receive message and send back bot responses, however this feature proposes a way to plug any pre-existing component to RASA-NLU pipeline, any component that implements a REST API can be integrated, for instance my original use case was that we had pre-existing pipeline written in Java and we needed to migrate to RASA, so I was thinking about just making A REST API that wraps the pipline and then add an HTTP component to RASA-NLU that would just send message to the API.

ah got it. @tmbo what do you think, does it make sense to add this?


Testing Package Upgrade

Make sure you have checked all steps below.
JIRA

[ ] My PR addresses the following Airflow JIRA issues and references them in the PR title. For example, "[AIRFLOW-XXX] My Airflow PR"

https://issues.apache.org/jira/browse/AIRFLOW-XXX
In case you are fixing a typo in the documentation you can prepend your commit with [AIRFLOW-XXX], code changes always need a JIRA issue.

Description

[ ] Here are some details about my PR, including screenshots of any UI changes:

Tests

[ ] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

[ ] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Documentation

[ ] In case of new functionality, my PR adds documentation that describes how to use it.

When adding new operators/hooks/sensors, the autoclass documentation generation needs to be added.

Code Quality

[ ] Passes git diff upstream/master -u -- "*.py" | flake8 --diff

Codecov Report

Merging #4 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master       #4   +/-   ##
=======================================
  Coverage   76.84%   76.84%
=======================================
  Files         204      204
  Lines       15485    15485
=======================================
  Hits        11899    11899
  Misses       3586     3586

Impacted Files
Coverage Δ

airflow/www_rbac/views.py
71.57% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 985a433...1cb417d. Read the comment docs.


not storing card when creating user

Cashier Version: 10.1
Laravel Version: 6
PHP Version: 7
Database Driver & Version: current

Description:
I am creating a new app using Cashier 10.1. In the past I would send a token from Stripe to the subscription function when registering a user with a subscription. Now it says it takes a Payment Method (id). I am registering a payment method with Stripe and passing that to my controller but it returns the error "This customer has no attached payment source". I read the docs but it only gives an example of how to add a subscription to a current user by passing to the view $user->createSetupIntent(). Below is the code for when a user registers:
Steps To Reproduce:
Component
       pay() {
            this.isLoading = true;

            if (this.form.payment_method == "cc") {
                let that = this;
                this.stripe
                    .createPaymentMethod({
                        type: "card",
                        card: that.card
                    })
                    .then(result => {
                        this.form.stripePayment = result.paymentMethod.id;
                        this.register();
                    })
                    .catch(e => {
                        console.log(e);
                    });
            } else {
                this.register();
            }
        },

        register() {
            this.form
                .post("/register")
                .then(data => {
                    this.isLoading = false;
                    if (data.type == "success") {
                        this.$swal({
                            type: "success",
                            title: "Great...",
                            text: data.message,
                            toast: true,
                            position: "top-end",
                            showConfirmButton: false,
                            timer: 2000
                        });

                        setTimeout(() => {
                            // window.location.replace(data.url);
                        }, 2000);
                    }
                })
                .catch(error => {
                    this.isLoading = false;
                });
        }

RegisterController
protected function create(request $request)
    {
        $request->validate([
            'name' => 'required',
            'email' => 'required|unique:users',
            'username' => 'required|alpha_dash|unique:users',
            'phone' => 'required',
            'city' => 'required',
            'state' => 'required',
            'password' => 'required|confirmed',
            'agree' => 'required',
        ]);

        $user = User::create([
            'username' => $request['username'],
            'name' => $request['name'],
            'email' => $request['email'],
            'phone' => $request['phone'],
            'city' => $request['city'],
            'state' => $request['state'],
            'password' => Hash::make($request['password']),
        ]);

        if ($request['subscription_type'] == 'premier' && $request['payment_method'] == 'cc') {

            $user->newSubscription('default',  env('STRIPE_PLAN_ID'))->create($request->input('stripePayment'), [
                'email' => $request['email'],
            ]);
        }

        if ($user) {
            $user->assignRole('subscriber');

            Auth::login($user);

            return response()->json([
                'type' => 'success',
                'message' => 'you are all set.',
                'url' => '/dashboard'
            ]);
        }

Hi there,
Thanks for reporting but it looks like this is a question which can be asked on a support channel. Please only use this issue tracker for reporting bugs with the library itself. If you have a question on how to use functionality provided by this repo you can try one of the following channels:

Laracasts Forums
Laravel.io Forums
StackOverflow
Discord
Larachat
IRC

However, this issue will not be locked and everyone is still free to discuss solutions to your problem!
Thanks.


Make it possible to remove projects from "Shared with me"

Description
I'd like to be able to remove projects from under "Shared with me".
I do not think this is currently possible. The delete symbol is obviously gone, since they're read-only, but there should be a way to simply remove them.

Use Case
After clicking on a bunch of shared documents my interface is cluttered with projects I'd like to remove. This seems like a basic feature to have.

Done

@reknih the button currently only appears when the projects are displayed as a grid, and not as a table.

Sorry for the oversight!


Device Reconnection

Manually disconnecting the device actually does more than just disconnecting, it also "unpairs" the device from the app, meaning it unregisters the device and removes its connection information from the connection file in the app's LocalState folder. This causes "reconnect to previous session" to not work (the app looks at the connection file and sees it is empty) and then no indication of success or failure is given to the user.
We should consider making it clearer that pairing and unpairing a device (which registers and unregisters its connection info) is different than connecting and disconnecting a device.

Currently connecting == registering and disconnecting == unregistering.  Do you have a suggestion how to split these? I would love to work with the community to make the tool easier to use and understand.

Yea, I noticed that when the device is unplugged and plugged back in again the heartbeat listener detects those changes and updates the UI to show the device's connection status in real time to the user. Right now, since connecting == registering and disconnecting == unregistering, device pairing does not feel very persistent.
In my team's work flow, we often deploy an app to several devices to test, and then need to quickly wipe these devices to check them back in (we have a pool of shared devices). To avoid having to constantly pair and unpair devices, it would be great if, when we use this app, we could assemble a list of all our paired devices (we have about 20) and give that file to all of our engineers. Then whenever someone runs the app it automatically connects to known devices on startup.

I currently have a change in my fork that allows for connecting/registering devices that cannot be reached. when they become available, they light up. is that something that would help your team? We used a variant of this at //build this year with a good deal of success.
I would also love to hear suggestions to making this better. Would renaming connect -> register and disconnect -> unregister help? What about allowing a user provided device collection file?

Yea, that change in your fork definitely sounds useful! Also, I agree with renaming connect and disconnect. We discussed doing the same thing on our team.
The user provided device collection file could potentially be good too. I think for right now we just want to have the app automatically reconnect with a device on startup (assuming you've paired it once before). That alone would be a huge time saver.

Auto-reconnect was a feature of a much older version (pre-open source) of the Commander. It was removed because of perf (and the desire to generally start with a clean slate) in favor of the Reconnect menu/button.
I am planning on adding a Settings button where we could add a checkbox to enable/disable auto-reconnect on startup.  Sound good?
Oh, and i'll make the UI rename (ex: connect->register) in my fork for my next PR.

Yea! I really like the idea of enable/disable. That will give our team the flexibility to speed stuff up while also accommodating other use cases. Awesome!
It is interesting to learn that auto-reconnect was scrapped from an earlier version. I will let my team know.
Thanks for listening to our feedback.

Auto reconnect is #127 and will be checked in independent of the UI rename.

UI rename will be part of the Connection Behavior change that is currently in testing

Connection behavior is in PR #128.
Auto-reconnect and save/load sessions are in testing in my fork.

closed with pr #133


Error when opening any file that launches a lsp

Describe the bug
Very recently I started to get the error shown in the screenshot below whenever I open a file that causes an LSP server to be launched. This happens for all LSP servers and not just clangd which is what is shown in the screenshot.
The nvim-lsp-installer.lua file that is mentioned in the error output is my config file for nvim-lsp-installer and contains the following:
local nvim_lsp = require('lspconfig')

-- Use an on_attach function to only map the following keys
-- after the language server attaches to the current buffer
local on_attach = function(client, bufnr)
  local function buf_set_keymap(...) vim.api.nvim_buf_set_keymap(bufnr, ...) end
  local function buf_set_option(...) vim.api.nvim_buf_set_option(bufnr, ...) end

  -- Enable completion triggered by <c-x><c-o>
  buf_set_option('omnifunc', 'v:lua.vim.lsp.omnifunc')

  -- Mappings.
  local opts = { noremap=true, silent=true }

  -- See `:help vim.lsp.*` for documentation on any of the below functions
  buf_set_keymap('n', 'gD', '<cmd>lua vim.lsp.buf.declaration()<CR>', opts)
  buf_set_keymap('n', 'gd', '<cmd>lua vim.lsp.buf.definition()<CR>', opts)
  buf_set_keymap('n', 'K', '<cmd>lua vim.lsp.buf.hover()<CR>', opts)
  buf_set_keymap('n', 'gi', '<cmd>lua vim.lsp.buf.implementation()<CR>', opts)
  buf_set_keymap('n', '<C-k>', '<cmd>lua vim.lsp.buf.signature_help()<CR>', opts)
  buf_set_keymap('n', '<space>wa', '<cmd>lua vim.lsp.buf.add_workspace_folder()<CR>', opts)
  buf_set_keymap('n', '<space>wr', '<cmd>lua vim.lsp.buf.remove_workspace_folder()<CR>', opts)
  buf_set_keymap('n', '<space>wl', '<cmd>lua print(vim.inspect(vim.lsp.buf.list_workspace_folders()))<CR>', opts)
  buf_set_keymap('n', '<space>D', '<cmd>lua vim.lsp.buf.type_definition()<CR>', opts)
  buf_set_keymap('n', '<space>rn', '<cmd>lua vim.lsp.buf.rename()<CR>', opts)
  buf_set_keymap('n', '<space>ca', '<cmd>lua vim.lsp.buf.code_action()<CR>', opts)
  buf_set_keymap('n', 'gr', '<cmd>lua vim.lsp.buf.references()<CR>', opts)
  buf_set_keymap('n', '<space>e', '<cmd>lua vim.lsp.diagnostic.show_line_diagnostics()<CR>', opts)
  buf_set_keymap('n', '[d', '<cmd>lua vim.lsp.diagnostic.goto_prev()<CR>', opts)
  buf_set_keymap('n', ']d', '<cmd>lua vim.lsp.diagnostic.goto_next()<CR>', opts)
  buf_set_keymap('n', '<space>q', '<cmd>lua vim.lsp.diagnostic.set_loclist()<CR>', opts)
  buf_set_keymap('n', '<space>f', '<cmd>lua vim.lsp.buf.formatting()<CR>', opts)

end

-- Add additional capabilities supported by nvim-cmp
local capabilities = vim.lsp.protocol.make_client_capabilities()
capabilities = require('cmp_nvim_lsp').update_capabilities(capabilities)

local lsp_installer = require("nvim-lsp-installer")
lsp_installer.on_server_ready(function(server)
  --[[
  local opts = {
    on_attach = on_attach,
    flags = {
      debounce_text_changes = 150,
    },
    capabilities = capabilities,
  }
  --]]
  opts = {}

  server:setup(opts)
end)

Expected behavior
The LSP server to launch without error and then work.
Screenshots

System info (please complete the following information):

OS: Ubuntu 20.04
Neovim version: v0.6.0-dev

Install log
If applicable, include nvim-lsp-installer's logs. See :help nvim-lsp-installer-debugging for instructions on how to set the log level and access the logs.
Paste your logs here

Hello! At first glance I'm not sure what could be happening here. I'll try to step through the call stack in your screenshot and see if there's anything obvious. Have you tried latest nightly build, does it still happen?

@matiasvc Having the same exact problem, with the same system info and similar config.

It does not seem to be happening any longer. So possible this was a bug in nvim-lsp-installer, or I suspect, in a dependency that has now been fixed.

I spoke too soon. It worked for a moment, then I opened a different C++ file and I got this error
Error detected while processing FileType Autocommands for "cpp":
E5108: Error executing lua /usr/share/nvim/runtime/lua/vim/lsp.lua:97: filename: expected string, got nil
stack traceback:
        /usr/share/nvim/runtime/lua/vim/lsp.lua:97: in function 't'
        vim/shared.lua:547: in function 'is_valid'
        vim/shared.lua:565: in function 'validate'
        /usr/share/nvim/runtime/lua/vim/lsp.lua:220: in function 'validate_client_config'
        /usr/share/nvim/runtime/lua/vim/lsp.lua:640: in function 'start_client'
        .../pack/packer/start/nvim-lspconfig/lua/lspconfig/util.lua:267: in function 'add'
        ...ck/packer/start/nvim-lspconfig/lua/lspconfig/configs.lua:220: in function 'try_add'
        [string ":lua"]:1: in main chunk

My entire neovim config is available here if that is of any help in debugging.

That is very odd. What is also odd is that I sync neovim config between my personal and work machine, and this error never appears on my work machine. Only my personal machine.

This is an interesting piece of information. There are similar reports in for example https://github.com/nvim-lualine/lualine.nvim/issues/462, where core maintainers seem to believe it might be due to a LuaJIT bug.
What's your personal and work computer specs, respectively?

architecture (Intel/ARM/etc)
platform (Debian/macOS/etc.)
which version of Neovim (which exact repo/built from source)

Both machines are x86_64. Personal is AMD, work is Intel.
Both machines use Ubuntu. Personal is 20.04, work is 18.04.
Both machines use http://ppa.launchpad.net/neovim-ppa/unstable/ubuntu which I update almost daily.

How are you opening the buffer? Do you have a recording or something? Are you editing an existing file like :e file.c or do you launch it directly from command line like nvim file.c? I've only taken a quick look at this so far, but I believe it might be trying to start a "single file" instance of the LSP server.

Also, do you have any of the following files in any of the parent directories of the file you're editing:

compile_commands.json
compile_flags.txt
.git/

So, did some tests and came up with some interesting results.
I created an empty folder with a main.cpp file in it.
If I edit the file using nvim main.cpp I get the following errors:
[nvim-lsp-installer] /usr/share/nvim/runtime/lua/vim/lsp.lua:97: filename: expected string, got nil
stack traceback:
^I/usr/share/nvim/runtime/lua/vim/lsp.lua:97: in function 't'
^Ivim/shared.lua:547: in function 'is_valid'
^Ivim/shared.lua:565: in function 'validate'
^I/usr/share/nvim/runtime/lua/vim/lsp.lua:220: in function 'validate_client_config'
^I/usr/share/nvim/runtime/lua/vim/lsp.lua:640: in function 'start_client'
^I.../pack/packer/start/nvim-lspconfig/lua/lspconfig/util.lua:267: in function 'add'
^I...ck/packer/start/nvim-lspconfig/lua/lspconfig/configs.lua:220: in function 'try_add'
^I...ck/packer/start/nvim-lspconfig/lua/lspconfig/configs.lua:236: in function 'try_add_wrapper'
^I...art/nvim-lsp-installer/lua/nvim-lsp-installer/server.lua:80: in function 'attach_buffers'
^I...art/nvim-lsp-installer/lua/nvim-lsp-installer/server.lua:69: in function 'setup'
^I...matiasvc/.config/nvim/lua/plugins/nvim-lsp-installer.lua:56: in function <...matiasvc/.config/nvim/lua/plugins/nvim-lsp-installer.lua:45>
^I[C]: in function 'pcall'
^I...nvim-lsp-installer/lua/nvim-lsp-installer/dispatcher.lua:9: in function 'dispatch_server_ready'
Press ENTER or type command to continue
^I...cker/start/nvim-lsp-installer/lua/nvim-lsp-installer.lua:220: in function <...cker/start/nvim-lsp-installer/lua/nvim-lsp-installer.lua:217>
Press ENTER or type command to continue

If I instead do just open nvim with nvim and then do :e main.cpp I still get an error, however a slightly different one:
Error detected while processing FileType Autocommands for "cpp":
E5108: Error executing lua /usr/share/nvim/runtime/lua/vim/lsp.lua:97: filename: expected string, got nil
stack traceback:
        /usr/share/nvim/runtime/lua/vim/lsp.lua:97: in function 't'
        vim/shared.lua:547: in function 'is_valid'
        vim/shared.lua:565: in function 'validate'
        /usr/share/nvim/runtime/lua/vim/lsp.lua:220: in function 'validate_client_config'
        /usr/share/nvim/runtime/lua/vim/lsp.lua:640: in function 'start_client'
        .../pack/packer/start/nvim-lspconfig/lua/lspconfig/util.lua:267: in function 'add'
        ...ck/packer/start/nvim-lspconfig/lua/lspconfig/configs.lua:220: in function 'try_add'
        [string ":lua"]:1: in main chunk
Press ENTER or type command to continue

If I however create an empty compile_command.json file or do git init to create a .git folder. Then both methods of opening the file works. The clangd LSP is launched and connected to the buffer and all LSP features works as expected.

Have you upgraded lspconfig recently? I can't really repro (only tried on Mac so far)

Yes, my nvim-lspconfig plugin is up to date. Made sure to upgrade to the very latest version just now, and the error still happens.

@matiasvc Could you try using
use { "williamboman/nvim-lspconfig", branch = "use-bufnr" }

Tried it. And I get the exact same errors as I posted above.

Hmm could you try pulling the latest commit and report what messages you get when opening the file? I get
:messages
new_config.root_dir: /private/var/folders/ky/s6yyhm_d24d0jsrql4t8k4p40000gn/T/tmp.DcF39T4hdM
root_dir: /private/var/folders/ky/s6yyhm_d24d0jsrql4t8k4p40000gn/T/tmp.DcF39T4hdM
fs_realpath(root_dir): /private/var/folders/ky/s6yyhm_d24d0jsrql4t8k4p40000gn/T/tmp.DcF39T4hdM

The path of the main.cpp file is /home/matiasvc/Downloads/test/main.cpp.
When running nvim main.cpp I get:
:messages
new_config.root_dir: /home/matiasvc/Downloads/test
root_dir: /home/matiasvc/Downloads/test
fs_realpath(root_dir): /home/matiasvc/Downloads/test
[nvim-lsp-installer] /usr/share/nvim/runtime/lua/vim/lsp.lua:97: filename: expected string, got nil
stack traceback:
^I/usr/share/nvim/runtime/lua/vim/lsp.lua:97: in function 't'
^Ivim/shared.lua:547: in function 'is_valid'
^Ivim/shared.lua:565: in function 'validate'
^I/usr/share/nvim/runtime/lua/vim/lsp.lua:220: in function 'validate_client_config'
^I/usr/share/nvim/runtime/lua/vim/lsp.lua:640: in function 'start_client'
^I.../pack/packer/start/nvim-lspconfig/lua/lspconfig/util.lua:270: in function 'add'
^I...ck/packer/start/nvim-lspconfig/lua/lspconfig/configs.lua:220: in function 'try_add'
^I...ck/packer/start/nvim-lspconfig/lua/lspconfig/configs.lua:236: in function 'try_add_wrapper'
^I...opt/nvim-lsp-installer/lua/nvim-lsp-installer/server.lua:80: in function 'attach_buffers'
^I...opt/nvim-lsp-installer/lua/nvim-lsp-installer/server.lua:69: in function 'setup'
^I...matiasvc/.config/nvim/lua/plugins/nvim-lsp-installer.lua:56: in function <...matiasvc/.config/nvim/lua/plugins/nvim-lsp-installer.lua:45>
^I[C]: in function 'pcall'
^I...nvim-lsp-installer/lua/nvim-lsp-installer/dispatcher.lua:9: in function 'dispatch_server_ready'
^I...packer/opt/nvim-lsp-installer/lua/nvim-lsp-installer.lua:222: in function <...packer/opt/nvim-lsp-installer/lua/nvim-lsp-installer.lua:219>

Running nvim and then :e main.cpp gives:
:messages
new_config.root_dir: /home/matiasvc/Downloads/test
root_dir: /home/matiasvc/Downloads/test
fs_realpath(root_dir): /home/matiasvc/Downloads/test
Error detected while processing FileType Autocommands for "cpp":
E5108: Error executing lua /usr/share/nvim/runtime/lua/vim/lsp.lua:97: filename: expected string, got nil
stack traceback:
        /usr/share/nvim/runtime/lua/vim/lsp.lua:97: in function 't'
        vim/shared.lua:547: in function 'is_valid'
        vim/shared.lua:565: in function 'validate'
        /usr/share/nvim/runtime/lua/vim/lsp.lua:220: in function 'validate_client_config'
        /usr/share/nvim/runtime/lua/vim/lsp.lua:640: in function 'start_client'
        .../pack/packer/start/nvim-lspconfig/lua/lspconfig/util.lua:270: in function 'add'
        ...ck/packer/start/nvim-lspconfig/lua/lspconfig/configs.lua:220: in function 'try_add'
        [string ":lua"]:1: in main chunk

Adding a .git folder I get the same prints without the error:
nvim main.cpp:
new_config.root_dir: /home/matiasvc/Downloads/test
root_dir: /home/matiasvc/Downloads/test
fs_realpath(root_dir): /home/matiasvc/Downloads/test

nvim + :e main.cpp:
new_config.root_dir: /home/matiasvc/Downloads/test
root_dir: /home/matiasvc/Downloads/test
fs_realpath(root_dir): /home/matiasvc/Downloads/test

Thanks @matiasvc, I'm at a loss atm 😂. Just one last thing, what's your exact neovim version?

nvim --version gives:
NVIM v0.6.0-dev
Build type: RelWithDebInfo
LuaJIT 2.1.0-beta3
Compilation: /usr/bin/cc -g -O2 -ffile-prefix-map=/build/neovim-hjJJHL/neovim-0.5.0+ubuntu2+git202108071752-35041432b-d569569c9=. -flto=auto -ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -DNVIM_TS_HAS_SET_MATCH_LIMIT -O2 -g -Og -g -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wshadow -Wconversion -Wmissing-prototypes -Wimplicit-fallthrough -Wvla -fstack-protector-strong -fno-common -fdiagnostics-color=auto -DINCLUDE_GENERATED_DECLARATIONS -D_GNU_SOURCE -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -DMIN_LOG_LEVEL=3 -I/build/neovim-hjJJHL/neovim-0.5.0+ubuntu2+git202108071752-35041432b-d569569c9/build/config -I/build/neovim-hjJJHL/neovim-0.5.0+ubuntu2+git202108071752-35041432b-d569569c9/src -I/build/neovim-hjJJHL/neovim-0.5.0+ubuntu2+git202108071752-35041432b-d569569c9/.deps/usr/include -I/usr/include -I/build/neovim-hjJJHL/neovim-0.5.0+ubuntu2+git202108071752-35041432b-d569569c9/build/src/nvim/auto -I/build/neovim-hjJJHL/neovim-0.5.0+ubuntu2+git202108071752-35041432b-d569569c9/build/include
Compiled by buildd@lcy01-amd64-002

Features: +acl +iconv +tui
See ":help feature-compile"

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/usr/share/nvim"

Run :checkhealth for more info

If it's any help. I ran into this error as well, but only when I opened vim for a directory view. If I opened in directly to file it was fine..

Hi,
I've encountered same issue after I updated both nvim-lspconfig and nvim-lsp-installer to latest.
When I revert to nvim-lspconfig commit 4f72377 and nvim-lsp-installer commit e65e4966, then everything works again. Those commits are simply the version I was using before updating.
Hope the info can help to narrow down the problem.

Are you folks sure you're running neovim 0.5.1 or later (lspconfig and now lsp-installer has a soft requirement on 0.6.0)? I'm simply unable to repro this, I even tried using your public neovim configs @cgjosephlee.
The only time I'm able to reproduce this is when using the 0.5.0 release:
Error detected while processing FileType Autocommands for "cpp":
E5108: Error executing lua ...3FztwWkk/nvim-linux64/share/nvim/runtime/lua/vim/lsp.lua:97: filename: expected string, got nil
stack traceback:
        ...3FztwWkk/nvim-linux64/share/nvim/runtime/lua/vim/lsp.lua:97: in function 't'
        vim/shared.lua:541: in function 'is_valid'
        vim/shared.lua:559: in function 'validate'
        ...3FztwWkk/nvim-linux64/share/nvim/runtime/lua/vim/lsp.lua:220: in function 'validate_client_config'
        ...3FztwWkk/nvim-linux64/share/nvim/runtime/lua/vim/lsp.lua:644: in function 'start_client'
        ...share/nvim/plugged/nvim-lspconfig/lua/lspconfig/util.lua:278: in function 'add'
        ...re/nvim/plugged/nvim-lspconfig/lua/lspconfig/configs.lua:239: in function 'try_add'
        [string ":lua"]:1: in main chunk

I was using vim 0.5.0. After upgrading to 0.6.1, the issues are solved. Thank you.


Missing period at the end of setup mobile app locally document

Describe the Issue
in the docs, there is a line that is missing period at the end of it.

We also recommend installing the official extensions

These should have period in the end of it
Here is the markdown file /docs/how-to-setup-freecodecamp-mobile-app-locally.md
Additional context
Please make sure you read our guidelines for contributing, we prioritize contributors following the instructions in our guides. Join us in our chat room or the forum if you need help contributing, our moderators will guide you through this.
Sometimes we may get more than one pull requests. We typically accept the most quality contribution, followed by the one that is made first.
Happy contributing.

I will work on that


support mariadb

can it support mariadb?

yeah it would be easy to add, i don't use mariadb or have time. if you make a pr i'll merge it


Migration to fabric-shim

As composer will no longer be getting updates from Fabric version 1.3, several people and projects, I imagine, would be looking to shift to either using go or nodejs for the chaincode.
I myself am migrating to nodejs and would like to create a public repository to demonstrate this exact same code base using nodejs but will require some additional collaborators to help out. Looking for some guidance.
Not sure where to post this so I opened an issue over here, hope that is ok with you. I am keen to learn and thought this is a good way to give back as well.

@varunagarwal315 - it is our plan to migrate this to Fabric and away from Composer.  We will have another pattern for this.  We should have this in Q1.

@ljbennett62 OK sounds great, but as I am in the process of learning myself, I would love to have a chance to contribute to the new repo/ migration as I am going to start migrating my pilot on supply chain using composer, away from composer as well.
Please let me know how I can contribute to the new pattern.

Those looking at this, the new repo should be https://github.com/ljbennett62/decentralized-energy-fabric
@ljbennett62 Please confirm, then I can close this issue.
Out of curiosity, any reason why people are using fabric-contract-api over fabric-shim (apart from less boilerplate). I have only used the shim APIs

@varunagarwal315 - so that is a temporary location - I will be moving this to the IBM org. I will be moving this week.  We are using fabric-contract-api based on guidance from the Blockchain documentation for using this with VS Code Blockchain extension.

@varunagarwal315 - I have transferred the updating decentralized energy to the IBM org: https://github.com/IBM/decentralized-energy-fabric-on-IBP20

Great, I close this issue then?
On Mon, 18 Feb 2019 11:18 ljbennett62<EMAIL_ADDRESS>wrote:

@varunagarwal315 https://github.com/varunagarwal315 - I have
transferred the updating decentralized energy to the IBM org:
https://github.com/IBM/decentralized-energy-fabric-on-IBP20
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/IBM/Decentralized-Energy-Composer/issues/37#issuecomment-464594090,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALuN-_2mBXD0r7CjwFyfoHaC4mSMvSbuks5vOj6fgaJpZM4Y7EKB
.

@varunagarwal315 - yes please - tx


Fix issue 48

fixes #48

@mietcls has this come up?

@mietcls ok, will fix merge conflict then

will replace this PR..

replaced by https://github.com/ugent-library/deliver/pull/84


[SPARK-24266][k8s] Back port spark 28423 to 2.4 to restart watcher

What changes were proposed in this pull request?
This patch processes the HTTP Gone event and restarts the pod watcher.
Why are the changes needed?
This is a backport of PR #28423 to branch-2.4.
The reasons are explained in SPARK-24266 that spark jobs using the k8s resource scheduler may hang.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
This was rolled into an image that is deployed into our test cluster.
We have not yet seen the hangs but will need more time to be confident.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Mistakenly forgot to redirect this at branch-2.4 now fixed.

@liyinan926 FYI

Thank you for making a backporting PR, @jkleckner .
Could you make a backporting PR to branch-3.0 first?
To prevent any regression from 2.4 to 3.0, we have a policy for backporting sequence. We cannot backport this to branch-2.4 directly.
BTW, cc @holdenk since she is the committer of the original PR.

@dongjoon-hyun  This originated on the master branch [1] as part of [2] and this patch is already the rework of that logic to pull it back to version 2.4.  Undoing that logic ought to result in [1].
It certainly deserves some scrutiny to ensure that it is reasonable.
[1] https://github.com/apache/spark/commit/0432379f9923768a767566e9ac5a4021cfe8d052
[2] https://github.com/apache/spark/pull/28423

@dongjoon-hyun After talking with Mike, we aren't sure how or whether to proceed since this is an attempt to backport apache/spark#28423 which is already merged to master.  What would be the steps?

You can make another backporting PR against on branch-3.0 while keeping this PR.
After that PR is merging, we can revisit here.

My blind spot while reading was that I thought it had already been merged into 3.0 and didn't realize it was only on master, sorry.

Ok, I created PR #29533 for branch 3.0.

We have also run into problems due to this issue. Since it is not clear, is this fix going to be part of the next 2.4.X release?

You are on the wrong thread. Currently, we are working on #29533 . Please comment on there to support @jkleckner . After that PR, we may restart to discuss on 2.4.x.

@SQUIDwarrior FYI, I have an image with the patch here [1] if you want to try it out (and of course you can build it for yourself).  It was built from this branch [2].
[1] registry.gitlab.com/jkleckner/spark/spark:v2.4.7-cphy1
[2] https://gitlab.com/jkleckner/spark/-/tags/v2.4.7-cphy1

@jkleckner Hi Jim, tried your fix and into a strange issue that makes the spark-submit quit immediately, with driver proceeding:
java.net.SocketException: Socket closed
	at java.net.SocketInputStream.socketRead0(Native Method)
	at java.net.SocketInputStream.socketRead(SocketInputStream.java:116)
	at java.net.SocketInputStream.read(SocketInputStream.java:171)
	at java.net.SocketInputStream.read(SocketInputStream.java:141)
	at sun.security.ssl.InputRecord.readFully(InputRecord.java:465)
	at sun.security.ssl.InputRecord.read(InputRecord.java:503)
	at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:990)
	at sun.security.ssl.SSLSocketImpl.readDataRecord(SSLSocketImpl.java:948)
	at sun.security.ssl.AppInputStream.read(AppInputStream.java:105)
	at okio.Okio$2.read(Okio.java:140)
	at okio.AsyncTimeout$2.read(AsyncTimeout.java:237)
	at okio.RealBufferedSource.request(RealBufferedSource.java:68)
	at okio.RealBufferedSource.require(RealBufferedSource.java:61)
	at okio.RealBufferedSource.readByte(RealBufferedSource.java:74)
	at okhttp3.internal.ws.WebSocketReader.readHeader(WebSocketReader.java:117)
	at okhttp3.internal.ws.WebSocketReader.processNextFrame(WebSocketReader.java:101)
	at okhttp3.internal.ws.RealWebSocket.loopReader(RealWebSocket.java:274)
	at okhttp3.internal.ws.RealWebSocket$2.onResponse(RealWebSocket.java:214)
	at okhttp3.RealCall$AsyncCall.execute(RealCall.java:206)
	at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)

Applying patch on top of 2.4.6.

@shockdm This is an attempt to backport the master branch fix which has that behavior [1].
Also this works fine in our environment for a while now.
As mentioned above [2], we are using further than v2.4.6 [3] since we wanted to bring in as many fixes as possible.
We launch using the spark-operator-on-k8s [4] mechanism with this version [5] and have not tried any other launch method.
So it is quite possible that there are issues with directly launching - how do you launch?
[1] https://github.com/apache/spark/blob/master/resource-managers/kubernetes/core/src/main/scala/org/apache/spark/deploy/k8s/submit/LoggingPodStatusWatcher.scala#L114
[2] https://github.com/apache/spark/pull/29496#issuecomment-682251482
[3] https://gitlab.com/jkleckner/spark/-/tags/v2.4.7-cphy1
[4] https://github.com/GoogleCloudPlatform/spark-on-k8s-operator
[5] https://gitlab.com/jkleckner/spark-on-k8s-operator/-/commit/f30dd1535220813315eea282a3d868aeb14cacb3

@jkleckner We are launching directly via a spark-submit invocation with the scheduler url set to kube api. That must be the difference. We are not using https://github.com/GoogleCloudPlatform/spark-on-k8s-operator.

@shockdm Post back on the thread here if you determine that this is cause.  Very likely would apply to the master branch as well.
If you have an example you would like me to run with something like spark-pi with specific arguments, I would be happy to run that in my environment.


[CoreText] Address multiple abandoned TODOs

There are few TODOs that are not being tracked in CoreText:

[ ] DWriteWrapper_CTFont::473
// TODO: The symbolic traits below are poorly documented/have no clear DWrite mapping
// kCTFontUIOptimizedTrait
// kCTFontCompositeTrait

[ ] DWriteWrapper_CTFont::477
// TODO: The upper 16 bits of symbolic traits describe stylistic aspects of a font, specifically its serifs,
// such as modern, ornamental, or sans (no serifs)
// DWrite has no such API for characterizing fonts

[ ] DWriteWrapper_CoreText::202
// TODO::
// Note here we only look at attribute value at first index of the specified range as we can get a default font size to use here.
`  // Per string range attribute handling will be done in _CreateDWriteTextLayout.

[ ] DWriteWrapper_CoreText::245
// TODO::
// We need too support widthFunc semantic to be able to support NSLayout*. We could either change the API signature of this API or
// create a new API to support dynamic width support.
//
// float width = widthFunc(widthParam, 0, 0, fontSize);

[ ] DWriteWrapper_CoreText::264
// TODO::
// Iterate through all attributed string ranges and identify attributes so they can be used to -
//  - set indentation
//  - etc.
//  These can be done using the DWrite IDWriteTextFormat range property methods.

[ ] DWriteWrapper_CoreText::434
// TODO:: find more precise value than 1.0 to increase width by to fully enclose frame

[ ] DWriteWrapper_CoreText::487
// TODO::
// This is a temp workaround until we can have actual glyph origins

[ ] DWriteWrapper_CoreText::555
// TODO:: find more precise value than 1.0 to increase width by to fully enclose frame

[ ] DWriteWrapper_CoreText::53 & CTFramesetter::92
The bug number #1121 associated with the TODO does correlate to the bug, is this valid?
// TODO 1121:: DWrite does not support line breaking by truncation, so just use clipping for now
// TODO 1121:: DWrite does not support line breaking by truncation, so we are using clipping, so need to adjust for truncation as well

@ms-jihua @aballway  Please take a look

DWriteWrapper_CTFont.mm::473, 477 : can probably just remove the TODO: portion of the comment and leave the comment - I don't think we can ever address these.
DWriteWrapper_CoreText.mm::202 : this doesn't actually seem like a TODO, just a comment
DWriteWrapper_CoreText::53 & CTFramesetter::92: this seems like the wrong issue number...?

DWriteWrapper_CoreText::53 & CTFramesetter::92: yea it looks like I put the wrong issue number on those, my b.
DWriteWrapper_CoreText::245: this is no longer needed and can be removed.
DWriteWrapper_CoreText::487: this depends on DWrite support but should not be necessary and can safely be removed
DWriteWrapper_CoreText::434, 555: This could be associated with a github issue if we wanted.  We could still look into finding a more precise value but 1 em is indistinguishably small, and has and will continue to suffice if we don't care to invest in perfecting it.


[DO NOT MERGE] Replace UA ecommerce tracking attributes with GA4 specific ones

What

Replaces UA ecommerce tracking attributes with GA4 specific ones in our GA4 ecommerce / smart answer trackers
Do not merge until these are deployed: https://github.com/alphagov/finder-frontend/pull/3195 and https://github.com/alphagov/smart-answers/pull/6591
I have tested this branch with a local version of finder-frontend running https://github.com/alphagov/finder-frontend/pull/3195, and used a diff checker to compare the dataLayer from this branch with the dataLayer currently on integration. I couldn't spot any issues with these changes. I have also done this with smart-answers.

Why

This is to decouple our GA4 analytics code from universal analytics
https://trello.com/c/gFiJmH3D/553-audit-and-ensure-that-every-data-attribute-relies-on-has-ga4-somewhere-in-its-name

Visual Changes

None.

@AshGDS are you okay to merge this? Happy to sort out deployment.


Species probability classes

I'm curious to learn about the probability class definition; where are they defined and on which basis? Is there any (scientific) documentation on that?

I'm not sure I can follow. If you have further information, let us know

As an addition: on the bottom of https://birdnet.cornell.edu you can find all scientific publications about BirdNET - thats all the scientific documentation that is available.

Thanks for replying. What I meant is the definition of classification categories: "Almost certain", "Highly uncertain", "uncertain" etc.: which ranges of uncertainty are you using for the app? Is there any documentation on that?

The probabilities of the categories should be the following:
Almost certain: >= 85 %
Highly likely: >= 65 %
Likely: >= 25%
Uncertain: >= 5%
Highly uncertain: >= 1.5%
Only a wild guess: < 1.5%


DevEx #621 updateGame() Refactor

Issue number
Relevant issue number

Resolves #621
Resolves #126

Please check the following

[x] Do the tests still pass? (see Run the Tests)
[x] Is the code formatted properly? (see Linting (Formatting))
For New Features:

[ ] Have tests been added to cover any new features or fixes?
[ ] Has the documentation been updated accordingly?

Please describe additional details for testing this change

Refactored updateGame() to dynamically update all the variables
Renamed state variables to better match what comes in from the game object

I'm not 100% sure this is the right way to go with this, but I believe looping through the object keys gets rid of the need for hasOwnProperty() and the nullish coalescing is a backup

@seriouslysean any thoughts on this?

I don’t have a lot of time to look at this, I’m in Disney for a couple more days. I can try and take another look tonight but I need to better understand what the purpose of the function is and the requirements and order of operations.
It might help if you documented some of those things and went through the changes you made and why? Don’t feel like you have to, @itsalaidbacklife likely knows more about this than I do, but it would help me give some more targeted feedback.

So the thought behind this is to remove calling .hasOwnProperty a bunch of times to check if the key-value pair is in the object and then set it to the corresponding store value, why not just loop through the object and set the store values based on what is in the object, considering almost all of them are the same name as the socket sends over. The if blocks are for the few edge cases like the cards that use a constructor to build them

It seems like just checking the props you need directly with optional chaining instead of hasOwnProperty might serve the same purpose without the complexity of requiring a loop and key check? You could also make a map and have some discrete functions for each of the actions, something like this:
const actionMap = {
    optionalKey1: optionalKey1Fn,
    optionalKey2: optionalKey2Fn,
};

Then you could break up the function and abstract the individual tasks to specific areas like this:
Object.keys(game).forEach(k => actionMap[k](game));

Okay, so I finally got back to this, and I refactored it to use nullish coalescing optional chaining, and the OR operator, I used the OR operator to set stuff back to itself if theres nothing inside the newGame object to match it, this way things like ID are never undefined

@itsalaidbacklife @seriouslysean any thoughts on this? Should we change this up or maybe wait until we change up the backend to implement this change?


fix: tx count in block search result

closes #1421

:tada: This PR is included in version 1.190.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


deps: Bump proxy_wasm_cpp_host -> 5d76116 (+ related deps)

Also bump

com_github_wamr -> 1.2.2
com_github_wasmtime -> 9.0.3

Fix #27748

Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

requires https://github.com/proxy-wasm/proxy-wasm-cpp-host/pull/355

cc @PiotrSikora thanks for help - seems to work once everything is updated
cc @RyanTheOptimist i think this one is high priority as i would like to backport it to pending releases

Are you going to backport proxy-wasm-cpp-host?

Are you going to backport proxy-wasm-cpp-host?

yeah its there already on the bp stacks - im just adding some final stuff to them

https://github.com/envoyproxy/envoy/pulls?q=is%3Apr+is%3Aopen+bp


Fix failing EQC test on GC manager [JIRA: RCS-285]

Test code update that amends code change at #1234 .
ok /= {postcondition,
          {'EXIT',
              {{badmatch,
                   {ok,{idle,not_running,
                           {gc_manager_state,undefined,undefined,[],
                               undefined,infinity,undefined,undefined}}}},
               [{riak_cs_gc_manager_eqc,postcondition,5,
                    [{file,"test/riak_cs_gc_manager_eqc.erl"},{line,164}]},
                {eqc_statem,run_commands,2,
                    [{file,"../src/eqc_statem.erl"},{line,737}]},
                {eqc_fsm,run_commands,2,
                    [{file,"../src/eqc_fsm.erl"},{line,658}]},
                {riak_cs_gc_manager_eqc,'-prop_manual_commands/0-fun-2-',1,
                    [{file,"test/riak_cs_gc_manager_eqc.erl"},{line,115}]}]}}}
riak_cs_gc_manager_eqc:81: eqc_test_...*failed*
in function riak_cs_gc_manager_eqc:'-eqc_test_/0-fun-8-'/1 (test/riak_cs_gc_manager_eqc.erl, line 81)
**error:{assertEqual_failed,[{module,riak_cs_gc_manager_eqc},
                     {line,81},
                     {expression,"eqc : quickcheck ( eqc : testing_time ( 30 , ? QC_OUT ( prop_manual_commands ( ) ) ) )"},
                     {expected,true},
                     {value,false}]}

Nice catch! Works as advertised :smile:

@borshop merge

No release note needed as this is a test code fix.


Feature Request:  Enable Renaming in by_vars Parameter

Feature Idea
For all functions (where it makes sense) the by_vars argument should allow renaming like the dplyr *_join() functions and derive_vars_joined().
Relevant Input
No response
Relevant Output
No response
Reproducible Example/Pseudo Code
adtr <- derive_vars_merged(
  tr,
  dataset_add = tu,
  new_vars = vars(TULOC),
  by_vars = vars (STUDYID, USUBID, TRLNKID = TULINKID)
)

@gg106046 can you finish this for v0.10 release?  Release is planned for March 5th - ideally one week before but there is some wiggle room.

@bms63 I should be able to do this by end of Feb.

@gg106046 can you finish this for v0.10 release? Release is planned for March 5th - ideally one week before but there is some wiggle room.

@bms63 I should be able to do this by end of Feb.

Identified the following functions that involve merging of 2 datasets with the argument by_vars:  derive_var_last_dose_amt, derive_var_last_dose_date, derive_var_last_dose_grp, derive_var_merged_cat, derive_var_merged_character, derive_var_merged_exist_flag, derive_var_merged_summary, derive_vars_joined, derive_vars_joined, derive_vars_merged, derive_vars_merged_lookup, derive_vars_transposed, derive_locf_records . Just putting it here for reference.


[1.16.5 FABRIC] the config is not in the config folder

AE2AO update : AE2AO-13.0.0
Since there is no config I can't change it

I'm sorry, I can't understand what this is connected with, try this version: https://www.curseforge.com/minecraft/mc-mods/ae2ao/files/4064777

site doesn't work

=

tried the alpha 13.0.1 and no config in config folder


[P2P / runtime] chore: p2p connection type

Description
Replaces boolean IsEmptyConnectionType with enum ConnectionType in P2PConfig to enable future support for additional connection types.
Issue
Fixes #268
Type of change
Please mark the relevant option(s):

[ ] New feature, functionality or library
[ ] Bug fix
[ ] Code health or cleanup
[ ] Major breaking change
[ ] Documentation
[x] Other: chore

List of changes

move ConnectionType enum into its own package to avoid a cyclic import between configs and defaults packages (i.e. configs -> defaults -> configs) in the resulting, generated go package
update makefile protogen_local target to build additional proto file and include it in the import path for runtime/configs/proto/p2p_config.proto
replace P2PConfig#IsEmptyConnectionType with P2PConfig#ConnectionType
replace DefaultP2PIsEmptyConnectionType with DefaultP2PConnectionType

Testing

[x] make develop_test
[x] LocalNet w/ all of the steps outlined in the README

Required Checklist

[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[x] I have tested my changes using the available tooling
[x] I have updated the corresponding CHANGELOG

If Applicable Checklist

[ ] I have updated the corresponding README(s); local and/or global
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added, or updated, mermaid.js diagrams in the corresponding README(s)
[ ] I have added, or updated, documentation and mermaid.js diagrams in shared/docs/* if I updated shared/*README(s)

@bryanchriswhite Friendly reminder :)

One more minor change request. See the definition of PROTOC as to why I'm suggesting it.
The only reason I'm not approving yet is that I saw you didn't check the LocalNet checkbox of the testing section. Until we have automated E2E tests, can you confirm that works?

No worries, regarding localnet: I made an attempt to follow the localnet instructions but lost the thread around steps 4/5:

Check the state of each node
Trigger the next view to ensure everything is working

I'm not sure what "working" looks like yet (expected behavior), is any other documentation that elaborates on this?

I'm not sure what "working" looks like yet (expected behavior), is any other documentation that elaborates on this?

Discussed offline but covering here.
The gif in https://github.com/pokt-network/pocket/blob/main/docs/development/README.md is a bit outdated but that's the closest "source of truth" we have for working at the moment. Simply making sure that the height increases from the logs.
We'll automate the test and improve the docs over time, but a manual sanity check of that for now should suffice.

@Olshansk after actually taking a second to read a bit of the makefile and get more familiar with the docker-compose file, I gave it another go and things seems to be making more sense, and indeed working. :smile: I think maybe what I was seeing before was related to timeouts but having no awareness of them (I'm blaming sensory overload :sweat_smile:).

FYI: that last force-push was me changing my mind about how I think it makes sense to handle merge conflict resolutions in changelogs genrally. In this case the upstream change had a newer date, but the same version.
I've collected my thoughts on the matter and opened #461.

@bryanchriswhite Make sure to squash-and-merge the PR with the Github's PR description as the commit message.


Fix: apply_ufunc with exclude_dims and vectorize

[x] Closes #3890
[x] Tests added
[x] Passes isort -rc . && black . && mypy . && flake8
[x] Fully documented, including whats-new.rst for all changes and api.rst for new API

This would be pretty useful when using apply_ufunc for e.g. statistical tests  that require vectorize=True and can consume data of unequal length (i.e. uses exclude_dims). This should also extend to dask arrays with dask="parallelized" once #4060 is implemented.

Sounds good. I can move _enumerate into to_gufunc_string. I think it makes sense to wait for #4060.

Inplemented @shoyer's suggestion to add exclude_dims as optional argument to to_gufunc_string. The readthedocs error is a timeout so should be fine to review.

The readthedocs error is a timeout

Unfortunately not. The timeout happened because of an error and the traceback is visible. The timeout doesn't happen on my own setup, so I asked support to help fix that. They removed stale memory constraints so now the traceback is visible, but somehow the build still times out.
In this case pandas has a minimum version requirement for xarray, but the detected version is 0.1. I'm not sure why that works for me but not for you, maybe because you didn't update the tags on your repo in a long time?

Thanks keewis! I don't think I would have figured that out. I pushed the tags to my fork.

But unfortunately this doesn't help :( If you have another idea I am all ears. But anyways it should not stop anyone from reviewing.

on my own setup the build completes: https://readthedocs.org/projects/xarray-keewis/builds/11696307/ So this is definitely an issue with the setup, but I don't know how to fix that...

@keewis In the xarray setup there is --prune-tags. In your setup this is not there. Not sure, if this might be connected.

thanks, @kmuehlbauer, good spot. However, that seems to come from the PR build (see also https://readthedocs.org/projects/xray/builds/11695402/, which doesn't fail), so I guess there has to be something in the code that changes the version.

the merge seems to have fixed it. Not sure why it didn't work before.

Thanks @keewis!


Adding slot field global_slot_number to PC block

Adding slot field global_slot_number to precomputed block (corresponding struct and impl), which corresponds to global_slot_since_genesis. This adds support for staking ledgers (current and next) at epoch boundaries and therefore unblocking that issue.

Looking closer at this, everything we need is already there! Let precomputed_block: PrecomputedBlock. Then global_slot_since_genesis can be obtained via precomputed_block.protocol_state.body.t.t.consensus_state.t.t.global_slot_since_genesis.t.t.

@Isaac-DeFrain I'm unsure if this works. If you have some free time in the morning, maybe we should sync up to discuss.

Commands cargo fmt, cargo clippy and cargo build all execute / working fine, but GitHub CI / Rustfmt is not passing (all others are so 6/7) because some tests are failing, so I'll update the logic for those tests.

Looking closer at this, everything we need is already there! Let precomputed_block: PrecomputedBlock. Then global_slot_since_genesis can be obtained via precomputed_block.protocol_state.body.t.t.consensus_state.t.t.global_slot_since_genesis.t.t.

@Isaac-DeFrain I'm unsure if this works. Is this .t your OCaml passion sneaking into some Rust code ;) If you have some free time in the morning, maybe we should sync up to discuss.

@Isaac-DeFrain Ah, it's wrapped, so that's .t


test: Cypress - add method for deleting branch

Description
Updates DeleteBranch test and adds common method for deleting branch
Testing

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Also list any relevant details for your test configuration.
Delete anything that is not relevant

[ ] Manual
[ ] JUnit
[ ] Jest
[ ] Cypress

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] PR is being merged under a feature flag

QA activity:

[ ] Speedbreak features have been covered
[ ] Test plan covers all impacted features and areas of interest
[ ] Test plan has been peer reviewed by project stakeholders and other QA members
[ ] Manually tested functionality on DP
[ ] We had an implementation alignment call with stakeholders post QA Round 2
[ ] Cypress test cases have been added and approved by SDET/manual QA
[ ] Added Test Plan Approved label after Cypress tests were reviewed
[ ] Added Test Plan Approved label after JUnit tests were reviewed

/ci-test-limit

Run it few more times just to be sure & revert limit test & PR can be merged.

/ci-test-limit

/ok-to-test

/ci-test-limit

@Parthvi12 -Oh, whats the difference please, between then & now?

Attaching the screenshot :

On release this test completes within 5 mins

Is the change after moving to a method from Helper. That is weird. Last has taken 6 mins. Try this a couple of times if time is consistent around 6mins , we can merge it. Else move the method back to local scope.

/ci-test-limit

@Aishwarya-U-R Latest run also too 15mins, I think we should move it to local scope.

Ok, let it stay as local scope. We can come back to this PR later.


[BUILD-997] Adds Console Sample for a build that pushes to external registry

This is an extension to #100.

Adds a sample example for build pushing to external registry.
Adds informative comments for references in all the builds. (At present, those comments are ignored when the sample yaml loads while creation of the instance. Checking with console team if this could be corrected with the upcoming versions).

/hold
It'll be better to have the correct source.url updated in all the examples with this PR itself.
Ref: https://github.com/redhat-openshift-builds/samples/pull/1


Currently, some hidden tumblr might fail to download.

I just re-added a blog that I used to have in in my list. Files for that blog were deleted from "index" folder. Immediately after adding that blog, the message about a post not being parsable shows up.
When I add that blog to the queue, it stalls. No progress. Setting the number to 1, does not help either. There is no progress at all of a sudden.
Closed app again, deleted both files from the Index folder. Added again, same result.
Deleted all IE cookies / temp files.
Started app, signed into tumblr again.
Closed app.
Started again, added blog anew, immediately the same message

It is a hidden blog
Other existing hidden blogs work fine

This could just be one of those cases where the current implementation cannot proceed, just bad luck. But I would be happy for any idea.
I will send you the blog name privately, Johannes.

Currently, some hidden tumblr might work for someone, for someone else not. Several people now wrote me that some hidden tumblr fail to be added with the error message: "cannot be parsed" and after hoovering over the error message the details say: unexpected character: "<".
I've found out that is has to do with the cookies. Maybe it's even related to your tumblr account settings. I don't know yet.
But I can say that sometimes it does download, sometimes not. Sometimes it helps to re-authenticate, sometimes not. The error also only started a few days ago (maybe as part of the new ToS/GDPR). I could also download a blog someone else showed with zero issues using my account while I couldn't download the blog using the account of my mail contact. I've also seen a video doing the same steps I've done where the download failed, while doing the same here, the download was possible.

I can confirm, the last release  TumblThree] v<IP_ADDRESS> fixes this. Tested with the test account I created as well. Thank you for getting this sorted out!  :)

Thanks for all your help, the blog and for sharing your account information! Much appreciated!
It's kinda weird for me though because I couldn't reproduce this error with my usual account. A newly created one had the same issues as yours. But based on the code I've changed and what I think the issue here was, it makes no sense that I didn't had this issue in the first place.

It was my pleasure. I agree it's odd. As if Tumblr treats accounts different based on something unknown. It can't be location based with both of us in Germany and frankly I will never get how tumblr decides to change code/API/the app/ the website it's shambles.


CA - LA County received messages with OBX Issues 8/14/24

Problem Statement
The RS Support team received an email in the Support inbox from Los Angeles County Department of Public Health regarding OBX values that did not transmit correctly, mainly in CLIA-related fields.
What you need to know
Email text follows:

Hi Report Stream Partners,
LA County has identified two OBX segment issues related to adding CLIAs as suffixes to this segment. Below is a summary of the information:
IRIS Lab Name
CMS Lab Name
CLIA
Issue
Report Count
Received Date
Prime Report Stream 0085 (ELR)
Premiere Medical Center of Burbank, Inc.
05D2002489
CLIA is missing the last digit in the OBX segment of the HL7 message
18
08/07/2024-08/12/2024
Prime Report Stream 0085 (ELR)
First Care Medical Centers, LLC
02D2091211
OBX segment not formatted correctly to include CLIA after facility name
1
08/12/2024
Please let me know if you need any additional information to resolve this moving forward.

Acceptance Criteria

[ ] Resolve issue causing OBX segment changes.

To Do

Review files that were sent to LA County
Determine cause of changes to OBX fields

Additional Comments
When researching this issue, I found several Report IDs related to Premier Medical Center of Burbank that were transmitted during the specified timeframe. The total number of results included in those files exceeds the number of messages they stated had errors. When reviewing the result data in Metabase, all CLIA values appear to be intact. I can provide those Report IDs if needed.

@victor-chaparro, may you please provide guidance on this issue?

@wcollin89 @TaneaY @MikaelahD13 I've reviewed a couple of files that were sent during that timeframe with that CLIA and the CLIA appears complete. It will be useful if we could get some accession numbers back from them or filenames that had this issue.

@victor-chaparro @TaneaY @MikaelahD13 The user replied back with the attached spreadsheet containing the accession numbers for the related messages.
Accession Numbers List_OBX Segment Issues.xlsx

Ok, I downloaded those specific files and all the reports have the CLIA complete.

@victor-chaparro Thank you for looking into it! I am reaching out to the user to request specifics on the OBX segments they received so we can see if it differs from what was sent.

@victor-chaparro the user replied back this morning with the following:

In the example from Premiere Medical Center of Burbank, you’ll notice that the CLIA is missing the last digit in OBX 23.1. The example from First Care has the CLIA completely missing from OBX 23.1. OBX 23.9 shows the CLIA correctly in both cases. I apologize, this is likely where the confusion came from- I didn’t specify which exact OBX segment we were discussing.
Premiere Medical Center of Burbank, Inc:
OBX|1|CE|94500-6^SARS-CoV-2 (COVID-19) RNA NAA+probe Ql (Respiratory system specimen)^LN||260373001^Detected^SCT^^Detected|||A^Abnormal (applies to non-numeric results)^HL70078^^^^2.5.1|||F|||20240806120000-0700|05D2002489^Premiere medical center of Burbank, inc.^CLIA||^BD Respiratory Viral Panel for BD MAX System^^^^^^^BD Respiratory Viral Panel for BD MAX System|00382904419165^^DII|20240806120000-0700||||Premiere medical center of Burbank, inc.-05D200248^^^^^CLIA&2.16.840.1.113883.4.7&ISO^XX^^^05D2002489|4418 VINELAND AVE SUITE 110^^Toluca Lake^CA^91602^USA||||||
First Care Medical Centers, LLC:
OBX|1|CE|94534-5^SARS-CoV-2 (COVID-19) RdRp gene NAA+probe Ql (Respiratory system specimen)^LN||260373001^Detected^SCT^^Detected|||A^Abnormal (applies to non-numeric results)^HL70078^^^^2.5.1|||F|||20240811235106-0700|02D2091211^First Care Medical Centers, LLC - Katherine Sterner, ANP^CLIA||^ID NOW^^^^^^^ID NOW|00811877010616^^DII|20240812000606-0700||||First Care Medical Centers, LLC - Katherine Sterne^L^^^^CLIA&2.16.840.1.113883.4.7&ISO^XX^^^02D2091211|1301 Huffman Rd Ste 100^^Anchorage^AK^99515-3568^USA^^^Anchorage||||||

Thank you!

@wcollin89 I finally found what the issue is.  OBX.23.1 max length is 50 characters, we are truncating that field per California's request. We can stop truncating it if that's what they need, but OBX.23.1 should only have the organization and the CLIA can be found in OBX.23.9.

@victor-chaparro thank you for your help! I have advised the user of this information and will let you know if they have any further requests.

@victor-chaparro the user responded this morning with the following request:

If it works for all parties, could the team truncate the reporting facility to 40 characters and append CLIA? That way it should not exceed 50 characters but will still contain a complete CLIA #. We use the CLIA from OBX 23.1 to identify the laboratory due to what’s available in our data system at this time. (We are not able to use OBX 23.9.)

They included Ellaison Carroll from CDPH on their response to confirm that CA will accept this change.

@victor-chaparro we received the following confirmation from Ellaison:

I’m good with truncating OBX-23.1 to 40 characters for the name of the reporting facility so the full CLIA is included.  I actually thought something like this was already in place, but for 35 characters instead of 40.  Is it possible to check the configuration history and see if it was and when it changed?

Thank you!

@victor-chaparro thank you for the update! I've provided this information to the user and will let you know of any resend requests.

@victor-chaparro I have sent a final follow-up message to the user, asking for confirmation that there have been no further issues or messages to resend, and advising that this issue is being marked as Resolved.
Thank you!

@victor-chaparro we received confirmation from the user today that there are no further OBX issues:

We were able to confirm that we’re receiving reports with these changes. We’ll connect with you again if we have any other issues.

Thank you for all your assistance!


SPAdes: 3.15.4 -> 3.15.5

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/SPAdes/versions.
meta.description for SPAdes is: "St. Petersburg genome assembler: assembly toolkit containing various assembly pipelines"
meta.homepage for SPAdes is: "http://cab.spbu.ru/software/spades/"
meta.changelog for SPAdes is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.15.5 with grep in /nix/store/z93c0fvgkh0d5srz9g9vabj6fyfywhqa-SPAdes-3.15.5
found 3.15.5 in filename of file in /nix/store/z93c0fvgkh0d5srz9g9vabj6fyfywhqa-SPAdes-3.15.5

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
SPAdes

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/z93c0fvgkh0d5srz9g9vabj6fyfywhqa-SPAdes-3.15.5 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A SPAdes https://github.com/r-ryantm/nixpkgs/archive/921b81745d34d07c767d2d0c32623b83126314e8.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/z93c0fvgkh0d5srz9g9vabj6fyfywhqa-SPAdes-3.15.5
ls -la /nix/store/z93c0fvgkh0d5srz9g9vabj6fyfywhqa-SPAdes-3.15.5/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

SPAdes

Maintainer pings
cc @bzizou for testing.

Result of nixpkgs-review pr 184694 run on x86_64-linux 1

1 package built:

SPAdes


The "Authorize the application to use the key or secret" section can also be done within the Azure portal.

From your key vault blade, go to "Access policies" and "Add new".
Select your application registration as the principal, and use the multi-select fields to provide the required access permissions for the app (e.g., Secret permissions > Get).
When you press OK, your app will now have the requested permissions for the key vault.

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

ID: 259ba844-605a-90de-611b-86be48852d5a
Version Independent ID: 093cdacd-b58d-bb93-61b2-0bf731f14648
Content: Get started with Azure Key Vault | Microsoft Docs
Content Source: articles/key-vault/key-vault-get-started.md
Service: key-vault
GitHub Login: @barclayn
Microsoft Alias: barclayn

@IanYates83 Thanks and yes you are correct on it. As the document from start is referring to powershell commands to accomplish each step hence that option is included for this section as well.

@IanYates83 We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


Make libmigraphx_onnx.so a private library

We need to make libmigraphx_onnx.so a private library since it does not have stable ABI.

PR: https://github.com/ROCm/AMDMIGraphX/pull/3184


Ran installer, nothing happened

Operating system: Windows 10 Professional
Build version (signal-back --version): https://github.com/xeals/signal-back/releases/download/v0.1.6/signal-back_windows_386.exe

Detailed description
I downloaded the installer into my Downloads folder and ran it. Windows intercepted it with a warning dialog. I clicked the More button and authorized the installation. That window closed. Nothing else seemed to happen. The Windows search box finds nothing but the installer, no actual program that can be run to decrypt Signal chat backups.
Full relevant output

Can someone please help me with this issue?

@Researchguy007 the .exe is not an installer, it's a command line executable, you have to open your command line in the folder where the executable is (in your case, Downloads) and type the following command :
signal-back_windows_386.exe format -f XML -o backup.xml <INSERT YOUR BACKUP FILE PATH>
This will write your backup in a file called "backup.xml"

If you're on windows x64 you should actually use back_windows_amd64.exe instead of not signal-back_windows_386.exe, which is for windows x86.


When verifying upgradeable contract: "Bytecode does not match with the current version of ERC1967Proxy in the Hardhat Upgrades plugin"

I deployed an ERC1967Proxy proxy contract and implementation without using hardhat-upgrades.
Then I tried to verify the contracts using await run("verify:verify", { address, constructorArguments }), but got the above error.
I noticed that the artifact ERC1967Proxy is obtained from @openzeppelin/upgrades-core:
https://github.com/OpenZeppelin/openzeppelin-upgrades/blob/a41b4317c0ca368cfc6b98b8fe6c33f480bbb766/packages/plugin-hardhat/src/verify-proxy.ts#L17
If I use that version then Etherscan shows a warning when viewing ERC1967Proxys source code:

The compiled contract might be susceptible to FullInlinerNonExpressionSplitArgumentEvaluationOrder (low-severity), MissingSideEffectsOnSelectorAccess (low-severity), AbiReencodingHeadOverflowWithStaticArrayCleanup (medium-severity), DirtyBytesArrayToStorage (low-severity), DataLocationChangeInInternalOverride (very low-severity), NestedCalldataArrayAbiReencodingSizeValidation (very low-severity) Solidity Compiler Bugs.

The contract was compiled with solidity v0.8.9+commit.e5eed63a, which would be the reason for the warnings and bytcode mismatch. I use the latest version of solidity (0.8.21).
Please fix this issue. Thank you.

The Hardhat Upgrades plugin can only verify proxy source code for proxies that were deployed by the plugin.  This is because verification requires the exact compiler settings which were used to compile the proxy, and those compiler settings (along with the source code) are provided by the plugin during Etherscan verification to match the proxy bytecode that it deployed.
If you deploy proxy contracts without using the plugin, you would need to verify them manually.
However, generally there is no need to deploy newer versions of the proxy contracts than the ones provided by the plugin.  If compiler bugs or other vulnerabilities affect the proxy contracts, we would publish a security advisory for OpenZeppelin Contracts https://github.com/OpenZeppelin/openzeppelin-contracts/security/advisories and would update the plugin to use the newer proxies as needed.

The latest version of @openzeppelin/contracts is v4.9.3 but openzeppelin-upgrades is still using v4.8.3:
https://github.com/OpenZeppelin/openzeppelin-upgrades/blob/483a43f4856d607dd3b38ab81931e0e777ccb82e/packages/core/package.json#L41C6-L41C29
You should keep it up-to-date.

While some source files have been modified (including for contracts that the proxies depend on) between OpenZeppelin Contracts v4.8.3 and v4.9.3, those specific changes were not deemed to affect proxy functionality.
We generally do not update the version of the proxies used in the Hardhat plugin unless there are changes that affect the proxies.  Updating the versions unnecessarily (if functionality does not change) would cause more difficulties for users.
For example, a benefit of keeping proxy bytecode the same is that many proxy deployments would automatically have "Similar Match Source Code" verified on Etherscan and related block explorers if they were verified by other users before.
As another example, the Hardhat plugin (as mentioned above) verifies proxy source code with the same bytecode that it deploys.  If a user deploys a proxy but did not verify it, then updates the plugin with an updated proxy, the verify task would not work because the plugin's updated proxy source code does not match with what was previous deployed.  There is an issue https://github.com/OpenZeppelin/openzeppelin-upgrades/issues/674 to improve this.


Switching to v2.0

How can i use this lib, but forcing it to use STIX v2.0 (and not v2.1)

Hi @sotiraki-sima, good question. You can find information about this here in our documentation. Please let us know if anything there is unclear.

Closing due to inactivity. Let us know if you have further questions. Thanks.