WebView2: Update documentation for SDK 1.0.707-prerelease

Docs Build status updates of commit 1350829:
:clock10: Pending: waiting for processors (45 builds ahead of you)
:warning: Docs Build is busy, currently there are 45 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 7189f08:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

 It might be caused your branch is deleted or force pushed. If it is not this case, please open a ticket on https://SiteHelp

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 6fbc34f:
:clock10: Pending: waiting for processors (6 builds ahead of you)
:warning: Docs Build is busy, currently there are 6 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 6fbc34f:
:warning: Validation status: warnings

File
Status
Preview URL
Details

1-0-707-prerelease/icorewebview2experimentalcompositioncontroller.md
:warning:Warning
View (webview2-1.0.707-prerelease)
Details

1-0-707-prerelease/webview2-idl.md
:warning:Warning
View (webview2-1.0.707-prerelease)
Details

1-0-707-prerelease/icorewebview2experimentalcompositioncontroller2.md
:bulb:Suggestion
View (webview2-1.0.707-prerelease)
Details

1-0-707-prerelease/icorewebview2experimentalcompositioncontroller3.md
:bulb:Suggestion
View (webview2-1.0.707-prerelease)
Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

1-0-674-prerelease/icorewebview2.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2acceleratorkeypressedeventargs.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2acceleratorkeypressedeventhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2addscripttoexecuteondocumentcreatedcompletedhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2calldevtoolsprotocolmethodcompletedhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2capturepreviewcompletedhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2containsfullscreenelementchangedeventhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2contentloadingeventargs.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2contentloadingeventhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2controller.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2createcorewebview2controllercompletedhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2createcorewebview2environmentcompletedhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2deferral.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2devtoolsprotocoleventreceivedeventargs.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2devtoolsprotocoleventreceivedeventhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2devtoolsprotocoleventreceiver.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2documenttitlechangedeventhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2environment.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2environmentoptions.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2executescriptcompletedhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2experimental.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2experimentalcompositioncontroller.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2experimentalcompositioncontroller2.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2experimentalcookie.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2experimentalcookielist.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2experimentalcookiemanager.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2experimentalcreatecorewebview2compositioncontrollercompletedhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2experimentalcursorchangedeventhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2experimentaldomcontentloadedeventargs.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2experimentaldomcontentloadedeventhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2experimentalenvironment.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2experimentalgetcookiescompletedhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2experimentalpointerinfo.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2experimentalwebresourceresponsereceivedeventargs.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2experimentalwebresourceresponsereceivedeventhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2experimentalwebresourceresponseview.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2experimentalwebresourceresponseviewgetcontentcompletedhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2focuschangedeventhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2historychangedeventhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2httpheaderscollectioniterator.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2httprequestheaders.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2httpresponseheaders.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2movefocusrequestedeventargs.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2movefocusrequestedeventhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2navigationcompletedeventargs.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

This comment lists only the first 50 files in the pull request.

1-0-707-prerelease/icorewebview2experimentalcompositioncontroller.md

Line 44, Column 28: [Warning-bookmark-not-found] Cannot find bookmark '#icorewebview2experimentalcompositioncontroller' in '1-0-707-prerelease/icorewebview2experimentalcompositioncontroller.md'.
Line 44, Column 350: [Warning-bookmark-not-found] Cannot find bookmark '#icorewebview2experimentalcompositioncontroller' in '1-0-707-prerelease/icorewebview2experimentalcompositioncontroller.md'.

1-0-707-prerelease/webview2-idl.md

Line 111, Column 1: [Warning-invalid-note-section] Text in the first line of Note/Section/Video is not valid. Will be rendered to <blockquote>

1-0-707-prerelease/icorewebview2experimentalcompositioncontroller2.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'This interface is continuation of the ICoreWebView2ExperimentalCompositionController interface.' is duplicated in '1-0-707-prerelease/icorewebview2experimentalcompositioncontroller2.md(2,14)', '1-0-707-prerelease/icorewebview2experimentalcompositioncontroller3.md(2,14)'. NOTE: This Suggestion will become a Warning on 1/29/21.

1-0-707-prerelease/icorewebview2experimentalcompositioncontroller3.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'This interface is continuation of the ICoreWebView2ExperimentalCompositionController interface.' is duplicated in '1-0-707-prerelease/icorewebview2experimentalcompositioncontroller2.md(2,14)', '1-0-707-prerelease/icorewebview2experimentalcompositioncontroller3.md(2,14)'. NOTE: This Suggestion will become a Warning on 1/29/21.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 18fd749:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

1-0-707-prerelease/icorewebview2experimentalcompositioncontroller2.md
:bulb:Suggestion
View (webview2-1.0.707-prerelease)
Details

1-0-707-prerelease/icorewebview2experimentalcompositioncontroller3.md
:bulb:Suggestion
View (webview2-1.0.707-prerelease)
Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

1-0-674-prerelease/icorewebview2.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2acceleratorkeypressedeventargs.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2acceleratorkeypressedeventhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2addscripttoexecuteondocumentcreatedcompletedhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2calldevtoolsprotocolmethodcompletedhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2capturepreviewcompletedhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2containsfullscreenelementchangedeventhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2contentloadingeventargs.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2contentloadingeventhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2controller.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2createcorewebview2controllercompletedhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2createcorewebview2environmentcompletedhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2deferral.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2devtoolsprotocoleventreceivedeventargs.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2devtoolsprotocoleventreceivedeventhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2devtoolsprotocoleventreceiver.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2documenttitlechangedeventhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2environment.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2environmentoptions.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2executescriptcompletedhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2experimental.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2experimentalcompositioncontroller.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2experimentalcompositioncontroller2.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2experimentalcookie.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2experimentalcookielist.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2experimentalcookiemanager.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2experimentalcreatecorewebview2compositioncontrollercompletedhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2experimentalcursorchangedeventhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2experimentaldomcontentloadedeventargs.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2experimentaldomcontentloadedeventhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2experimentalenvironment.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2experimentalgetcookiescompletedhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2experimentalpointerinfo.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2experimentalwebresourceresponsereceivedeventargs.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2experimentalwebresourceresponsereceivedeventhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2experimentalwebresourceresponseview.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2experimentalwebresourceresponseviewgetcontentcompletedhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2focuschangedeventhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2historychangedeventhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2httpheaderscollectioniterator.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2httprequestheaders.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2httpresponseheaders.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2movefocusrequestedeventargs.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2movefocusrequestedeventhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2navigationcompletedeventargs.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2navigationcompletedeventhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2navigationstartingeventargs.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

This comment lists only the first 50 files in the pull request.

1-0-707-prerelease/icorewebview2experimentalcompositioncontroller2.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'This interface is continuation of the ICoreWebView2ExperimentalCompositionController interface.' is duplicated in '1-0-707-prerelease/icorewebview2experimentalcompositioncontroller2.md(2,14)', '1-0-707-prerelease/icorewebview2experimentalcompositioncontroller3.md(2,14)'. NOTE: This Suggestion will become a Warning on 1/29/21.

1-0-707-prerelease/icorewebview2experimentalcompositioncontroller3.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'This interface is continuation of the ICoreWebView2ExperimentalCompositionController interface.' is duplicated in '1-0-707-prerelease/icorewebview2experimentalcompositioncontroller2.md(2,14)', '1-0-707-prerelease/icorewebview2experimentalcompositioncontroller3.md(2,14)'. NOTE: This Suggestion will become a Warning on 1/29/21.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 7c473e9:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

1-0-674-prerelease/icorewebview2.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2acceleratorkeypressedeventargs.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2acceleratorkeypressedeventhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2addscripttoexecuteondocumentcreatedcompletedhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2calldevtoolsprotocolmethodcompletedhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2capturepreviewcompletedhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2containsfullscreenelementchangedeventhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2contentloadingeventargs.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2contentloadingeventhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2controller.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2createcorewebview2controllercompletedhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2createcorewebview2environmentcompletedhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2deferral.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2devtoolsprotocoleventreceivedeventargs.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2devtoolsprotocoleventreceivedeventhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2devtoolsprotocoleventreceiver.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2documenttitlechangedeventhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2environment.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2environmentoptions.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2executescriptcompletedhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2experimental.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2experimentalcompositioncontroller.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2experimentalcompositioncontroller2.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2experimentalcookie.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2experimentalcookielist.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2experimentalcookiemanager.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2experimentalcreatecorewebview2compositioncontrollercompletedhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2experimentalcursorchangedeventhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2experimentaldomcontentloadedeventargs.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2experimentaldomcontentloadedeventhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2experimentalenvironment.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2experimentalgetcookiescompletedhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2experimentalpointerinfo.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2experimentalwebresourceresponsereceivedeventargs.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2experimentalwebresourceresponsereceivedeventhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2experimentalwebresourceresponseview.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2experimentalwebresourceresponseviewgetcontentcompletedhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2focuschangedeventhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2historychangedeventhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2httpheaderscollectioniterator.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2httprequestheaders.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2httpresponseheaders.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2movefocusrequestedeventargs.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2movefocusrequestedeventhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2navigationcompletedeventargs.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2navigationcompletedeventhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2navigationstartingeventargs.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2navigationstartingeventhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

1-0-674-prerelease/icorewebview2newbrowserversionavailableeventhandler.md
:white_check_mark:Succeeded
View (webview2-1.0.674-prerelease)

This comment lists only the first 50 files in the pull request.
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Update notation in neoclassical_growth, and pretend we don't know the steady-state

I want to update the neoclassical growth model to be as simple as possible and to test removing the dependence on the stationary solution.  The task list is:

[x] Change all notation to match HJBE_discretization.pdf as much as possible

e.g. s -> gamma
df to Delta or whatever is the correct match)
min(mub,0) instead introduced mu_B_m max(muf,0)introducesmu_F_p`, etc.

[x] Add comment pointing to the equation number in the latex file for each line of code involving algebra.  If you need to add in more equations (or want to rearrange equations) in that document, then go for it.
[ ] We want to write the equations of the model pretending that we don't know the steady-state.  To do this, we will need to play around with what is currently equation (19) in the notes.

First, we need to ensure that all cases of $\mu_F$ and $\mu_B$ signs are properly dealt with in the logic, as I am not sure the code/algebra is correct as stated.  In particular, it should be clear what happens if both  $\mu_F > 0$ and $\mu_B < 0$ at the same time in (19) as opposed to a footnote.  Next, what happens if the drifts are exactly 0?
I believe that one way to write it where nothing falls through the cracks is as follows:
$
{v_i^n}'={v_{i,F}^n}'\bold{1}{{ \mu{i,F} \geq 0}}+{v_{i,B}^n}\bold{1}{{ \mu{i,B}\leq 0 \text{ and } \mu_{i,F} < 0 }}+{\bar{v}i^n}'\bold{1}{{ \mu_{i,F}<0<\mu_{i,B} }}\label{eq:dv-upwind}
$
See if that changes the solution.
Next, lets see what happens if we change the behavior around the steady state to pretend we don't know it.  In particular, one thing to try is whether (with a fine enough grid) we can just use $\mu_{i,F}$?  In that case it would be something like
$
{v_i^n}'={v_{i,F}^n}'\bold{1}{{ \mu{i,F} \geq 0}}+{v_{i,B}^n}\bold{1}{{\mu{i,F} < 0 }}
$
Then check if it also works for taking the average.  i.e. something like
$
{v_i^n}'={v_{i,F}^n}'\bold{1}{{ \mu{i,F} \geq 0}}+{v_{i,B}^n}\bold{1}{{ \mu{i,B}\leq 0 \text{ and } \mu_{i,F} < 0 }}+{\frac{v_{i,F}^n + v_{i,B}^n}{2}}'\bold{1}{{ \mu{i,F}<0<\mu_{i,B} }}\label{eq:dv-upwind}
$
In all cases, when you check if it "works", you should be seeing if the solution changes much, and (especially) if the correct steady state comes out naturally.  Also, play around to see if it converges for different initial guesses on the value function.
Leave (commenting out whichever one you aren't using) code for the 3 cases in the file, so we can play with it a bit

Notation has been changed and comments added for equation numbers.
All three of the variations are currently resulting in messy graphs with imaginary components. I think this may be due to dV_Upwind taking negative values --> c=dV_Upwind^(-1/gamma) then has a complex component? Not sure if it's design or coincidence that the original equation for dV_Upwind never turns out negative values
I have committed a version of the code containing the cases as stated above and am currently trying different variations (labelled 1(a), 2(a), etc.) on those to see if anything works.

Great.  I may play around with it as well.  If the dV_upwind is taking negative values, then maybe the right approach for the tie breaking rule is to take the max of the two.  We can check if it ever takes negative values for both, which seems a little odd since the marginal value should always be positive here.

Looking at the code, it seems a little odd that we are getting negative values.  That would mean (11) and (12) have decreasing value in k...   Seems like there might be something odd going on during the convergence?

I think I found the issue.  You didn't rename dk to $\Delta$, and instead had them as two separate numbers.
I have made the changes and am pushing to the server.  It seems to give the same, or close to, the correct answer (except at the top corner).  But I am also not convinced that the dV_f logic in the original code was ideal, so it isn't necessarily a mistake in the setup.
If you have made any local changes, I would Discard them by going into the github desktop, right clicking on the file you modifed, and saying "Discard Changes...".
I am taking over the file now, thanks so much!  When you have time to work on this again, I would go to #2 so we can try the alternative method of solving this problem.  But this can wait a week.

@wangxy373 See latest comment if you didn't get the email.


v4.0.0

List of issues and PRs that may be suited for next major release.
Issues

[ ] (#479) Option to shrink path in dir section
[ ] (#426) Option to print prompt in non-bold font
[x] (#307) Use zsh-async for rendering sections
[x] (#508) spaceship options from prompt specific configuration files
[ ] (#375) Support custom git sections
[ ] (#341) Make new sections opt-in
[x] (#318) Insert custom spaceship functions without disturbing other sections
[ ] (#563) Use zstyle for configuration

Pull requests

[x] (#315, #499) Async rendering using zsh-async
[ ] (#391) Modularize git_status section

[ ] (#392) OMZ style git_status
[ ] (#393) git_index subsection for git section

[ ] (#468) spaceship options per-project/directory
[ ] (#519) Option for non-bold prompt

It would be great if we get consensus about what should be part of v4.0.0 and what can be delayed or advanced.

Ref #563

Most of the collaborators are busy with work. Check this for pending tasks, hope we could get back to finish next version ASAP. Any help with these are highly appreciated :v:

Hey! What would be the best way to use 4.x before it gets released? I'd really love to get that async rendering speedup!

v4.0.0 is released. Not everything planed is included, but the main features are on board. This unblocks implementing other features.


Adding '$pshome/cultureName/default.help.txt' to PowerShell Windows Core project.

Fixing issue '$pshome/cultureName/default.help.txt' is missing #1731
Added package PowerShellHelpFiles to the PowerShell Windows Core project (src/powershell-win-core/project.json) to include the help files when PowerShell is published.
Added a test to validate that '$pshome/cultureName/default.help.txt' is present. This is done by calling 'get-help' which returns information about the help system.
Updated the get-help cmdlet to force return a metadata driven object when the test hook BypassOnlineHelpRetrieval is enable.
Updated get-help -online tests to not delete the help files before running, and updated the comments in the test code.

:clock1:

:clock1:

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@1431105).

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 1431105...f57bb0f. Read the comment docs.

@mirichmo @daxian-dbw : Could you please merge this PR when you have time? Thanks in advance.


fix(v2): fix navigation from homepage

Motivation
Hotfix.
There was an error in #4125, as a result of which when we try to click on any internal link from the homepage, we get a blank page with errors in the console:

Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
Preview.
Related PRs
(If this PR adds or changes functionality, please take some time to update the docs at https://github.com/facebook/docusaurus, and link to your PR here.)

thanks, will try to find another way to do this


Add connection ID scope to HubConnection

Fixes https://github.com/aspnet/SignalR/issues/2153
There is also the same logging scope in HttpConnection. Should it be removed?

Unfortunately this isn't how scopes work with logging because internally it uses a ThreadStatic

Yes, they never worked on the client and they should be removed... They don't use a ThreadStatic, they use async locals (I know you mean that but better to call it out).

An example of what a fixed version looks like:

👍

They don't use a ThreadStatic, they use async locals

Haha, whoops

🆙 📅


ability to detect if its a search engine or not ?

I was wondering if we can detect if its a search engine or a normal user ?

If it is a search engine crawler, then the parser would identify it as a bot. I do not plan on expanding the scope of this project to distinguish what sort of bot the user-agent is though.

I think for that use case, the other traditional user-agent parsers based on regexes would be more appropriate.
This one tries to be as lightweight and fast as possible so adding additional features that require us to add to the API can be unnecessarily expensive.

Ah, are you referring to the main Medama app? In that case, we already filter out any bots/search engines etc, if detected by this library.


Long integers

Often you need to deal with large numbers in games: scores, distances, etc.. While floats offer a wide range, they're terribly slow. 16-bit integers are fast, but very limited in range.
XC=BASIC should offer variable type that is a good balance between range and performance. Here are some ideas:

a large signed integer, possibly 32 bits wide, offering a range from −2,147,483,648 to 2,147,483,647
an unsigned fixed point decimal, again 32 bits wide, ranging from 0 to 999,999.99 (two decimal places after the radix point)

Please add your thoughts and ideas in the comments.

I think a signed integer is more flexible. In an arcade game bigger scores feel better. In a puzzle game negative scores could be possible (e.g. pushing boxes will lower the score). Fixed point decimals could be "simulated" with string functions.
On the other hand I'd like to have unsigned byte and integer. But you already know that. :P

I agree with Oliver. Signed integers are a good choice.

Another advantage for the long integer is that they're very easy to convert to/from other integer types.
@oliverhermanni Unsigned integer output is also planned to be implemented in v2.2. No need to introduce a new type for that, as integer arithmetic is the same when signed or unsigned. Only the output formatting decides if it's signed or unsigned.

Another question raises: what sigil to use for the new type? Almost the whole ASCII-table is already reserved :-D I'm thinkink to take away # from the integer (as it can be omitted and I strongly believe that no-one actually uses it) and give it to the new type.

Would it be possible to define them by a keyword like other languages do? Eg. uint, int, etc. Code could look like this:
int money = -5000
uint score = 0

@oliverhermanni I'd keep the sigil notation for backwards compatibility and as a tribute for the BASIC language.

@neilsf I understand that, but why hold on to something, which might sooner or later become a handicap? Of course sigils need to be kept, e.g. for strings, hexadecimals and binary numbers. But IMHO for decimal numbers they are not intuitive in XC=BASIC. I'm not sure how many times I miss a ! for a byte. Also if I need to switch from byte to integer in a project I need to search and replace the whole code.
With new keywords this would be much easier. Adding new number formats would be much easier to add also. Currently I can think of byte, ubyte (or ascii like it's used in PureBasic), int, uint, float, ufloat. A number not defined could automatically be defined as integer.
And isn't XC=BASIC itself a tribute to BASIC? ;)

Well I understand your point but it's still a backwards-incompatible change which can be implemented in a later major version.

Let me add another note here. The optimizer's main task is to rewrite the code in such a way that it stores values in registers instead of the stack wherever possible. Now the problem with long integers is that we only have three registers, A, X and Y and therefore they can't be optimized the same way as bytes or short integers.
So I came up with the idea of defining the long integer as 24 bits wide instead of 32 bits. This way the value range is much smaller (−8,388,608 to 8,388,607) but computing speed could be considerably higher.
It's still an open question, no decision have yet been made.

I gueess, that's more than enough.

Well if someone wants to implement a flipper game with crazy scores like 99,999,999 that won't work :-D
But I think 24 bits could be a good trade-off.

Flipper games can leave the two last numbers as 00 and let the lowest possible score for anything be 100, and still make you feel like a king with those 99,999,999 points =)

Implemented in V3


Auto completion is strange

For example, in C++
#include <iostream>

int main()
{
   std::cou <HERE>

Try to complete std::cout. The proposed choice removes the typed 'u'. You can't iterate on the completions either, if you press Ctrl + Space, the line is indented instead.
I don't think Ctrl+Space should ever trigger a "tab" command.
Yet, this works:
#include <iostream>

struct T
{
   void onSomething() {}
   void onReturn() {}
}

int main()
{
   T t;
   t.on <HERE>

Here, you can iterate the 2 choices... But if you validate the completion by pressing right key, sometimes (not everytime), a additional space is added after the completion. Pressing "tab" only indent the line
Finally, if autoCompleteDetails is true, it opens a pane with only the function return type or a lot of empty lines like this:
  1 #include <iostream>
   2
   3 class Test{
   4 public:
   5     void test(){
   6         std::cout<<"Test"<<std::endl;
   7     }
   8     void test2() {}
   9 };
  10
>>11 int main(){
  12     Test test;
  13     test.test2 (test)// After pressing Ctrl+Space here completion event should be triggered but nothing happens
>>14     return 0;
  15 }
>>16

a.cpp + (13,17) | ft:c++ | unix | utf-8                                                                                Alt-g: bindings, Ctrl-Backspace: help
  1 Test                                                                                2                                                                                3 int                                                                                4                                                                                5                                                                                6                                                                                7                                                                                8                                                                                9                                                                                10
 11
 12
 13 size_t
 14
 15
 16
 17
 18
 19
 20
 21
 22
 23 void
 24 void
 25
 26
 27
 28 bool
 29
 30
 31
 32
 33
 34 bool
 35 std::nullptr_t
 36
 37
 38
 39
 40 size_t

For me, when I press Ctrl+Spacebar, the text which I typed disappears.
Following is my setup

lsp  - 0,6.2
micro - 2.0.13
os - Ubuntu 22.04
lsp.server - clangd

Say for example, I type std::cou and press Ctrl+Spacebar then I am only left with std::


Support and test for SSR

Closes #1760
Summary

Element proptypes shouldn't be checked in non-browser environments as it's not available, instead can be .any
Add basic test to ensure that the package can be imported in node environments (would have caught these proptype issues)

Change List (commits, features, bugs, etc)

modify component proptypes to conditionally check Element proptypes
add new test file
modify jest config to not patch browser apis in non-browser environments
reinstate the integrated terminal config for vscode's debugger

Acceptance Test (how to verify the PR)

Tests should pass

:tada: This PR is included in version 2.141.0-next.22 :tada:
The release is available on:

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 2.141.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Static files are not served properly

After fixed a problem with a missing package, the application has not displayed static files properly (render only raw HTML). Probably this is any problem with Heroku.
AC:

Application displays a static files properly

Can you please provide steps to replicate the problem?


Arabic translation of Advanced Algorithm Scripting

[ ] Validate US Telephone Numbers Incomplete
[ ] Symmetric Difference Incomplete
[ ] Exact Change Incomplete
[ ] Inventory Update Incomplete
[ ] No repeats please Incomplete
[ ] Friendly Date Ranges

Closed in favor of https://github.com/FreeCodeCamp/TranslationExpansion/issues/30


Sparse Big Bitvectors

Problem: Right now, big bitvectors (ie more than 64 bits) are represented with the class BigBitvector in pydrofoil, which stores an instance of rbigint making all operations on them pretty expensive. Also the JIT is bad at reasoning about them (no range analysis, no arithmetic simplification, etc). A lot of the times, these big bitvectors have few bits set in practice.
Idea: add another more efficient implementation for sparse big bitvectors. It's only used if all the set bits are in the lowest 64 bits of the bitvector (but the size of the bitvector is larger than 64). If that is no longer true, we switch to using the fully general BigBitvector.
This is a mid-sized project and needs to be very carefully done with lots of focus on how to properly test this, because mistakes are very hard to catch and lead to wrong behavior in the simulators.
Some possible steps:

check the test coverage of the existing bitvector implementations using coverage and improve it where it is lacking.
start a SparseBitVector class that stores the bitvector size (always >64) and a r_uint that stores the lowest 64 bits of the bitvector. The higher bits are assumed to be 0.
All operations on that class simply convert the argument into a BigBitvector and then call the equivalent method on that.
SparseBitVector instances will be constructed in bitvector.from_ruint if size > 64
If all this is done, we can start adding operations to SparseBitVector incrementally, adding careful tests as we go.
All testing should be done using both hand-written examples as well as extra tests with Hypothesis.

here are some methods that should be relatively straightforward to do in SparseBitVector:

rshift
arith_rshift
rshift_bits
xor, or_, and
zero_extend
sign_extend
subrange
subrange_unwrapped_res
update_bit
signed
unsigned
eq
toint
touint
tobigint
replicate
truncate

harder:

lshift
add_* and sub_*
invert (impossible!)

here's the branch where @naseweisssss is doing this work: https://github.com/pydrofoil/pydrofoil/compare/main...naseweisssss:pydrofoil:sparse-bitvector-branch

@naseweisssss here are some changes to SmallBitVector that you can do if you have extra time:

change the places that compute the highest bit manually to use self.read_bit(size - 1). this happens in the methods SmallBitVector.arith_rshift and SmallBitVector.sign_extend. This is in preparation for the eventual unification of SmallBitVector and SparseBitVector
some methods should switch to returning SparseBitVector: SmallBitVector.zero_extend, SmallBitVector.sign_extend, and maybe something good can be done in BitVector.append and Bitvector.append_64 as well.

also, here's the diagram that we drew while talking about this:

closing this, it's done after #79 and #80.


Cannot add key to multisig 2-of-2 account

I created a multisig 2-of-2 account, but I cannot add new keys to it.

solved


KAFKA-5989: resume consumption of tasks that have state stores but no changelogging

Stores where logging is disabled where never consumed as the partitions were paused, but never resumed.

@guozhangwang this is the same as https://github.com/apache/kafka/pull/4002 which i've merged to trunk, but the cherry-pick failed as i targeted the wrong branch

LGTM!

Merged to 1.0.


⚠ Bofrost.at has degraded performance

In 9f95c53, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1437 ms

Resolved: Bofrost.at performance has improved in b654818.


升级 ThinkJS 依赖模块的版本

DESC
ENV
Platform:
Node.js Version:
ThinkJS Version:

https://github.com/75team/thinkjs/commit/1f668d92e83fe48942b72d4e79ebab0877cfc193


Update README.md

Add some resources about git, regular expressions

Hello! 👋
Exercism is already added in the Competitive Programming and Learn Python sections.


Add searchFieldStyle

Description
Add searchFieldStyle in SearchDelegate to let the user customize the style of the text in the search field.
Related Issues
#54673
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I signed the CLA.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I updated/added relevant documentation (doc comments with ///).
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Did any tests fail when you ran them? Please read Handling breaking changes.

[x] No, no existing tests failed, so this is not a breaking change.
[ ] Yes, this is a breaking change. If not, delete the remainder of this section.

[ ] I wrote a design doc: https://flutter.dev/go/template Replace this with a link to your design doc's short link
[ ] I got input from the developer relations team, specifically from: Replace with the names of who gave advice
[ ] I wrote a migration guide: Replace with a link to your migration guide

I see now that it may be worth considering using the same color both for the TextField and the hint text. For instance, now if a custom style is used inside the SearchDelegate it will still use the color provided by the current theme for the user's input text. If that's okay for you I might open a PR to solve it. Maybe @darrenaustin will you be so kind and review this?


get_common_X_path functions into a library

Those methods in actor/init.py have been static anyway, by moving them
out not only we do the right thing, but make them accessible in non-actor
libraries like command libraries.

Can one of the admins verify this patch?

/rerun

/rerun

@vinzenz All resolved, thanks!

/rerun


Last sync not showing for all rows in /repos

I just encountered a bug where the Last sync value was missing from several of the rows in the /repos table.

I will move this one to blocked for now because I haven't been able to reproduce it.

@amenowanna  @patrickdevivo  so far I can't reproduce this.I will import a large import to double check this otherwise we should be able to close this

We are now using a new backend for all of this so closing


meteor _id and ios entity attributes

Hey,
First off, awesome work! This is a huge help in my project.
I'm trying to fetch a record using the meteor auto-generated '_id', but I can't add the same attribute to the corresponding Core Data entity because it won't allow me to start an attribute with anything other than a letter. Is there a graceful solution to this?

Good to hear you're finding it useful, even without decent documentation! Are you using it from Swift or Objective-C?
The _id- field is actually used to construct the Core Data objectID. METCoreDataDDPClient exposes  objectIDForDocumentKey: that you can use to get from a key (a combination of collection name and documentID) to an NSManagedObjectID:
NSManagedObjectID *objectID = [client objectIDForDocumentKey:[METDocumentKey keyWithCollectionName:@"todos" documentID:@"bla"]];
NSManagedObject *object = [managedObjectContext objectWithID:objectID];

I'm still working out the API, so consider this a temporary solution. What is your intended usage pattern here? Where does the _id value come from?

It is pretty difficult without docs, I'm also new to iOS development so the difficulty is compounded, I'm basically muddling through. Do you have a swift example? I'm just trying to lookup an existing object and update some values.

I can imagine the difficulty! Hopefully I'll find some time over the next few weeks to work on the documentation and maybe even write a tutorial. I'm in the middle of a deadline for a project and the API is still in a bit of a flux, so it'll be a while before things get stable. Core Data in itself isn't very user friendly, so I'm also working on some helper classes and extensions in Swift to make things easier.
This should work for now:
let objectID = Meteor.objectIDForDocumentKey(METDocumentKey(collectionName: "todos", documentID: "bla"))
let object = managedObjectContext.objectWithID(objectID)

That's great, worked for me, thanks!

Hey again, I'm now looking for a way to get the meteor ID of an object I've created. Essentially, I'm creating an object, then creating related objects and need to add the ID of the original object to the related ones. How can I get the ID of an object I already have in the managed object?

I'm planning on simplifying this, but right now you can get the document ID of an object by using:
let object: NSManagedObject = ...
let documentID = Meteor.documentKeyForObjectID(object.objectID).documentID

I'm not sure how you're setting up relationships, but in most cases it shouldn't be necessary to connect objects manually by ID. If you define a relationship in your Core Data model and set its value, a field with the related document ID (or array of document IDs) will be managed for you.

That would be better, can you point me to the place in your Todos example where I can get a sense of how to make that connection? I did some setup to relationships in the Core Data model, but I must be missing something because its not adding the IDs for me

It should work with any properly set up Core Data relationship. There is no additional code required, you simply define the relationship in the managed object model. The only issue to keep in mind is that by default it will add IDs on both sides of the relationship. You'll have to specify 'storage = false' as user info on one of the relationship sides to suppress this (for many-to-many you need both sides).
Here are two screenshots from the Todos example:

I have it setup essentially the same as in the screens, but it doesn't seem to be adding the values automatically. To be clear, I'm looking to have the MongoDB '_id' field for the List object inserted into the todo object as a new field on creation. Is that what should be happening?

Yes, if you set todo.list to a List object, a listId field with the list _id value should be inserted automatically into the todo document. Are you sure you're setting the list property? And have you defined it as a managed property in the Todo class?
@NSManaged var list: List!

ah yes! I was trying to add it manually as a new field, but this is much better. Thanks!


Space between required and optional group should be required

For example, the following should match
Pattern
:[1] :[?2]

Text (without quotes)
(Has trailing space)
"a "

Bug fixed in dev-0.9 branch and test added


Automated publishing of model cluster benchmark data, now.

For the short term, specifically, we need a public, persistent location for model cluster benchmark data.
A Github repo with the structured portion of the standard analyses seems like an appropriate option.
The name could be cardano-perf-data.
This would require some workbench integration.

A different approach has been decided upon, where the benchmark data is stored in a Postgres DB.
This enables both querying / filtering all data points with a well known query languagy like SQL, as serving a REST API directly from views defined upon these data points (by means of an additional service).
The latter allows basically any front-end facing application or service to process or visualize model cluster benchmark data.
Tracked in PR #4615


Word / Excel 97-2003 files may be detected as MSDOC

Word / Excel 97-2003 files may be detected as MSDOC type and not WORD or EXCEL.
I faced the issue by creating a blank Excel file in Excel 2007 and save it as XLS (check blank.zip)
From what I could check, Office 97-2003 file signatures are based on "subheaders" and there might have several of them without a clear documentation. However the library would detect it as MSDOC type.
I would therefore suggest to

Rename MSDOC type as MS_OFFICE to be more accurate
Add the list of known MS office extensions (at least doc,ppt,xls)

or the list as defined here

Something like
// OLECF - Object Linking and Embedding (OLE) Compound File (CF)
// Compound Binary File format by Microsoft, used by Microsoft Office 97-2003 applications(Word, Powerpoint, Excel, Wizard)
public readonly static FileType MS_OFFICE = new FileType(new byte?[] { 0xD0, 0xCF, 0x11, 0xE0, 0xA1, 0xB1, 0x1A, 0xE1 }, "doc,ppt,xls", "application/octet-stream");
Since the type appears after WORD and EXCEL types, the detection would first match based on subheaders and default to this one if the subheader does not match.

@superjulius I'm trying to find some older versions of Office to generate test data for this.


Feature : Ask for file configuration at opening

A feature like in libreoffice (when open a csv file) to configure separator and more.

For reference, here is a screenshot of libreoffice options when opening a csv:


Promisification

First stab at fixing #1.
Not sure about the new options argument (to receive the complete res or headers in the response). Happy to fix it however you see fit.

Not sure about the new options argument (to receive the complete res or headers in the response)

I don't really see the point of that. Why would you need the headers? I'd rather just keep the output as it was without complicating it.

Noticed some inconsistent indentation. Make sure you've used tab indentation.

The headers are handy for the ratelimit, that's about it. But the limits are very generous (with a token), so it might not be an issue. I can remove all that, you're probably right. I'm coming the the search api and the limit are a bit stricter there.

I guess I should now update the code (and watch the indent) given the notes above?

If you need the rate limit info, you could expose it as a hidden property on the returned object:
Object.defineProperty(ret, 'rateLimit', {
  value: headers.rateLimit
});

Yup

I also added the hidden rate limit property in another branch - let me know if I should merge it with this or submit another pull request.
Thanks for the guidance, I appreciate it.

Thanks :)

let me know if I should merge it with this or submit another pull request.

Another PR.


Enable push update for alarm_control_panel

Hub will send alarm status as mesh data. This code will allow alarm status to be instantly updated as apposed to polling the alarm state every few seconds.

@tam-wh does your XiaomiGateway3 fork have a working push update for alarm_control_panel that allows triggering the alarm?


Refining Token Functions and Docs

:tada: This PR is included in version 1.3.1 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:


Display installed plugins or features

Is your feature request related to a problem? Please describe.
Once we install external plugins, it would be beneficial to list the plugins somewhere for an overview
Describe the solution you'd like
In About menu, there can be another option for this
Describe alternatives you've considered
NA
Additional context
NA

✅ done


Add Bitcoinemv.eth to gov.bitcoinevm.com

Added custom domain for bitcoinevm.eth
Hi! What is your PR about?

[ ] Add or edit a skin
[x] Add a custom domain for your space
[ ] Add an alias to migrate your space

Can we get this merged @gokaiorg Thanks

Good


WIP: Chat clean 1

TODO

[x] split pr
[ ] team join error/success needs to move ot team
[ ] blue bar goes away too early
[ ] remove withstate
[ ] error message component commented out
[ ] check old sagas

done

[x] comments
[x] android touchable on messages black
[x] append teams tab not working
[x] select non existant convo does a preview
[x] no red banner on teams
[x] split actions file
[x] race w/ app focus on mobile
[x] loadingmap with push goes negative
[x] mobile save needs to check type? pdf crash?
[x] thread not marked read when entering for mobile push notification
[x] team header debug button
[x] info pane
[x] new-team-dialog
[x] block-conversation-warning
[x] create-team-header
[x] check for noflow
[x] preview convo
[x] selecting a thraed making multiple calls to load thread?
[x] message popup goes under keyboard
[x] big team header always on in desktop?
[x] mobile load from cold into thread, click back to inbox has a loading bar and is doing a ton of stuff maybe
[x] thread loading bar
[x] copy text missing
[x] snippets being lost?
[x] mulitple sync start calls maybe possible, use a count and not a bool
[x] dump chat button
[x] channels being lost / moving around?
[x] try remove clipped subview flag
[x] edit not prefilling
[x] unsent text isn't persisted
[x] push fast path
[x] custom menus for mobile popup
[x] inbox empty parts
[x] temp all acitons logged
[x] overdraw
[x] securing gif on bottom, load cnojima5 to see
[x] new convo button
[x] chat header has you
[x] attachment
[x] delete history (https://github.com/keybase/client/pull/10556)
[x] list scrolldown on change, lock to bottom moved to container
[x] reset users red message
[x] you are reset
[x] open selected folder
[x] reset let them in / chat w/o them
[x] participant rekey / rekey
[x] mark as read
[x] nav badges broken?
[x] typers
[x] superseded back  (71 has some w/ 74), component is ther but .need thread (untrusted cache doesn't have the superses) so we have to bookkeep and call it i guess. talk to mike about this
[x] superseded forward
[x] open in chat works w/ team folders
[x] small teams
[x] temp not loading localMetadata
[x] big teams
[x]  channel name mentions
[x] remove constants/chat
[x] delete attachment
[x] filtering
[x] login/logout not wokring?
[x] remove types/chat
[x] new chat updates snippet
[x] deleting snippet message
[x] editing snippet message
[x] muting updates inbox
[x] rekey (temp to force errors)
[x] rekey others
[x] empty
[x] always show
[x] loading
[x] reset participants
[x] unread
[x] badged
[x] notifications
[x] thread
[x] scrollback
[x] stale
[x] show menu
[x] selected message
[x] delete text (actually delete)
[x] send text
[x] pending => sent (grey/black)
[x] store partial input text (note: route tree change)
[x] typing is slow (note: resize multi line is slow)
[x] sorted immutable
[x] error list
[x] only update subsets of meta which actually change (participants, etc)
[x] edit text
[x] tabbbar thrash on inbox change
[x] edit last message (with tests)
[x] join / leave / system message types
[x] make inbox call on startup]
[x] send to unmade
[x] keep unsent text input
[x] create convo works (header isn't search actually)
[x] search works
[x] reset last select convo on search exit
[x] banner container
[x] disconnect routestate from selected convo
[x] identifybehavior switch
[x] editing recently sent
[x] new convo to existing broken?
[x] chat from team folder
[x] at mentions styling
[x] channel mentions
[x] user mention fullname search
[x] show notif
[x] read attachments
[x] full screen
[x] download attachments
[x] download progress
[x] download in menu
[x] show in finder links
[x] incoming attachment image shows as file
[x] delete message attachment plumbing not navigate up
[x] upload attachments (ensure messageid===ordinal so paths stay fixed), this outbox handling / mapping is complicated. lets try and not do this

[x] click
[x] drag drop

[x] upload to start a conv (maybe if its easy)
[x] edit too long doesnt' work
[x] send into nonexistant convo
[x] pending in its own list
[x] move broken tracker to new user meta store
[x] mark authors broken
[x] upload progress
[x] orange line

replaced by https://github.com/keybase/client/pull/10755


[bug] leading_ones failed test

#[test]
fn test_leading_ones() {
    use bitvec::prelude::*;
    const N: usize = 224;
    let mut map: BitArr!(for N, in LocalBits, u32) = BitArray::zeroed();
    for i in 0..N {
        map.set(i, true);
    }
    assert_eq!(map.leading_ones(), N); // actual value is 0
}

with N = 223 or N = 225 test is ok.
bitvec version = "0.22.3"
os = maxOS Catalina

This is the same error as reported in #127. I am currently focusing on releasing v1, and encourage my users to upgrade to it when able. If you are not, I am willing to release a fix on 0.22 once 1.0.0 is done.
Thank you for reporting it, though.

Okay now that I have a tracker for it, I'm going to close this. Please do re-open or otherwise ping me if you prefer to stay on 0.22 instead of move to 1.0, though! Closure is just to track what I have left to do, not a dismissal.


refactory AbstractChannelHandlerContext and DefaultChannelPipeline to avoid tight coupling

In the code of class AbstractChannelHandlerContext and DefaultChannelHandlerContext, DefaultChannelPipeline is used directly, not the interface ChannelPipeline.
I tried to replace DefaultChannelPipeline with interface ChannelPipeline, but found that in AbstractChannelHandlerContext the method DefaultChannelPipeline.touch() is invoked, which is not defined in the interface ChannelPipeline.
The way to resolve this is add the touch() method in the interface ChannelPipeline, then we can safely replace all the DefaultChannelPipeline with ChannelPipeline. --- This is what I do in the first commit.
Yet here it is still a question: should the touch() method be a part of ChannelPipeline? Of cause not.
So I tried to do the second update: I found that the implementation of touch() method is independent to the actual implementation of ChannelPipeline, and only class AbstractChannelHandlerContext invokes the touch() method. It is reasonable to move the touch() logic from ChannelPipeline to AbstractChannelHandlerContext.
The final result of above two commit:

the touch() method and touch attribute are moved from class DefaultChannelPipeline to class AbstractChannelHandlerContext.

AbstractChannelHandlerContext and DefaultChannelHandlerContext now use pure interface ChannelPipeline, not implementation DefaultChannelPipeline any more.

interface ChannelPipeline is not changed.

It seems more clear and less coupling now. Do you like this refactory?

@skyao the reason why the touch boolean was at pipeline once instead of each context was to minimize menory impact

"private final boolean touch = ResourceLeakDetector.isEnabled();"
Perhaps we should change this touch boolean to static so that we will only have ONE touch boolean?

No because you can change the detector level ob the fly

Am 19.12.2015 um 15:32 schrieb Sky Ao<EMAIL_ADDRESS>"private final boolean touch = ResourceLeakDetector.isEnabled();"
Perhaps we should change this touch boolean to static so that we will only have ONE touch boolean?
—
Reply to this email directly or view it on GitHub.

In current implementation, boolean touch is defined in class DefaultChannelPipeline:
"private final boolean touch = ResourceLeakDetector.isEnabled();"
When the instance of DefaultChannelPipeline is created, this touch boolean will initial and never change later.
The only chance that we can make updated detector level to work is when we create new DefaultChannelPipeline instance, it means new Channel / new connection.

Moving touch boolean from class DefaultChannelPipeline to class AbstractChannelHandlerContext won't change this logic.
But the code is more clear. I don't like the code style that AbstractChannelHandlerContext can/must "see" DefaultChannelPipeline ^0^

@skyao it is correct that the touch stuff can only change for "new connections", but that is good enough. As @ninja- already said it was done this way because of memory usage. This is because it is not unusually to have a ChannelPipeline with a lot of ChannelHandlers that each has an ChannelHandlerContext. This may sound not as a big problem but we are talking about serving a lot of concurrent connections and so want to safe as much memory as possible in the core.
So I'm sorry I will close this because of the stated reasons.


Ensure ObjectWriter package does not get used on ObjWriterBuild mode

Thanks jan! I'll follow up soon on the test fails.


Refactoring existing input text/ query dynamic input text/ query input text/ num input components

Add support for multiline inputs in following components:

[ ] DynamicTextControl
[ ] InputTextControl

@rashmi-rai to be linked to the ADS PR

@ayushpahwa @Irongade could you please confirm if this is already done? I think Rashmi had mentioned that she had worked on this with her ADS PR.

@nidhi-nair this is a nice to have feature and we should avoid making changes to the current redux-form lib as it is already deprecated. We should work on this once we pick up more performant libraries like hookforms for our editor. Have updated the description of the issue too.


support pre / post middlewares

Hey, I've been using tsoa & typoa in sort of a mix and wanted to know if it's possible to add support of tsoa's 'PreMiddleware' capability to the generated clients
It's coming very handy in adding headers, and in general intercepting requests.
Thanks!

That's a great idea, why did you close the issue?

I realized it's a feature that the codegen library needs to add, am I wrong? Opened it there as a feature request


Web console: quote columns, datasources in auto complete if needed

Auto complete should add the proper quotes if the column / datasource / schema needs it (like if it is reserved).

@vogievetsky , cool this is handled in the UI. I want to make sure from the docs side we're making it clear about the appropriate use of quotes in query syntax.


ASR Diarization Endpoint

So looks like the ASR repo is adding whisperx support, which adds diarization options.
https://github.com/ahmetoner/whisper-asr-webservice/pull/125
I def want to add this but wanted to touch base on how you wanted to do it. I'm thinking we need an additional option in the command palette to trigger the transcribe option, but not sure yet if we need to use the min/max speaker options as well.
I'll keep you posted once the ASR PR is done.

As a community thought, I would think having a min/max/auto option for quantity of speakers would be goods.

An additional option only available when ASR is selected would make the most sense. Don't have bandwidth for major additions like this at the moment, will review PR.

Roger that. The ASR PR has some problems and could be some time for me as well. I'll keep you posted when there's an update.

Not sure if this is the right place to ask but could I ask what ASR url should I provide in the plugin setting? I tried hosting a docker run locally and provided ip address (e.g. http://<IP_ADDRESS>:9000/asr) but didn't work.
Any help is appreciated!


No display in terminal window when launched from finder when not added to os path (macOS)

There seems to be a regression with the terminal display (downloaded today's nightly for macOS) where there is no display in the terminal window when launched from finder.  However after adding oni2 to the os path and launching from the terminal it works fine. Then when launching from finder/spotlight after that the terminal displays correctly.  I can't post a screenshot anymore as it now works fine for me, but will be an issue for new users (I just setup a new machine) that haven't yet added oni2. to the system path.

Thanks for reporting the issue, @yunti !
Trying to reproduce this - what version of OSX does the machine have? I'm assuming Catalina / 10.15?
I haven't been able to reproduce it yet - but it's interesting that the problem went away after the first time launching from the terminal. Trying to set up a fresh catalina install to reproduce that issue.
I noticed that, on catalina, we're defaulting to the bash shell instead of zsh for some instances - but I don't think that would cause the terminal not to show at all.

I haven't been able to reproduce this in the latest builds (I've been exercising this as a test case: https://github.com/onivim/oni2/blob/master/manual_test/cases.md#12-validate-launches-from-dock-in-osx-2659)
Let me know if you happen to see it again, though


RFC: Frontend event tracking

This is an RFC which outlines a solution for collecting analytics events on the frontend. Please see the 'files changed' diff for the full text.
Reviewers

@krysal
@dhruvkb

Deadline
2022-12-16

Thanks for confirming.

@krysal I've added questions each event aims to answer in the comments of each event. I've also made many updates based on user feedback; please see the commit history for detail on each of these additions. This is ready for a final re-review and anyone can provide additional feedback. Thank you!

@zackkrida Something that just occurred to me, do you think we could implement RUM performance data into the events here or should we use a separate tool for it? RUM performance data can be super useful for identify performance issues that only affect a small subsection of clients. It could also supplement things like Google Lighthouse scores and trying to debug issues with specific parts of the lighthouse score.

@sarayourfriend I think that's a great idea. It honestly didn't occur to me either. We could definitely do this by creating new events which track Core Web Vitals-esque events, and maybe by adding performance timing information to appropriate events already defined here.
My only initial concern is that those events might add considerable time and testing to implement, and I am undecided if they should be in the first 'mvp' of this event tracking or if they would be better-suited to a standalone project. One consideration pushing me towards waiting is that Cloudflare already has some tracking of RUM metrics. They provide the 50th, 75th, 90th, 99th percentile performance for a few metrics:

Cumulative Layout Shift (CLS)
First Input Delay (FID)
Largest Contentful Paint (LCP)

Details here. We can evaluate that for Openverse and see if it's sufficient prior to doing our own implementation. A good test would actually be to use that CloudFlare information to see if @obulat's cookie PR shows a reduction in layout shift!
Do you think that's reasonable? Is it preferable to prioritize RUM in this RFC?

One consideration pushing me towards waiting is that Cloudflare already has some tracking of RUM metrics.

Do you think that's reasonable? Is it preferable to prioritize RUM in this RFC?

I think it is reasonable to intentionally exclude it, but that we should prioritise writing a follow up RFC that includes a wholistic approach to analysis that would include data aside from multiple sources (database, Cloudflare, custom events). It seems to me this would fit quite naturally in the scope of the RFC you mentioned @dhruvkb is interested in writing regarding the usage of the data (including the backend provider for event ingestion).

I read the questions we would like to get answers to, and I think we are covering most use cases.
@krysal pointed out the amount of copying attribution information, and I would link it with clicking on Use this [content type] button to see the relationship. This flow is crucial to see whether using a piece of content is concatenated to copying the attribution information.
Here are other questions I am curious to know per feature/section:

Use of filters: How often is the filter opened/closed during a search? There is a question about visibility preference, but I am curious if users shift between showing and hiding the sidebar during one search.
Browsing on All content results: When opening content details from All content results, do users keep browsing on the same content type or go back to All content results? The point behind this is understanding whether All content results works as showcasing content type and Openverse potential, or as a result page to keep browsing.
Using meta search: After how many loading results do users use the meta search feature? To see users' tolerance for getting no "relevant results", or results not matching what they expect to see.

Great document. It describes clearly what we aim for.

@krysal I'll address your other comments too, but regarding the implementation of this and the concern that "this would largely be a wasted effort":
Even if we knew what backend we were using today, we still have to implement the frontend event tracking. Which will take time; likely weeks. I am not saying we can't or shouldn't work on the backend, only that this frontend work shouldn't be coupled to that backend work. I don't think having all the event tracking code written, but disabled behind a flag to not actually post anywhere is a waste of time.
Also, I am recommending here that each event be written as a separate small issue. To me, it makes sense to write and add these events individually while the feature is disabled. Instead of enabling events one by one into a live analytics system. This way we can turn on analytics tracking at one time and all of the initial events outlined here will have the same start date.
I would definitely recommend we come up with a backend as soon as we reasonably can, something like you suggested, or a single postgres table somewhere. Anywhere we can store the actual events and query them later, import them into a UI, etc. The only point I'm suggesting is that the frontend work, which needs to happen regardless, isn't blocked by the backend.
Regarding the number of events, is this section:

each one of the 21 types of events

meant to suggest you think there are too many events here for the initial implementation? If so, that sounds like important information to share. I would definitely be open to narrowing the list to a smaller subset of events for the initial implementation if anyone felt that was a better path forward and explained why 😄.

@zackkrida I see your point on the backend planning not blocking the frontend work, and agree. Maybe I just have said that as a whole project, this RFC alone feels sort of incomplete, but if a subsequent one will come after this, then it makes sense to start this implementation in parallel to the planning of the backend 💯

Regarding the number of events, is this section:

each one of the 21 types of events

meant to suggest you think there are too many events here for the initial implementation?

No, I think is a good number! 😄 I just would need to give it a look at another time, so I'll come back to this next week. Thanks for addressing some of the concerns so quickly!

Also, if @obulat approves before I get to it, that can count as my approval well 😄 Given @obulat is one of the main contributors to the frontend her opinion is extremely relevant here.

Although the log file would surely need rotational maintenance due to all the per-session events that would be handled, it would grow incredibly fast

We could use logs as a temporary backend but:

It is relatively (though not prohibitively) expensive to store, as Krystle mentioned
It is expensive to query, both monetarily and in time
It offers us relatively zero easily-usable immediate feedback for any of this data and would require additional time that I assume most dedicated analytics providers automatically do (event frequency, session browsing, etc)
Because it is technically unstructured we'd have to parse logs ourselves to get them into an eventual data lake for further processing (for example, document relevance derivation) or extract it from the logstash's index (probably not possible with CloudWatch and difficult otherwise)

On the other hand, it is extremely portable given we could switch our log transport to use Loki instead of CloudWatch via Grafana Cloud. Loki's approach is more appropriate for that kind of thing than CloudWatch's... but again, we lose the significant benefits that an actual analytics provider would give us.

I came across some documentation about the Reporting API [MDN] and [Chrome]. It's an additional piece that can be factored in as an extra data source on the frontend to capture some dev-specific metrics like crashes and deprecations.

@dhruvkb Sentry already collects that data. Do you think it's necessary to duplicate it in our own event stream?

I read some post about the ReportingObserver API and it seemed like a good integration so I shared those links. I didn't know Sentry already collected that which is my bad, I didn't do my due diligence there.
Based on a cursory look at their docs, it seems like it is an optional integration that could be enabled. Nonetheless, if that info is (or can be) collected in Sentry, that's a better, more logical place to have that info.

Based on a cursory look at their docs, it seems like it is an optional integration that could be enabled. Nonetheless, if that info is (or can be) collected in Sentry, that's a better, more logical place to have that info.

@dhruvkb (and for anyone else unaware) It is enabled by default via the NuxtJS plugin that we use to configure Sentry: https://sentry.nuxtjs.org/sentry/options#clientintegrations
This issue in the frontend repository includes links to some issues that were surfaced from the ReportingObserverAPI in Sentry: https://github.com/WordPress/openverse-frontend/issues/1610
I only know about this because I had to triage those issues when they first appeared :sweat_smile: Unless the integration is broken we should still be getting ReportingObserverAPI issues.

@krysal thank you so much! You identified some critical missing data in a few of these events. This is ready for re-review when you are able.

@WordPress/openverse I'm not able to figure out this linting issue. The precommit and linting works locally without any changes. Any ideas what's going on here?

@zackkrida I had the same inability to reproduce the linting error locally. It turned out it needed a rebase. I rebased and pushed the linting fix.


Docker version of cloud-nuke

Here is my take on a docker version of cloud-nuke, as per the issue https://github.com/gruntwork-io/cloud-nuke/issues/164
I've added a Dockerfile, a .dockerignore file and a small shell script to build and verify the binary.

@sev-obviux  I would add an args function to allow people to do things like excludes.

@sev-obviux  I would add an args function to allow people to do things like excludes.

I'll follow your suggestions and update the PR and let you know

I'll follow your suggestions and update the PR and let you know

I've updated the PR with my response to your feedback.
I'm not comfortable with writing a Go test yet, and cannot really justify the time for it. Sorry.
I had an idea while refactoring.... do you want to have all the docker things in a subfolder instead of the root?

I've updated the PR with my response to your feedback.
I'm not comfortable with writing a Go test yet, and cannot really justify the time for it. Sorry.
I had an idea while refactoring.... do you want to have all the docker things in a subfolder instead of the root?

I've updated the PR with my response to your feedback.
I'm not comfortable with writing a Go test yet, and cannot really justify the time for it. Sorry.

I understand. Unfortunately, if it's not tested in our CI build, it will likely break over time, so I don't think we could merge it.

I had an idea while refactoring.... do you want to have all the docker things in a subfolder instead of the root?

That seems like a good idea!

I've updated the PR with my response to your feedback.
I'm not comfortable with writing a Go test yet, and cannot really justify the time for it. Sorry.

I understand. Unfortunately, if it's not tested in our CI build, it will likely break over time, so I don't think we could merge it.

I had an idea while refactoring.... do you want to have all the docker things in a subfolder instead of the root?

That seems like a good idea!

I understand. Unfortunately, if it's not tested in our CI build, it will likely break over time, so I don't think we could merge it.

I see. So what do we do here? Do you or anyone on your team want to make the unit test?
I can make it easy, so there's a unit test bash script that you just run and then check that the return code is 0
If you agree to that, then I'll make the unit test script and put it in docker/unit-test.sh

I understand. Unfortunately, if it's not tested in our CI build, it will likely break over time, so I don't think we could merge it.

I see. So what do we do here? Do you or anyone on your team want to make the unit test?
I can make it easy, so there's a unit test bash script that you just run and then check that the return code is 0
If you agree to that, then I'll make the unit test script and put it in docker/unit-test.sh

I understand. Unfortunately, if it's not tested in our CI build, it will likely break over time, so I don't think we could merge it.

I see. So what do we do here? Do you or anyone on your team want to make the unit test?
I can make it easy, so there's a unit test bash script that you just run and then check that the return code is 0
If you agree to that, then I'll make the unit test script and put it in docker/unit-test.sh

As you can see in the delays in my replies, we are super buried right now, and unfortunately, can't devote as much time as we'd like to cloud-nuke. Even adding a simple test can turn into a long yak shave that derails some of our other work. Sorry about that 😞

I understand. Unfortunately, if it's not tested in our CI build, it will likely break over time, so I don't think we could merge it.

I see. So what do we do here? Do you or anyone on your team want to make the unit test?
I can make it easy, so there's a unit test bash script that you just run and then check that the return code is 0
If you agree to that, then I'll make the unit test script and put it in docker/unit-test.sh

As you can see in the delays in my replies, we are super buried right now, and unfortunately, can't devote as much time as we'd like to cloud-nuke. Even adding a simple test can turn into a long yak shave that derails some of our other work. Sorry about that 😞

I understand, that happens to me all the time too. No hard feelings.
Would you like me to cancel the PR or do you want to keep it around for whenever?

Let's keep it open in case someone in the future has the time to fill in the gaps! If we close now, we'll prob forget it about it otherwise, and we can always close later.

Deal :)

I'm cleaning up my repos. This PR is so old that it now has conflicts with master and I cannot priorititze fixing it. I'm cancelling this PR and nuking my fork, to clean up.

Thanks @sev-obviux for your contribution despite not being able to support you fully on it!


Text & Indicator Colors

How to change text(skip) and indicator color in bottom layout? (By default just White Color) Thanks

This is done with styles. Look at LightWelcomeScreenTheme in the sample styles for an example.


Build hypertopolvm inside docker

support docker multi-stage build.

@toshipp Thanks for replying.
OK. I'll do that.

I think now all points are fixed.

Fixed dockerfile and Makefile.
(Sorry force pushing. I missed committing some debug line)


ES6. double letter with detect methods or var.

all version vs code have bug with ES6 + Russian language

then press tab or click

and we have ккомпонент in place компонент - double кк, first letter.

is this our word definition?

word, class, property

tab

class БазоваяВыборка {
constructor(имяКлассаДиалогаЛиста) {
}
}

yeah, internally we have regular expression that defines a word. I guess we only match on a subset of the unicode characters. Thanks for pasting, with that I can play.

This is an issue with the JS word def. Will take for Jan16


Group update suggests incompatible upgrade with Cargo

Is there an existing issue for this?

[X] I have searched the existing issues

Package ecosystem
cargo
Package manager version
No response
Language version
No response
Manifest location and content before the Dependabot update
Main one: https://github.com/metatypedev/metatype/blob/main/Cargo.toml
Nested one: https://github.com/metatypedev/metatype/blob/main/meta-cli/Cargo.toml and more
dependabot.yml content
version: 2
updates:
  - package-ecosystem: github-actions
    directory: /
    schedule:
      interval: monthly
    groups:
      deps:
        patterns:
          - "*"
  - package-ecosystem: cargo
    directory: /
    schedule:
      interval: monthly
    groups:
      deps:
        patterns:
          - "*"
  - package-ecosystem: pip
    directory: /typegraph
    schedule:
      interval: monthly
    groups:
      deps:
        patterns:
          - "*"
  - package-ecosystem: pip
    directory: /
    schedule:
      interval: monthly
    groups:
      deps:
        patterns:
          - "*"
  - package-ecosystem: npm
    directory: /website
    schedule:
      interval: monthly
    groups:
      deps:
        patterns:
          - "*"

Updated dependency
https://github.com/metatypedev/metatype/pull/362
What you expected to see, versus what you actually saw

indexmap is considered as incompatible, it should not be included
swc_* are pinned, they should not be included

See native output below.
Native package manager behavior
    Checking meta-cli's dependencies
name          old req compatible latest  new req note
====          ======= ========== ======  ======= ====
clap          4.3.11  4.3.14     4.3.14  4.3.14
globset       0.4.10  0.4.11     0.4.11  0.4.11
anyhow        1.0.71  1.0.72     1.0.72  1.0.72
indoc         2.0.2   2.0.3      2.0.3   2.0.3
serde         1.0.166 1.0.171    1.0.171 1.0.171
serde_json    1.0.100 1.0.103    1.0.103 1.0.103
tar           0.4.38  0.4.39     0.4.39  0.4.39
serde_yaml    0.9.22  0.9.23     0.9.23  0.9.23
indexmap      1.9.3   1.9.3      2.0.0   1.9.3   incompatible
enum_dispatch 0.3.11  0.3.12     0.3.12  0.3.12
semver        1.0.17  1.0.18     1.0.18  1.0.18
assert_cmd    2.0.11  2.0.12     2.0.12  2.0.12
    Checking typescript's dependencies
name                           old req   compatible latest  new req   note
====                           =======   ========== ======  =======   ====
anyhow                         1.0.71    1.0.72     1.0.72  1.0.72
swc_common                     =0.31.12  0.31.12    0.31.17 =0.31.12  pinned
swc_ecma_ast                   =0.104.5  0.104.5    0.107.1 =0.104.5  pinned
swc_ecma_parser                =0.134.12 0.134.12   0.137.3 =0.134.12 pinned
swc_ecma_codegen               =0.139.17 0.139.17   0.142.3 =0.139.17 pinned
swc_ecma_visit                 =0.90.5   0.90.5     0.93.1  =0.90.5   pinned
swc_ecma_transforms_typescript =0.177.23 0.177.23   0.180.8 =0.177.23 pinned

Images of the diff or a link to the PR, issue, or logs
No response
Smallest manifest that reproduces the issue
No response

Dependabot will update pinned dependencies, that's normal behavior. You can set an ignore rule to get it to leave a dependency alone.
Dependabot doesn't currently filter out incompatible releases for Cargo, that seems like it would be a nice feature. It's not obvious to me why it's incompatible though?


[Recommend] Add a brand new command: az next

Description

Add a new command az next.  This command is not fully complete yet. Just for illustration purposes only.
Testing Guide

No local test yet.
History Notes

[Web API] Query next command from web API. (not tested yet)
TODO List

[ ] Send feedback
[ ] Get last command from local history
[ ] Update UI/UX for multiple recommendations.

Move code to another branch


README.md is inaccurate for totp.verify_with_drift_and_prior

verify_with_drift_and_prior returns nil (not false) when OTP is invalid.

Could you elaborate more on your case @samueltangz ?
I did a quick check of the source code. And the result should come from
https://github.com/mdp/rotp/blob/c82113eee6c9e7d0a03df8cf65ea50a2653c3916/lib/rotp/otp.rb#L86
which, as you can see, always return a boolean result of a comparison with 0

Sorry for being unclear...  when using totp.verify_with_drify_and_prior, the doc said that it would return the timestamp when the token is valid, and false otherwise:
https://github.com/mdp/rotp#preventing-reuse-of-time-based-otps
However, from the line of code below, it returns nil instead of false.
https://github.com/mdp/rotp/blob/master/lib/rotp/totp.rb#L72

@samueltangz I think I know what you mean now. Just submitted a PR for that ^

seems legit. many thanks!

Updated the v3.x docs to reflect this error. It's been out in the wild for a while now and rather than fix it in v3.x, I'm going to let it stand in an abundance of caution to not break anyone implementation, as the latest version (4.x) doesn't have this issue.


Present the offence class(es), comma separated

Description of change
This is a tweak to adapt the way we show the offence class in the views, to the requirements of the design.
First, we unify the presentation of the class in just one single place (OffencePresenter). This presenter works with Offence instances thus always will have class attributes.
Additionally modify the existing ChargePresenter use the new OffencePresenter also to present information related to the offence, including the class.
Last, a new OffenceCollectionDecorator takes care of the offences dropdown, also presenting them with the new OffencePresenter so class is presented comma-separated as well.
Screenshots of changes (if applicable)

How to manually test the feature
See in the dropdown the different classes, and add some with one or more classes to see them in the basket too.

Only thing I was thinking is that we could have map_with_decorator / map_with_presenter and it might look more rubyish small thing though

@willmcb Yeah, I was unsure on the naming tbh. I went with those naming because didn't want to imply a yielding method.
For example, #map_with_decorator it feels to me like it will yield each element, like this:
@collection.map_with_decorator(Decorator) do |elem|
[...]
end

# as in a traditional map:
@collection.map do |elem|
[...]
end

So I thought, maybe naming it in the "past", implies that the operation was performed, and thus it returns the result, not giving a sense of yielding each element? 🤔

Yeah I can see that, it does sort of mix meanings with the traditional each_with_object kind of way - I think what we have is fine tbh 👍


New name of project

I think, what current name is temporary. Good chance for change name when this project get breaking changes


Remove nocheck option

Remove the option nocheck. It's described as follows in the current (v0.04) version:

nocheck                    Do not show suggestions to check and only show style problems

Note that this should also be removed in the help file

#26 is still not working for me, and I believe the issue is still related to #30

resolved by #26

@luizaandrade can we close this issue now or should we wait until #32 is merged into main?


fatal error: 'opencv2/core/version.hpp' file not found (Apple M1)

Plugin Version or Commit ID
V0.10.0
Unity Version
2021.3.3.f1
Your Host OS
Apple M1 MacOS Monterey
Target Platform
UnityEditor, Mac Standalone
[Windows Only] Visual Studio C++ and Windows SDK Version
No response
[Linux Only] GCC/G++ and GLIBC Version
No response
[Android Only] Android Build Tools and NDK Version
No response
[iOS Only] XCode Version
No response
Command Sequences
python build.py build --desktop cpu -vv
Log
external/com_google_mediapipe/mediapipe/framework/port/opencv_core_inc.h:18:10: fatal error: 'opencv2/core/version.hpp' file not found
#include <opencv2/core/version.hpp>
^~~~~~~~~~~~~~~~~~~~~~~~~~
1 error generated.
Error in child process '/usr/bin/xcrun'. 1
Target //mediapipe_api:mediapipe_desktop failed to build
INFO: Elapsed time: 2.086s, Critical Path: 1.03s
INFO: 156 processes: 132 internal, 24 darwin-sandbox.

Additional Context
I am trying to build the package on M1 laptop but keep getting this error. The OpenCV was installed under the /opt/homebrew/opt/opencv@3.

Thank you for reporting the issue.
This is fixed by #592.
You can also work around this issue by linking OpenCV dynamically (python build.py build --desktop cpu --opencv cmake -vv).

Thanks for the swift fix! It works now.


[Event Request] Table 1237 Transformation Rule

The following events are required for this object:
    [IntegrationEvent(false, false)]
    procedure OnBeforeTestTransformationType(var TransformationRule: Record "Transformation Rule"; xTransformationRule: Record "Transformation Rule"; var IsHandled: Boolean)
    begin
    end;

        field(16; Length; Integer)
        {
            BlankZero = true;
            Caption = 'Length';

            trigger OnValidate()
            var
                IsHandled: Boolean;
            begin
                if "Transformation Type" = "Transformation Type"::Substring then
                    if Length < 0 then
                        Error(MustBeGreaterThanZeroErr);

                //EVENT REQUEST
                IsHandled := true;
                OnBeforeTestTransformationType(Rec, xRec, IsHandled);
                if IsHandled then
                    exit;
                //EVENT REQUEST

                if Length <> 0 then begin
                    TestField("Transformation Type", "Transformation Type"::Substring);
                    Validate("Ending Text", '');
                end;
            end;
        }

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 11320.


Bug: Entry resolves before async resolve call the callback function

This is a regression from beta.25 or higher.
Expected Behaviour
The resolve event should be asynchronous and need to wait for all plugins callbacks before continuing the resolution, but doesn't (at least for the entry).
Actual Behaviour
Right now, webpack does not wait for all resolve handlers before continuing the resolution.
The following Webpack configuration (custom plugin) will finish the bundle, THEN wait 10 seconds for the resolve to finish.
module.exports = {
  resolve: {
    extensions: ['.js']
  },
  entry: './entry.js',
  output: {
    path: './dist',
    publicPath: 'dist/',
    filename: 'app.main.js'
  },
  plugins: [
    new function () {
      this.apply = function (compiler) {
        compiler.plugin('after-resolvers', function (compiler) {
          compiler.resolvers.normal.plugin('resolve', function (request, cb) {
            setTimeout(cb, 10000);
          });
        });
      };
    },
  ]
};

It's correct this way.
with your resolve plugin you add an alternative how to resolve modules. Because you add it after the original resolvers the original resolving algorithm has higher priority. From logical point of view your plugin is only used if the original algorithm is not successful. For performance reasons hooks are not executed in sequence but parallel (see applyPluginsParallelBailResult in tapable) with a bailing callback handler. This means if the first plugin (the original resolving algorithm) returns a result the result of the second plugin is ignored and it doesn't need to wait for it.
You can try to resolve a request that can't be resolved by the original algorithm (like ./eeeentry.js) and it should wait for your plugin to finish.

So you're saying the best way for me to wait for my entry point's dependency (because TypeScript will error if I compile too early) to be ready is to either rename the entry point to something that doesn't exist, or hook up before-resolve?
I understand how and why you do it, but isn't there a way to shut the original resolver for certain filetypes?

As there seams to be nothing happening anymore here, I will close this for now.
Feel free to reopen, if you think this needs to be resolved.


Add Experience Section #547

Purpose
Add Experience Section. Fixes #538
This is a correction to my first commit: Pull #547
Screenshots

Documentation
I've added the files using the name "work". I've also changed the config.toml file to include the date format for the experiences (under param.work). Also, I've included the specific translations to the language files, and some CSS options for the work widget.

@shaform @prateekkumarweb Thank you for the heads up. I've corrected it.

Closing as this is very similar to #378

Hi @gcushen, but #378 doesn't seem to have an implementation yet. Is there any plans to actually implement it in the near future? Thanks.


Produce correct tables in SQL PGDS acceptance tests

The previous logic created a table for each reltype (e.g. R) according
to the OKAPI schema. However, (A)-[R]->(B) and (A)-[R]->(C) are
different rel types in DDL/SQL PGDS world. We therefore need to create
tables for each DDL rel Type in order to create non-overlapping input
tables. This is achieved by joining relation tables with their incident
node tables to get the actual relationships.

Thanks a lot for this fix.
So there was never an issue with the DDL or SQL PGDS, but only with how we generated the tables for the initial test graphs?

Yes. We can add validation in the GraphDDL IR construction that checks if the same view is not used for multiple rel types (same for nodes).