[Xamarin.Android] Add docs for xamarin android

Adds documentation for xamarin android and API definitions

Docs Build status updates of commit fc6bf75:
:warning: Validation status: warnings

File
Status
Preview URL
Details

AdaptiveCards/sdk/rendering-cards/xamarin/android/Xamarin.Android.docs.md
:warning:Warning

Details

AdaptiveCards/sdk/rendering-cards/xamarin/android/actions.md
:warning:Warning

Details

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-renderin-xamarin-android-renderer-actionhandler-icardactionhandler.md
:warning:Warning

Details

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-objectmodel-featureregistration.md
:warning:Warning

Details

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-renderer-adaptivecardrenderer.md
:warning:Warning

Details

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-renderer-cardrendererregistration.md
:warning:Warning

Details

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-renderer-renderedadaptivecard.md
:warning:Warning

Details

AdaptiveCards/sdk/rendering-cards/xamarin/android/getting-started.md
:warning:Warning

Details

AdaptiveCards/sdk/rendering-cards/xamarin/android/host-config.md
:warning:Warning

Details

AdaptiveCards/sdk/rendering-cards/xamarin/android/render-a-card.md
:warning:Warning

Details

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-objectmodel-adaptivecard.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/xamarin/android/native-styling.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/xamarin/android/Xamarin.Android.docs.md

[Warning] Missing attribute: author. Add the current author's GitHub ID.
[Warning] Missing attribute: title. Add a title string to show in search engine results.
Line 0: [Warning] Invalid file link:(~/sdk/rendering-cards/xamarin/android/adaptivecardrenderer-func-render0).
Line 0: [Warning] Invalid file link:(~/sdk/rendering-cards/xamarin/android/adaptivecardrenderer-func-render1).
Line 0: [Warning] Invalid file link:(~/sdk/rendering-cards/xamarin/android/funcDeserializeFromString).
Line 0: [Warning] Invalid file link:(~/sdk/rendering-cards/xamarin/android/funcDeserializeFromString).
Line 0: [Warning] Invalid file link:(~/sdk/rendering-cards/xamarin/android/funcDeserializeFromString).
Line 0: [Warning] Invalid file link:(~/sdk/rendering-cards/xamarin/android/funcDeserializeFromString).
Line 0: [Warning] Invalid file link:(~/sdk/rendering-cards/xamarin/android/funcDeserializeFromString).
Line 0: [Warning] Invalid file link:(~/sdk/rendering-cards/xamarin/android/funcDeserializeFromString).
Line 0: [Warning] Invalid file link:(~/sdk/rendering-cards/xamarin/android/funcDeserializeFromString).
Line 0: [Warning] Invalid file link:(~/sdk/rendering-cards/xamarin/android/feature-registation-func-addfeature).
Line 0: [Warning] Invalid file link:(~/sdk/rendering-cards/xamarin/android/icardactionhandler-func-onmediaplay).
Line 0: [Warning] Invalid file link:(~/sdk/rendering-cards/xamarin/android/icardactionhandler-func-onaction).
Line 0: [Warning] Invalid file link:(~/sdk/rendering-cards/xamarin/android/icardactionhandler-func-onmediastop).
Line 0: [Warning] Invalid file link:(~/sdk/rendering-cards/xamarin/android/cardrendererregistration-func-registerfeatureregistration).
Line 0: [Warning] Invalid file link:(~/sdk/rendering-cards/xamarin/android/renderedadaptivecard-func-addwarning).
Line 7: [Warning] Invalid link: 'Summary'. The file sdk/rendering-cards/xamarin/android/Xamarin.Android.docs.md doesn't contain a bookmark named 'adaptive-card-summary'.
Line 8: [Warning] Invalid link: 'Public Constructors'. The file sdk/rendering-cards/xamarin/android/Xamarin.Android.docs.md doesn't contain a bookmark named 'adaptive-card-public-ctors'.
Line 9: [Warning] Invalid link: 'Public Methods'. The file sdk/rendering-cards/xamarin/android/Xamarin.Android.docs.md doesn't contain a bookmark named 'adaptive-card-public-methods'.
Line 16: [Warning] Invalid link: 'Renderer'. The file sdk/rendering-cards/xamarin/android/Xamarin.Android.docs.md doesn't contain a bookmark named 'renderer'.

AdaptiveCards/sdk/rendering-cards/xamarin/android/actions.md

Line 11: [Warning] Invalid file link:(~/sdk/rendering-cards/xamarin/android/icardactionhandler.md).

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-renderin-xamarin-android-renderer-actionhandler-icardactionhandler.md

Line 0: [Warning] Invalid file link:(~/sdk/rendering-cards/xamarin/android/icardactionhandler-func-onmediaplay).
Line 0: [Warning] Invalid file link:(~/sdk/rendering-cards/xamarin/android/icardactionhandler-func-onaction).
Line 0: [Warning] Invalid file link:(~/sdk/rendering-cards/xamarin/android/icardactionhandler-func-onmediastop).
Line 9: [Suggestion] H1 is required. Use a single hash (#) followed by a space to create your top-level heading. NOTE: This Suggestion will become a Warning on 01/06/2020.

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-objectmodel-featureregistration.md

Line 0: [Warning] Invalid file link:(~/sdk/rendering-cards/xamarin/android/funcDeserializeFromString).
Line 0: [Warning] Invalid file link:(~/sdk/rendering-cards/xamarin/android/funcDeserializeFromString).
Line 0: [Warning] Invalid file link:(~/sdk/rendering-cards/xamarin/android/feature-registation-func-addfeature).

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-renderer-adaptivecardrenderer.md

Line 0: [Warning] Invalid file link:(~/sdk/rendering-cards/xamarin/android/adaptivecardrenderer-func-render0).
Line 0: [Warning] Invalid file link:(~/sdk/rendering-cards/xamarin/android/adaptivecardrenderer-func-render1).
Line 9: [Suggestion] H1 is required. Use a single hash (#) followed by a space to create your top-level heading. NOTE: This Suggestion will become a Warning on 01/06/2020.

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-renderer-cardrendererregistration.md

Line 0: [Warning] Invalid file link:(~/sdk/rendering-cards/xamarin/android/cardrendererregistration-func-registerfeatureregistration).
Line 9: [Suggestion] H1 is required. Use a single hash (#) followed by a space to create your top-level heading. NOTE: This Suggestion will become a Warning on 01/06/2020.

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-renderer-renderedadaptivecard.md

Line 0: [Warning] Invalid file link:(~/sdk/rendering-cards/xamarin/android/renderedadaptivecard-func-addwarning).

AdaptiveCards/sdk/rendering-cards/xamarin/android/getting-started.md

Line 25: [Warning] Invalid file link:(~/sdk/resources/media/tools/wpfvisualizer.png).
Line 33: [Warning] Invalid file link:(~/sdk/rendering-cards/xamarin/android/class-index.md).

AdaptiveCards/sdk/rendering-cards/xamarin/android/host-config.md

Line 11: [Warning] Invalid file link:(~/sdk/rendering-cards/host-config.md).
Line 13: [Warning] Invalid file link:(~/sdk/rendering-cards/xamarin/android/hostconfig.md).
Line 13: [Warning] Invalid file link:(~/sdk/rendering-cards/xamarin/android/hostconfig.md#something).

AdaptiveCards/sdk/rendering-cards/xamarin/android/render-a-card.md

Line 39: [Warning] Invalid file link:(~/sdk/rendering-cards/xamarin/android/icardactionhandler.md).

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 9189d1b:
:warning: Validation status: warnings

File
Status
Preview URL
Details

AdaptiveCards/sdk/rendering-cards/xamarin/android/actions.md
:warning:Warning

Details

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-renderin-xamarin-android-renderer-actionhandler-icardactionhandler.md
:warning:Warning

Details

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-objectmodel-featureregistration.md
:warning:Warning

Details

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-renderer-adaptivecardrenderer.md
:warning:Warning

Details

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-renderer-cardrendererregistration.md
:warning:Warning

Details

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-renderer-renderedadaptivecard.md
:warning:Warning

Details

AdaptiveCards/sdk/rendering-cards/xamarin/android/getting-started.md
:warning:Warning

Details

AdaptiveCards/sdk/rendering-cards/xamarin/android/host-config.md
:warning:Warning

Details

AdaptiveCards/sdk/rendering-cards/xamarin/android/render-a-card.md
:warning:Warning

Details

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-objectmodel-adaptivecard.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/xamarin/android/native-styling.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/xamarin/android/actions.md

Line 11: [Warning] Invalid file link:(~/sdk/rendering-cards/xamarin/android/icardactionhandler.md).

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-renderin-xamarin-android-renderer-actionhandler-icardactionhandler.md

Line 0: [Warning] Invalid file link:(~/sdk/rendering-cards/xamarin/android/icardactionhandler-func-onmediaplay).
Line 0: [Warning] Invalid file link:(~/sdk/rendering-cards/xamarin/android/icardactionhandler-func-onaction).
Line 0: [Warning] Invalid file link:(~/sdk/rendering-cards/xamarin/android/icardactionhandler-func-onmediastop).
Line 9: [Suggestion] H1 is required. Use a single hash (#) followed by a space to create your top-level heading. NOTE: This Suggestion will become a Warning on 01/06/2020.

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-objectmodel-featureregistration.md

Line 0: [Warning] Invalid file link:(~/sdk/rendering-cards/xamarin/android/funcDeserializeFromString).
Line 0: [Warning] Invalid file link:(~/sdk/rendering-cards/xamarin/android/funcDeserializeFromString).
Line 0: [Warning] Invalid file link:(~/sdk/rendering-cards/xamarin/android/feature-registation-func-addfeature).

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-renderer-adaptivecardrenderer.md

Line 0: [Warning] Invalid file link:(~/sdk/rendering-cards/xamarin/android/adaptivecardrenderer-func-render0).
Line 0: [Warning] Invalid file link:(~/sdk/rendering-cards/xamarin/android/adaptivecardrenderer-func-render1).
Line 9: [Suggestion] H1 is required. Use a single hash (#) followed by a space to create your top-level heading. NOTE: This Suggestion will become a Warning on 01/06/2020.

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-renderer-cardrendererregistration.md

Line 0: [Warning] Invalid file link:(~/sdk/rendering-cards/xamarin/android/cardrendererregistration-func-registerfeatureregistration).
Line 9: [Suggestion] H1 is required. Use a single hash (#) followed by a space to create your top-level heading. NOTE: This Suggestion will become a Warning on 01/06/2020.

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-renderer-renderedadaptivecard.md

Line 0: [Warning] Invalid file link:(~/sdk/rendering-cards/xamarin/android/renderedadaptivecard-func-addwarning).

AdaptiveCards/sdk/rendering-cards/xamarin/android/getting-started.md

Line 25: [Warning] Invalid file link:(~/sdk/resources/media/tools/wpfvisualizer.png).
Line 33: [Warning] Invalid file link:(~/sdk/rendering-cards/xamarin/android/class-index.md).

AdaptiveCards/sdk/rendering-cards/xamarin/android/host-config.md

Line 11: [Warning] Invalid file link:(~/sdk/rendering-cards/host-config.md).
Line 13: [Warning] Invalid file link:(~/sdk/rendering-cards/xamarin/android/hostconfig.md).
Line 13: [Warning] Invalid file link:(~/sdk/rendering-cards/xamarin/android/hostconfig.md#something).

AdaptiveCards/sdk/rendering-cards/xamarin/android/render-a-card.md

Line 39: [Warning] Invalid file link:(~/sdk/rendering-cards/xamarin/android/icardactionhandler.md).

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit eab71a3:
:warning: Validation status: warnings

File
Status
Preview URL
Details

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-objectmodel-adaptivecard.md
:warning:Warning

Details

AdaptiveCards/sdk/rendering-cards/xamarin/android/host-config.md
:warning:Warning

Details

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-renderin-xamarin-android-renderer-actionhandler-icardactionhandler.md
:bulb:Suggestion

Details

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-renderer-adaptivecardrenderer.md
:bulb:Suggestion

Details

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-renderer-cardrendererregistration.md
:bulb:Suggestion

Details

AdaptiveCards/sdk/rendering-cards/xamarin/android/actions.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-objectmodel-featureregistration.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-renderer-renderedadaptivecard.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/xamarin/android/getting-started.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/xamarin/android/native-styling.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/xamarin/android/render-a-card.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-objectmodel-adaptivecard.md

Line 74: [Warning] Invalid link: 'DeserializeFromString(string jsonString, string rendererVersion, ParseContext context)'. The file sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-objectmodel-adaptivecard.md doesn't contain a bookmark named 'deserializefromstring1'.

AdaptiveCards/sdk/rendering-cards/xamarin/android/host-config.md

Line 11: [Warning] Invalid file link:(~/sdk/rendering-cards/host-config.md).

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-renderin-xamarin-android-renderer-actionhandler-icardactionhandler.md

Line 9: [Suggestion] H1 is required. Use a single hash (#) followed by a space to create your top-level heading. NOTE: This Suggestion will become a Warning on 01/06/2020.

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-renderer-adaptivecardrenderer.md

Line 9: [Suggestion] H1 is required. Use a single hash (#) followed by a space to create your top-level heading. NOTE: This Suggestion will become a Warning on 01/06/2020.

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-renderer-cardrendererregistration.md

Line 9: [Suggestion] H1 is required. Use a single hash (#) followed by a space to create your top-level heading. NOTE: This Suggestion will become a Warning on 01/06/2020.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Can you also update the toc.yml file so it shows up in the left navigation:
https://github.com/MicrosoftDocs/AdaptiveCards/edit/user/almedina-ms/XamarinAndroidDoc/AdaptiveCards/sdk/rendering-cards/toc.yml
Also in case you weren't aware, you can preview these changes on the docs site using the following URL:
https://review.docs.microsoft.com/en-us/adaptive-cards/?branch=user%2Falmedina-ms%2FXamarinAndroidDoc

Docs Build status updates of commit 4e00248:
:warning: Validation status: warnings

File
Status
Preview URL
Details

AdaptiveCards/sdk/rendering-cards/toc.yml
:warning:Warning

Details

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-objectmodel-adaptivecard.md
:warning:Warning

Details

AdaptiveCards/sdk/rendering-cards/xamarin/android/host-config.md
:warning:Warning

Details

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-renderin-xamarin-android-renderer-actionhandler-icardactionhandler.md
:bulb:Suggestion

Details

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-renderer-adaptivecardrenderer.md
:bulb:Suggestion

Details

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-renderer-cardrendererregistration.md
:bulb:Suggestion

Details

AdaptiveCards/sdk/rendering-cards/xamarin/android/actions.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-objectmodel-featureregistration.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-renderer-renderedadaptivecard.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/xamarin/android/getting-started.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/xamarin/android/native-styling.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/xamarin/android/render-a-card.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/toc.yml

Line 0: [Warning] Invalid file link:(~/sdk/rendering-cards/xamarin/android/extensibility.md).

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-objectmodel-adaptivecard.md

Line 74: [Warning] Invalid link: 'DeserializeFromString(string jsonString, string rendererVersion, ParseContext context)'. The file sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-objectmodel-adaptivecard.md doesn't contain a bookmark named 'deserializefromstring1'.

AdaptiveCards/sdk/rendering-cards/xamarin/android/host-config.md

Line 11: [Warning] Invalid file link:(~/sdk/rendering-cards/host-config.md).

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-renderin-xamarin-android-renderer-actionhandler-icardactionhandler.md

Line 9: [Suggestion] H1 is required. Use a single hash (#) followed by a space to create your top-level heading. NOTE: This Suggestion will become a Warning on 01/06/2020.

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-renderer-adaptivecardrenderer.md

Line 9: [Suggestion] H1 is required. Use a single hash (#) followed by a space to create your top-level heading. NOTE: This Suggestion will become a Warning on 01/06/2020.

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-renderer-cardrendererregistration.md

Line 9: [Suggestion] H1 is required. Use a single hash (#) followed by a space to create your top-level heading. NOTE: This Suggestion will become a Warning on 01/06/2020.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit deefc1d:
:warning: Validation status: warnings

File
Status
Preview URL
Details

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-objectmodel-adaptivecard.md
:warning:Warning

Details

AdaptiveCards/sdk/rendering-cards/xamarin/android/host-config.md
:warning:Warning

Details

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-renderin-xamarin-android-renderer-actionhandler-icardactionhandler.md
:bulb:Suggestion

Details

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-renderer-adaptivecardrenderer.md
:bulb:Suggestion

Details

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-renderer-cardrendererregistration.md
:bulb:Suggestion

Details

AdaptiveCards/sdk/rendering-cards/toc.yml
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/xamarin/android/actions.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-objectmodel-featureregistration.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-renderer-renderedadaptivecard.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/xamarin/android/getting-started.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/xamarin/android/native-styling.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/xamarin/android/render-a-card.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-objectmodel-adaptivecard.md

Line 74: [Warning] Invalid link: 'DeserializeFromString(string jsonString, string rendererVersion, ParseContext context)'. The file sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-objectmodel-adaptivecard.md doesn't contain a bookmark named 'deserializefromstring1'.

AdaptiveCards/sdk/rendering-cards/xamarin/android/host-config.md

Line 11: [Warning] Invalid file link:(~/sdk/rendering-cards/host-config.md).

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-renderin-xamarin-android-renderer-actionhandler-icardactionhandler.md

Line 9: [Suggestion] H1 is required. Use a single hash (#) followed by a space to create your top-level heading. NOTE: This Suggestion will become a Warning on 01/06/2020.

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-renderer-adaptivecardrenderer.md

Line 9: [Suggestion] H1 is required. Use a single hash (#) followed by a space to create your top-level heading. NOTE: This Suggestion will become a Warning on 01/06/2020.

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-renderer-cardrendererregistration.md

Line 9: [Suggestion] H1 is required. Use a single hash (#) followed by a space to create your top-level heading. NOTE: This Suggestion will become a Warning on 01/06/2020.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit f38418c:
:warning: Validation status: warnings

File
Status
Preview URL
Details

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-objectmodel-adaptivecard.md
:warning:Warning

Details

AdaptiveCards/sdk/rendering-cards/xamarin/android/host-config.md
:warning:Warning

Details

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-renderin-xamarin-android-renderer-actionhandler-icardactionhandler.md
:bulb:Suggestion

Details

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-renderer-adaptivecardrenderer.md
:bulb:Suggestion

Details

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-renderer-cardrendererregistration.md
:bulb:Suggestion

Details

AdaptiveCards/sdk/rendering-cards/toc.yml
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/xamarin/android/actions.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-objectmodel-featureregistration.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-renderer-renderedadaptivecard.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/xamarin/android/getting-started.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/xamarin/android/native-styling.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/xamarin/android/render-a-card.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-objectmodel-adaptivecard.md

Line 74: [Warning] Invalid link: 'DeserializeFromString(string jsonString, string rendererVersion, ParseContext context)'. The file sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-objectmodel-adaptivecard.md doesn't contain a bookmark named 'deserializefromstring1'.

AdaptiveCards/sdk/rendering-cards/xamarin/android/host-config.md

Line 11: [Warning] Invalid file link:(~/sdk/rendering-cards/host-config.md).

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-renderin-xamarin-android-renderer-actionhandler-icardactionhandler.md

Line 9: [Suggestion] H1 is required. Use a single hash (#) followed by a space to create your top-level heading. NOTE: This Suggestion will become a Warning on 01/06/2020.

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-renderer-adaptivecardrenderer.md

Line 9: [Suggestion] H1 is required. Use a single hash (#) followed by a space to create your top-level heading. NOTE: This Suggestion will become a Warning on 01/06/2020.

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-renderer-cardrendererregistration.md

Line 9: [Suggestion] H1 is required. Use a single hash (#) followed by a space to create your top-level heading. NOTE: This Suggestion will become a Warning on 01/06/2020.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

@almedina-ms  Also can you please look at the warnings that the docs output has generated. Would be great if we can publish these before the week ends and we head on vacation :)

Docs Build status updates of commit 348b9a8:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

AdaptiveCards/sdk/rendering-cards/toc.yml
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/xamarin/android/actions.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-renderin-xamarin-android-renderer-actionhandler-icardactionhandler.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-objectmodel-adaptivecard.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-objectmodel-featureregistration.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-renderer-adaptivecardrenderer.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-renderer-cardrendererregistration.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-renderer-renderedadaptivecard.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/xamarin/android/getting-started.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/xamarin/android/host-config.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/xamarin/android/native-styling.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/xamarin/android/render-a-card.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit b1bec40:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

AdaptiveCards/sdk/rendering-cards/toc.yml
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/xamarin/android/actions.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-renderin-xamarin-android-renderer-actionhandler-icardactionhandler.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-objectmodel-adaptivecard.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-objectmodel-featureregistration.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-renderer-adaptivecardrenderer.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-renderer-cardrendererregistration.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/xamarin/android/adaptivecards-rendering-xamarin-android-renderer-renderedadaptivecard.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/xamarin/android/getting-started.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/xamarin/android/host-config.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/xamarin/android/native-styling.md
:white_check_mark:Succeeded

AdaptiveCards/sdk/rendering-cards/xamarin/android/render-a-card.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Add HydePHP - Elegant and powerful static site generator

Adds HydePHP - Elegant and powerful static site generator with rich support for blogs, documentation sites, and more using Markdown and/or Blade - #PHP #Laravel

Thanks for merging!


Can I obtain the bearer token from librespot?

I want to show the current playing track on my i3status bar. Most scripts require spotify to be running which I don't have as I use musl and sndio.
Alternatively is there a trivial way to convert the track ID to a "Artist - Track" format?

Thanks

Why is this not merged? Seems like such a useful commit.

That was my initial hacky way to grab some metadata. Don't think it should be merged into librespot.
But IMO all these extras like metadata should be implemented into librespotd - leaving librespot as the library.


[d3d8] Relax viewport validation in windowed mode

Technically shouldn't be needed, but it addresses some problems @Blisto91 has been having with Rainbow Six 3 (in windowed mode), which sets the viewport a whole pixel wider than the render target, after some window resize shenanigans cause the swapchain to be reset like 3 times and end up with a width of 1 pixel less than the initial size that the game sets it to.
I have no idea why this happens, but this workaround should be pretty harmless.

Verified

If it works around the issue, I guess it's ready to ship. Also verified that GameMaker games are still fine, but those had a fullscreen viewport problem in the first place anyway.

This is pretty ugly but I don't really know how to debug why this happens. I guess it would be fine as a totally not permanent temporary workaround.

I guess it would be fine as a totally not permanent temporary workaround.

My thoughts exactly. If it gets some problematic game behavior out of the way, I don't mind stepping an inch out of spec (at least for now).


Texture the player prefab

The player prefabs needs to be UV-Mapped and get some textures

Done, at least partially. What remains is improvements.


Add flipping box loading

@rohit8020 I kept getting merge conflicts every time you merge the pull requests I think this one should work fine.

Merged.
Star the repo and follow me on github. Thanks!


Problems fetching sources from mirrors stored in gitlab lfs

See original issue on GitLab
In GitLab by [Gitlab user @jjardon] on May 10, 2020, 13:15
Job #541785581 failed for a0d92fd8758d737885bf55bbe3b7c48139467707:

In GitLab by [Gitlab user @jjardon] on May 10, 2020, 13:15
Fixed with !1898 (bst-1) and !1897

In GitLab by [Gitlab user @jjardon] on May 10, 2020, 13:15
Fixed with !1898 (bst-1) and !1897

In GitLab by [Gitlab user @jjardon] on May 10, 2020, 13:15
closed

In GitLab by [Gitlab user @jjardon] on May 10, 2020, 13:15
closed

In GitLab by [Gitlab user @jjardon] on May 10, 2020, 13:16
mentioned in merge request !1898

In GitLab by [Gitlab user @jjardon] on May 10, 2020, 13:16
mentioned in merge request !1898

In GitLab by [Gitlab user @jjardon] on May 10, 2020, 13:17
Dupe of #1285

In GitLab by [Gitlab user @jjardon] on May 10, 2020, 13:17
Dupe of #1285


VW - Active link to supporting documentation for applicants

Ability to (actively) link to supporting documentation for applicants → start with adding “href” tags? Other solution…? Documents can be stored in Google Drive, for example, then retrieved from app via link. Need to think about security and privacy issues in the implemented model.

This was done for Project folders. Can we do the same thing for the Application folders?

Also, need to think about where on the application this link to the Google Drive should go.

Mike did this for Site Assessment, and has a solution for the Application View and Worksheet View but has a few issues to resolve before it is ready. He is working on it.

Mike implemented this in the June updates he made. They have been pushed to master for production use. Thank you, Mike!


Problems with events.

http://codepen.io/anon/pen/pjNzor?editors=001
Hover over a circle ten times and watch the meter. The rate will increase exponentially. This is due to the fact that listeners are not removed.  Why is it so?

Found the cause. But there is another question  - Then another question - why when the app is initialized run mouseover listener?


Minor typo

@Rob-S : Thanks for your contribution! The author, @VanMSFT, has been notified to review your proposed change.

Thank you so much, @Rob-S!
#sign-off


Add shellcheck as a configured linter

Shellcheck (https://github.com/koalaman/shellcheck) is a useful shell script linter.

I want to remove the linter integration from the repo. See #152


Promote FreeBSD and MacOS to non-exprimental

MacOS and FreeBSD are currently tagged as "experimental platforms":
https://github.com/ocurrent/ocaml-ci/blob/bd28414e04b4d743f290a0f6e3ff27ad8797cef4/lib/build_info.ml#L10-L37
Which means that even if those CI checks have failed or are not finished, the overall status of a job can show as green. This recently led to a problem, reported by @polytypic, where the development CI was showing all green, masking non-completing FreeBSD jobs that were actually signs of a problem.
MacOS was added in cffaa14c320cc2803722f36bc1bcb9d208b86264, in Oct of 2022 and marked as experimental in Dec with b8f1733 .
FreeBSD was added more recently, just under a year ago, in c2df7fea51f0f166c06c19d2ff0f4fcb73a7ed0b.
However, we think it may be time to promote these variants to non-experimental targets.
Thoughts?

Yes.  If some platform on OCaml-CI is too unstable for some reason for some project I'm developing, I might, for example, exclude that platform (at the package level) or skip tests via other means on OCaml-CI for that platform.

I would like to see both FreeBSD and macOS promoted out of experimental.

I agree they are both stable and have sufficient capacity to be promoted
out of experimental.
On Tue, 11 Jun 2024 at 12:59 AM, Mark Elvers @.***>
wrote:

I would like to see both FreeBSD and macOS promoted out of experimental.
—
Reply to this email directly, view it on GitHub
https://github.com/ocurrent/ocaml-ci/issues/944#issuecomment-2158596948,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABJXOIEGWPUUAGKWQ66IY3ZGW5NBAVCNFSM6AAAAABIXQP62GVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJYGU4TMOJUHA
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Remove text/css

This removes the type='text/css' from the style elements. According to here it is unnecessary.

Is it causing issues? Even if it's optional (link to the W3C standard, instead of random blog would be appreciated), what's the benefit from removal?

https://html.spec.whatwg.org/multipage/semantics.html#the-style-element

Its not a problem I guess, just normally following the spec is best.

This PR looks good!
He is right ngl.

Please squash the two commits into one, and edit the commit message to be more explicit (e.g. "Remove optional 'text/css' attribution in HTML templates"). See PR workflow for instructions.

I tried to find something about how to squash commits but I can’t find anything for GitHub and I don’t have a local fork.

Sorry, I have been trying for 2 hours to squash the commits and it can't get them to squash.

What exactly goes wrong for you? You will need to squash your commits for the other PR as well if it’s approved https://github.com/godotengine/godot/pull/47083, so you better learn how to do it now.

@MrBrain295 Perhaps this may help: https://docs.godotengine.org/en/latest/community/contributing/pr_workflow.html#the-interactive-rebase
(P.S. @pycbouh You should only comment if you actually have something to add; also, saying "You better figure it out" helps nobody, and only makes you seem rude.)

@LikeLakers2 Instead of guessing, I've asked, verbatim, "What exactly goes wrong for you?", because otherwise we cannot help our potential contributor fix their issue. "You better learn how to do it now" is an encouragement to tackle the issue now and don't rely on maintainers merging the PR in its current state.
You, on the other hand, provided the same link as Akien already did, and then blamed me for being rude. This is unprofessional and has no place in our public work environment.

@pycbouh Ah, my apologies. I actually didn't notice Akien's link -- and even if I did, I probably would not have inspected it enough to notice that it links to the same section. But still, my apologies.

To clarify, it's not possible to squash or do any kind of advanced editing of Pull Requests using the online GitHub web editor.
That's why our documented PR workflow is based on command line Git with a local Git clone (it's also possible to use Git GUI with a local Git clone).
Using the GitHub web editor is fine for contributions to some projects/repository, but Godot is a huge codebase with thousands of contributors and we have stricter requirements to ensure that developers can work efficiently. That's why we require small changes which don't impact the dev workflow to be self-contained in a single commit that does the relevant changes, so that it doesn't take the focus away from other commits which have a significantly stronger impact on all users and contributors.
When contributing to an open source project, it's always good to review how existing contributors work, both from their documented workflow (PR workflow page, CONTRIBUTING.md) and the existing commit history to see how things typically look like: https://github.com/godotengine/godot/commits/
What kind of language/format is used in commit messages? How big are commits in terms of impact they have on the codebase compared to other projects? Etc.
Note: This is in no way a criticism, nor intended only for @MrBrain295, this is just additional context on why we have specific requirements and why some extra work is put on the contributors' side instead of the maintainers' side.
That being said, I'm aware that the path from the current state to a "correct" PR with changes squashed and including #47083 is a steep learning curve for a contributor not experienced with Git, so I'll amend the PR myself. For future PRs, I suggest reading our PR workflow documentation and trying that workflow out, instead of using the GitHub web editor.

That being done, from what I've read in the spec and on the linked stackoverflow answer, I'm not sure this is actually a useful change.
Yes, the type attribute can be omitted because the browsers can guess it from the actual file's MIME type... but we can also save them the guesswork which doesn't seem to have any negative impacts?
I'll leave it up to @Faless to decide as he's the maintainer of the HTML5 platform.

I would rather not do this for the export template, where compatibility is more important even when servers report bogus mime types (which reminds me, I should also force the mime type when fetching the wasm).

@Faless should I add type=text/css from editor.html?

should I add type=text/css to editor.html?

no, the editor requires proper server headers configuration anyway (due to COOP/COEP requirements).


YOUR USE OF JW LIBRARY®

What proper use? JW Library has been designed to download, organize, and display Watch Tower's electronic publications for your personal, non-commercial use only. Hence, you may not post any portion of the Watch Tower’s electronic publications on the Internet or on any other electronic network or use the publications commercially or in exchange for money — even if no profit is involved. Modification of the JW Library app is not permitted.

I await reply!

No, never. Despite the name, I'm not modifying the app, I'm modifying the publications.

Just one more thing. Maybe put the restore function from the deprecated version!
Hug!

Yeah, they have already asked me 😅. It will arrive in a future update.


Blobs: introduce EFR32xG27 BLE/RAIL binary blobs

Origin
This is a follow up to #54865 and #57181.
Three binary blobs are to be introduced:

libbluetooth_controller_efr32xg27_gcc_release.a
libbgcommon_efr32xg27_gcc_release.a
librail_efr32xg27_gcc_release.a

The origin of these binary blobs is the Silicon Labs Gecko SDK repository: https://github.com/SiliconLabs/gecko_sdk.
Type

[x] Precompiled library
[ ] Firmware image

Module
hal_silabs: https://github.com/zephyrproject-rtos/hal_silabs/.
Purpose
Precompiled static libraries (binary blobs) supporting EFR32 RF subsystems in EFR32xG27-based boards.
Pull Request
Zephyr PR: https://github.com/zephyrproject-rtos/zephyr/pull/57891
HAL PR: https://github.com/zephyrproject-rtos/hal_silabs/pull/30
Dependencies

hal_silabs (Zephyr module): https://github.com/zephyrproject-rtos/hal_silabs.
mbedtls (Zephyr module): https://github.com/zephyrproject-rtos/mbedtls.

License

libbluetooth_controller_efr32xg27_gcc_release.a - MSLA
libbgcommon_efr32xg27_gcc_release.a - MSLA
librail_efr32xg27_gcc_release.a - Zlib

MSLA (Silicon Labs Master Software License Agreement) license text is located in hal_silabs repository under the following path: zephyr/blobs/license/MSLA.txt.
Zlib license text is located in hal_silabs under the following path: zephyr/blobs/license/Zlib.txt.

According to the Zephyr Project TSC Mtg docs, these blobs have been approved, so I'm closing this issue.


Closing modal causes focus on bad element

What should happen?
Focus should go to clicked element
What happens instead?
Focus go to some other element opening the same modal
Possible Solution
Capture clicked element to open modal and re-attribute focus on close
Test Case and/or Steps to Reproduce
Have 2 buttons, 1 in header the second in footer opening the same modal.
Open modal using the header button then close modal. Focus goes to footer button.
I temporary fixed by commenting out line this.$anchor.focus(); in foundation.reveal.js

I close this issue since it seems to be fixed in newer versions.


[Group] Remove TODO

Problem
fix #11850
Change overview
Removed TODO since changes are not needed.
Testing
Not Tested, comments only.

Closing for now


Add missing LICENSE

Thank you for the blog post and for publishing this library. Would it be possible to state the LICENSE for this code?

added the LICENSE


Make the galleryBanner light themed

Fixes #19

I believe this should invert the banner's text color.

Awesome - thanks! 👍


Add the Labels property to the TokenDBValue struct

This patch extends the TokenDBValue struct in order to allow storing "labels" associated
with a user directly in the data structure, ie. without a need for secondary storage for lookup.
I'm aware that this changes a core entity, but we haven't found a simpler and non-invasive way of doing that, when working on the possibility of using Github teams as "labels" in the ACL configuration.
We think that it simplifies the workflow for anybody who would like to use a similar mechanism for authentication and authorization — after all, the amount of data to store in the token is very small, basically an array of strings.

This change is

Hello, can we get some feedback on this patch?

Hello @rojer, can we get some feedback on this patch?

@rojer I bet you'll need this PR in order to fix the compile.

indeed, just realized it


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-source-version-target/pull/13 is merged into live branch.
Auto archive content to https://github.com/VSC-Service-Account/docs-archive-test-source-version-target.git

Docs Build status updates of commit acd4e78:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

versioningArchiveSourceFolder/TOC.yml
:white_check_mark:Succeeded
View (sql-server-2014 || azuresqldb-current || azuresqldb-mi-current || azure-sqldw-latest || >= aps-pdw-2016 || >= sql-server-2016 || >= sql-server-linux-2017 || sql-server-previousversions || sqlallproducts-allversions)

versioningArchiveSourceFolder/docfx.json
:white_check_mark:Succeeded

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


E-prime linting doesn’t support smart quotes

E-prime linting doesn’t report errors for words including to be that use contractions containing curly/smart/typographer’s quotations marks.
To reproduce:

enable E-prime linting (Settings / Additional arguments / --yes-eprime)
save a document containing the words isn’t isn't

Expected: both words trigger the is a form of 'to be' linting error/warning.
Observed: isn’t doesn’t result in an error.

Hey @hilton linter-write-good is just a wrapper for the upstream library write-good! Please file your issue there https://github.com/btford/write-good


instance profile aws-elasticbeanstalk-ec2-role associated with the environment does not exist

Hello:   working through a basic tutorial to set up a flask app using Elasticbeanstalk.     After running the "eb create" command, the progress stops at setting up the ec2 instance because  "..role associated with the environment doesn't exist"  Shouldn't this be created automatically, using EB.
Any assistance apprecriated.
eb init -p python-3.7 flask-tutorial --region us-east-1
Application flask-tutorial has been created.
eb create flask-tutorial-env
WARNING: Insufficient IAM privileges. Unable to determine if instance profile 'aws-elasticbeanstalk-ec2-role' exists, assuming that it exists.
Creating application version archive "app-230227_173422822109".
Uploading flask-tutorial/app-230227_173422822109.zip to S3. This may take a while.
Upload Complete.
Environment details for: flask-tutorial-env
Application name: flask-tutorial
Region: us-east-1
Deployed Version: app-230227_173422822109
Environment ID: e-w3akuiz72v
Platform: arn:aws:elasticbeanstalk:us-east-1::platform/Python 3.7 running on 64bit Amazon Linux 2/3.4.4
Tier: WebServer-Standard-1.0
CNAME: UNKNOWN
Updated: 2023-02-27 17:34:26.024000+00:00
Printing Status:
2023-02-27 17:34:24    INFO    createEnvironment is starting.
2023-02-27 17:34:26    INFO    Using elasticbeanstalk-us-east-1-385844938637 as Amazon S3 storage bucket for environment data.
2023-02-27 17:37:33    ERROR   The instance profile aws-elasticbeanstalk-ec2-role associated with the environment does not exist.
2023-02-27 17:37:33    ERROR   Failed to launch environment.

This issue is resolved.  I don't remember the exact warning but I believe the method I was using to install awsebcli was deprecated.  Following the instructions in the current EB CLI  repository addressed the conflicts. No issues.
I'm closing this ticket.


chore: update build tasks and changelog

PR Checklist

[ ] Unit Tests have been added for new changes
[ ] API tests have been updated if applicable
[ ] All commented code has been removed
[ ] If you've added a dependency, you've ensured license is compatible with Apache 2.0 and clearly outlined the added dependency.

What are you changing?

Anything the reviewer should know when reviewing this PR?
If the there are associated PRs in other repositories, please link them here (i.e. open-amt-cloud-toolkit/repo#365 )

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

GitHub release
v2.3.10

Your semantic-release bot :package::rocket:


FINERACT-1113 add total_recovered_derived field to LoanSummaryData object

Description
Describe the changes made and why they were made. Ignore if these details are present on the associated Jira ticket
Checklist
Please make sure these boxes are checked before submitting your pull request - thanks!

[ X] Commit message starts with the issue number from https://issues.apache.org/jira/projects/FINERACT/. Ex: FINERACT-646 Pockets API.

[X ] Coding conventions at https://cwiki.apache.org/confluence/display/FINERACT/Coding+Conventions have been followed.

[ X] API documentation at fineract-provider/src/main/resources/static/api-docs/apiLive.htm has been updated with details of any API changes.

[ X] Integration tests have been created/updated for verifying the changes made.

[ X] All Integrations tests are passing with the new commits.

[ X] Submission is not a "code dump".  (Large changes can be made "in repository" via a branch.  Ask on the list.)

Our guidelines for code reviews is at https://cwiki.apache.org/confluence/display/FINERACT/Code+Review+Guide

@percyashu , @thesmallstar , Will you like to review this one?

@percyashu @luckyman20 Yes this is the fineract side change for cui-2225.  @luckyman20 have you already done the community app changes for this?  if so, are you able to test against this PR? totalRecovered amount has been added to the loan summary, you would only have to compare this with totalWrittenOff to hide the button as you have suggested. or if you prefer I can do the community app side change too.

We can merge this ahead of community-app changes as this is only an addition to the fineract. I will create the PR on community-app after this is merged.

@tonic889 thanks for the PR,
Will, you also like to write a test for this (not necessarily now, but later maybe?)

@vorburger @ptuomola Is it good to merge? If yes, then I think we shouldn't delay it.

@luckyman20 I was waiting for a reply to the question from @thesmallstar above... but the code looks OK to me, so happy to merge.

Please make sure that the Fix Version on issues for merged PRs is set (this one in FINERACT-1113 was not); else they'll miss in the Release Notes.


feat(network): protobuf update

Pull Request type
Please check the type of change your PR introduces:

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build-related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

Issue Number: N/A
What is the new behavior?

Does this introduce a breaking change?

[ ] Yes
[ ] No

Other information

This change is

Current dependencies on/for this PR:

new_streamed_data

PR #1201   👈

This comment was auto-generated by Graphite.


Adds the bibliographic presenter filter back to the Admin UI

Resolves (the very detailed and nicely written) issue #3768.
Does what is described in the title.
@KatrinIhler, you removed the presenter filter (among others) some months ago for performance reasons I think. Would you be opposed to adding it back in? I'd argue that it makes sense to have it, since it's effectively still usable (by clicking on a presenter name in the events table) and it is confusing to not have the filter pop up in the filter box in that case. Or do you think it be better to remove the ability to click on presenters in the events table?

Just from memory, so take with a grain of salt: Afair the problem with the filter was that it loads a list of users you can select in a drop down menu, and if you have a lot of users, that can take... a while. Iirc there was also more than one filter who does this, so it loads the users more than once. As long as the available filters aren't loaded, you can't see any active filters either, which is a real pain. It's possible you can deactivate this in some other way (list provider config maybe, just exclude all users?), but it seems unwise to let people run into this by default if the filter isn't used much.
I didn't know you can still use this filter in another way, to be honest. Maybe there's a way to show it without adding the user loading back in? But I don't know how much work that would be.

Can we get a perf check on this with a cluster with lots of users? It's hard to make a call on whether this is reasonable without knowing if we're going to sink adopter clusters.

@gregorydlogan I currently don't have access to a client system with that many users. We deactivated this for SWITCH because for them, it took minutes to load the filter view.

Would it be reasonable to make this filter (and only this filter) something that can be easily turned off?
I suppose we could add an 'expensive' option to turn all of the expensive ones on and off, assuming there is more than one like that.

Not necessarily against marking some filters as "can slow your system to a crawl", but just noting that making the filter configurable would require to solve the initially linked issue some other way.

@Arnei Agreed.  Do you think you (or someone else) would have time to address this?

@Arnei Agreed. Do you think you (or someone else) would have time to address this?

I don't have time for that currently.

So, is this still relevant in Picard?  I'm assuming so.  But this has been hanging around so long I suspect that it's not going to be merged, especially at the end of the support window.

Is indeed relevant for picard (although picard will actually display that a filter was set, just not which one, so it's a little less bad there). This is definitely not gonna get merged as is, the performance dip would just not be worth it, so I'd be fine with closing it.

Done


Added a comment that destination of import should not start with '/'

Addresses #6600
Change Description
As a quick workaround, adding a comment to not accept an import that start with '/'. A better solution would be to not allow the code to accept it and present a suitable message.

With the improved import dialog, thanks to @johnnyaug it is now clear the final import path for import. The Destination field starts with repository/branch/ (readonly) so it is very clear the user should not add extra '/'.
Can I close this issue?


Script updates

This makes sure that when users change their password, it's done
properly and the console login screen is updated.

I should mention that puppet appears to work properly after this, but we should validate and do much testing before actually releasing this on a VM.


Update exampel dependencies.

Removed workspace dependecy from example apps to deploy nextjs exmaple.

Conflicts in deployment dependencies in vercel resolved!
Removed example apps and website from pnpm-workspace.yaml and package.json in the root of the repository.


pembuat desing foto

Imagination is more important than knowledge.
For knowledge is limited, whereas imagination embraces the entire world,
stimulating progress, giving birth to evolution.

Why:

Closes [issue link]
What's being changed:

Check off the following:

[ ] I have reviewed my changes in staging. (look for the deploy-to-heroku link in your pull request, then click View deployment)
[ ] For content changes, I have reviewed the localization checklist
[ ] For content changes, I have reviewed the Content style guide for GitHub Docs.

Imagination is more important than knowledge.
For knowledge is limited, whereas imagination embraces the entire world,
stimulating progress, giving birth to evolution.

Install
Clone this project

git clone https://github.com/ArugaZ/whatsapp-bot.git
cd whatsapp-bot


chore: trying a different format for PR message

Thanks for the PR! :metal:
Please create PRs in draft :construction: mode.  Mark as ready to enable below workflow
After merge, new images are deployed using below workflow

Deployments :rocket:, as required, will be available below:
Analysis Workflow :gear:
Merge Workflow :gear:

Frontend
Backend

how does it look now @DerekRoberts @cberg-aot

leave it to teams, if they want fancy things


Added Consul TCP Health Check

Adds a Consul TCP health check by specifying ..._CHECK_TCP=true
https://github.com/gliderlabs/registrator/issues/225

I will put in a new pull request from master.


Broken behavior: write_{format} methods crate wrong csv files in local FS

Describe the bug
Methods write_csv, write_parquet, write_json and etc have been broken after switching to object-store.
They produce files with wrong extension with additional suffix, for example: filename_4.csv#1
The name seems to change here and is not controlled directly by datafusion.
I think this is more an issue of object_store for local file-system implementation, but the behavior have been broken for datafusion after switching so I raised the issue.
It would be nice to cover with tests.
To Reproduce
    let ctx = SessionContext::new();
    // register tables
    let data_frame = ctx.sql("...").await?; // any valid SELECT

    data_frame.write_csv().await?;

Expected behavior
Filenames should be with correct extension, without suffix of #1.
write_{format} methods used to create file per thread (currently it's controlled by per_thread_output: true) with correct names and an index: {filename}_{index}.{ext}.
Additional context
No response

Which version of DataFusion are you using? I was not able to replicate this behavior using the current main branch or using v30.0.0. I
If you are using DataFusion version prior to 30.0.0, try that and see if it is resolved.

I encountered it exactly against '30.0.0' after updating from '28.0.0'.
Let me provide some reproducible example

Sorry, my bad. Seems it works as expected
Looks like it happens in case of:

error in one of threads which interrupts the execution of others (when files weren't fully written to disk)
stopping of the runtime

I.e when rename call by object_store wasn't completed (https://github.com/apache/arrow-rs/blob/cb793a5d54e155b121bc5c33534a37bf94651c84/object_store/src/local.rs#L8111)

I think there may still be an issue here with the behavior you are seeing. When one thread encounters an error, no files should be written to disk, so we may want to add some logic to clean up the staged local files (unclear to me if that logic should be in the ObjectStore crate or DF at a glance).

That's definitely right point to avoid staged files.
I think ObjectStore should create staged files as a temporary files (probably just hidden ones) with Drop logic to delete them in case they weren't completed.
I don't think DF should care of the way object_store handles the staging. If a file write/upload wasn't completed - intermediate files should be cleaned up.  Probably this may be configurable behavior
WDYT?
cc @tustvold @alamb

Yes ideally we would stage the files in such a way that they get automatically cleaned up if the operation aborts. On Unix platforms this is fairly straightforward as there is the unlink command, it gets a bit mess on Windows though... I can add it to my list

Yeah, that's true
Perhaps a wrapper with Drop (with remove file call) is an option? as a fallback, it can of course fail and is not guaranteed, but at least it covers typical flows.

Would it be good to file a ticket in arrow-rs / obect-store for this behavior (even if it is non trivial to implement)?

I created https://github.com/apache/arrow-rs/issues/4778 to track although I'm not sure how actually sure how to implement it, as Rust futures don't have an async Drop facility...


Training Tutorial

Hello, in your Dataset Tutorial you have a link with training tutorial, but it's empty https://colab.research.google.com/drive/1LUC0MqFYK39xG5AV9kQi5hIBsi9eCpS0?usp=sharing

Can you share this notebook?

Did you find the training tutorial?


Added all HttpRequest Extensions from https://github.com/TechSar-dev/…

I was recently about to start work on a similar project which aims to simplify the Dart SDK API. It's a huge task and will take time, so I am adding things as I need them. I would like to merge what I have so far and work on this project moving forward.
Hopefully this pr is acceptable, if not - please let me know if I need to change anything to meet the conventions of this library.
Thanks.

Wow thanks, that's amazing! Do you also have unit tests?

Hi, I haven't had a chance to add any tests as of yet. They are all just getters and setters, but I can add a bunch of tests over the weekend and do another pr once that's complete.

Maybe we create a dev branch and you open another PR so we can work together on tests...

Could you please open another PR against the "develop" branch.

Just opened it.


github copilot is not working on vscode

VS CODE -
Version: 1.53.2
Commit: 622cb03f7e070a9670c94bae1a45d78d7181fbd4
Date: 2021-02-11T11:45:54.515Z
Electron: 11.2.1
Chrome: 87.0.4280.141
Node.js: 12.18.3
V8: <IP_ADDRESS>-electron.0
OS: Darwin x64 18.7.0
======
Error while installing 'GitHub Copilot Chat' extension.
Unable to install 'github.copilot-chat' extension because it is not compatible with the current version of VS Code (version 1.53.2).
on ...  Mac OS10.14.
was working a few days ago ...?????
Fix??

Mine is not showing too
Version: 1.88.0-insider (Universal)
Commit: f7c827a5e0ddbba66425ea54e33430bce8f53c84
Date: 2024-03-20T05:50:33.199Z (1 day ago)
Electron: 28.2.6
ElectronBuildId: 27476517
Chromium: 120.0.6099.291
Node.js: 18.18.2
V8: 12.0.267.19-electron.0
OS: Darwin arm64 23.4.0

Please give this a try on a newer release of vscode.


gRPC support

First pass at gRPC support. Only one method implemented, if the approach looks good I can fill in the rest.
└─(130:31)% go build && ./quiver --rpc-port=1234 --grpc-port=1337 a=./hfile/testdata/pairs.hfile
2019/04/13 11:03:59 Quiver version HEAD? (built unknown?, go1.12.2).

2019/04/13 11:03:59 Loading collections...
2019/04/13 11:03:59 [Reader.NewReader] Reading in a (1.71mb)...
2019/04/13 11:03:59 [Reader.NewReader] Loaded a.
2019/04/13 11:03:59 Serving on http://kudu:9999/
2019/04/13 11:03:59 [9999]
2019/04/13 11:03:59 adminz registered
2019/04/13 11:03:59 Watching paths for killfile: [/dev/shm/healthz/kill.9999 /dev/shm/healthz/kill.all]
2019/04/13 11:03:59 Listening for raw RPC on 1234
2019/04/13 11:03:59 Listening for gRPC on 1337

┌─(cy@kudu:~/go/src/github.com/foursquare/quiver)
└─(25)% grpc_cli call localhost:1337 foursquare.quiver.client.QuiverService/GetValuesSingle "hfile_name:'a' sorted_keys:'\0\0\0\1'"
connecting to localhost:1337
values {
  value: "~1"
}
key_count: 1

Rpc succeeded with OK status

For some background, at Slack we only use the SingleHFileKeyRequest.  We use both thrift and grpc here.  This change would allow us to use a grpc sidecar on our webserving nodes for more stable connections.
If you have any concerns, we are happy to address them!  @jvandew

holy cow this looks awesome, thank you!
I'll give this an in-depth read through in the next day or two if that works, and hopefully find someone with more go expertise than I have to take a look as well heh

Thanks Jacob!  Happy to provide a bit more context if it is helpful

Thanks for the review @ghthor !


Add two courses to extras

Add "An Introduction to Interactive Programming in Python" part 1 and 2 to extras.
Note: I don't know if these courses are worthy of being displayed in this list, but they are where I learned Python (and programming in general), so I'll just give them as a suggestion.

@lumidify thank you for your contribution! :pray:
Your feedback is a prove that these courses fit well in this section, that is an introduction to computer science/programming. :smile:


Are we using signed or unsigned LEB128?

If I read the Python code correctly, the LEB128 lengths in strings and typed arrays are unsigned LEB128, and for the 0xBB typed values we use signed LEB128, but it isn't specified anywhere else. Maybe that should be clarified in the images and presentation.

That's correct. Will be documented soon

Related to #8


feat: add vite-plugin-ssr test suite, telefunc test suite, and a new option beforeInstall

The pnpm run setup step is needed to initialize the libframe Git submodule at https://github.com/brillout/vite-plugin-ssr and https://github.com/vikejs/telefunc.

Let me know if you encounter test flakiness. They have been stable the last couple of weeks, but the Cloudflare tests used to be flaky (the Cloudflare Workers servers had regular downtimes).

Thanks a lot for connecting these test suites @brillout, I'll run them now so we see them in the #ecosystem-ci channel

👍 (Btw Dominik was very much right about pnpm being much better :-).)


SVG export doesn't escape source text

e.g:
<dc:source>
<empty> (flattened)
</dc:source>

Fixed by #116


Added secret filtering

Overview
While many CI\CD tools already have the capability to filter secrets, it is best that any tools do not output secrets to the console or logs. This pull request has an implementation of secrets filtering. It takes an aggressive approach and filters any text that matches a secret.
A naming convention is used to 'tag' a variable as a secret and either of the following conventions can be used:

The variable name has the word secret in it.   config: 1
   vars:
      bucket_name: S3://......  # not a secret
      secret_key: 567576D8E  # a secret

The variable is a child of a key named secrets.   config: 1
   vars:
     secrets:
         my_key: 567576D8E # a secret
     aws:
        bucket_name: S3://......  # not a secret
        secrets:
           encryption_key: FGDSUUEHDHJK # a secret
           us_east_1:
               encryption_key: sdsdsd # a secret

In addition this pull request pretty prints the --vars when they are rendered to the console.
#Pretty printing variables
the demo citibike_jinja has been modified to have some secrets. The variables will not be displayed on the screen as follows:
schemachange version: 3.4.0
Using config file: .\schemachange-config.yml
Using root folder ......\schemachange\demo\citibike_jinja\scripts
Using Jinja modules folder ......\schemachange\demo\citibike_jinja\modules
Using variables:
  database_name: SCHEMACHANGE_DEMO_JINJA
  secrets:
    trips_s3_bucket: ******************************************
    weather_s3_bucket: ***************************************

deploy command
When the deploy commands is executed with verbose it displays the sql scripts to the console. These are also filtered for secrets.
render command
The render command is the exception and secrets filtering has not be implemented.  Since this command is intended to support development and troubleshooting of scripts using jinja. I felt it would not be appropriate to apply filtering here.

Hey there @saperry, thanks again for contributing! I like this change and think it makes sense. I took a quick look at the changes and they look pretty good. Anything you want to update/finalize before doing a detailed/final review?

@sfc-gh-jhansen This is good for final review.  I have also included a couple of README.md fixes and additions beyond the secret filtering feature.

Looks good, thanks @saperry!


added warning for recursive schema

added warning for recursive schema
closes #18

@alexzielenski , @apelisse . can you please review this pr ?

@alexzielenski I don't get what you mean by tests here as schema-visitor does not have a unit test associated with it ?

Could add an e2e/integration test that asserts the expected log output, and shows that the files using recursive schema are skipped.


Add distributed tensorflow

What this PR does / why we need it:
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:

/ok-to-test

I noticed a few problems. Will review later.

@unguiculus please review again when you have time. Thanks.

Add distributed-tf.jpg to .helmignore
Already add *.jpg, I think it's enough.

/ping @unguiculus

/lgtm


[AutoDiff][SIL] Improve JVP/VJP type mismatch verification error.

Show expected vs actual JVP/VJP types when they do not match.

Before:
SIL verification failed: Unexpected VJP function type: expectedVJPType == vjpType

After:
SIL verification failed: VJP type does not match expected VJP type
  $@convention(method) (Float, @thick Super.Type) -> (@owned Super, @owned @callee_guaranteed (@guaranteed Super.AllDifferentiableVariables) -> Float)
  $@convention(method) (Float, @owned Super) -> (@owned Super, @owned @callee_guaranteed (@guaranteed Super.AllDifferentiableVariables) -> Float)

@swift-ci Please test tensorflow


chore: fix snapshot of testng

Summary

Checklist

[ ] Tests updated (or not required).
[ ] Documentation updated (or not required).

!test-ng


Add CfP 2023 page content

I've added the content using the format from 2020. Could I please ask @benabraham to have a look and fix the visuals here? :) Please feel free to push into this branch. Also if there's something I can do to make your life easier, or I've made some significant mistakes - please do let me know so I can learn.
To do:

[ ] Add the link to the CfP form (don't forget about the fin aid section, last sentence)

n00b Question:
I see diff in these files, should those be committed?

You probably ran some node stuff. This part of website (/2023/) is true static no build stuff. Just return those files back to their original state and don’t run node scripts.


.exe on dist being flagged by some antivirus vendors are malware

From VirusTotal.
Both Fortinet and Ikarus flag the .exe on dist as a threat.

Hi vico93, I believe there are always some antivirus programs that flag it as a threat. So I'm not quite sure what to do about it. Alternatively you can run app.py manually if you don't trust the .exe.


Make IR ir.Del free until legalized.

As title.

This essentially prevents ir.Del from being present in the IR until it is legalised. It's fine for a pass to generate ir.Del nodes for whatever reason and then strip them before the pass completes. Strict enforcement is applied to passes inheriting from numba.core.compiler_machinery.FunctionPass.

/AzurePipelines run

CI is stuck because of a github outage, the close/open might un-stick it.

The following tests are failing on my osx machine
ERROR: test_obj_func_match (numba.tests.test_ir_utils.TestIrUtils)
FAIL: test_dead_code_elimination (numba.tests.test_ir_utils.TestIrUtils)

/AzurePipelines run

Bizarrely https://github.com/numba/numba/pull/5271/commits/7c02c07daa9335e37c6ee51f4a49a72c2170b35b passed, which is identical to this branch apart from a dead import statement.

Bizarrely 7c02c07 passed, which is identical to this branch apart from a dead import statement.

Rerun is showing the failures you saw @sklam, I guess github issues yesterday lead to a false pass.

@sklam thanks for the review, I think I've addressed everything.


🐛 Android video is dark & stretched on front camera

What's happening?
The camera is very dark when using react-native-vision-camera when compared to the Android Camera (Front camera only)
Front
Previous versions (Such as v2) do not have this dark of a front camera. I did notice when loading the app, the first frame is correctly bright, once it finishes loading it dims.
react-native-vision-camera

Android Camera

Back
Seems good enough (I assume some pre-processing is done with Android's camera making it slightly brighter
react-native-vision-camera

Android Camera

Camera is also vertically stretched when using the front camera within react-native-vision-camera. (In addition to the zoom thats been existing even in v2)
(Challenging to get photos of this as the image is very dark, but let me know if you'd like some screenshots)
Reproduceable Code
Latest Example app from react-native-vision-camera https://github.com/mrousavy/react-native-vision-camera/tree/main/package/example
Relevant log output
No errors / warnings / logs were displayed.
Let me know if there is debug logging I can enable.
Camera Device
[
  {
    "formats": [
    ],
    "hardwareLevel": "full",
    "hasFlash": true,
    "hasTorch": true,
    "id": "0",
    "isMultiCam": false,
    "maxZoom": 4,
    "minZoom": 1,
    "name": "BACK (0)",
    "neutralZoom": 1,
    "physicalDevices": [
      "wide-angle-camera"
    ],
    "position": "back",
    "sensorOrientation": "landscape-right",
    "supportsFocus": true,
    "supportsLowLightBoost": false,
    "supportsRawCapture": true
  },
  {
    "formats": [
    ],
    "hardwareLevel": "full",
    "hasFlash": false,
    "hasTorch": false,
    "id": "1",
    "isMultiCam": false,
    "maxZoom": 4,
    "minZoom": 1,
    "name": "FRONT (1)",
    "neutralZoom": 1,
    "physicalDevices": [
      "wide-angle-camera"
    ],
    "position": "front",
    "sensorOrientation": "landscape-left",
    "supportsFocus": true,
    "supportsLowLightBoost": false,
    "supportsRawCapture": true
  }
]

Device
Samsung Galaxy A03s (Android 13)
VisionCamera Version

=3.3.0

Can you reproduce this issue in the VisionCamera Example app?
Yes, I can reproduce the same issue in the Example app here
Additional information

[ ] I am using Expo
[ ] I have enabled Frame Processors (react-native-worklets-core)
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar issues in this repository and found none.

Interesting - try this:

Remove video and frameProcessor props to see if the VIDEO template makes it darker
Try to use a lower fps (e.g. fps={15}) to see if that makes it brighter

I believe the only thing that's a bug here is that the selfie camera is stretched. I don't know why that's happening tbh, @blancham do you have any ideas?

This is somehow related to https://github.com/mrousavy/react-native-vision-camera/pull/2018 and how we are computing the preview size's aspect ratio (sometimes width / height, others height / width)
One way you can go around it  @MassimoDeLuca is to set an aspectRatio (same as the format you are using) on your View

Dark Front Camera:
@mrousavy

Removing video and frameProcessor props do brighten the capture (Both need to be removed)
Setting FPS to 15, 5, 1 do not reduce the preview FPS nor the output video FPS. The camera is also still dark (Attempted with frameProcessor removed from props).

Interestingly, v3.0.0 example has the opposite issue where the camera is darkened when video and frameProcessor are removed from props.
Stretched Front Camera:
v3.0.0 example does not have this issue, assuming its a regression or intended functionality changed since then (although seems odd)
@blancham
In the latest example, I did attempt aspectRatio={format.videoHeight/format.videoWidth} which did not work (It returns 0.45 for my device). I also tried hardcoding it to 0.3 which didn't make a visual difference.
Sometimes when it hot reloads it will fix the aspect ratio itself (Even if the changes are unrelated).
Please let me know how I can provide additional logs / details.

I had same issue with 3.6.4. Downgrading to 3.4.1 fixed the issue.
Also useCamera device function without any filters.

@MassimoDeLuca I guess you tested on a Samsung device? Apparently setting FPS doesnt work on samsung at all; I fixed this here: https://github.com/mrousavy/react-native-vision-camera/pull/2138

@mrousavy I have similar issue where camera is stretched on some android devices ( not all devices ) , I would like to get this fix for fps, is it going to be released soon?
Thanks

I would like to get this fix for fps

sure, how much are you currently sponsoring?

@MassimoDeLuca I guess you tested on a Samsung device? Apparently setting FPS doesnt work on samsung at all; I fixed this here: #2138

Yes, Using Samsung Galaxy A03s (Android 13).
Setting FPS now works, as you've mentioned.
<20 FPS has correct lighting. Anything between 1-20 FPS visually appears to have the same lighting.
Once FPS is set >20 FPS, it starts to darken.
Still experiencing stretched screen in the example with no changes (Although I don't believe any fix was made yet to address this)

Indeed, in my app I also found that you need to set at max 20 fps when using the front camera. I am testing on a Vivo phone
Also, when I switch from the back to the front camera, the view is stretched out vertically BUT, when I update the format 2 times (I can cycle through 4:3 and 16:9 on my app so I change to 16:9 then go back to 4:3), everything goes back to normal!
What I saw is that when changing the format the PreviewView's onMeasure is triggered but when changing the camera device, it's not. Maybe this is the root cause @mrousavy

yea, maybe race condition. I think the format is the source of truth, then we just need to always apply that to the PreviewView and keep showing that. Not sure which View Lifecycle methods we need, onMeasure? onLayout? idk

Hey! Does this fix your issue maybe? https://github.com/mrousavy/react-native-vision-camera/pull/2377 (still testing)

Hey!
After 8 hours of debugging, I finally found the culprit! I fixed the preview stretching issue in this PR: https://github.com/mrousavy/react-native-vision-camera/pull/2377
If you appreciate my dedication and free support, please consider 💖 sponsoring me on GitHub 💖 so I can keep providing fixes and building out new features for my open-source libraries in my free time.

3.7.1 doesn't seem to fix the issue. Revert to 3.6.16 works for me as well

works for me on 3.7.1

On my end the stretching issue has been fixed in 3.7.1 but still experiencing dark video when the frame processor is enabled.

Dark Video is maybe just because of the Frame Rate. Or Video stream. Not a lot I can do, you can try setting fps to something like 10, and  exposure to a really high value.

Still not working 🤷♂

@mrousavy Apologies for the delayed response. The stretching issue will be occur in all devices. In some devices it looks fine and in some devices it still looks stretched. The one I am testing it with is a Galaxy M33 5G. Also, this stretched preview only appears for the time when we open camera by user (example - tap on open camera button) action. Once the camera opens, the preview appears stretched.. BUT as soon as I lock the device on open camera and then unlock it again, the preview is NO MORE stretched. So, in short, the preview initially appears stretched but after a device lock and unlock the stretched preview gets fixed on its own. See if this helps you debug it further.

Created a PR to fix this issue once and for all: https://github.com/mrousavy/react-native-vision-camera/pull/2519 💪🚀
Thanks to everyone who sponsored me on GitHub to fix this bug!! 💖
Try the PR and see if it works (by checking out that branch and running the example app)


Model not initialized - addModels

Here's a reproduction: https://github.com/kamilkisiela/sequelize-init

I have two models, a oneToMany relation. I read #366 and what I get is:

Model not initialized: "Message" needs to be added to a Sequelize instance before association can be resolved

import { Message } from './models/message';
import { User } from './models/user';
import { Sequelize } from 'sequelize-typescript';

const sequelize = new Sequelize({...});

sequelize.addModels([User, Message]);

// Message.ts

@Table
export class Message extends Model<Message> {
  @BelongsTo(() => User, {
    foreignKey: 'senderId',
    targetKey: 'id',
  })
  sender: User;

  @Column
  content: string;
}

// User.ts
@Table
export class User extends Model<User> {
  @Column
  username: string;

  @HasMany(() => Message, {
    foreignKey: 'senderId',
    sourceKey: 'id',
  })
  senderMessages: Message[];
}

@kamilkisiela can we close this issue now?

i`m also this question
@Table
class Book extends Model {
@BelongsToMany(() => Author, () => BookAuthor)
authors: Author[];
}
@Table
class Author extends Model {
@BelongsToMany(() => Book, () => BookAuthor)
books: Book[];
}
@Table
class BookAuthor extends Model {
@ForeignKey(() => Book)
@Column
bookId: number;
@ForeignKey(() => Author)
@Column
authorId: number;
}

Error: Model not initialized: "Author" needs to be added to a Sequelize instance before association can be resolved.

can i understand each ref problem

Hey @adminparry, thanks for reporting. Can you submit a new issue for that? An example repo would be great as well. Thanks!

Hey Guys, was getting this issue as well recently and managed to get the Model by passing an instance of the connection to my Repository and get the model from the Sequelize instance.
This is how I tackled it and it works.
private async GetModel(): Promise<T> {         const connection = await this.db.Connection(). //Returns my sequelize instance         return connection.model('MODEL_NAME') //can also pass the type of the model required.    }
Hope this helps


Issue439

uses same logic already working for textArea for textField

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


High Price Impact for very small trades

Describe the bug
On both Polygon and Arbitrum the UI sometimes says a trade has a High price impact even when the amount is < $5. This isn't happening for larger trades.
This appears to be happening because we have some unbalanced pools with really low liquidity, and so SOR will route through those pools when possible, but because the ratio is so different than the market price it says the trade is significantly moving the price.
We could fix this by calculating the total liquidity available for a trade and if the amount being traded is < 1% (or smaller) of the total available liquidity then we never show the price impact warning.
We are already calculating the total liquidity available here: https://github.com/balancer-labs/balancer-sor/blob/master/src/router/index.ts#L24 we would need to expose this to the frontend somehow.
To Reproduce
Steps to reproduce the behavior:

Perform a trade on Polygon/Arbitrum with a very small amount of a common trade amount (I tried MATIC/ETH on Polygon and USDC/ETH on Arbitrum)

Screenshots

Cleaning up old issues, please reopen if applicable


Validate on dataset creation

What will really make a difference in terms of improving data quality will be the integration of the validation process in the process for adding new datasets.
Running the validation before the creation of the dataset will highlight errors early in process and engage publishers in fixing those issues.
The actual workflow will depend on each CKAN instance and the publishers needs, for instance some might prevent the dataset from being created if there are errors, or allow the creation of the dataset but not upload it to the DataStore, or in some case cases just warn the user.
Regardless of how the process continues after the validation, the main implementation issue would be how to integrate an asynchronous validation job with the multi-step process now in place for creating datasets. The resource endpoints of the package controller are infamous for their complexity, caused by how this multi-stage process is implemented.
TODO: expand potential implementation and estimate

There is no easy solution to hooking the validation to a point where the file has been uploaded but the metadata has not yet been committed. Most elegant approaches require significant changes to CKAN core and so would require CKAN 2.8 (also see https://github.com/frictionlessdata/ckanext-validation/issues/12):

Separate endpoint for file uploading, independent from the creation process.
Move the upload earlier on the call, before metadata is validated or stored, and add a new endpoint (see https://github.com/ckan/ckan/issues/3790#issuecomment-326311859).
Override the whole of resource_create and resource_update and add our validation logic where needed.

The last option is not ideal as we need to track changes in the core functions and as mentioned in https://github.com/ckan/ckan/issues/3790#issuecomment-326311859 we add even more time for the transaction to fail, but it's the only option not currently blocked and we can always refactor.
Estimate is based on this option.


Add "mpp_state" stim.Tableau.to_circuit type

The circuit should measure each of the stabilizers using MPP, and then perform feedback operations to force them into the right eigenstate.

This was added.


The primitive type and the literal type of the primitive type Union

I found a really small bug.
This is also happening in typia@next.
const wrongCase = typia.random<{ a: 3 | number }>(); // type is { a: 3 | number }

const rightCase = typia.random<3 | number>(); // type is just number

Can I try this problem today? (Maybe at night)

I gave up.

This is a problem in the highlighting, in fact the type is always number
https://typia.io/playground/?script=JYWwDg9gTgLgBDAnmYBDANHA3g1BzAZzgF84AzKCEOAIiRVRoG4AoFgYwgDsD4B3SlzwBhVAQCmcALwJkaAHRRUXACZUAPDlQAuOAGY4AHzhcAriABG4qCQB8ACgCUrFvUkwAjNOxwd+oybmVjbErsjuAEzeBsZmltZhYO4GMp4A2jSMALqJ7gAs3m4QZHAC3CJi4vKoQA


Skip JavaDoc generation

JavaDoc generation is being triggered in the release process and breaking the build

ping @wilderrodrigues


Update front end to work with weather back end

We want the mbaas component able to communicate with a gps location provided by the front end.

Finished ayy


feature：init namingserver client

[ ] I have registered the PR changes.

Ⅰ. Describe what this PR did
Seata client for invoking the Naming Server
Ⅱ. Does this pull request fix one issue?

Ⅲ. Why don't you add test cases (unit test/integration test)?
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report
Attention: Patch coverage is 0.54348% with 366 lines in your changes missing coverage. Please review.

Project coverage is 49.72%. Comparing base (933b492) to head (5197420).
Report is 32 commits behind head on 2.x.

Additional details and impacted files

@@             Coverage Diff              @@
##                2.x    #6536      +/-   ##
============================================
- Coverage     51.13%   49.72%   -1.41%
- Complexity     5317     5595     +278
============================================
  Files           950     1029      +79
  Lines         33448    35808    +2360
  Branches       4048     4253     +205
============================================
+ Hits          17103    17807     +704
- Misses        14666    16235    +1569
- Partials       1679     1766      +87

Files
Coverage Δ

...mon/src/main/java/org/apache/seata/common/XID.java
92.30% <ø> (ø)

...java/org/apache/seata/common/metadata/Cluster.java
0.00% <ø> (ø)

...try/namingserver/NamingserverRegistryProvider.java
0.00% <0.00%> (ø)

...registry/namingserver/NamingRegistryException.java
0.00% <0.00%> (ø)

...org/apache/seata/common/metadata/MetaResponse.java
0.00% <0.00%> (ø)

...in/java/org/apache/seata/common/metadata/Unit.java
0.00% <0.00%> (ø)

...in/java/org/apache/seata/common/metadata/Node.java
45.56% <5.55%> (-38.65%)
:arrow_down:

...ava/org/apache/seata/common/metadata/Instance.java
0.00% <0.00%> (ø)

.../namingserver/NamingserverRegistryServiceImpl.java
0.00% <0.00%> (ø)

... and 124 files with indirect coverage changes


Google HTTP java client

Hi,
I got several hits from Google-HTTP-Java-Client\/1.17.0-rc (gzip) User-Agent. That one is not considered a bot. Stricto sensu, it is not since it's only the medium, but it denotes a programmatic connection and then eventually a crawler.
What about adding this one?

I guess that one could be added since we already have phpcrawler and so on in regexes ; though I'm waiting on my other PR not to have a conflict.

Yes, I think it is definitely worth adding :+1:

Good, then I'm adding it to my current PR.


Docker image out of date

Thanks for your great work on this library! I'm using GPflow for a programming assignment in a class that I'm teaching. I was hoping to point students towards your docker image. Unfortunately, it appears the docker image is still running 0.3.5. Is it indeed out of date, or might I have done something silly?

Hello, looking to run the latest version of GPflow with docker. Is this PR ready to be finalised.

@awav  do we not have a new Docker image now?

It looks like the Docker image linked to from the documentation (https://gpflow.readthedocs.io/en/develop/intro.html, even for 2.0 version) is massively out of date (still 0.3.5). Should we remove the link, or update the docker image? (Who even has permission to update the docker image, and who knows what would be needed for that?)


Release Google.Cloud.AssuredWorkloads.V1Beta1 version 1.0.0-beta07

Changes in this release:

Commit aff9821:

feat: Add Canada Regions And Support compliance regime
fix: ResourceType CONSUMER_PROJECT is deprecated
feat: ResourceType CONSUMER_FOLDER and KEYRING are added
feat: display_name is added to ResourceSettings
fix: billing_account is now optional in Workload
feat: resource_settings is added to CreateWorkloadOperationMetadata

Created release for Google.Cloud.AssuredWorkloads.V1Beta1-1.0.0-beta07


Teleport Location

Hello ,
With the New update, teleportations is not possible with location, error : Spawn location does not exist or world is not loaded.
With other update, this issues is not there.

Unable to reproduce this issue. Try updating to latest release


Elasticsearch index lifecycle

Description
After bin/console es:index has been called, it doesn't automatically create the aliases needed for the integration to work. You have to call es:create:alias manually. This command is flagged as "Dev only" and should therefore not be necessary to use in a production environment.
Also after you reindex, the old indizes are never deleted. Therefore there's no cleanup implemented. That does work only a couple of times until your elasticsearch cluster runs full.
Possible Solution
Finalize elasticsearch index lifecycle.

Hey @hhoechtl,
the alias will be generated automatically over the scheduled task. We can not create the index immediately after indexing because the indexing is done over multiple queue worker.
The create alias task is configured to run each 5 minutes. In a production system with elastic search, you should have a cronjob which runs the scheduled tasks.
This cron job will add the https://github.com/shopware/platform/blob/6.1/src/Elasticsearch/Framework/Indexing/CreateAliasTask.php to the message queue.
The task is handled by this handler: https://github.com/shopware/platform/blob/6.1/src/Elasticsearch/Framework/Indexing/CreateAliasTaskHandler.php
The workflow is decribed here:
https://docs.shopware.com/en/shopware-platform-dev-en/how-to/using-elasticsearch

Hi @OliverSkroblin thanks for clarifying, but the cleanup is missing, right?

Thats right @hhoechtl. I will create a ticket that we will implement a command for it

Here the ticket: https://issues.shopware.com/issues/NEXT-7034

@hhoechtl you probably want to use this command :wink: https://github.com/shopware/platform/blob/6.1/src/Elasticsearch/Framework/Command/ElasticsearchCleanIndicesCommand.php
@OliverSkroblin I will close the ticket, as there is already a command

Just for reference this should be setup as a CRON. We have set this on a CRON every 15 minutes to clear the old indices :)
Also to say if you ever need to create an alias on your dev (when your not running scheduled tasks via a CRON) if you have a look in the elasticsearch_index_task and copy the values for the index and alias table (after running es:create:alias) you can map them by running (assuming you are using localhost and port 9200)
curl -X PUT "http://localhost:9200/[INDEX]/_alias/[ALIAS]?pretty"
and then check to see if the alias is created using
curl -X GET "http://localhost:9200/_cat/aliases/"
Not sure if that helps :)


Question: is it possible to remotely update the content inside of a Paragraph?

If I have access to a Terminal that contains a Paragraph, is the only way to update the Text in a Paragraph to tear down the old one and replace it with a new one? I don't see any obvious update methods on either Text or Paragraph.

tui provides an immediate mode API. All widgets that are part of the UI are supposed to be built from scratch at each draw call. Therefore, when the text you want to print to the terminal changes, you simply have to construct a new Paragraph with its value and the crate will take care of the rest (i.e emitting the minimal number of ANSI escapes sequences required to update the terminal).
For example, let's say you want to have a text that changes every second:
    // Our state
    let mut i = 0;
    loop {
        terminal.draw(|f| {
            // The UI text is derived from our state
            let text = if i & 1 == 0 {
                format!("{} is even", i)
            } else {
                format!("{} is odd", i)
            };
            let paragraph = Paragraph::new(text);
            // register the widget for this draw call
            f.render_widget(paragraph, f.size());
        })?;
        // Update our state
        i += 1;
        thread::sleep(Duration::from_secs(1));
    }


The IP address of the host in ports is dropped when services are created

Docker version: 17.05.0-ce, build 89658be
OS: 16.04.1-Ubuntu 4.8.0-51-generic x86_64
Steps to Reproduce:

Set Ports with IP in the Catalog's docker-compose.yml, like below:

ports: "<IP_ADDRESS>:8081:80"

Create a Stack StackA from this Catalog.

Results:
The StackA's generated docker-compose.yml has wrong Ports config, like below:

ServiceA:
PORTS:
*:8081->80/tcp

Expected:
The StackA's generated docker-compose.yml should have the same IP & ports with the Catalog's docker-compose.yml:

ServiceA:
PORTS:
"<IP_ADDRESS>:8081->80/tcp"

@waterelder this issue seems related to Docker Swarm Mode. This repo is about Docker Swarm, which is a different project. Check the README here: https://github.com/docker/swarm
Please open this issue at https://github.com/moby/moby.