fix(doc): fixes helm command for updating the openebs from 0.7.x-0.8.0

Signed-off-by: Ashish Ranjan<EMAIL_ADDRESS>This commit fixes helm command for updating the openebs from 0.7.x-0.8.0

@AmitKumarDas do you have any further comments on this?


REQUEST: Have ability to easily toggle on/off AutoLogisticsDroneSetup

There are times when I want to set up certain types of builds (like storage "modules") and I do not want to have any drones inserted into the PLS or ILS when setting them down.
This can be a problem when using a blueprint that has requests and demands already set inside of it for the stations, because as soon as they get put down then the auto-placed drones start running off.

I thought about doing something similar at one point got lazy. Maybe I'll take another look and see if I can figure out how to do it, because it's a good idea

I added an in-game config menu that lets you turn off adding drones for ILS or PLS on the go


New install of 0.90.86 fails on create pid directory

Installing Karabiner-Elements on a machine that previously had Karabiner but never had elements, fails at launch with following Error in report:
Process:               Karabiner-Elements [859]
Path:                  /Applications/Karabiner-Elements.app/Contents/MacOS/Karabiner-Elements
Identifier:            org.pqrs.Karabiner-Elements-Preferences-Window
Version:               0.90.86 (0.90.86)
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           Karabiner-Elements [859]
User ID:               501
Date/Time:             2017-02-05 13:38:47.463 -0500
OS Version:            Mac OS X 10.12.3 (16D32)
Report Version:        12
Anonymous UUID:        DE005134-8803-9FAB-2079-404ECA47C943
Time Awake Since Boot: 160 seconds
System Integrity Protection: enabled
Crashed Thread:        0  Dispatch queue: com.apple.main-thread
Exception Type:        EXC_CRASH (SIGABRT)
Exception Codes:       0x0000000000000000, 0x0000000000000000
Exception Note:        EXC_CORPSE_NOTIFY
Application Specific Information:
terminating with uncaught exception of type std::runtime_error: failed to create pid directory
abort() called

It's strange.
Could you show me the result of the following commands in Terminal?
ls -dl ~/.local
ls -dl ~/.local/share
ls -dl ~/.local/share/karabiner
mkdir -p  ~/.local/share/karabiner/pid

the last mkdir command might solve this issue.

Sorry for the delay in reply:
mark-MB:~ mark$ ls -dl ~/.local
drwxr-xr-x  3 root  staff  102 Dec  8  2015 /Users/mark/.local
mark-MB:~ mark$ ls -dl ~/.local/share
drwxr-xr-x  4 root  staff  136 May 28  2016 /Users/mark/.local/share
mark-MB:~ mark$ ls -dl ~/.local/share/karabiner
ls: /Users/mark/.local/share/karabiner: No such file or directory
mark-MB:~ mark$ mkdir -p ~/.local/share/karabiner/pid
mkdir: /Users/mark/.local/share/karabiner/pid: Permission denied
mark-MB:~ mark$ sudo mkdir -p ~/.local/share/karabiner/pid
Password:
mark-MB:~ mark$ ls -dl ~/.local/share/karabiner/pid
drwxr-xr-x  2 root  staff  68 Feb  9 20:14 /Users/mark/.local/share/karabiner/pid
mark-MB:~ mark$
Still didn't work but error changed to failed to create pid file. chmod pid to 777 and karabiner launched right up.
Thanks.

Let Karabiner-Elements running, and "System Preferences > Security & Privacy > Click "Allow".
My KE version is 12.1.0 and OS version is Sierra 10.13.6


activity feed documentation related ADO 1286442

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

File
Status
Preview URL
Details

msteams-platform/graph-api/activity-feed/feed-notifications.md
:white_check_mark:Succeeded
View

msteams-platform/graph-api/rsc/resource-specific-consent.md
:white_check_mark:Succeeded
View

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

Hi, Eddie.
I cannot tell which activity feed notification payload property you are now referencing. You highlighted all in your commentary. Clearly there is more than one because you say, “We should not expose this” and later you say, ”This also should not be exposed.”
Please let me know what should and should not be exposed so that I can provide accurate information for our developers. 🙂
Thank you,
La
From: eddie-lee-msft<EMAIL_ADDRESS>Sent: Friday, June 5, 2020 4:34 PM
To: MicrosoftDocs/msteams-docs<EMAIL_ADDRESS>Cc: la januari<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/msteams-docs] activity feed documentation (#1733)
@eddie-lee-msft commented on this pull request.

In msteams-platform/graph-api/activity-feed/feed-notifications.mdhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fmsteams-docs%2Fpull%2F1733%23discussion_r436206573&data=02|01|la.januari%40microsoft.com|516fdfe8e01a40f22b3408d809a8e9ed|72f988bf86f141af91ab2d7cd011db47|0|0|637269968377126827&sdata=HLUSER70L%2BODPp6QiI1pDcXNB8%2Br3gAkdJEcL5SEHsU%3D&reserved=0:

 {

   "type": "creatorTaskCreated",

   "description": "Created Task Created",Co

   "templateText": "The Creator created task {taskId} for you"

 }

]

},

+```

+## Activity feed notification payload properties

+| Property | Type | Required | Description |
+|-----|------|------|-----|
+|topic|teamworkActivityTopic | ✔ | represents what is being referenced in the feed item|
+|activityType | string | ✔| Represents the type of activity and must be declared in the Teams App Manifest|
+|recipient | teamworkNotificationRecipient |  ✔ | The intended receiver. A recipient must be a Teams user with the ability to post notifications to everyone in a team, channel, and chat.|
All but the one I commented on (teamsAppId and from) can be exposed :)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fmsteams-docs%2Fpull%2F1733%23discussion_r436206573&data=02|01|la.januari%40microsoft.com|516fdfe8e01a40f22b3408d809a8e9ed|72f988bf86f141af91ab2d7cd011db47|0|0|637269968377126827&sdata=HLUSER70L%2BODPp6QiI1pDcXNB8%2Br3gAkdJEcL5SEHsU%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAMBJMSUABMTONK3JZYJLOITRVF6GHANCNFSM4NSFVNVQ&data=02|01|la.januari%40microsoft.com|516fdfe8e01a40f22b3408d809a8e9ed|72f988bf86f141af91ab2d7cd011db47|0|0|637269968377136823&sdata=MF3smOOoYj%2Fp5pI0NJjZPUy73B2czM6wK8PkHYt0ItU%3D&reserved=0.

Docs Build status updates of commit 5413e37:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/graph-api/activity-feed/feed-notifications.md
:warning:Warning
View
Details

msteams-platform/assets/images/Capture.PNG
:white_check_mark:Succeeded
View

msteams-platform/graph-api/activity-feed/test-activity-feed-json-file.md
:white_check_mark:Succeeded
View

msteams-platform/graph-api/activity-feed/test-activity-feed-notifications.md
:white_check_mark:Succeeded
View

msteams-platform/graph-api/rsc/resource-specific-consent.md
:white_check_mark:Succeeded
View

msteams-platform/graph-api/rsc/test-resource-specific-consent.md
:white_check_mark:Succeeded
View

msteams-platform/graph-api/activity-feed/feed-notifications.md

Line 50: [Warning-InvalidBookmark] Invalid link: 'Install your app directly in Teams'. The file graph-api/activity-feed/feed-notifications.md doesn't contain a bookmark named 'install-your-app-directly-in-teams'.

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

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

File
Status
Preview URL
Details

msteams-platform/assets/images/Capture.PNG
:white_check_mark:Succeeded
View

msteams-platform/graph-api/activity-feed/feed-notifications.md
:white_check_mark:Succeeded
View

msteams-platform/graph-api/activity-feed/test-activity-feed-json-file.md
:white_check_mark:Succeeded
View

msteams-platform/graph-api/activity-feed/test-activity-feed-notifications.md
:white_check_mark:Succeeded
View

msteams-platform/graph-api/rsc/resource-specific-consent.md
:white_check_mark:Succeeded
View

msteams-platform/graph-api/rsc/test-resource-specific-consent.md
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit 1c6607a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/assets/images/Capture.PNG
:white_check_mark:Succeeded
View

msteams-platform/graph-api/activity-feed/feed-notifications.md
:white_check_mark:Succeeded
View

msteams-platform/graph-api/activity-feed/test-activity-feed-json-file.md
:white_check_mark:Succeeded
View

msteams-platform/graph-api/activity-feed/test-activity-feed-notifications.md
:white_check_mark:Succeeded
View

msteams-platform/graph-api/rsc/resource-specific-consent.md
:white_check_mark:Succeeded
View

msteams-platform/graph-api/rsc/test-resource-specific-consent.md
:white_check_mark:Succeeded
View

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

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

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Capture.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/find-tenant-id.PNG
:white_check_mark:Succeeded
View

msteams-platform/graph-api/activity-feed/feed-notifications.md
:white_check_mark:Succeeded
View

msteams-platform/graph-api/activity-feed/test-activity-feed-json-file.md
:white_check_mark:Succeeded
View

msteams-platform/graph-api/activity-feed/test-activity-feed-notifications.md
:white_check_mark:Succeeded
View

msteams-platform/graph-api/rsc/resource-specific-consent.md
:white_check_mark:Succeeded
View

msteams-platform/graph-api/rsc/test-resource-specific-consent.md
:white_check_mark:Succeeded
View

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

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

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Capture.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/find-tenant-id.PNG
:white_check_mark:Succeeded
View

msteams-platform/graph-api/activity-feed/feed-notifications.md
:white_check_mark:Succeeded
View

msteams-platform/graph-api/activity-feed/test-activity-feed-json-file.md
:white_check_mark:Succeeded
View

msteams-platform/graph-api/activity-feed/test-activity-feed-notifications.md
:white_check_mark:Succeeded
View

msteams-platform/graph-api/rsc/resource-specific-consent.md
:white_check_mark:Succeeded
View

msteams-platform/graph-api/rsc/test-resource-specific-consent.md
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit 013cb4a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Capture.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/find-tenant-id.PNG
:white_check_mark:Succeeded
View

msteams-platform/graph-api/activity-feed/feed-notifications.md
:white_check_mark:Succeeded
View

msteams-platform/graph-api/activity-feed/test-activity-feed-json-file.md
:white_check_mark:Succeeded
View

msteams-platform/graph-api/activity-feed/test-activity-feed-notifications.md
:white_check_mark:Succeeded
View

msteams-platform/graph-api/rsc/resource-specific-consent.md
:white_check_mark:Succeeded
View

msteams-platform/graph-api/rsc/test-resource-specific-consent.md
:white_check_mark:Succeeded
View

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

Hi @eddie-lee-msft. Above you mentioned :This actually isn't the whole story. If they intend on using the Postman test code linked above, then they'll need to replace a bunch more things than the client_Id, client_Secret, etc. They will also need to replace a number of IDs.
But in the docs that you sent it says:
Try the postman collection steps from the earlier section. Make sure that in whichever ‘Authentication’ call you use you replace ‘client_id’ with the AAD App ID you received. Replace ‘client_secret’ with the above client secret. Replace the tenant Id with yours as well (highlighted in screenshot below). Of course, replace other parameters (‘username’, ‘password’, etc.) as appropriate.
It does not mention updating the chatId etc...

Hi @eddie-lee-msft. Above you mentioned :This actually isn't the whole story. If they intend on using the Postman test code linked above, then they'll need to replace a bunch more things than the client_Id, client_Secret, etc. They will also need to replace a number of IDs.
But in the docs that you sent it says:
Try the postman collection steps from the earlier section. Make sure that in whichever ‘Authentication’ call you use you replace ‘client_id’ with the AAD App ID you received. Replace ‘client_secret’ with the above client secret. Replace the tenant Id with yours as well (highlighted in screenshot below). Of course, replace other parameters (‘username’, ‘password’, etc.) as appropriate.
It does not mention updating the chatId etc...

You are right. We were vague on the onboarding doc. I guess it depends on our audience - if they have prior experience with graph APIs and can recognize that the sample must have various IDs replaced then maybe it's not necessary to include any extra hints to them. Not sure :)

Docs Build status updates of commit 76ec546:
:warning: Validation status: warnings

File
Status
Preview URL
Details

msteams-platform/graph-api/activity-feed/feed-notifications.md
:warning:Warning
View
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Capture.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/find-tenant-id.PNG
:white_check_mark:Succeeded
View

msteams-platform/graph-api/activity-feed/test-activity-feed-json-file.md
:white_check_mark:Succeeded
View

msteams-platform/graph-api/activity-feed/test-activity-feed-notifications.md
:white_check_mark:Succeeded
View

msteams-platform/graph-api/rsc/resource-specific-consent.md
:white_check_mark:Succeeded
View

msteams-platform/graph-api/rsc/test-resource-specific-consent.md
:white_check_mark:Succeeded
View

msteams-platform/graph-api/activity-feed/feed-notifications.md

Line 134: [Warning-InvalidFileLink] Invalid file link:(~/graph-api/activity-feed/graph/api/team-sendactivitynotification?view=graph-rest-beta&tabs=http).

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

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

File
Status
Preview URL
Details

:x:Error

Details

[Error-PullRequestMergeConflict] Cannot sync git repo to specified state. Please make sure the pull request is mergeable.

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

Docs Build status updates of commit 171efdf:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/graph-api/activity-feed/feed-notifications.md
:bulb:Suggestion
View
Details

msteams-platform/graph-api/activity-feed/test-activity-feed-json-file.md
:bulb:Suggestion
View
Details

msteams-platform/graph-api/activity-feed/test-activity-feed-notifications.md
:bulb:Suggestion
View
Details

msteams-platform/graph-api/rsc/resource-specific-consent.md
:bulb:Suggestion
View
Details

msteams-platform/graph-api/rsc/test-resource-specific-consent.md
:bulb:Suggestion
View
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Capture.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/find-tenant-id.PNG
:white_check_mark:Succeeded
View

msteams-platform/graph-api/activity-feed/feed-notifications.md

Line 68, Column 1: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: /graph/auth-v2-user?view=graph-rest-1.0#3-get-a-token
Line 134, Column 1: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: /graph/api/team-sendactivitynotification?view=graph-rest-beta&tabs=http

msteams-platform/graph-api/activity-feed/test-activity-feed-json-file.md

Line 2, Column 8: [Suggestion-duplicate-titles] Title 'Testing activity feed notifications in Teams - Teams' is duplicated in: 'graph-api/activity-feed/test-activity-feed-json-file.md(2,8), graph-api/activity-feed/test-activity-feed-notifications.md(2,8)'. Titles must be unique within a docset.

msteams-platform/graph-api/activity-feed/test-activity-feed-notifications.md

Line 2, Column 8: [Suggestion-duplicate-titles] Title 'Testing activity feed notifications in Teams - Teams' is duplicated in: 'graph-api/activity-feed/test-activity-feed-json-file.md(2,8), graph-api/activity-feed/test-activity-feed-notifications.md(2,8)'. Titles must be unique within a docset.

msteams-platform/graph-api/rsc/resource-specific-consent.md

Line 95, Column 1: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: /graph/auth-v2-user?view=graph-rest-1.0#3-get-a-token

msteams-platform/graph-api/rsc/test-resource-specific-consent.md

Line 89, Column 1: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: /graph/api/resources/teams-api-overview?view=graph-rest-1.0

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

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

File
Status
Preview URL
Details

msteams-platform/graph-api/activity-feed/feed-notifications.md
:bulb:Suggestion
View
Details

msteams-platform/graph-api/activity-feed/test-activity-feed-json-file.md
:bulb:Suggestion
View
Details

msteams-platform/graph-api/activity-feed/test-activity-feed-notifications.md
:bulb:Suggestion
View
Details

msteams-platform/graph-api/rsc/resource-specific-consent.md
:bulb:Suggestion
View
Details

msteams-platform/graph-api/rsc/test-resource-specific-consent.md
:bulb:Suggestion
View
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Capture.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/find-tenant-id.PNG
:white_check_mark:Succeeded
View

msteams-platform/graph-api/activity-feed/feed-notifications.md

Line 68, Column 1: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: /graph/auth-v2-user?view=graph-rest-1.0#3-get-a-token

msteams-platform/graph-api/activity-feed/test-activity-feed-json-file.md

Line 2, Column 8: [Suggestion-duplicate-titles] Title 'Testing activity feed notifications in Teams - Teams' is duplicated in: 'graph-api/activity-feed/test-activity-feed-json-file.md(2,8), graph-api/activity-feed/test-activity-feed-notifications.md(2,8)'. Titles must be unique within a docset.

msteams-platform/graph-api/activity-feed/test-activity-feed-notifications.md

Line 2, Column 8: [Suggestion-duplicate-titles] Title 'Testing activity feed notifications in Teams - Teams' is duplicated in: 'graph-api/activity-feed/test-activity-feed-json-file.md(2,8), graph-api/activity-feed/test-activity-feed-notifications.md(2,8)'. Titles must be unique within a docset.

msteams-platform/graph-api/rsc/resource-specific-consent.md

Line 95, Column 1: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: /graph/auth-v2-user?view=graph-rest-1.0#3-get-a-token

msteams-platform/graph-api/rsc/test-resource-specific-consent.md

Line 89, Column 1: [Suggestion-preserve-view-not-set] Did you mean to link to a specific version? If so, add &preserve-view=true to the URL: /graph/api/resources/teams-api-overview?view=graph-rest-1.0

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

Docs Build status updates of commit 4b5d4b7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Capture.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/find-tenant-id.PNG
:white_check_mark:Succeeded
View

msteams-platform/graph-api/activity-feed/feed-notifications.md
:white_check_mark:Succeeded
View

msteams-platform/graph-api/activity-feed/test-activity-feed-json-file.md
:white_check_mark:Succeeded
View

msteams-platform/graph-api/activity-feed/test-activity-feed-notifications.md
:white_check_mark:Succeeded
View

msteams-platform/graph-api/rsc/resource-specific-consent.md
:white_check_mark:Succeeded
View

msteams-platform/graph-api/rsc/test-resource-specific-consent.md
:white_check_mark:Succeeded
View

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

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

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Capture.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/find-tenant-id.PNG
:white_check_mark:Succeeded
View

msteams-platform/graph-api/activity-feed/feed-notifications.md
:white_check_mark:Succeeded
View

msteams-platform/graph-api/activity-feed/test-activity-feed-json-file.md
:white_check_mark:Succeeded
View

msteams-platform/graph-api/activity-feed/test-activity-feed-notifications.md
:white_check_mark:Succeeded
View

msteams-platform/graph-api/rsc/resource-specific-consent.md
:white_check_mark:Succeeded
View

msteams-platform/graph-api/rsc/test-resource-specific-consent.md
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit 12ffe38:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

msteams-platform/assets/images/Capture.PNG
:white_check_mark:Succeeded
View

msteams-platform/assets/images/find-tenant-id.PNG
:white_check_mark:Succeeded
View

msteams-platform/graph-api/activity-feed/feed-notifications.md
:white_check_mark:Succeeded
View

msteams-platform/graph-api/activity-feed/test-activity-feed-json-file.md
:white_check_mark:Succeeded
View

msteams-platform/graph-api/activity-feed/test-activity-feed-notifications.md
:white_check_mark:Succeeded
View

msteams-platform/graph-api/rsc/resource-specific-consent.md
:white_check_mark:Succeeded
View

msteams-platform/graph-api/rsc/test-resource-specific-consent.md
:white_check_mark:Succeeded
View

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

@eddie-lee-msft, closing this PR for now. If this needs to be re-opened. Please let us know.


Deal with Enums

If one passes an enum as a parameter in JsonObject's put, it should be handled by the query executor.

With Couchbase 4.6.1 filtering for enum is working


[Swift 4.2] Updated LRU Cache

Checklist

[X] I've looked at the contribution guidelines.
[X] This pull request is complete and ready for review.

Description

No migration needed for Swift 4.2. References #748.

Thanks for the update!


Feature: Safe App access policy fields

This pull request adds a new Client table (only the url field for now) and a field exclusive_clients to the Safe App model.
It also adds filtering to the view to allow clients to specify the domain URL in the GET request and receive apps guaranteed to work on the client on this domain.
Closes #351
Original issue https://github.com/gnosis/safe-react/issues/2672
Example request/response:
GET /api/v1/safe-apps/?client_url=safe.com

[
   {
      "id":0,
      "url":"https://shaw.net/",
      "name":"Reid, Sanchez and Bailey",
      "iconUrl":"https://placekitten.com/71/525",
      "description":"Focused fresh-thinking Graphic Interface",
      "chainIds":[
         956
      ],
      "provider":"None",
      "accessControl":{
         "type":"DOMAIN_ALLOWLIST",
         "value":[
            "safe.com"
         ]
      }
   },
   {
      "id":1,
      "url":"http://www.hernandez-gonzalez.com/",
      "name":"Haynes LLC",
      "iconUrl":"https://dummyimage.com/71x402",
      "description":"Front-line foreground open architecture",
      "chainIds":[
         5737,
         9036
      ],
      "provider":"None",
      "accessControl":{
         "type":"NO_RESTRICTIONS"
      }
   }
]

@fmrsabino good catch, I actually forgot to register it to the admin panel. I fixed and it and tested it

works as expected

Thanks for the thorough review, @fmrsabino. Is it good to go now, or should we wait for a review from Uxio?

Thanks for the thorough review, @fmrsabino. Is it good to go now, or should we wait for a review from Uxio?

Let's merge it 🙌 We can start testing with the clients on staging!


Appreciate App v1.5

Fixed an issue where Appreciate app users wearing avatars without a specific joint wouldn't hear the Appreciate sound or see the Appreciation Dodecahedron
To test:

Wear an avatar without RightHandMiddle2 and LeftHandMiddle2 joints and WITH RightArm and LeftArm joints

Verify that the Appreciation Dodecahedron and sound comes from between your two arm joints.

Wear an avatar without RightHandMiddle2 and LeftHandMiddle2 joints and ALSO without RightArm and LeftArm joints

Verify that the Appreciation Dodecahedron and sound comes from your avatar's position (probably at torso).


subscribe to topics

Hi, would it be possible to use this plugin to subscribe/unsubscribe to FCM topics?
Thanks

Right now you can do it server side - https://developers.google.com/instance-id/reference/server
Its very easy to implement in the client too, I just havent got to it yet. see https://firebase.google.com/docs/cloud-messaging/topic-messaging#subscribe-to-a-topic-with-ios

Thanks, but I know nothing about iOS development, so I will keep an eye at this project.
Keep the good work! :-D


feat: multipart support

Tried to acknowledge the contributions of the previous contributors to for getting multipart geometries working. Closes https://github.com/robertleeplummerjr/Leaflet.glify/issues/42 and https://github.com/robertleeplummerjr/Leaflet.glify/pull/66 and https://github.com/robertleeplummerjr/Leaflet.glify/pull/158
Co-authored-by: Kanahiro Iguchi<EMAIL_ADDRESS>@Kanahiro
Co-authored-by: Liam O'flynn<EMAIL_ADDRESS>@quorth0n
Includes Prettier formatting

@robertleeplummerjr I tested this using the Antarctica.geojson file and it seems to render "good enough" for now. A strange overlap issue could be addressed down the road, when someones use case requires it. Can be merged. I will be depending on this PR branch till then.

Also willing to take responsibility for managing this repo if you find yourself too busy. Add me as a contributor if you'd like a teammate in this. (Still highly undereducated in the GL space, but managing repos/packages is a bit more straightforward)

I am having a problem with the click and popup handlers. It doesnt seem related to this because the example works fine, but curious to explore deeper into this to resolve.

@robertleeplummerjr this should be ready to merge and all related issues/pr's can be closed.
Just a reminder there are some stragler issues to close from my previous PR, see this comment

@robert-lore @robertleeplummerjr  thank you for the merge. Do you plan to make a release and close the resolved issues? I can help you manage this repo if you find yourself without time.

I'm installing it on my mac and was having trouble.

@robert-lore  Were they from my contributions or your machine?

not yet available in https://yarnpkg.com/package?q=leaflet.glify&name=leaflet.glify  ? Thank you so much

@charlieforward9  does your fix support combination of Polygon and MultiPolygon on a FeatureCollection? 🙇

Just removed canvas, which was causing my install issue, and published.

@charlieforward9 does your fix support combination of Polygon and MultiPolygon on a FeatureCollection? 🙇

Worth taking a look and letting me know. I just took the contributions of @quorth0n and @Kanahiro and applied them to the latest branch, so please let me know if you have any issues.

@charlieforward9 does your fix support combination of Polygon and MultiPolygon on a FeatureCollection? 🙇

@arvii , yes it works also for a combination of polygons and multipolygons.

@charlieforward9 does your fix support combination of Polygon and MultiPolygon on a FeatureCollection? 🙇

@arvii , yes it works also for a combination of polygons and multipolygons.

Hi @trafficonese Thank you so much for checking also. Could you please send me the sample data you tested? I want to verify if my format is correct. I tested it with a combination of Polygon and MultiPolygon in a GeoJSON FeatureCollection, but only the Polygon rendered. When I tested a GeoJSON Feature with a single MultiPolygon, it rendered correctly. Thank you so much! 🙇

@arvii It's a very simple Featurecollection:
const data: FeatureCollection<Geometry> = {
  type: "FeatureCollection",
  features: [
    {
      type: "Feature",
      properties: { name: "Polygon 1" },
      geometry: {
        type: "Polygon",
        coordinates: [
          [
            [102.0, 0.0],
            [103.0, 0.0],
            [103.0, 1.0],
            [102.0, 1.0],
            [102.0, 0.0],
          ],
        ],
      },
    },
    {
      type: "Feature",
      properties: { name: "MultiPolygon 1" },
      geometry: {
        type: "MultiPolygon",
        coordinates: [
          [
            [
              [100.0, 0.0],
              [101.0, 0.0],
              [101.0, 1.0],
              [100.0, 1.0],
              [100.0, 0.0],
            ],
          ],
          [
            [
              [100.2, 0.2],
              [100.8, 0.2],
              [100.8, 0.8],
              [100.2, 0.8],
              [100.2, 0.2],
            ],
          ],
        ],
      },
    },
    {
      type: "Feature",
      properties: { name: "Polygon 2" },
      geometry: {
        type: "Polygon",
        coordinates: [
          [
            [104.0, 0.0],
            [105.0, 0.0],
            [105.0, 1.0],
            [104.0, 1.0],
            [104.0, 0.0],
          ],
        ],
      },
    },
    {
      type: "Feature",
      properties: { name: "MultiPolygon 2" },
      geometry: {
        type: "MultiPolygon",
        coordinates: [
          [
            [
              [102.0, 2.0],
              [103.0, 2.0],
              [103.0, 3.0],
              [102.0, 3.0],
              [102.0, 2.0],
            ],
          ],
          [
            [
              [102.2, 2.2],
              [102.8, 2.2],
              [102.8, 2.8],
              [102.2, 2.8],
              [102.2, 2.2],
            ],
          ],
        ],
      },
    },
  ],
};


Spring '22 release

Upgraded API to v54.0
Enforced FLS on all SOQL queries
Bump node dependencies

Codecov Report

Merging #93 (bf6a82a) into master (0fd885e) will decrease coverage by 48.50%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #93       +/-   ##
==========================================
- Coverage   52.96%   4.46%   -48.51%
==========================================
  Files          30      11       -19
  Lines         825     291      -534
  Branches       48      48
==========================================
- Hits          437      13      -424
+ Misses        352     242      -110
  Partials       36      36

Flag
Coverage Δ

Apex
?

LWC
4.46% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

src/main/default/lwc/gameApp/gameApp.js
0.00% <ø> (ø)

src/main/default/classes/QuizAnswerService.cls

src/main/default/classes/QuizPlayerService.cls

src/main/default/classes/QuizQuestionService.cls

src/main/default/classes/QuizSessionService.cls

src/main/default/classes/QuizSettingsService.cls

...c/main/default/classes/QuizAnswerTriggerHelper.cls

src/main/default/classes/QuizEditorController.cls

src/main/default/classes/QuizController.cls

src/main/default/classes/QuizPostInstallScript.cls

... and 10 more

Continue to review full report at Codecov.

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


Add ndipebot and campoy to the OWNERS file

This will allow us to test and review PRs too.
cc @ndipebot

/verify-owners

/approve
I think this may be done through another mechanism that syncs the OWNERs file...

plz update this: https://github.com/kubernetes/org/blob/162bcdc731c2b670b380e4a600604f74e86f6d7c/config/kubernetes-sigs/sig-instrumentation/teams.yaml#L75

Closed and replaced by https://github.com/kubernetes/org/pull/4167


updated dependency of ParseUI and removed deprecated refreshInBackgroundWithBlock

What is the reasoning behind making ParseUI a dependency?

Hi, PFImageView is in ParseUI now. If you just add the pod as is, it will error on compile.

On 31 Mar 2015, at 19:41, Eneko Alonso<EMAIL_ADDRESS>wrote:
What is the reasoning behind making ParseUI a dependency?
—
Reply to this email directly or view it on GitHub https://github.com/hathway/Parse-PromiseKit/pull/4#issuecomment-88165385.

as described here https://github.com/hathway/Parse-PromiseKit/issues/3

Thanks for submitting this, I hadn't had a chance to get to it yet. Merging.


librosa: fix test broken scipy

Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

https://github.com/librosa/librosa/issues/1737

I submitted this change in #248476.
Could you please check it?


[ADP-2391] implement model API for submissions store

[x] implement model API operations for submissions store

Comments

Issue Number
ADP-2391

bors r+

bors r+

bors r-

bors r+

bors r+

bors r+


improve jnp.reshape's error message

At HEAD, here's the traceback we get by evaluating jnp.reshape(3, 2) in ipython with JAX_TRACEBACK_FILTERING='auto':

Here's the message after this PR:

If we didn't want to add these __tracebackhide__ = True lines, we'd get this:

I think I like the __tracebackhide__s, but what do you think, reviewer? The addition to the meth function will affect other Array/ShapedArray method call tracebacks, not just those of jnp.reshape, but I don't think that frame is ever useful...

There are some bugs to fix, but I requested a review for the basic strategy; assume I'll fix the failures!

Maybe we should gate the addition of __tracebackhide__ = True on the config option? We'd only be able to switch it at import time though...

Would it be doable with the help of some indirection (e.g. jax_tracebackhide) coupled with our traceback filtering machinery?

An excellent suggestion, wish I had thought if it myself :P
I'll give it a shot.

Hrm, I realized the perhaps-obvious issue that our traceback filtering machinery isn't even being applied here, so we'd have to start applying it.
Also, ipython already has ways to adjust how it managers __tracebackhide__ frames, namely the %xmode --show or %xmode Verbose magics, or the skip_hidden False ipdb command.
Since I don't want to start applying the general traceback hiding machinery somewhere we aren't already using it, I started to lean back towards land-and-iterate-if-we-come-up-with-improvements.


Support Package Signing

Type:  Feature request
NPE version: <IP_ADDRESS>
Installed from:  Windows Store
NPE should be updated to be aligned with NuGet Package signing https://github.com/NuGet/Home/issues/2577
I'd suggest the next User Stories by priority

P0. Disable edits if the package is signed.
P1. Show signature information.
P1. Allow removing the signature when saving.
P2. Allow signing packages.

Is there any news on signing into for non-MS projects?

Hi @maartenba
We are finishing the signature format spec, although we have started the implementation in the https://github.com/NuGet/NuGet.Client/commits/dev-feature-signing branch
We will announce progress once we publish the spec and have beta bits with signing support.

Thanks!

@maartenba I have a client app impl that uses Key Vault to do the sign operations and uses Bouncy Castle to generate the SignedCms message (since the APIs in the .NET one to do what I need don't exist yet):
https://github.com/onovotny/NuGetKeyVaultSignTool

P0 is done, P1 is partial (show signature information shows the publisher, but not validation status yet).

We now support showing signature information. Removing signature info and signing will likely wait until the next release.

The P0 and P1 items are both done now.

Closing out this issue as #292 tracks signing packages from NPE and the rest of the items here have been completed.


Google analytics switching to analytics.js

Google Analytics suggests upgrading to analytics.js for all users. Had this changed for my page layout and tested ok.
Would you like a pull request for this change?

Would you like a pull request for this change?

Yes please!

Thanks for the merge 👍


WIP: HIV transmission for short term partners

Still needs tests to check that things are correct, which might benefit from some refactoring. Not all factors for HIV transmission are accounted for yet, as they don't exist in the model, but I did add a dummy initialisation for viral load groups since that was the most complicated effect and central to the calculation rather than just being a post-factor.
We will need a data file for transmission properties too but I think this should be a separate PR

test_rred keeps failing on this and another branch but not on my machine; is this because of the pandas issue we saw before?

No, it's a pandas bug in 1.5.0, see also this comment. We're pinning it to 1.3.x in #71 but haven't added that here.


Slider callback not working

Callback value is not updating when sliding bar. It can be seen also on example gif.
Edit1: typos in
sliderOneValuesChangeStart
sliderOneValuesChange
sliderOneValuesChangeFinish

first letter was capital. Fixing this causes:
"undefined is not a function (evaluating 'this.setState({sliderOneChanging:true})')

using  = () => { solves the issue. My mistake.

👍


updated dependencies

updated the modules and configuration to be au goût du jour

Ah, it seems like after merging your PR there's a conflict now...

voilà it's done!

Thanks!


General fixes/improvements

[x] Fix openTicket throws error if user deletes the message
[x] Fix error being thrown due to incomplete translation file
[x] Update dependencies
[x] Check the existence of TOKEN environment variable
[x] Check if #181 bug was caused by non-latest 18.x of node

PR n°200 🎉

PR n°200 🎉

Oh, I just noticed that lol

On vscode i see it as 2 spaces

i use tab on all my projects

i use tab on all my projects

Oh, I moved away from tab because on some of my projects (especially involving python), mixing tab and space can cause all kinds of issue and space is just easier to deal with.
But ye, I'll revert it

Alr, we should be good now.


Postcss loader seems not working

Hello
I have trouble with postcss-loader.
from my webpack.config.babel.js
{
module: {
  loaders: [{
      test: /\.css$/,
      loader: ExtractTextPlugin.extract("style-loader", "css-loader!postcss-loader")
    }]
  },
  postcss: () => [
    require("postcss-import")({
      addDependencyTo: webpack,
      path: [
        path.join(__dirname, 'node_modules'),
        path.join(__dirname, 'src')
      ]
    }),
    require("postcss-url"),
    require("postcss-cssnext")
  ]

postcss use a special key from the webpack config to work.

@lionelB, that is weird. Let me check if the config is merge correctly by kotatsu.

Is your project available somewhere so I can help you better?

not yet but I can push it :)

As you wish :).

take a look here https://github.com/lionelB/lumographe.fr/tree/reboot

note this is a big Work In Progress

I promise I won't judge.

I notice that I should probably finish up plugins' merging.

Ok, I see where this went wrong. Damn Babel .default thingy...

Let me fix all that in the afternoon/evening.

thanks a looooot

Hi,
I've open a bunch of issue but I didn't manage to make kotatsu working using my current webpack.config file having weird eslint issues (like it tries to lint the transpiled file :/ )
I need to craft a smaller webconfig file (entry and specific loaders for file / css) and made a fresh test.
I confess I switch to webpack-dev-server but I definitly looking for a simpler solution to start with new project


Update plugins 17 September, 2024.

Plugin updates
advanced-custom-fi | 6.3.5  => 6.3.6
faustwp            | 1.3.2  => 1.4.1
taxopress-pro      | 3.23.0 => 3.25.1
wp-graphql         | 1.28.0 => 1.28.1
wordpress-seo      | 23.3   => 23.4

@rpeterman-gp or @brandonhundt can you review this? i can use this PR to test the automatic deploy production feature with it :)

@gtenaschuk go for it!

Thanks!
I have made the merge with [deploy:live] and the merge was pushed to dev -> test -> live environments automatically.
I added more info here https://github.com/PRX/cms.theworld.org/issues/227


Unable to resolve download.dnscrypt.info

Having problem with this domain, so can't download public resolver list. Please check.
nslookup download.dnscrypt.info
Server:  google-public-dns-a.google.com
Address:  <IP_ADDRESS>
*** google-public-dns-a.google.com can't find download.dnscrypt.info: Server failed

Should be fixed now, thanks!


Fix issue #371

Coverage remained the same at 100.0% when pulling 27a03bc63443641781ae210cc1e51caa00d1179c on issue_371 into 7576091b7b91fd20d4c3cf97e5b7b68b09ec4de1 on master.


Team Builder: Broken Image

When initially creating a team, the logo is uploaded and immediately shows "broken image", as the image then is loaded from the endpoint. At this point, the endpoint however, does not have the image yet (as the team is unsaved).

Fixed!

Fixed!


zotero <IP_ADDRESS>

Thank you for the contribution. It was merged directly as 3945645e47432f6488412b7186a652d898faa3f0 to keep commit history cleaner. Your contribution is still credited to you.


:disabled isn't a thing

:disabled is not a thing, ya dingus. Line 67 should be .#{$scales-namespace}[disabled],

I need ☕


[ WIP | Discussion ] React / Sutil inspired state handling

This is a prototype for a React/Sutil inspired state handling library for FuncUI.
There is an example contact app included to test it.

Feedback is appreciated.

This looks really cool!

Looking at your ContactBook example now...
Your componentized app is very clean. I love it! So happy to see this.

Looking at your ContactBook example now...
Your componentized app is very clean. I love it! So happy to see this.

Great to hear!
There are a few things I'm not yet sure about:

Naming. IWire is terrible, not sure if IReadable + IWritable or a variation of it would be better.

When using a useState hook in react its value is consistent during one render.

let counter = React.useState 0
React.useEffectOnce (fun _ ->
    counter.set (counter.current + 1)
    counter.set (counter.current + 1)
    counter.set (counter.current + 1)
)
counter.set (counter.current + 1)
counter.set (counter.current + 1)
counter.set (counter.current + 1)

// current render 'counter' = 0
// next render 'counter' = 1

Naming. IWire is terrible, not sure if IReadable + IWritable or a variation of it would be better.

I like publish/subscribe because it is used a lot in UI frameworks for sharing between view models in MVVM.
Rx uses Observable/Observer/Subject (where Subject can publish and subscribe). Still not as clear as publish/subscriber though IMO.

When using a useState hook in react its value is consistent during one render.

let counter = React.useState 0
React.useEffectOnce (fun _ ->
    counter.set (counter.current + 1)
    counter.set (counter.current + 1)
    counter.set (counter.current + 1)
)
counter.set (counter.current + 1)
counter.set (counter.current + 1)
counter.set (counter.current + 1)

// current render 'counter' = 0
// next render 'counter' = 1

Not sure yet if we should copy this behaviour.

I don’t have a strong opinion because I am wary of multiple renders in React and so I would never do this - I would just set one state at time. I also only use a single useState at a time to prevent confusing multi pass render scenarios.

We currently depend on call order or hooks like react. I don't really like this as we can't conditionally add hooks to the component.

Alternatives to make a call to ctx.useWhatever unique could be:

implicitly passing a key to ctx.useWhatever that we supply via the CallerLineNumberAttribute
explicitly passing a key

I am already used to React not allowing conditional hooks, so this limitation doesn’t really bother me.

One of the most exciting features I have seen in a while for F# on desktop 😍 looking forward to dig into this further.
One thing I didn't see in the example is the array dependencies for effects which re-triggers the effect when one of it's dependencies change:
// currently this is the API usage
let contact = ctx.useTap contact
let image = ctx.useAsync Api.randomImage

// In case the image is _dependant_ on the contract
let contact = ctx.useTap contact
let image = ctx.useAsync(Api.contactImage contact.Id, [ contact.Id ])

@JordanMarr

I wonder if there would be value in utilizing the built-in IObservable<'T>, IObserver<'T> and Subject<'T> for the underlying pub/sub mechanism.
While I admittedly don't quite have my head wrapped around the nuances of everything Wire.fs, it seems like it is very similar.
Potential benefits might be:
Mainly, the ability for an end user to take advantage of more advanced Rx capabilities on the incoming subscriptions.
For example: if you wanted to share an IObservable of keystrokes from one component to another, the user could use Rx debounce to limit observed messages to avoid unnecessary refreshes. This is a fairly common request that would be a pain to implement manually.
A secondary benefit would be a familiar pub/sub model with known names (IObservable instead of ITap, Subject instead of IWire, etc).

Initially considered this, but IObservable does not contain a value.
IValue could/should implement IObservable I think, but It's not sufficient on it's own.
https://fsprojects.github.io/FSharp.Data.Adaptive/ could work instead of our own values, but I don't fully get it. From looking at the code it does a lot I don't understand.

One of the most exciting features I have seen in a while for F# on desktop 😍 looking forward to dig into this further.
One thing I didn't see in the example is the array dependencies for effects which re-triggers the effect when one of it's dependencies change:
// currently this is the API usage
let contact = ctx.useTap contact
let image = ctx.useAsync Api.randomImage

// In case the image is _dependant_ on the contract
let contact = ctx.useTap contact
let image = ctx.useAsync(Api.contactImage contact.Id, [ contact.Id ])

@Zaid-Ajaj Thanks for the kind words. I have time next week to hopefully make some progress on this. If you have any suggestions just let me know. Happy to discuss anything.

I haven't had a chance to properly check all of the code, but I gotta say that this looks absolutely amazing and really promising! 😃
Just a couple of thoughts I have in my head after a quick check:

After your latest commit I have to say that the naming is much clearer now, but I feel like the hooks could be more self-explanatory like: useValue -> useState; usePassedValue -> usePassedState or useExternalState. Basically to better define the notion that a value can be modified and acts as a state holder. Wouldn't say it's a must since the current naming is not bad at all, but it took me a second to realize that useValue meant creating a state.
I was going over the list of built-in React hooks and I think making our own version of useEffect (I'd say even two: useEffect that takes a dependency array and a useOnStartEffect or useEffectOnce that executes only the first time) and useMemo would be a great addition to the current bunch.
useAsync is an awesome idea and makes such a common thing incredibly easy to implement, awesome job!

I haven't had a chance to properly check all of the code, but I gotta say that this looks absolutely amazing and really promising! 😃

Still an early prototype.

Just a couple of thoughts I have in my head after a quick check:

After your latest commit I have to say that the naming is much clearer now, but I feel like the hooks could be more self-explanatory like: useValue -> useState; usePassedValue -> usePassedState or useExternalState. Basically to better define the notion that a value can be modified and acts as a state holder. Wouldn't say it's a must since the current naming is not bad at all, but it took me a second to realize that useValue meant creating a state.

Like your suggestions, would favor names that are different from react. I fear (and I might be wrong) that having similar names with different behavior could confuse people.

I was going over the list of built-in React hooks and I think making our own version of useEffect (I'd say even two: useEffect that takes a dependency array and a useOnStartEffect or useEffectOnce that executes only the first time) and useMemo would be a great addition to the current bunch.

I have a implementation that implements effects. It currently is super buggy, will post here in a few days with more details/ problems that come with effects.

useAsync is an awesome idea and makes such a common thing incredibly easy to implement, awesome job!

Update
Better Names
Component (fun ctx ->
    let contacts = ctx.usePassedState ContactStore.shared.Contacts
    let selectedId = ctx.useState (None: Guid option)
    let filter = ctx.useState (None: string option)
    ..
)

Conditionally render hooks.
This is archived by using the line number a hook was invoked from as the identity instead of the call order. The line number is implicitly passed.
type Context with
    member this.useState<'value>(init: 'value, [<CallerLineNumber>] ?identity: int) : IWritable<'value> =
        this.useHook<'value>(
            StateHook.Create (
                identity = $"Line: {identity.Value}",
                state = StateHookValue.Lazy (fun _ -> new State<'value>(init) :> IConnectable),
                renderOnChange = true
            )
        ) :?> IWritable<'value>

..

Effects
Render only once after component is initialised / after first render
Component (fun ctx ->
    this.useEffect (
        handler = (fun _ ->
            ..
        ),
        triggers = [ EffectTrigger.AfterInit ]
    )
    ..
)

Render after every render.
Component (fun ctx ->
    this.useEffect (
        handler = (fun _ ->
            ..
        ),
        triggers = [ EffectTrigger.AfterRender ]
    )
    ..
)

Render when dependencies changed.
Component (fun ctx ->
    let contacts = ctx.usePassedState ContactStore.shared.Contacts
    let selectedId = ctx.useState (None: Guid option)

    this.useEffect (
        handler = (fun _ ->
            ..
        ),
        triggers = [
            EffectTrigger.AfterChange selectedId.Any
            EffectTrigger.AfterChange selectedContact.Any
        ]
    )
    ..
)

@Zaid-Ajaj  @JordanMarr @sleepyfran Thoughts?

@Zaid-Ajaj @JordanMarr @sleepyfran Thoughts?

My thoughts are that you are on 🔥!
I like the React-y hook names.
One question about re-rendering when dependencies change:
        triggers = [
            EffectTrigger.AfterChange selectedId.Any
            EffectTrigger.AfterChange selectedContact.Any
        ]

Is it possible to pass in any value on the model to AfterChange?
For example passing an arbitrary property that lives on the useState model -- or does it always check the entire model?

@Zaid-Ajaj @JordanMarr @sleepyfran Thoughts?

My thoughts are that you are on 🔥!
I like the React-y hook names.
One question about re-rendering when dependencies change:
        triggers = [
            EffectTrigger.AfterChange selectedId.Any
            EffectTrigger.AfterChange selectedContact.Any
        ]

Is it possible to pass in any value on the model to AfterChange?

EffectTrigger.AfterChange works with anything that implements the IAnyReadable interface.
Types that implement Readable<'t> (like State<'t>) are extended to have an Any : IAnyReadable property.
https://github.com/fsprojects/Avalonia.FuncUI/blob/7d089335946b1e3f9dd45c66172d7ece807f9c53/src/Avalonia.FuncUI.Components/State/State.fs#L46-L59

For example passing an arbitrary property that lives on the useState model -- or does it always check the entire model?

Right now it does not even check if there was really a change to the value. It just subscribes to the passed dependencies. Those dependencies might have a unique value filter.
It's also possible to "focus" state and add a unique value filter to it.
https://github.com/fsprojects/Avalonia.FuncUI/blob/7d089335946b1e3f9dd45c66172d7ece807f9c53/src/Avalonia.FuncUI.Components/State/State.Functions.fs#L38-L43
Component.create ("Person", fun ctx ->
    let name =
        person
        |> State.readMap (fun person -> person.FullName)
        |> State.readUnique
        |> ctx.usePassedState (* the context already supports state that does not trigger a render on change. there are just no overloads for it yet.  *)

    this.useEffect (
        handler = (fun _ ->
            ..
        ),
        triggers = [
            EffectTrigger.AfterChange name.Any
        ]
    )

    ..
)

To test more advanced scenarios I ported an app (FSharpGeneticAlgorithm) from @IntegerMan to FuncUI and the new state management.
There are still a few small bugs I need to fix, but I went pretty smooth overall.

@JaggerJo This looks absolutely amazing 😍 😍 can't wait to try it out!

Nice!
I plan on trying out your component system by recreating my chord parser UI in the very near future.
Of course I will need to contrive a reason to have more than one screen to fully test the components aspect. 🤔

Nice!
I plan on trying out your component system by recreating my chord parser UI in the very near future.
Of course I will need to contrive a reason to have more than one screen to fully test the components aspect. 🤔

Could be a nice app to include in the Examples if that would be ok for you.

This is absolutely amazing, @JaggerJo, really really great work! The latest changes look amazing. What's left for this to be ready for review? Planning on taking a deep look soon, just want to know if you think it's ready or still needs some time 😄

This is absolutely amazing, @JaggerJo, really really great work! The latest changes look amazing. What's left for this to be ready for review? Planning on taking a deep look soon, just want to know if you think it's ready or still needs some time 😄

Thanks for the compliment 🙂
There is still a lot to work on and discuss.
General

[ ] G.1 Counterpart to useRef needs to be finished.

Right now RenderOnChange is always set to true
https://github.com/fsprojects/Avalonia.FuncUI/blob/86e68fd76f6cd93907a39cc0388263ecf30c2915/src/Avalonia.FuncUI.Components/Context/Context.StateHook.fs#L53-L56

[ ] G.2 API needs some polishing.

ctx.usePassedStateReadOnly is way too long IMHO. Alternatives could be ctx.read.usePassed - and for rw ctx.usePassed.

Convention for read only State functions / functions that return IReadable<'value>.

https://github.com/fsprojects/Avalonia.FuncUI/blob/86e68fd76f6cd93907a39cc0388263ecf30c2915/src/Avalonia.FuncUI.Components/State/State.Functions.fs#L36-L48

[ ] G.3 Add more State functions to fill the gaps.

While porting the Genetic Algorithm UI I notices that a map function was missing, so I quickly added one. If we release this with a lot of missing state transformation functions potential users could be frustrated quickly. So I'd like to port a few more apps and see what's still missing.

[ ] G.4 Code needs documentation comments and in general more comments.

Tests

[ ] T.1 Tests need to be fixed (currently don't compile)
[ ] T.2 Tests regarding keyed components should be added [optional]
[ ] T.3 Tests for adapters should be added [optional]

Thanks for the detailed answer @JaggerJo! Do you want to divide the effort a bit? I might be able to help you with the tests and such 😃

Thanks for the detailed answer @JaggerJo! Do you want to divide the effort a bit?

@sleepyfran yes, happy to split the work.

I might be able to help you with the tests and such 😃

Would be great! If you see anything that's not immediately clear feel free to attach a ? comment in this PR and I'll try to add a better comment.

Worked on a simple inspector / debug tool. Still an early prototype, but I think this has some potential.

Inspector Prototype merged!
Had to get rid of a few features I really wanted (visual selection, sending values, better value view), but they took way too much time for something that initially was intended to be a proof of concept.

ctx.attrs can be used to attache attributes directly to the component control.
This does not work because the Dock property is set on the TextBlock, not on the component directly.
DockPanel.create [
    DockPanel.children [
        Component.create ("", fun ctx ->
            TextBlock.create [
                TextBlock.dock Dock.Top
                TextBlock.text "Should be on top!"
            ]
        )

        Component.create ("", fun ctx ->
            TextBlock.create [
                TextBlock.dock Dock.Bottom
                TextBlock.text "Should be on the bottom!"
            ]
        )
    ]
]

This works, as it sets the attributes on the component.
DockPanel.create [
    DockPanel.children [
        Component.create ("", fun ctx ->
            ctx.attrs [ Component.dock Dock.Top ]

            TextBlock.create [
                TextBlock.text "Should be on top!"
            ]
        )

        Component.create ("", fun ctx ->
            ctx.attrs [ Component.dock Dock.Top ]

            TextBlock.create [
                TextBlock.text "Should be on the bottom!"
            ]
        )
    ]
]

It is now possible to get the underlaying reference of a view - (called an outlet in the code).

Right now all the state management / component related stuff is located in a separate project.
Thinking about merging the Avalonia.FuncUI and Avalonia.FuncUI.Components Projects.

After that I think this is ready for a preview/beta release.
@JordanMarr Thoughts?

Agree with merging the components project inside of the FuncUI project. I've started working on a project using the hooks, it's really lovely to use!
Also spent a bit the other day taking a deeper look on how everything works. I imagine that when you refer to add tests for keyed components you mean to test the way the differ uses the view key to determine the diff? Is there another piece of logic that relies on the key or any other tests you can think of? 😄

@sleepyfran
Thanks for the patience. Currently renovating our new Apartment and about to move.

Agree with merging the components project inside of the FuncUI project.

👍🏼

I've started working on a project using the hooks, it's really lovely to use!

Nice! Were there any ruff edges? / Things we should improve?

Also spent a bit the other day taking a deeper look on how everything works. I imagine that when you refer to add tests for keyed components you mean to test the way the differ uses the view key to determine the diff?

Exactly.

Is there another piece of logic that relies on the key or any other tests you can think of? 😄

No, should only be relevant for the differ.

@JaggerJo no worries, thanks for the response and good luck with the moving 😃

Nice! Were there any ruff edges? / Things we should improve?

I haven't really got past a basic UI app with a couple of screens so I might discover more stuff later, but the only thing I'm missing is a Map function in the useState hook similar to how React accepts a function instead of a value when calling setState. It's not really that important since you can always use the current state value, but it'd make mapping operations a bit easier. Aside from that I'd say it's been a really pleasurable experience and having that many examples from the beginning gave me a really good starting point, so props for that!

On a side note I've started the process of fixing/adding tests in the universal-hooks-tests branch, started by solving the Outlet not being specified there.
I've only encountered one problem that I'm not entirely sure how to solve: ever since the introduction of the Outlet property we can't really do Assert.Equal anymore, since Outlet is a function and equality checking is not supported. So not really sure how to process on equality comparing in these cases: should we ignore the actual value of the outlet and just check whether the Option Some/None matches or can you think of another way of doing it? Since the function also returns unit there's really not that much we can do with it.
As you can see in the branch I've basically implemented the custom equality attr in the ViewDelta, which is not the prettiest thing but it's the only way I can think of doing so. If you have any other ideas please let me know 😃
Will update the thread once I finish the rest of the tests.

I started a sample component UI today to better understand how it works.
My current dilemma is that I created some state using useState, but when I try to set the state, it fails because it is not writable. Is there a special way I need to create It to make it writable?

I started a sample component UI today to better understand how it works.
My current dilemma is that I created some state using useState, but when I try to set the state, it fails because it is not writable. Is there a special way I need to create It to make it writable?

@JordanMarr can you give me an example?

@JaggerJo no worries, thanks for the response and good luck with the moving 😃

Nice! Were there any ruff edges? / Things we should improve?

I haven't really got past a basic UI app with a couple of screens so I might discover more stuff later, but the only thing I'm missing is a Map function in the useState hook similar to how React accepts a function instead of a value when calling setState. It's not really that important since you can always use the current state value, but it'd make mapping operations a bit easier. Aside from that I'd say it's been a really pleasurable experience and having that many examples from the beginning gave me a really good starting point, so props for that!

@sleepyfran there currently are 2 mapping adapters, one for read and one for read + write. The write one has no convenient pipe-able function yet (was not sure about the signature, think we could do cool things with quotations..).

Should be simple to add tho.

On a side note I've started the process of fixing/adding tests in the universal-hooks-tests branch, started by solving the Outlet not being specified there.
I've only encountered one problem that I'm not entirely sure how to solve: ever since the introduction of the Outlet property we can't really do Assert.Equal anymore, since Outlet is a function and equality checking is not supported. So not really sure how to process on equality comparing in these cases: should we ignore the actual value of the outlet and just check whether the Option Some/None matches or can you think of another way of doing it? Since the function also returns unit there's really not that much we can do with it.
As you can see in the branch I've basically implemented the custom equality attr in the ViewDelta, which is not the prettiest thing but it's the only way I can think of doing so. If you have any other ideas please let me know 😃
Will update the thread once I finish the rest of the tests.

Ahh, yeah. I think we can ignore the Outlet field entirely.

t dilemma is that I created some state using useState, but when I try to set the state, it fails because it is not writable. Is there a special way I need to create It to make it

Never mind - it was a dumb mistake.
I failed to notice that useState returns an IWritable<'T> because I am so used to it returning 'T in React and Feliz.
The fix was to call model.Current. Somehow I missed that detail when looking at your samples.

PR  #182 adds a ChordParser sample UI (based on my FParsec project).
I also added an experiment useElmish hook that wraps useState that was inspired by Feliz!

One of the things I really like about Feliz is the ability to use useState for simple components or useElmish for more complex components.
The useElmish hook also allows you to refer to model and dispatch directly in your component, so no need to call model.Current
There are currently two overloads of useElmish: one that takes an IWritable<'Model>' and one that takes a 'Model`.

What do you think? Should I continue work on it?

PR #182 adds a ChordParser sample UI (based on my FParsec project). I also added an experimental useElmish hook that wraps useState (inspired by Feliz)!

One of the things I really like about Feliz is the ability to use useState for simple components or useElmish for more complex components.
The useElmish hook also allows you to refer to model and dispatch directly in your component, so no need to call model.Current
There are currently two overloads of useElmish: one that takes an IWritable<'Model>' and one that takes a 'Model`.

What do you think? Should I continue work on it?

Like it, but think we should move it to the FuncUI.Elmish Project.

I've also finished the tests for the keyed views in #183. @JaggerJo let me know if you miss anything 😃

It would be nice if useState behaved the same way as it does in React and Feliz by returning a tuple.
Ex:
let filter, setFilter = useState filter

This is nice because it makes your UI code easier to write by eliminating the extra calls to .Set and .Current.
However, I realize that IWritable<'value> is fundamental for passing stuff between components.
Maybe there could be a different useState overload that works like classic React / Feliz?
Alternatively, maybe there could be a simple built-in function to easily convert an IWritable<'value> to a tuple:
/// Needs a better name that this...
let split (writable: IWritable<_>) =
        writable.Current, writable.Set

Usage
let enabled, setEnabled = ctx.useState true |> split

I've also finished the tests for the keyed views in #183. @JaggerJo let me know if you miss anything 😃

Nice!

It would be nice if useState behaved the same way as it does in React and Feliz by returning a tuple.
Ex:
let filter, setFilter = useState filter

This is nice because it makes your UI code easier to write by eliminating the extra calls to .Set and .Current.
However, I realize that IWritable<'value> is fundamental for passing stuff between components.
Maybe there could be a different useState overload that works like classic React / Feliz?
Alternatively, maybe there could be a simple built-in function to easily convert an IWritable<'value> to a tuple:
/// Needs a better name that this...
let split (writable: IWritable<_>) =
        writable.Current, writable.Set

Usage
let enabled, setEnabled = ctx.useState true |> split

I personally never liked the way react does this and would not include a function that seperates current and set right now.
It can easily be added tho by people not liking the current model - but if you ever need to pass that state down you need to reconstruct a Readable somehow, making the events work, ... so I would not encourage doing this by including it in the lib.

Super busy right now unfortunately.
This is ready to merge after combining the FuncUI and FuncUI.Components projects. Would someone take over that part?

Super busy right now unfortunately.
This is ready to merge after combining the FuncUI and FuncUI.Components projects. Would someone take over that part?

Awesome to hear it's ready! I'll take care of combining both modules, solving all the conflicts and merging tomorrow 😃

Super busy right now unfortunately.
This is ready to merge after combining the FuncUI and FuncUI.Components projects. Would someone take over that part?

Awesome to hear it's ready! I'll take care of combining both modules, solving all the conflicts and merging tomorrow 😃

IIRC there is already a namespace + folder in the FuncUI project - but it's meaning is a bit different. Might be good to change that as I see the could lead to confusion.

@sleepyfran let me know if you need help!

@sleepyfran let me know if you need help!

Thanks :)
I actually haven't had that much time, but I started the process the other day on the branch universal-hooks-moving, having some compilation issues that for some reason didn't arise when the code was in a separate project, but as I said I haven't had much time to look into it, hopefully I can finish the work soon.
How should we name the code that is currently sitting in the components folder, though? It's just the Hosts, Lazy and DataTemplateView, so not sure what the correct naming for that one should be.

@sleepyfran let me know if you need help!

Thanks :)
I actually haven't had that much time, but I started the process the other day on the branch universal-hooks-moving, having some compilation issues that for some reason didn't arise when the code was in a separate project, but as I said I haven't had much time to look into it, hopefully I can finish the work soon.
How should we name the code that is currently sitting in the components folder, though? It's just the Hosts, Lazy and DataTemplateView, so not sure what the correct naming for that one should be.

No worries, can relate. Time is flying by right now.
Regarding the stuff currently in the components folder:

Move hosts & data template views to top-level namespace
Delete Lazy (components should be used instead)

@sleepyfran let me know if you need help!

Thanks :)
I actually haven't had that much time, but I started the process the other day on the branch universal-hooks-moving, having some compilation issues that for some reason didn't arise when the code was in a separate project, but as I said I haven't had much time to look into it, hopefully I can finish the work soon.
How should we name the code that is currently sitting in the components folder, though? It's just the Hosts, Lazy and DataTemplateView, so not sure what the correct naming for that one should be.

No worries, can relate. Time is flying by right now.
Regarding the stuff currently in the components folder:
* Move hosts & data template views to top-level namespace

* Delete Lazy (components should be used instead)

Thanks a lot! I finished the whole thing and published the PR in #188, take a look whenever you get some time, but this should be ready to roll! 😃

It looks like there were still some conflicts even after merging my branch, should be good now. Also bumped the dotnet version in the Actions so that they don't fail while trying to compile the Chord Parser project 😃

We're live 🚀
Thanks @JaggerJo for the amazing work 😃

@sleepyfran nice! @JordanMarr
How do we go about releasing this? I guess we should also change the package name to not include 'Jaggerjo'.

@sleepyfran nice! @JordanMarr
How do we go about releasing this? I guess we should also change the package name to not include 'Jaggerjo'.

@sleepyfran nice! @JordanMarr
How do we go about releasing this? I guess we should also change the package name to not include 'Jaggerjo'.

Agree, we were having that conversation as part of #173. My favorite option was FSharp.Avalonia as @JordanMarr suggested, but I'm up for whatever other naming scheme. I've never published anything on NuGet, is it enough with renaming the Product/PackageId fields in the fsproj file or is there any other change required in NuGet itself?

Also created #189 to track the steps needed for before/after the release of the new version so that the docs and other resources are in good health, feel free to suggest any other steps to be added 😃


Implement Handle::clone()

Closes #24

If no one objects to this PR, I'd like to merge it in a few days.  Thanks!


[Toolchain] Add unit tests

This commit adds unit tests for toolchain related classes.
ONE-vscode-DCO-1.0-Signed-off-by: Jiyoung Yun<EMAIL_ADDRESS>

Origin
2022-08-04 11:37 AM d776d3e7ec74d26eebd4a2367e9c2339e879cc4e

Patch 1 https://github.com/Samsung/ONE-vscode/pull/1148/commits/3320e247bf769f291fc2bfd288db26df5a9fb99c

Patch 2 https://github.com/Samsung/ONE-vscode/commit/ece91b676a075afea94e478bf7f0090ef3aca1fa

Patch 3 https://github.com/Samsung/ONE-vscode/pull/1148/commits/065ef7bb3cc94f5e6a431b9c4d0e12429c762a93

Patch 4.5.6 https://github.com/Samsung/ONE-vscode/pull/1148/commits/33fe291e9f8c955c101e47206fd3e6bc0fe43b3b

All done!


update the infant uuid as a new form was published

Requirements

[ ] This PR has a title that briefly describes the work done including the ticket number. If there is a ticket, make sure your PR title includes the ticket number in the format OHRI-123 My PR title.
[ ] My work includes tests or is validated by existing tests.

Summary

update the infant uuid as a new form was published
Screenshots

Related Issue

Other

Closing this PR-- will do a config override instead.


Button spinners - again

This is 3 commits which add back in the import button, and the media-quota button spinners.
The original problem seems to have stemmed from the fact that chrome doesn't seem to like both the onsubmit and onclick events together.
In addition to this it seems that (with chrome) disabling a button while submitting, can cause the form parameters to be disabled too. I suspect that in this case the code was simply waiting for input which never appeared. Hence the spinner just kept spinning.
Finally, it seems that for the media/quota the onsubmit event was placed on both the submit button and the form itself. I have no idea how the event handler will decide what should be done first, but I wouldn't be surprised if it got a bit confused.
I have placed the onsubmit event on the form only (in both button cases). The submit button only has an onclick event.
The button disabling is handled within the called javascript functions by passing a parameter.
Unfortunately the import and media/quota code handles the submission response differently. The import will use jquery to raise a popup when the import has completed. Once detected the spinner is stopped.
The media/quota code calls a javascript 'alarm' to create a popup once the file has been uploaded. This causes a problem in that the spinner is stopped only after the user has clicked on OK. I'm not totally happy with it, but I cannot find any other way of handling this. Secondly, I would hope that users simply click on the 'OK' button in the popup, and be happy that the spinner does stop.
I have tested these commits with Linux using firefox and chrome. I have also tried it using chrome under Windows 7. It worked as expected.

@jayaich @torinfo this seems to be working fine now.


Combine api & serialization into gokzg4844 package

This PR will:

Replace go-proto-danksharding-crypto with go-kzg-4844.
Update package name at the top of each file.
Merge errors.go files.
Remove api. and serialization. in non-test files.
Replace api. and serialization. with gokzg4844. in test files.
Move api/* and serialization/* files into the project root.

Necessary if you don't want a weird imports like:

✅ import gokzg4844 "github.com/crate-crypto/go-kzg-4844"
❌ import "github.com/crate-crypto/go-kzg-4844/gokzg4844"

Moving the files might be controversial, but it's pretty common. See go-kzg.

Ah you're right, I didn't notice that. Will update.


[Doc] [Google federated authenticator] Google federated authenticator page is not updated.

when following https://is.docs.wso2.com/en/next/guides/authentication/social-login/add-google-login/,
we can see that UI on Google API & Services is not updated in our doc space,

This is fixed. https://is.docs.wso2.com/en/latest/guides/authentication/social-login/add-google-login/


How to boot directly into a chroot?

I've just started using crouton, nice project!
However I didn't yet understand if it would be possible (maybe with a rootfs modification) to automatically start a chroot when the chromebook boots up. Actually, I'd also be interested in not starting the ChromeOS session manager :)
I just noticed that network is not connected when I am logged out from the ChromeOS session, is there a way to enable network without logging in?
Has anybody attempted this? I guess it's something more difficult than an /etc/inittab modification

I just found https://github.com/dnschneid/crouton/wiki/Autostart-crouton-chroot-at-ChromeOS-startup
So I guess I could automate this if #1777 was addressed.. :\


Question: Sending actions from layout to child routes component

Lets say I have a HomeLayout that has child routes: Products and Services
export default (store) => ({
  component: HomeLayout,
  getChildRoutes: (location, next) => {
    require.ensure([], (require) => {
      next(null, [
        require('./Products').default(store),
        require('./Services').default(store)
      ])
    })
  }
})

The home layout has my Header with a Refresh button, when the refresh button is clicked it should refresh the product list or service list.
Right now I do this by dispatching refresh actions based on the router location
if location is /products dispatch refreshProducts()
else if location is /services dispatch refreshServices()
Am I doing the right thing? Or Is there a better way to do this?

When you start to have actions that start to do different things based on your current route, it's a sign that you need to rethink that action's responsibility and possibly break it down into separate more targeted actions. However, that's difficult to do with your use case, so I'd say it's somewhat of a necessary evil.
I'm at a bit of a loss as far as figuring out an alternative, and if I were in your position I'd probably move the refresh button to a component that's tied more directly into the current route (i.e. the button can be provided a callback to do exactly what you want).
Sorry I couldn't be more of help. I suggest posting this in StackOverflow or another community more targeted at helping understand best practices.


Update GH files for issue templates and Jira automation

This PR updates the .github files to

Ensure we have a file for tasks/enhancements
Ensure we expose dod in task issues
Use the FastAPI for ticket sync, and not JIRA_URL

Reminder to self, don't add orthogonal tasks in the same PR (jira automation and task renames) 😅