The table above is too old, 4 month back, and need to update.

We have CN2/CE2 GA last month, couple of new VM SKUs and services landed in China, e.g. Dv3, Ev3, B series VM, Azure Advisor, Azure Functions, IoT Suite Remote Monitoring solution, Azure Analysis. Can you please update the data above.

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

ID: ddec58f7-e882-4f3d-8c31-500565e81d4a
Version Independent ID: 06dc5fba-2fdc-2cea-9f61-76e0fe72f840
Content: Azure service availability in China
Content Source: articles/china/china-get-started-service-availability.md
Service: china
GitHub Login: @v-wimarc
Microsoft Alias: v-wimarc

Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.

@MicahMcKittrick-MSFT  This content is now owned by the China Business Team. Please check with Monica Rush and Josephine Qiu to see who this should be assigned to. Thanks - mw

Monica and Josephine,
Can you provide some guidance for Micah on who this bug should be assigned to? It’s an update request for the Mooncake content and I’m not sure what the status is as far as who owns it at this point. Thanks - mw
From: Micah<EMAIL_ADDRESS>Sent: Wednesday, July 4, 2018 8:31 AM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: Marc Wilson (Resources Online<EMAIL_ADDRESS>Assign<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] The table above is too old, 4 month back, and need to update. (#11182)
Assigned #11182https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F11182&data=02|01|v-wimarc%40microsoft.com|14bfd344804a40013abf08d5e1c31ba8|72f988bf86f141af91ab2d7cd011db47|1|0|636663150452059813&sdata=QiUvH9pLEP0tHvs956XJ8WsU2GRc757FAKa5eQH4bAw%3D&reserved=0 to @v-wimarchttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fv-wimarc&data=02|01|v-wimarc%40microsoft.com|14bfd344804a40013abf08d5e1c31ba8|72f988bf86f141af91ab2d7cd011db47|1|0|636663150452059813&sdata=5PweFdRYJ4L21bKD7%2Ff8hhUilwiIEc8W2Fu65pQx56c%3D&reserved=0.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F11182%23event-1716583006&data=02|01|v-wimarc%40microsoft.com|14bfd344804a40013abf08d5e1c31ba8|72f988bf86f141af91ab2d7cd011db47|1|0|636663150452059813&sdata=VmP3%2FghJ%2FIpU%2FAd%2BzsEpQupOT7S4WuPYH6m6wqBoaxs%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAeVXQohOq8MCURDWeDH6RDJvZ642ddI_ks5uDN-jgaJpZM4VB7ML&data=02|01|v-wimarc%40microsoft.com|14bfd344804a40013abf08d5e1c31ba8|72f988bf86f141af91ab2d7cd011db47|1|0|636663150452059813&sdata=Hu6keSQpOV6yD5bPYb0qtokQL0f7F0ZBagGQf%2Be5LRk%3D&reserved=0.

Josephine, can you assign to the appropriate PM/writer?
A few more comments:

I have cc’ed Julia Kornich, who is the new PM for sovereign clouds (Julia, this is just FYI for now)
Josephine, I think that once you determine who the PM/writer is, the article should be reassigned from Marc to that writer
All articles should be assigned to another PM/writer, and Marc’s name should be removed. Josephine, would you be able to take care of that at this point?

Julia will be in touch soon to coordinate work going forward. But I am assuming that Josephine can address the above issues for now.
Please let me know if you have comments or questions re: my reply. Thanks to everyone -- Monica
From: Marc Wilson (Resources Online)
Sent: Thursday, July 5, 2018 7:53 AM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Monica Rush<EMAIL_ADDRESS>Josephine Qiu<EMAIL_ADDRESS>Cc: Assign<EMAIL_ADDRESS>Subject: RE: [MicrosoftDocs/azure-docs] The table above is too old, 4 month back, and need to update. (#11182)
Monica and Josephine,
Can you provide some guidance for Micah on who this bug should be assigned to? It’s an update request for the Mooncake content and I’m not sure what the status is as far as who owns it at this point. Thanks - mw
From: Micah <notifications<EMAIL_ADDRESS>Sent: Wednesday, July 4, 2018 8:31 AM
To: MicrosoftDocs/azure-docs <azure-docs<EMAIL_ADDRESS>Cc: Marc Wilson (Resources Online) <v-wimarc<EMAIL_ADDRESS>Assign <assign<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] The table above is too old, 4 month back, and need to update. (#11182)
Assigned #11182https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F11182&data=02|01|v-wimarc%40microsoft.com|14bfd344804a40013abf08d5e1c31ba8|72f988bf86f141af91ab2d7cd011db47|1|0|636663150452059813&sdata=QiUvH9pLEP0tHvs956XJ8WsU2GRc757FAKa5eQH4bAw%3D&reserved=0 to @v-wimarchttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fv-wimarc&data=02|01|v-wimarc%40microsoft.com|14bfd344804a40013abf08d5e1c31ba8|72f988bf86f141af91ab2d7cd011db47|1|0|636663150452059813&sdata=5PweFdRYJ4L21bKD7%2Ff8hhUilwiIEc8W2Fu65pQx56c%3D&reserved=0.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F11182%23event-1716583006&data=02|01|v-wimarc%40microsoft.com|14bfd344804a40013abf08d5e1c31ba8|72f988bf86f141af91ab2d7cd011db47|1|0|636663150452059813&sdata=VmP3%2FghJ%2FIpU%2FAd%2BzsEpQupOT7S4WuPYH6m6wqBoaxs%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAeVXQohOq8MCURDWeDH6RDJvZ642ddI_ks5uDN-jgaJpZM4VB7ML&data=02|01|v-wimarc%40microsoft.com|14bfd344804a40013abf08d5e1c31ba8|72f988bf86f141af91ab2d7cd011db47|1|0|636663150452059813&sdata=Hu6keSQpOV6yD5bPYb0qtokQL0f7F0ZBagGQf%2Be5LRk%3D&reserved=0.

Hi Monica, glad to know PM for sovereign clouds has onboarded.
About the feedback on the article Azure service availability in Chinahttps://docs.microsoft.com/en-us/azure/china/china-get-started-service-availability#feedback, I am going to contact you about that.  Azure.cn is going to release a web page of Product available by region next Monday. The page on staging server can be access here http://atomtest.chinacloudsites.cn/zh-cn/home/features/products-by-region ).  It’s similar to this pagehttps://azure.microsoft.com/en-us/global-infrastructure/services/ in Azure.microsoft.com. So I think there is no reason we keep maintenance on the docs article Azure service availability in Chinahttps://docs.microsoft.com/en-us/azure/china/china-get-started-service-availability#feedback. Can we remove it, and redirect user who wants this information to Azure.cn portal landing page? I can give you the URL. It will be https://www.azure.cn/home/features/products-by-region (not available until next Monday)  with both English and Chinese languages support.
Regards,
Josephine Qiu, ACN
From: Monica Rush
Sent: Thursday, July 5, 2018 11:22 PM
To: Marc Wilson (Resources Online<EMAIL_ADDRESS>MicrosoftDocs/azure-docs<EMAIL_ADDRESS>MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Josephine Qiu<EMAIL_ADDRESS>Cc: Assign<EMAIL_ADDRESS>Julia Kornich<EMAIL_ADDRESS>Subject: RE: [MicrosoftDocs/azure-docs] The table above is too old, 4 month back, and need to update. (#11182)
Josephine, can you assign to the appropriate PM/writer?
A few more comments:

I have cc’ed Julia Kornich, who is the new PM for sovereign clouds (Julia, this is just FYI for now)
Josephine, I think that once you determine who the PM/writer is, the article should be reassigned from Marc to that writer
All articles should be assigned to another PM/writer, and Marc’s name should be removed. Josephine, would you be able to take care of that at this point?

Julia will be in touch soon to coordinate work going forward. But I am assuming that Josephine can address the above issues for now.
Please let me know if you have comments or questions re: my reply. Thanks to everyone -- Monica
From: Marc Wilson (Resources Online)
Sent: Thursday, July 5, 2018 7:53 AM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>MicrosoftDocs/azure-docs <azure-docs<EMAIL_ADDRESS>Monica Rush <monicar<EMAIL_ADDRESS>Josephine Qiu <yiqiu<EMAIL_ADDRESS>Cc: Assign <assign<EMAIL_ADDRESS>Subject: RE: [MicrosoftDocs/azure-docs] The table above is too old, 4 month back, and need to update. (#11182)
Monica and Josephine,
Can you provide some guidance for Micah on who this bug should be assigned to? It’s an update request for the Mooncake content and I’m not sure what the status is as far as who owns it at this point. Thanks - mw
From: Micah <notifications<EMAIL_ADDRESS>Sent: Wednesday, July 4, 2018 8:31 AM
To: MicrosoftDocs/azure-docs <azure-docs<EMAIL_ADDRESS>Cc: Marc Wilson (Resources Online) <v-wimarc<EMAIL_ADDRESS>Assign <assign<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] The table above is too old, 4 month back, and need to update. (#11182)
Assigned #11182https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F11182&data=02|01|v-wimarc%40microsoft.com|14bfd344804a40013abf08d5e1c31ba8|72f988bf86f141af91ab2d7cd011db47|1|0|636663150452059813&sdata=QiUvH9pLEP0tHvs956XJ8WsU2GRc757FAKa5eQH4bAw%3D&reserved=0 to @v-wimarchttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fv-wimarc&data=02|01|v-wimarc%40microsoft.com|14bfd344804a40013abf08d5e1c31ba8|72f988bf86f141af91ab2d7cd011db47|1|0|636663150452059813&sdata=5PweFdRYJ4L21bKD7%2Ff8hhUilwiIEc8W2Fu65pQx56c%3D&reserved=0.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F11182%23event-1716583006&data=02|01|v-wimarc%40microsoft.com|14bfd344804a40013abf08d5e1c31ba8|72f988bf86f141af91ab2d7cd011db47|1|0|636663150452059813&sdata=VmP3%2FghJ%2FIpU%2FAd%2BzsEpQupOT7S4WuPYH6m6wqBoaxs%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAeVXQohOq8MCURDWeDH6RDJvZ642ddI_ks5uDN-jgaJpZM4VB7ML&data=02|01|v-wimarc%40microsoft.com|14bfd344804a40013abf08d5e1c31ba8|72f988bf86f141af91ab2d7cd011db47|1|0|636663150452059813&sdata=Hu6keSQpOV6yD5bPYb0qtokQL0f7F0ZBagGQf%2Be5LRk%3D&reserved=0.

Hi, Azure.cn is going to release a web page of Product available by region next Monday (July 9th). The page on staging server can be access here (http://atomtest.chinacloudsites.cn/zh-cn/home/features/products-by-region ).  It’s similar to this page in Azure.microsoft.com.  ACOM is maintenance these information in marketing portal,  I think there is no reason we keep maintenance on the article Azure service availability in China under Sovereign Docs. Can we remove it, and redirect user to Azure.cn "Products by Region" landing page? I can give you the URL now. It will be https://www.azure.cn/home/features/products-by-region (go live on July 9th) with both English and Chinese languages support.

For your information, there will be one day delay of publishing this page https://www.azure.cn/home/features/products-by-region.  Please expect it go live on Tuesday.  And let me know what do you think on my proposal.  Thanks.
Regards,
Josephine Qiu, ACN
From: Josephine Qiu
Sent: Friday, July 6, 2018 11:54 AM
To: Monica Rush<EMAIL_ADDRESS>Marc Wilson (Resources Online<EMAIL_ADDRESS>MicrosoftDocs/azure-docs<EMAIL_ADDRESS>MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: Assign<EMAIL_ADDRESS>Julia Kornich<EMAIL_ADDRESS>Subject: RE: [MicrosoftDocs/azure-docs] The table above is too old, 4 month back, and need to update. (#11182)
Hi Monica, glad to know PM for sovereign clouds has onboarded.
About the feedback on the article Azure service availability in Chinahttps://docs.microsoft.com/en-us/azure/china/china-get-started-service-availability#feedback, I am going to contact you about that.  Azure.cn is going to release a web page of Product available by region next Monday. The page on staging server can be access here http://atomtest.chinacloudsites.cn/zh-cn/home/features/products-by-region ).  It’s similar to this pagehttps://azure.microsoft.com/en-us/global-infrastructure/services/ in Azure.microsoft.com. So I think there is no reason we keep maintenance on the docs article Azure service availability in Chinahttps://docs.microsoft.com/en-us/azure/china/china-get-started-service-availability#feedback. Can we remove it, and redirect user who wants this information to Azure.cn portal landing page? I can give you the URL. It will be https://www.azure.cn/home/features/products-by-region (not available until next Monday)  with both English and Chinese languages support.
Regards,
Josephine Qiu, ACN
From: Monica Rush
Sent: Thursday, July 5, 2018 11:22 PM
To: Marc Wilson (Resources Online) <v-wimarc<EMAIL_ADDRESS>MicrosoftDocs/azure-docs<EMAIL_ADDRESS>MicrosoftDocs/azure-docs <azure-docs<EMAIL_ADDRESS>Josephine Qiu <yiqiu<EMAIL_ADDRESS>Cc: Assign <assign<EMAIL_ADDRESS>Julia Kornich <juliako<EMAIL_ADDRESS>Subject: RE: [MicrosoftDocs/azure-docs] The table above is too old, 4 month back, and need to update. (#11182)
Josephine, can you assign to the appropriate PM/writer?
A few more comments:

I have cc’ed Julia Kornich, who is the new PM for sovereign clouds (Julia, this is just FYI for now)
Josephine, I think that once you determine who the PM/writer is, the article should be reassigned from Marc to that writer
All articles should be assigned to another PM/writer, and Marc’s name should be removed. Josephine, would you be able to take care of that at this point?

Julia will be in touch soon to coordinate work going forward. But I am assuming that Josephine can address the above issues for now.
Please let me know if you have comments or questions re: my reply. Thanks to everyone -- Monica
From: Marc Wilson (Resources Online)
Sent: Thursday, July 5, 2018 7:53 AM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>MicrosoftDocs/azure-docs <azure-docs<EMAIL_ADDRESS>Monica Rush <monicar<EMAIL_ADDRESS>Josephine Qiu <yiqiu<EMAIL_ADDRESS>Cc: Assign <assign<EMAIL_ADDRESS>Subject: RE: [MicrosoftDocs/azure-docs] The table above is too old, 4 month back, and need to update. (#11182)
Monica and Josephine,
Can you provide some guidance for Micah on who this bug should be assigned to? It’s an update request for the Mooncake content and I’m not sure what the status is as far as who owns it at this point. Thanks - mw
From: Micah <notifications<EMAIL_ADDRESS>Sent: Wednesday, July 4, 2018 8:31 AM
To: MicrosoftDocs/azure-docs <azure-docs<EMAIL_ADDRESS>Cc: Marc Wilson (Resources Online) <v-wimarc<EMAIL_ADDRESS>Assign <assign<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] The table above is too old, 4 month back, and need to update. (#11182)
Assigned #11182https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F11182&data=02|01|v-wimarc%40microsoft.com|14bfd344804a40013abf08d5e1c31ba8|72f988bf86f141af91ab2d7cd011db47|1|0|636663150452059813&sdata=QiUvH9pLEP0tHvs956XJ8WsU2GRc757FAKa5eQH4bAw%3D&reserved=0 to @v-wimarchttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fv-wimarc&data=02|01|v-wimarc%40microsoft.com|14bfd344804a40013abf08d5e1c31ba8|72f988bf86f141af91ab2d7cd011db47|1|0|636663150452059813&sdata=5PweFdRYJ4L21bKD7%2Ff8hhUilwiIEc8W2Fu65pQx56c%3D&reserved=0.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F11182%23event-1716583006&data=02|01|v-wimarc%40microsoft.com|14bfd344804a40013abf08d5e1c31ba8|72f988bf86f141af91ab2d7cd011db47|1|0|636663150452059813&sdata=VmP3%2FghJ%2FIpU%2FAd%2BzsEpQupOT7S4WuPYH6m6wqBoaxs%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAeVXQohOq8MCURDWeDH6RDJvZ642ddI_ks5uDN-jgaJpZM4VB7ML&data=02|01|v-wimarc%40microsoft.com|14bfd344804a40013abf08d5e1c31ba8|72f988bf86f141af91ab2d7cd011db47|1|0|636663150452059813&sdata=Hu6keSQpOV6yD5bPYb0qtokQL0f7F0ZBagGQf%2Be5LRk%3D&reserved=0.

Hi all,  MC Azure products available by region page is online now! With this table, you can see all MC available services/service series/features in the 4 datacenters. It’s just a start, and ACN will work with Mooncake operation team to maintain it from now on.
Chinese version: https://www.azure.cn/zh-cn/home/features/products-by-region
English version:  https://www.azure.cn/en-us/home/features/products-by-region
As for the article in Azure service availability in Chinahttps://docs.microsoft.com/en-us/azure/china/china-get-started-service-availability#feedback, I suggest we stop the maintenance in Sovereign Cloud Docs, but redirect user to the marketing page above.  Thanks.
Regards,
Josephine Qiu, ACN
From: Josephine Qiu
Sent: Monday, July 9, 2018 5:45 PM
To: Monica Rush<EMAIL_ADDRESS>Marc Wilson (Resources Online<EMAIL_ADDRESS>'MicrosoftDocs/azure-docs'<EMAIL_ADDRESS>'MicrosoftDocs/azure-docs'<EMAIL_ADDRESS>Cc: 'Assign'<EMAIL_ADDRESS>Julia Kornich<EMAIL_ADDRESS>Zihong Chen<EMAIL_ADDRESS>Langjie Xi (Wicresoft<EMAIL_ADDRESS>Subject: RE: [MicrosoftDocs/azure-docs] The table above is too old, 4 month back, and need to update. (#11182)
For your information, there will be one day delay of publishing this page https://www.azure.cn/home/features/products-by-region.  Please expect it go live on Tuesday.  And let me know what do you think on my proposal.  Thanks.
Regards,
Josephine Qiu, ACN
From: Josephine Qiu
Sent: Friday, July 6, 2018 11:54 AM
To: Monica Rush <monicar<EMAIL_ADDRESS>Marc Wilson (Resources Online) <v-wimarc<EMAIL_ADDRESS>MicrosoftDocs/azure-docs<EMAIL_ADDRESS>MicrosoftDocs/azure-docs <azure-docs<EMAIL_ADDRESS>Cc: Assign <assign<EMAIL_ADDRESS>Julia Kornich <juliako<EMAIL_ADDRESS>Subject: RE: [MicrosoftDocs/azure-docs] The table above is too old, 4 month back, and need to update. (#11182)
Hi Monica, glad to know PM for sovereign clouds has onboarded.
About the feedback on the article Azure service availability in Chinahttps://docs.microsoft.com/en-us/azure/china/china-get-started-service-availability#feedback, I am going to contact you about that.  Azure.cn is going to release a web page of Product available by region next Monday. The page on staging server can be access here http://atomtest.chinacloudsites.cn/zh-cn/home/features/products-by-region ).  It’s similar to this pagehttps://azure.microsoft.com/en-us/global-infrastructure/services/ in Azure.microsoft.com. So I think there is no reason we keep maintenance on the docs article Azure service availability in Chinahttps://docs.microsoft.com/en-us/azure/china/china-get-started-service-availability#feedback. Can we remove it, and redirect user who wants this information to Azure.cn portal landing page? I can give you the URL. It will be https://www.azure.cn/home/features/products-by-region (not available until next Monday)  with both English and Chinese languages support.
Regards,
Josephine Qiu, ACN
From: Monica Rush
Sent: Thursday, July 5, 2018 11:22 PM
To: Marc Wilson (Resources Online) <v-wimarc<EMAIL_ADDRESS>MicrosoftDocs/azure-docs<EMAIL_ADDRESS>MicrosoftDocs/azure-docs <azure-docs<EMAIL_ADDRESS>Josephine Qiu <yiqiu<EMAIL_ADDRESS>Cc: Assign <assign<EMAIL_ADDRESS>Julia Kornich <juliako<EMAIL_ADDRESS>Subject: RE: [MicrosoftDocs/azure-docs] The table above is too old, 4 month back, and need to update. (#11182)
Josephine, can you assign to the appropriate PM/writer?
A few more comments:

I have cc’ed Julia Kornich, who is the new PM for sovereign clouds (Julia, this is just FYI for now)
Josephine, I think that once you determine who the PM/writer is, the article should be reassigned from Marc to that writer
All articles should be assigned to another PM/writer, and Marc’s name should be removed. Josephine, would you be able to take care of that at this point?

Julia will be in touch soon to coordinate work going forward. But I am assuming that Josephine can address the above issues for now.
Please let me know if you have comments or questions re: my reply. Thanks to everyone -- Monica
From: Marc Wilson (Resources Online)
Sent: Thursday, July 5, 2018 7:53 AM
To: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>MicrosoftDocs/azure-docs <azure-docs<EMAIL_ADDRESS>Monica Rush <monicar<EMAIL_ADDRESS>Josephine Qiu <yiqiu<EMAIL_ADDRESS>Cc: Assign <assign<EMAIL_ADDRESS>Subject: RE: [MicrosoftDocs/azure-docs] The table above is too old, 4 month back, and need to update. (#11182)
Monica and Josephine,
Can you provide some guidance for Micah on who this bug should be assigned to? It’s an update request for the Mooncake content and I’m not sure what the status is as far as who owns it at this point. Thanks - mw
From: Micah <notifications<EMAIL_ADDRESS>Sent: Wednesday, July 4, 2018 8:31 AM
To: MicrosoftDocs/azure-docs <azure-docs<EMAIL_ADDRESS>Cc: Marc Wilson (Resources Online) <v-wimarc<EMAIL_ADDRESS>Assign <assign<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/azure-docs] The table above is too old, 4 month back, and need to update. (#11182)
Assigned #11182https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F11182&data=02|01|v-wimarc%40microsoft.com|14bfd344804a40013abf08d5e1c31ba8|72f988bf86f141af91ab2d7cd011db47|1|0|636663150452059813&sdata=QiUvH9pLEP0tHvs956XJ8WsU2GRc757FAKa5eQH4bAw%3D&reserved=0 to @v-wimarchttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fv-wimarc&data=02|01|v-wimarc%40microsoft.com|14bfd344804a40013abf08d5e1c31ba8|72f988bf86f141af91ab2d7cd011db47|1|0|636663150452059813&sdata=5PweFdRYJ4L21bKD7%2Ff8hhUilwiIEc8W2Fu65pQx56c%3D&reserved=0.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F11182%23event-1716583006&data=02|01|v-wimarc%40microsoft.com|14bfd344804a40013abf08d5e1c31ba8|72f988bf86f141af91ab2d7cd011db47|1|0|636663150452059813&sdata=VmP3%2FghJ%2FIpU%2FAd%2BzsEpQupOT7S4WuPYH6m6wqBoaxs%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAeVXQohOq8MCURDWeDH6RDJvZ642ddI_ks5uDN-jgaJpZM4VB7ML&data=02|01|v-wimarc%40microsoft.com|14bfd344804a40013abf08d5e1c31ba8|72f988bf86f141af91ab2d7cd011db47|1|0|636663150452059813&sdata=Hu6keSQpOV6yD5bPYb0qtokQL0f7F0ZBagGQf%2Be5LRk%3D&reserved=0.

@johnneycao This article will be removed, and point to https://www.azure.cn/zh-cn/home/features/products-by-region instead.
Thanks for bringing it to our attention. Sorry for the added noise.
@v-wimarc the email formatting is making the github thread unreadable.  Please don't reply any further.
Thanks, Jason

Fixed by MicrosoftDocs/azure-docs-pr#47455
#please-close

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


Unable to install hakatime

Hello, I have tried to deploy hakatime using the docker compose file located in the README.MD but it stuck on Starting hakatime server ...
Here is my log:
root@docker2:~# docker compose -f ./docker-compose-deploy.yml up
[+] Running 3/3
 ✔ Volume "root_deploy_db_data"  Created                                                                                0.0s
 ✔ Container haka_db             Created                                                                                0.5s
 ✔ Container hakatime            Created                                                                                0.5s
Attaching to haka_db, hakatime
hakatime  | HAKA_DB_HOST: haka_db
hakatime  | HAKA_DB_PORT: 5432
hakatime  | HAKA_DB_USER: test
hakatime  | HAKA_DB_NAME: test
hakatime  | Waiting for the PostgreSQL service to become available ...
haka_db   | The files belonging to this database system will be owned by user "postgres".
haka_db   | This user must also own the server process.
haka_db   |
haka_db   | The database cluster will be initialized with locale "en_US.utf8".
haka_db   | The default database encoding has accordingly been set to "UTF8".
haka_db   | The default text search configuration will be set to "english".
haka_db   |
haka_db   | Data page checksums are disabled.
haka_db   |
haka_db   | fixing permissions on existing directory /var/lib/postgresql/data ... ok
haka_db   | creating subdirectories ... ok
haka_db   | selecting dynamic shared memory implementation ... posix
haka_db   | selecting default max_connections ... 100
haka_db   | selecting default shared_buffers ... 128MB
haka_db   | selecting default time zone ... UTC
haka_db   | creating configuration files ... ok
haka_db   | running bootstrap script ... ok
haka_db   | sh: locale: not found
haka_db   | 2024-02-07 17:33:33.847 UTC [30] WARNING:  no usable system locales were found
haka_db   | performing post-bootstrap initialization ... ok
haka_db   | syncing data to disk ... ok
haka_db   |
haka_db   |
haka_db   | Success. You can now start the database server using:
haka_db   |
haka_db   |     pg_ctl -D /var/lib/postgresql/data -l logfile start
haka_db   |
haka_db   | initdb: warning: enabling "trust" authentication for local connections
haka_db   | You can change this by editing pg_hba.conf or using the option -A, or
haka_db   | --auth-local and --auth-host, the next time you run initdb.
haka_db   | waiting for server to start....2024-02-07 17:33:36.423 UTC [36] LOG:  starting PostgreSQL 12.17 on x86_64-pc-linux-musl, compiled by gcc (Alpine 13.2.1_git20231014) 13.2.1 20231014, 64-bit
haka_db   | 2024-02-07 17:33:36.427 UTC [36] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
haka_db   | 2024-02-07 17:33:36.452 UTC [37] LOG:  database system was shut down at 2024-02-07 17:33:34 UTC
haka_db   | 2024-02-07 17:33:36.460 UTC [36] LOG:  database system is ready to accept connections
haka_db   |  done
haka_db   | server started
haka_db   | CREATE DATABASE
haka_db   |
haka_db   |
haka_db   | /usr/local/bin/docker-entrypoint.sh: ignoring /docker-entrypoint-initdb.d/*
haka_db   |
haka_db   | waiting for server to shut down....2024-02-07 17:33:36.866 UTC [36] LOG:  received fast shutdown request
haka_db   | 2024-02-07 17:33:36.871 UTC [36] LOG:  aborting any active transactions
haka_db   | 2024-02-07 17:33:36.880 UTC [36] LOG:  background worker "logical replication launcher" (PID 43) exited with exit code 1
haka_db   | 2024-02-07 17:33:36.880 UTC [38] LOG:  shutting down
haka_db   | 2024-02-07 17:33:36.920 UTC [36] LOG:  database system is shut down
haka_db   |  done
haka_db   | server stopped
haka_db   |
haka_db   | PostgreSQL init process complete; ready for start up.
haka_db   |
haka_db   | 2024-02-07 17:33:37.008 UTC [1] LOG:  starting PostgreSQL 12.17 on x86_64-pc-linux-musl, compiled by gcc (Alpine 13.2.1_git20231014) 13.2.1 20231014, 64-bit
haka_db   | 2024-02-07 17:33:37.008 UTC [1] LOG:  listening on IPv4 address "<IP_ADDRESS>", port 5432
haka_db   | 2024-02-07 17:33:37.009 UTC [1] LOG:  listening on IPv6 address "::", port 5432
haka_db   | 2024-02-07 17:33:37.016 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
haka_db   | 2024-02-07 17:33:37.061 UTC [51] LOG:  database system was shut down at 2024-02-07 17:33:36 UTC
haka_db   | 2024-02-07 17:33:37.076 UTC [1] LOG:  database system is ready to accept connections
hakatime  | Connected to PostgreSQL
haka_db   | 2024-02-07 17:33:37.215 UTC [59] ERROR:  relation "users" does not exist at character 22
haka_db   | 2024-02-07 17:33:37.215 UTC [59] STATEMENT:  select count(*) from users
hakatime  | ERROR:  relation "users" does not exist
hakatime  | LINE 1: select count(*) from users
hakatime  |                              ^
hakatime  | Database test does not exist. Initializing database ...
hakatime  | BEGIN
hakatime  | CREATE TABLE
hakatime  | CREATE TABLE
hakatime  | CREATE TABLE
hakatime  | CREATE TABLE
hakatime  | CREATE TABLE
hakatime  | CREATE INDEX
hakatime  | CREATE EXTENSION
hakatime  | CREATE TABLE
hakatime  | COMMIT
hakatime  | Database test initialized
hakatime  | Running migrations from files found in /app/migrations
hakatime  | Initializing schema
hakatime  | Migrations schema initialized
hakatime  | Executing:  00001-add-tags.sql
hakatime  | Adding '00001-add-tags.sql' to schema_migrations with checksum '"wDEDYHIMlMhgupK95xXXbQ=="'
hakatime  | Executed:   00001-add-tags.sql
hakatime  | Executing:  00002-add-token-name.sql
hakatime  | Adding '00002-add-token-name.sql' to schema_migrations with checksum '"CMlXJxnilQ25c0PbjnSxMw=="'
hakatime  | Executed:   00002-add-token-name.sql
hakatime  | Executing:  00003-rename-empty-project.sql
hakatime  | Adding '00003-rename-empty-project.sql' to schema_migrations with checksum '"BQGiYxpiw+J/hR+z3GmcEQ=="'
hakatime  | Executed:   00003-rename-empty-project.sql
hakatime  | Migrations applied successfully
hakatime  | Starting hakatime server ...

Did you try to access the web page to verify if it's working? That logline doesn't mean it's not accessible or stuck.

Yes I have try and nothing appen


graspers, finity

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.2
logical conflict every: 1000
sleep for: 2100s
close stale after: 24 hours
[pullrequest]
requests per hour: 120
deps=[f,g]

/trunk merge


Possibility to hide "Welcome" Page

Is your feature request related to a problem? Please describe.
I don't want to expose too much information about my TUS instance, e.g. the accurate version i am using and especially the metrics URL.  I want to keep metrics accessible behind an URL of my choice, but since the accurate path is displayed on the welcome page, there is no way to make a "hidden" url out of the box.
I could hide TUS behind a reverse proxy and prohibit GET requests on the / url, but that seems like a very big hammer for a very small nail.
Describe the solution you'd like
Introduce a flag e.g. --hide-welcome-page like the --expose-metrics flag. This would make it possibe to use an obscure URL to make it harder to find the metrics URL without completely disabling metrics.
Describe alternatives you've considered
No other solution.
Can you provide help with implementing this feature?
Sadly not.
Additional context
No context, but a huge thanks for this great piece of software!

Yes, I can see that this would be helpful. However, since this is a relatively low-priority task, I doubt we will work on this soon, unless someone can help.


to use reload command, check if message came from main server in config

resolved with Richardson-Media-House/Kirbi#142


⚠ Bofrost.de has degraded performance

In fb3e428, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1392 ms

Resolved: Bofrost.de performance has improved in 94757f7 after 50 minutes.


fix: Windows path issue in $saber.getPageLink

Summary

Fixes #460
What kind of change does this PR introduce? (check at least one)

[x] Bugfix
[ ] Feature
[ ] Code style update
[ ] Refactor
[ ] Docs
[ ] Build-related changes
[ ] Other, please describe:

If changing the UI/CSS related code, please provide the before/after screenshot:
Does this PR introduce a breaking change? (check one)

[ ] Yes
[x] No

If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:

[x] Briefly describing what this PR does in the title in Angular Commit Message Conventions, e.g. fix: rebuild when a page is added

To avoid wasting your time, it's best to open a feature request issue first and wait for approval before working on it.
Other information:

IssueHunt Summary

Referenced issues
This pull request has been submitted to:

#460: Windows path issue in $saber.getPageLink

IssueHunt has been backed by the following sponsors. Become a sponsor

I want it to eliminate the use of path 😄

I want it to eliminate the use of path to reduce bundle size 😄
a-ha! I see 😃


Raising version?

Upgrading StAPI created a situation where, while the mod's API itself was left completely stable (no annotation was renamed, and the entrypoint is also left unchanged), there exist now two different "GCAPI 1.1.6", one for StAPI < 2.0.0-alpha.1 and one of StAPI >= 2.0.0-alpha.1
While this means the new GCApi version shouldn't be a new major version as the API wasn't even changed (arguably, this is fundamentally a refactor, and dependant mods that don't make any reference to methods and classes renamed in StAPI 2.0.0-alpha.1 won't even notice the change), it could still create confusion.
My PR upgrading StAPI originally included a major version bump, but it got accidentally rolled back during a careless push of a modified gradle.properties. This is for the best as it was overkill.
It would make sense though to bump the version to 1.2.0, and publish a simple Compatibility Matrix in the README to clarify the situation.

Closing by myself, it was fixed by the latest commit.


Rust node can't bootstrap if starts earlier then OCaml peers

It seems that there is an issue with retry logic for getting best tip from peers. If all the nodes (an OCaml seed node, and OCaml and Rust nodes having it as an initial peer) start at the same time, the Rust node don't query best tip from the seed node at all, fails to receive it from another OCaml node (because it didn't get it yet), and never retries with that.
logs.tar.gz

Here is the p2p.peers piece of the state:
peers.json


Bumping to go 1.20.3 and golangci-lint changes

Bumping to go 1.20.3 for CVE fixes

/cherry-pick v0.36.x


Improve Documentation of and Remove Dead Code for the LwIP TUN/TAP Shim Interface

Codecov Report

Merging #112 into master will increase coverage by <.01%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master     #112      +/-   ##
==========================================
+ Coverage   68.39%   68.39%   +<.01%
==========================================
  Files         467      467
  Lines       82816    82821       +5
==========================================
+ Hits        56642    56648       +6
+ Misses      26174    26173       -1

Impacted Files
Coverage Δ

src/lwip/TapInterface.c
0% <0%> (ø)
:arrow_up:

src/tools/weave/CertUtils.cpp
42.61% <0%> (-0.43%)
:arrow_down:

src/lib/core/WeaveFabricState.cpp
79.89% <0%> (+0.17%)
:arrow_up:

src/test-apps/TestCASE.cpp
96.1% <0%> (+0.22%)
:arrow_up:

...les/data-management/Current/SubscriptionClient.cpp
54.6% <0%> (+0.29%)
:arrow_up:

src/lib/profiles/time/WeaveTimeServer.cpp
91.57% <0%> (+0.52%)
:arrow_up:

src/lib/profiles/time/WeaveTimeCoordinator.cpp
100% <0%> (+3.22%)
:arrow_up:

Continue to review full report at Codecov.

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


The CI step indicated in the readme doesn't work

Cargo doesn't allow passwords in custom registry URLs (https://github.com/rust-lang/cargo/pull/6242). Even though ssh doesn't allow passwords in its URIs, cargo still sees it as one (it's been the case since at least 1.40 which is the oldest version I tested).

Thanks for the report, an easy workaround could be using CARGO_NET_GIT_FETCH_WITH_CLI with git in your path pointing to a wrapper script calling sshpass

Actually, scratch all of that. We expect the password to be in the username so modifications would be needed for the above. Maybe .ssh/config setting the Username to gitlab-ci-token:$GITLAB-CI-TOKEN for Host *.

Got it to work with that:
- echo -e "Host \"gitlab.host\" exec \"test %p = 2222\"\n    User gitlab-ci-token:$CI_JOB_TOKEN\n    StrictHostKeyChecking no" > ~/.ssh/config
- ssh-keygen -t ed25519 -q -f "~/.ssh/id_ed25519" -N ""
- sed -i<EMAIL_ADDRESS>.cargo/config

It's a bit annoying because it requires a key that would be valid as authentication method but it works.

Note that this is not actually a solution if you need to publish a package depending on another package in a custom registry.
The changed URL will be saved by cargo into the package metadata and it'll completely break down the line as you'll have packages coming from<EMAIL_ADDRESS>and gitlab.host.

Second note, you don't need to do the sed dance if you don't precise git@ in the registry URL. Since gitlab-cargo-shim doesn't look at the username unless it's for CI, this should solve that last issue.


Add support for Azure via OpenaiChatModel

Builds on PR https://github.com/jackmpcollins/magentic/pull/64 from @kaaloo
I add api_type to the magentic settings so that it can be set globally and also on individual prompts. Also added a note to the README.
@kaaloo Could you test that this branch works for your use case please? You should be able to set env var MAGENTIC_OPENAI_API_TYPE="azure" or set this in code with
@prompt(
    "This is a test",
    model=OpenaiChatModel("gpt-4", api_type="azure")
)
def do_test() -> str:
    ...

From https://github.com/openai/openai-python/tree/9f828cb1ea7c22a6388fcd71b5de1a0dde3a9a9f#microsoft-azure-openai I see there's also an azure_endpoint parameter which it might also make sense to add.

Hi @jackmpcollins , I like the way you solved this and it works great but like you say it could maybe be improved.  There are a couple of environment variables I had to setup for this to work.   Being able to pass these values in the prompt parameters could be more readable.
os.environ["AZURE_OPENAI_API_KEY"] = "*****"
os.environ["AZURE_OPENAI_ENDPOINT"] = "*****"
# may change in the future
# https://learn.microsoft.com/en-us/azure/ai-services/openai/reference#rest-api-versioning
os.environ["OPENAI_API_VERSION"] = "2023-09-01-preview"

Thanks! I'll release this now so you are unblocked.
Re the other variables, do you need to change these per prompt? If not then I think it's fine to leave them set at the very top-level as env vars.

Thanks so much @jackmpcollins !  I updated to 0.11.1 and everything's working well.  👏🏼 💯


fix(ollama): correct Ollama baseURL

This PR fixes the Ollama baseURL to add the missing /api path, it will also try to lookup the host from $OLLAMA_HOST which is a standard variable for Ollama clients.

Isn't it automatic already?

Could you please open an issue on the Ollama provider repository?
Feel like this repo is not the right place to address the issue.
Link:
https://github.com/sgomez/ollama-ai-provider


Support platform indicator for push channel

Pushing to elisee/test-game:win32 fails while elisee/test-game works.

Targets are now parsed by the API, so the problem has been moved elsewhere!


python311Packages.meilisearch: 0.28.2 -> 0.28.4

Diff: https://github.com/meilisearch/meilisearch-python/compare/refs/tags/v0.28.2...v0.28.4
Changelog: https://github.com/meilisearch/meilisearch-python/releases/tag/v0.28.4
Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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
[ ] 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

[ ] Fits CONTRIBUTING.md.

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

4 packages built:

python310Packages.meilisearch
python310Packages.meilisearch.dist
python311Packages.meilisearch
python311Packages.meilisearch.dist


typo: notificationhubs/resource-manager/Microsoft.NotificationHubs

Aauthorization -> Authorization
Availibility -> Availability
availabile -> available
Pproperties -> Properties
APNS capitalization
MPNS capitalization
Regenrate -> Regenerate
notificationhub -> NotificationHub
reponse -> response

Automation for azure-sdk-for-js

Automation for azure-sdk-for-python

Automation for azure-sdk-for-ruby

Automation for azure-sdk-for-java


The Joyn tab should not be visible for services outside BE

There are a few merchants of CDR that were 'interested' in joyn.

It looks like that service has the 'joyn' module, which is why it shows up. Did we accidentally add that to all services?

can this be closed?

Probably manually added by sam


Remove outdated reference to oc being necessary

What is the purpose of this change? What does it change?
Simple doc change, see: $subject
Was the change discussed in an issue?
Fixes: #1044
How to test changes?
Nothing to test, only docs affected

:white_check_mark: odo build 600 completed and artifacts can be found here (for commit https://github.com/redhat-developer/odo/commit/3c6b1b1099 by @geoand)

I have restarted the last Travis job which seemed to be stuck...

Travis works now :)

@geoand Great :+1:


Show the whole history that can be visible when you scroll the mouse wheel up just 1 tick

The default chat frame has this feature. If I was away for a while, I just usually scroll up the chat very very slightly (1 tick as mentioned in the title), and the whole history that can fit in the chat frame, shows up.
This would be a nice option to have, even if it wouldn't be a feature by default.

Not sure I'm understanding this correctly, but Glass already does this. When you scroll up, all chat messages that fit within the window are shown.

Scrolling didn't work properly for me, so I couldn't tell that this was a feature. Sorry about this.


Benchmark different threshold values for PhenoDigm evidence

As suggested by @d0choa during one of the stand-ups, we can use the association benchmark script to evaluate how well different thresholds for PhenoDigm evidence perform. This would allow us to be less arbitrary in choosing the said theshold.

I believe @ireneisdoomed had some extra results on this

Duplicated from #1782


Dynamic buffer access

Similar to #81, this adds support for DynamicBuffer access.
What is the current behaviour?

Had to manually include DynamicBuffers and remember the attributes for the different use cases of read/write.

What is the new behaviour?

Wrapped structs that configure the DynamicBuffer for you.

NOTE:

I have not yet included support for the case where you want multiple threads to work on the same DynamicBuffer but different indicies. That will come later as its a more specialized case and I feel like it's going to share some work/functionality with the more general case of sharing the same NativeArray or NativeList etc.

What issues does this resolve?

None

What PRs does this depend on?

None

Does this introduce a breaking change?

[ ] Yes
[x] No

Tag Alongs

Some naming fixes and better error messaging.

I have not yet included support for the case where you want multiple threads to work on the same DynamicBuffer but different indicies. That will come later as its a more specialized case and I feel like it's going to share some work/functionality with the more general case of sharing the same NativeArray or NativeList etc.

Fair, it's probably just the same case because of DynamicBuffer.AsNativeArray(). Aside from any resize functionality.


Create a configuration option to only call the Initial Request on dashboard load?

Is it possible to configure the Data Manipulation panel to only call the Initial Request on dashboard load?  I have this panel on a dashboard that has other panels that require regular updates and I have an auto refresh interval set.  Right now the Initial Request gets called at every refresh.  The problem with this is that if the user is changing values on the Data Manipulation panel, they all get reset based on the Initial Request being called every refresh cycle.
If this is not already configurable, could you consider adding this as a configuration option? Sort of like the drop down when configuring a dashboard query variable.  Something like:
Initial Request Refresh: "On dashboard load"/"default"

I am not actually sure what the default should be called or how you would describe it.
Thanks
-Ray

You can probably fix this by using a global variable on dashboard. Create a new variable called "dload" and set the initial value to none, then on the code for loading of plugin check if the variable has value as "none", if yes, do the request and then change the variable to I don't know, whatever.
Next time the refresh hits, since the variable is not "none" anymore, the request will not be executed.
Thanks

@rantinray Thanks for the request.
You can use custom code for making initial requests and update elements to prevent rewriting of element values after dashboard refresh.
Example of custom code for initial request:
const getValues = async () => {
  const isFirstLoad = elements.every((element) => !element.value) // check if all values are empty;

  if (isFirstLoad) {
    const response = await fetch(); // get some data
    const json = await response.json();

   // update initial element values
   onChange(elements.map((element) => ({
     ...element,
     value: json[element.id],
   }))
  }
}

return getValues();

Please let us know if it works for you

@asimonok Thank you.
Documentation updated: https://volkovlabs.io/plugins/volkovlabs-form-panel/code/


Remove calls to deprecated PSP functions

As part of the changes for PSP trac [cfs_psp:7] and [cfs_psp:93] the following functions are proposed to be deprecated:
{{{
int32 CFE_PSP_PortRead8         (cpuaddr PortAddress, uint8 *ByteValue);
int32 CFE_PSP_PortWrite8        (cpuaddr PortAddress, uint8 ByteValue);
int32 CFE_PSP_PortRead16        (cpuaddr PortAddress, uint16 *uint16Value);
int32 CFE_PSP_PortWrite16       (cpuaddr PortAddress, uint16 uint16Value);
int32 CFE_PSP_PortRead32        (cpuaddr PortAddress, uint32 *uint32Value);
int32 CFE_PSP_PortWrite32       (cpuaddr PortAddress, uint32 uint32Value);
int32 CFE_PSP_MemRead8          (cpuaddr MemoryAddress, uint8 *ByteValue);
int32 CFE_PSP_MemWrite8         (cpuaddr MemoryAddress, uint8 ByteValue);
int32 CFE_PSP_MemRead16         (cpuaddr MemoryAddress, uint16 *uint16Value);
int32 CFE_PSP_MemWrite16        (cpuaddr MemoryAddress, uint16 uint16Value);
int32 CFE_PSP_MemRead32         (cpuaddr MemoryAddress, uint32 *uint32Value);
int32 CFE_PSP_MemWrite32        (cpuaddr MemoryAddress, uint32 uint32Value);
int32 CFE_PSP_EepromWrite8      (cpuaddr MemoryAddress, uint8 ByteValue);
int32 CFE_PSP_EepromWrite16     (cpuaddr MemoryAddress, uint16 uint16Value);
int32 CFE_PSP_EepromWrite32     (cpuaddr MemoryAddress, uint32 uint32Value);
int32 CFE_PSP_MemCpy            (void *dest, const void *src, uint32 n);
int32 CFE_PSP_MemSet            (void *dest, uint8 value, uint32 n);
}}}
For CFE_PSP_MemCpy/CFE_PSP_MemSet it is preferred to use the C library memcpy/memset call instead.  For the access functions, just dereference the pointer locally (as this is all they ever did).

Imported from trac issue 322.  Created by jphickey on 2019-08-20T11:05:49, last modified: 2019-08-29T13:01:35

Trac comment by jphickey on 2019-08-20 11:18:51:
Pushed commit [changeset:873b7dd] on branch trac-322-cleanup-deprecated for review.
The only functions actually called from CFE were CFE_PSP_MemRead8 (in the CRC calculation) and CFE_PSP_MemSet (in SB).  These refs were removed along with a doxygen comment.

Trac comment by jhageman on 2019-08-21 14:10:54:
CCB 8/21/2019 - changeset reviewed and approved for test

Trac comment by jhageman on 2019-08-22 15:55:11:
CCB - marked for delta code review.

Trac comment by jphickey on 2019-08-22 15:15:28:
Amendment required: Integration revealed a UT failure, because the Data buffer passed to CRC function was not initialized.  Resolved with a memset() call.
New commit: [changeset:1d4b669]

Trac comment by jphickey on 2019-08-22 16:06:59:
Merged into branch ic-ccb-20190821

Trac comment by jphickey on 2019-08-29 10:48:13:
Confirmed that ic-ccb-20190821 merge is acceptable for development merge

Trac comment by jhageman on 2019-08-29 13:01:35:
CCB 8/28/2019 - delta code review and approved for merge to dev

Trac comment by jphickey on 2019-08-29 10:53:33:
Merged to development branch


Sent Message Confirmation

After sending a canned message there is no confirmation that the message was sent. Adding one would enable the user to be confident the message was sent properly.

This would be great with the canned responses but also with the voice & keyboard replies. Thanks!

Sounds good! I'll add the feature to all responses.

The confirmation page was added see release 1.6.

I installed the update and it works, along with https://github.com/integraloftheday/Pebble-Imessager/issues/4 !  Thank you!  Note that I had to uninstall the previous version and reconfigure 1.6 as 1.5.1 was still present.


[Function App] Update in stacks API to include PowerShell on Linux support

as titled.
cc: @pragnagopa , @AnatoliB , @Francisco-Gamino , @gzuber

Adding Stack API PR link: https://github.com/pragnagopa/azure-functions-supported-runtime-stacks/pull/29.

route to service team


panic at membersAt func due to index out of range

panic: runtime error: index out of range [255] with length 255
goroutine 152195 [running]:
github.com/dusk-network/dusk-blockchain/pkg/core/consensus/committee.(*Handler).membersAt(0xc001131480, 0xd664ff, 0x0)
	/opt/gocode/src/github.com/dusk-network/dusk-blockchain/pkg/core/consensus/committee/handler.go:88 +0xdd
github.com/dusk-network/dusk-blockchain/pkg/core/consensus/committee.(*Handler).Committee(0xc001131480, 0x5d2, 0xff, 0x40, 0x0, 0x0, 0x0, 0x0)
	/opt/gocode/src/github.com/dusk-network/dusk-blockchain/pkg/core/consensus/committee/handler.go:52 +0x38
github.com/dusk-network/dusk-blockchain/pkg/core/consensus/committee.(*Handler).IsMember(0xc001131480, 0xc00003c480, 0x81, 0x81, 0x5d2, 0xff, 0x40, 0x20)
	/opt/gocode/src/github.com/dusk-network/dusk-blockchain/pkg/core/consensus/committee/handler.go:42 +0x4f
github.com/dusk-network/dusk-blockchain/pkg/core/consensus/committee.(*Handler).AmMember(...)
	/opt/gocode/src/github.com/dusk-network/dusk-blockchain/pkg/core/consensus/committee/handler.go:36
github.com/dusk-network/dusk-blockchain/pkg/core/consensus/reduction.(*Handler).AmMember(...)
	/opt/gocode/src/github.com/dusk-network/dusk-blockchain/pkg/core/consensus/reduction/handler.go:35
github.com/dusk-network/dusk-blockchain/pkg/core/consensus/reduction/secondstep.(*Reducer).CollectStepVotes(0xc000f0c870, 0x10554c0, 0xc00139aa20, 0x977811, 0xc0013281c0)
	/opt/gocode/src/github.com/dusk-network/dusk-blockchain/pkg/core/consensus/reduction/secondstep/reducer.go:190 +0x336
github.com/dusk-network/dusk-blockchain/pkg/core/consensus.(*SimpleListener).NotifyPayload(0xc000c3ce70, 0x10554c0, 0xc00139aa20, 0x10554c0, 0xc00139aa20)
	/opt/gocode/src/github.com/dusk-network/dusk-blockchain/pkg/core/consensus/component.go:105 +0x3d
github.com/dusk-network/dusk-blockchain/pkg/core/consensus.(*roundStore).Dispatch(0xc000ea2940, 0x10650e0, 0xc0012d2e60)
	/opt/gocode/src/github.com/dusk-network/dusk-blockchain/pkg/core/consensus/round.go:122 +0x2d8
github.com/dusk-network/dusk-blockchain/pkg/core/consensus.(*Coordinator).CollectEvent(0xc0002fc580, 0x10650e0, 0xc0012d2e60, 0xc000144250, 0x1)
	/opt/gocode/src/github.com/dusk-network/dusk-blockchain/pkg/core/consensus/round.go:356 +0x74c
github.com/dusk-network/dusk-blockchain/pkg/util/nativeutils/eventbus.(*CallbackListener).Notify(0xc000227940, 0x10650e0, 0xc0012d2e60, 0x1, 0x1)
	/opt/gocode/src/github.com/dusk-network/dusk-blockchain/pkg/util/nativeutils/eventbus/listener.go:32 +0x9d
github.com/dusk-network/dusk-blockchain/pkg/util/nativeutils/eventbus.(*multiListener).Forward(0xc0001ef6c0, 0x20, 0x10650e0, 0xc0012d2e60)
	/opt/gocode/src/github.com/dusk-network/dusk-blockchain/pkg/util/nativeutils/eventbus/listener.go:180 +0x13c
created by github.com/dusk-network/dusk-blockchain/pkg/util/nativeutils/eventbus.(*EventBus).Publish
	/opt/gocode/src/github.com/dusk-network/dusk-blockchain/pkg/util/nativeutils/eventbus/publisher.go:26 +0x244

Rather than fix this problem, we should make sure that when it panics, it provides the right information about what is going on

Closed via #631


add repeated sequence to repeats.fa

Hi,
I wanted to use your program to get E. coli spacers. It work well on some of my strains but for some of them there are missing spacers due to some mismatch in the last repeat sequence.
Is there a way to update the repeats.fa file in the db folder with my own list of repeated sequences ?
Have a nice day,
Fabien

Hi Fabien,
Yes you can. If you use conda you can find the db directory inside the conda environment. Then you simply add your repeats to the repeats.fa file (give them unique names, not overlapping with any of the other names). When you run cctyper with the conda environment it will then use the updated file.
However, the repeats.fa is only used if minced is not finding a CRISPR array near a cas operon. Therefore, it will most likely not make any difference for you


Refactor as a Platform

Refactors the Alarm.com Homebridge plugin to expose a platform instead of a single accessor, as proposed in #10. Currently, the platform only exposes a single security system accessory and behaves almost the same as before. However, this sets the stage for implementing accessories for other integrations supported by Alarm.com.
As far as behavior changes, this pull request removes some of the verbose logging for logic that is — at this point — pretty reliable and unnecessary. I've abstracted the WrapAPI request logic so that it can be used by all of the accessories (and not only the security system). This also helped me realize that a good future enhancement would be to reuse sessionUrl tokens whenever possible, which will improve responsiveness of commands.

I forgot to mention... since this changes the UUIDs associated with the former accessory, this is a breaking change in two ways:

~/.homebridge/config.json needs to be updated per README.md.
Any settings or scenes on the existing accessory will be lost and have to be reconfigured.

@yungsters Thanks for doing this. I, too, had considered reusing the sessionUrl. I'll add that to the list. I'm going to merge this in. I added you as a collaborator, if you're so inclined.


Check for tty before coloring

This accounts for redirecting (for example for log files). So the string only gets colored if the user is going to see it, otherwise we don't color to prevent cruft in log files.

closing old prs


Cannot push to PSGallery

Steps to reproduce
Publish-Module -Name xxxxx -NuGetApiKey xxxx -Verbose

Expected behavior
Work normally

Actual behavior
Publish-PSArtifactUtility : Failed to generate the compressed file for module 'Cannot index into a null array.'.
At C:\Program Files\WindowsPowerShell\Modules\PowerShellGet\2.2.3\PSModule.psm1:10946 char:17
+ ...             Publish-PSArtifactUtility @PublishPSArtifactUtility_Param ...
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [Write-Error], WriteErrorException
    + FullyQualifiedErrorId : FailedToCreateCompressedModule,Publish-PSArtifactUtility

Environment data

> $PSVersionTable
Name                           Value
----                           -----
PSVersion                      5.1.18362.628
PSEdition                      Desktop
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0...}
BuildVersion                   10.0.18362.628
CLRVersion                     4.0.30319.42000
WSManStackVersion              3.0
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>

> Get-Module PowerShellGet
ModuleType Version    Name                                ExportedCommands
---------- -------    ----                                ----------------
Script     2.2.3      PowerShellGet                       {Find-Command, Find-DscResource, Find-Module, Find-RoleCap...

I found the code which gives the exception

The error in PS 7.
My Windows 10 is 1903. Some 1909 can push successfully.

Thanks for pin-pointing the problem!  From your original post it seems like the nupkg is getting created properly but somehow parsing the full file name isn't working.  Could you let me know if the nupkg exists in the temporary folder that gets created (particularly when running in Windows PS since I see that the nupkg is definitely getting created there)?

@alerickson I think the NUGET package doesn't exit? My Windows user name is chinese, may it affect results?

@KevinZonda thank you!  That's unfortunate, from the logs it seemed like the .nupkg was getting created properly, but not pushed (possibly due to incorrect parsing), but I'll have to dig in a bit more to see why exactly the nupkg isn't getting created properly.
I have a few more questions for you:
Do you have the nuget executable installed?
What is your $env:ProgramData path?
Could you install the nuget exe from https://aka.ms/psget-nugetexe to "C:\Program Files\nuget"?

I'm seeing this behaviour as well (V 2.2.4). If needed, I can provide additional information about my system and environment. dotnet SDK is installed as well.
Using WindowsPowershell mitigates the problem (V 2.0.1)
ProcMon Traces and similar would be possible, as well as screen sharing via Teams or S4B

I'm seeing this behaviour as well (V 2.2.4). If needed, I can provide additional information about my system and environment. dotnet SDK is installed as well.
Using WindowsPowershell mitigates the problem (V 2.0.1)
ProcMon Traces and similar would be possible, as well as screen sharing via Teams or S4B

I install dotnet SDK too. What's ur Windows build? 1809, or...?

The latest installed dotnet SDK is 3.1.202
Windows Version is 1903

The latest installed dotnet SDK is 3.1.202
Windows Version is 1903

I want to upgrade my Windows. May it works.

Can you give any progress on this?
Or can we provide anything to allow you fixing the bug or providing us a workaround?

I just did some digging and I think I found the underlying problem:
Text-Parsing!
$stdOut -match "Successfully created package '(.*.nupkg)'" | Out-Null
$nupkgFullFile = $matches[1]

My machine speaks german. It'll probably report "Nuget-Packet erfolgreich erstellt" or something similar.


Create a mutex package for go-cgo and go-nocgo

Currently users can mistakenly install go-cgo and go-nocgo in the same environment. This is leads to clobbering and at the end of the day with only the nocgo compiler active.
We need a mutex-like/variant control package to ensure only one of the compilers is installed in a given environment.
cf: #38
cc: @stuarteberg, @pearu

This is was closed in conda-forge/staged-recipes#9471. Currently, the select package supports three flavors of go:

precompiled
cgo
nocgo


Isolated flag is not switched on in isolated service declarations

Description:
$title
listener Listener aListener = new ();

isolated service / on aListener {

}

Steps to reproduce:
Affected Versions:
OS, DB, other environment details and versions:
Related Issues (optional):

Suggested Labels (optional):

Suggested Assignees (optional):

@dulajdilshan, can you please elaborate on how this check is done?
The following prints true.
import ballerina/io;

listener Listener aListener = new ();

isolated service / on aListener {

}

class Listener {

    public function init() {
    }

    public function attach(service object {} s, string|string[]? name = ()) returns error? {
        io:println(s is isolated service object {});
    }

    public function detach(service object {} s) returns error? {
    }

    public function 'start() returns error? {
    }

    public function gracefulStop() returns error? {
    }

    public function immediateStop() returns error? {
    }
}

Checked on slbeta2 also, which was released before September 2021.

Closing this issue because it works as mentioned in https://github.com/ballerina-platform/ballerina-lang/issues/32661#issuecomment-1055461272


Find image in image?

Hello,
I want to make a simple AI that plays a game using the screenshots. The game is simple 2D game so it shouldn't be hard. Main thing to do is to be able to find image in the screenshots to locate interactive objects. What's a good getting started guide to do that?

The type of guide you wanted is somewhat vague. However, this guide should help assuming you want to use Python and have a webcam pointed at the screen.
http://community.dur.ac.uk/m.j.r.bordewich/rpi/BrickPiRobot.html
This guide shows how to program a robot to chase a ball using a webcam and Python. Presumably, the 2d game you specified will have a several ball like objects to track and will use math to compare the positions of the objects. It would really help if I had a better description of the game. I want to help if possible.

Sorry that comment has nothing to do with JavaScript. I didn't realize that it was in a repository because I had a link directly to this thread on a mobile device. However, how are you going to get screenshots with JavaScript?

I really would recommend you use Python instead of JavaScript because it is much simpler to use complex library's and has more tutorials. Unless if you have a reason not to.

My question was regarding the jsfeat library (which is in Javascript). I want to use javascript because I already obtain screenshot using javascript. I already have a simple AI that looks for pixel color and makes decision on that, but I wanted something smarter. I wanted to know whether jsfeat library can handle the task.

How did you get screenshots with JavaScript?

https://www.npmjs.com/package/adbkit

@Darker I've used opencv MatchTemplate for this - https://github.com/peterbraden/node-opencv/blob/13a1de4f9259b5e745021f3198a8339ac99edecd/src/Matrix.cc#L95


Created TokenStore protocol for storing Token type

Summary
Abstracted the logic for storing and retrieving a Token to a protocol, such that any object that conforms to it can be used to store and retrieve a Token type.
Why
By abstracting the implementation of the logic responsible to store/retrieve an object to a protocol, the user's of the library can provide his own [..]TokenStore that better fits his needs.
i.e.: this feature made possible to support iCloud Key Value Store very easily by gaining the opportunity to store a Token in the iCloud Key Value Store Container.
Note
As proof of concept I've implemented this protocol to support NSUserDefaults and NSUbiquitousKeyValueStore.

I love it !!! 😻
There are a few changes I would like to make but I'll come back tomorrow.
Thanks a lot @fabiomassimo !

Merged!
The two main changes are:

tokenStore is a public variable (set to NSUserDefaults.standardUserDefaults() by default). A provider can't be initialized with a tokenStore
I extended NSUserDefaults and NSUbiquitousKeyValueStore instead of the wrappers

let provider: Provider = .Instagram(clientID: "***", redirectURL: "foo://callback")
provider.tokenStore = NSUbiquitousKeyValueStore.defaultStore()

Thanks 👍

I see your point but I'm concerned to expose a public variable to the client.
By mistake the provider could have been initialised with one store and later on switched to another by causing miss of information.
My idea was that a Provider is initialised with a TokenStore that is immutable for the all lifetime of the Provider. A Provider is equipped with one and only TokenStore that the client can not mess with.
What do you think?
Thank you for your time.

extension NSUserDefaults: TokenStore  { ... }
extension NSUbiquitousKeyValueStore: TokenStore  { ... }

I went for an encapsulating struct (UserDefatulsTokenStore and UbiquitousTokenStore) because I didn't want to expose this feature directly to NSUserDefaults and NSUbiquitousKeyValueStore. I wanted to enclose it in a struct which belonged to the library instead of extending the Foundation struct.
In other words: making and extension makes getTokenForProvider and setToken available everywhere while I think it is better they are all exposed through an object that belongs to the library.
What do you think?

I see your point but I'm concerned to expose a public variable to the client.

By mistake the provider could have been initialised with one store and later on switched to another by causing miss of information.

I want to provide a nice, short, and straightforward API for the basic usage and, at the same time, to provide full flexibility when you want to do something a bit more advanced.
If the user changes the tokenStore, I assume he knows what he's doing and the fact that he could switch to another one later by mistake is not my concern ahah
The same could be said for the additionalParams properties btw.
Here is how we should use it:
let github: Provider = {
    let github: Provider = .GitHub(clientID: "***", clientSecret: "***", redirectURL: "***")
    github.tokenStore = someStore
    github.additionalAuthRequestParams["allow_signup"] = "false"
    return github
}()

// And then use only this one across all the app

went for an encapsulating struct (UserDefatulsTokenStore and UbiquitousTokenStore) because I didn't want to expose this feature directly to NSUserDefaults and NSUbiquitousKeyValueStore

I prefer to publicly extend NSUserDefaults and NSUbiquitousKeyValueStore with two methods rather than exposing two wrapper structs.
Also, you have a much clearer mental representation of this:
provider.tokenStore = NSUserDefault.standardUserDefaults()

rather than this:
provider.tokenStore = UserDefaultsTokenStore(innerStore: NSUserDefault.standardUserDefaults())


Test FDO disk re-encryption

We need to setup the service info api server configuration to also do device re-encryption during tests. We should then check that the device starts re-encrypting and possibly also that re-encryption works - for this we'd need TPMs in the vms we should for testing too.

cc @henrywang


Update Podspec to use RAC 4.2.1

Maybe a version bump and/or a release would be better than applying a
defined commit number.

I don't know why this is not linting on Travis, as it goes fine in local, I think creating a tag and modifying the target tag for the podspec should fix it.

A dirty fix for us CocoaPods lovers could be to make a 0.10.0a or similar that's tied to a specific commit. But I would prefer going through official releases :)

I'm really waiting for someone to make a new tag in the repo so I can change the podspec, no intention in merge this as it is right now because I understand how dirty my initial solution is ;)

I just added a 0.11.0-beta.1 tag but don't have time currently to cut an official release w/ notes.

Superseded by #141.


Enable support for OpenH264 in ffmpeg for Chrome builds

Enable the necessary bits to be able to build the Chrome configuration of
the internal ffmpeg library so that it also builds the ff_libopenh264_decoder
symbol, and add that to the list of codecs available in the "free" version.
Since the current implementation of libopenh264.so contains only the base profile,
we can't still enable it as the sole H264 decoder, so we keep the ff_h264_decoder
around for now for the non-free version of the ffmpeg library, which should be at
some point in the future replaced with the ff_libopenh264_decoder symbol there too.
Last, note that this patch makes the internal ffmpeg build link against libopenh264.so,
which will be present under /var/lib/codecs when the real implementation from Cisco is
installed (i.e. by default on non-free images, via a downloader on free ones), as well
as under /usr/lib/, as a "fake" version that is only there to satisfy the
linkage requirements from Chromium and the GStreamer plugin.
We initially wanted to make this dynamic (i.e. not linking) via dlopen() and dlsym(),
but unfortunately that's not possible since Chromium's sandboxed nature would prevent
that from happening, and also because GStreamer would blacklist the OpenH264 plugin
if it can't find the library it links against... so we ended up with this idea of
always shipping a dummy implementation in the OSTree that gets "overriden" by other
one if present under /var/lib/codecs automagically, via the dynamic linker.
https://phabricator.endlessm.com/T23345

bot, build this please

bot, test this please

@ltilve ok to merge this and #102?


[3.x] [HTML5] Implement WebGL fallback.

According to project settings and when WebGL2 is not available.
Fixes #26899

Thanks!


Design Sender Guide/Documentation

Problem statement
As a Sender, I would like some instructions to help me register for and use the CSV upload feature in ReportStream because I am either considering using the feature or am having problems using it.
Acceptance criteria

We need content and design to provide Senders with the following information

Value of the CSV upload feature
How to gain access to the CSV upload feature with a link to the intake form for senders

To do

[ ] Content: we need content
[ ] Design: we need layout for the content

@loripusey - this might be a dupe of this issue: https://app.zenhub.com/workspaces/prime-data-hub-5ff4833beb3e08001a4cacae/issues/cdcgov/prime-reportstream/1579


Change DAG syncing to transfer all files from the source to the target including file removal too

There are two behaviors of the DAG synchronization that prevents us transfer DAGs in the way how we expect:

those DAGs are not transferred from S3 bucket to EFS, that are having the same size but changed content
if a DAG is removed from the S3 bucket then it won't be removed from the related target EFS

It would be needed to resolve these cases by transferring all files from source to the target side, including also removing those files that were removed on the source side.

After some investigation, it turned out that maintaining the access time and modification time between S3 and EFS is not handled by the DataSync AWS service currently. Therefore, this option had to be disabled using the related datasync options. Besides this, the preserve deleted files option was also set to remove which lead to removing files also from the target side during the synchronization.


ReadOnly option should only be used by cluster client.

According to the doc https://redis.io/commands/readonly READONLY is a cluster command so the corresponding ReadOnly option should only be used by a cluster client.  However, in the current implementation, ReadOnly can be set for single-node client, which leads to a This instance has cluster support disabled error when baseClient.initConn is called.
It would be a easy fix to just rename ReadOnly to readOnly.

Sounds good. Do you want to send a PR?


Add board flash 0x9f SPI command to web config

This adds the 0x9f SPI identification command to the web config memory info.
The system stats now show the actual board flash size identified by the flash chip itself.

This crashes the board randomly :(
Before I close this as not an option, I am going to try to add the SPI flash cmd to the beginning of main() and see if we can consistently pull that at the beginning.
It's a neat feature but not worth crashing web config.

A MUCH better idea is to do this in the gp2040 setup() or before that somewhere we know will not crash
TO-DO:
add this code to setup()
uint8_t txbuf[FLASH_STORAGE_TOTAL_BYTES] = {0};
uint8_t rxbuf[FLASH_STORAGE_TOTAL_BYTES] = {0};
txbuf[0] = FLASH_STORAGE_CMD;
flash_do_cmd(txbuf, rxbuf, FLASH_STORAGE_TOTAL_BYTES);

then store the value into a permanent location so it only happens once!


SAM backend multi mask is true or false??

Hello CVAT community,
I have tried using CVAT with SAM, I encountered some problems there.

I am labeling agriculture data with crops and weeds. Problem is when i use SAM to label. it is labeling soil too sometimes. I have tried my SAM standalone with the same data, but i didn't encounter that issue when i switched to multi-mask=false. Can you let me know how to change that in CVAT?
Is there any way to undo with SAM ?

Hi @vijayreddysamula
As far as I remember, onnx decoder was prepared with --return-single-mask argument.

You can cancel any drawn point by clicking it again.

Hi bsekachev,
Thanks for the reply. But SAM in serverless is implemented through pytorch not via onnx. If possible can you share where is the exact location?

@vijayreddysamula
It is only encoder working serverless on pytorch. Decoder is running in the browser as onnx network.
multimask_output is decoder argument.

Decoder can be found here: https://github.com/opencv/cvat/tree/develop/cvat-ui/plugins/sam/assets
Code running decoder is here: https://github.com/opencv/cvat/blob/develop/cvat-ui/plugins/sam/src/ts/index.tsx
But --return-single-mask is onnx compilation argument, it is not available in runtime for onnx. Please, refer to SAM repository for details.

@bsekachev
Thank you for the information.


Do not build docker container for docs and example changes

We could be more selective with container builds and skip them for docs and example changes.
Benefits:

faster builds
less noise in container registry

CI runs are under 5 minutes which IMO is acceptable.

faster builds

General build/test/lint steps are around ~3 minutes. Container builds are 3 to 5 minutes. We only gain anything if we disable CI all together for those paths.

less noise in container registry

Images built by PR triggers are not pushed to the registry anyway.
The problem with running CI selectively, is that we also have to disable required checks, because they apply to PRs universally.
From this perspective, waiting 5 minutes for each PR to become green is not a high price to pay IMO.
(You can always ignore those if absolutely necessary and merge PRs bypassing checks.)

Okay, makes sense. Thanks for highlighting the tradeoffs. Closing it.


lazy: add assertions against common problems

checks that the provided name (vim.lazy.plugins.<name>) is same as package.pname

if a custom load function is given this check is bypassed because they probably know what they're doing

allow null package for more advanced uses (like auto-loading nvim's optional plugins)

Sanity Checking

[ ] I have updated the changelog as per my changes.
[x] I have tested, and self-reviewed my code.
Style and consistency

[x] I ran Alejandra to format my code (nix fmt).
[x] My code conforms to the editorconfig configuration of the project.
[x] My changes are consistent with the rest of the codebase.

If new changes are particularly complex:

[x] My code includes comments in particularly complex areas
[ ] I have added a section in the manual.
[ ] (For breaking changes) I have included a migration guide.

Package(s) built:

[x] .#nix (default package)
[ ] .#maximal
[ ] .#docs-html

Tested on platform(s)

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

Add a :+1: reaction to pull requests you find important.

I'm assuming this was not meant to be based on main?


Can u increase hit area of thumb ?

First sorry for my english, i used your library for my project, i really like it, but one small thing, it's too difficult for hit the thumb, my thumb size is 12dp.

I'm sorry to tell you not to support it for this version. It will be improved in the  next version. You can pay attention to the ToDoList to get the latest progress!

thanks, now i'm waiting for the next version :laughing:  your library very helpful :+1:  1 :star:

Thank you for waiting，it support now, you can see the Guide


fix(Forms): add ability to disable auto-focus and auto-scroll on Form submission error

FX-2356
SPB-2864
Description

If there multiple form on page and we submit them, we have to manually control auto-focus, since, Picasso is doing it wrong.
Sometimes you don't need an auto-focus for error fields or auto-sroll to error fields.

How to test
Submit form with an error (try switching off internet connection), see no scroll or auto-focus.
Screenshots
N/A
Review

[x] Read CONTRIBUTING.md and Component API principles
[x] Annotate all props in component with documentation
[x] Create examples for component
[x] Ensure that deployed demo has expected results and good examples
[x] Ensure that tests pass by running yarn test
[x] Ensure that visuals tests pass by running yarn test:visual. If not - check the documentation how to fix visual tests
[x] Ensure the changed/created components have not caused accessibility issues. How to use accessibility plugin in storybook.

PR commands

List of available commands:

@toptal-bot run all - Run whole pipeline
@toptal-bot run build - Check build
@toptal-bot run visual - Run visual tests
@toptal-bot run deploy:documentation - Deploy documentation
@toptal-bot run package:alpha-release - Release alpha version

PR Review Guidelines

When to approve? ✅
You are OK with merging this PR and

You have no extra requests.
You have optional requests.

Add nit:  to your comment. (ex. nit: I'd rename this variable from makeCircle to getCircle)

When to request changes? ❌
You are not OK with merging this PR because

Something is broken after the changes.
Acceptance criteria is not reached.
Code is dirty.

When to comment (neither ✅ nor ❌)
You want your comments to be addressed before merging this PR in cases like:

There are leftovers like unnecessary logs, comments, etc.
You have an opinionated comment regarding the code that requires a discussion.
You have questions.

How to handle the comments?

An owner of a comment is the only one who can resolve it.
An owner of a comment must resolve it when it's addressed.
A PR owner must reply with ✅ when a comment is addressed.

I think this is really cool feature, and probably it will be commonly used. Do you think we should maybe provide an example in the storybook for this? For example Form in Modal or something.

I can do small inline edits, as it's being used on the Staff portal

WDYT?

@TomasSlama @OleksandrNechai comments addressed, example has been added

✅

Oh, btw, why is this a fix? Sounds like a new feature to me

Oh, btw, why is this a fix? Sounds like a new feature to me

It might be a future for the Picasso itself, but it's required to fix an issue within Staff portal.
Tell me if I need to alter it.

rejecting due to missing automated tests.
I'll cover, Form is not covered at all, though

@OleksandrNechai ✅


Add source for Floyd County, GA

Skipping the city/state/zipcode attributes from the source since they are referencing the owner mailing address, not necessarily the property address.

Closes #2619

rerun this please


[Feature][FLINK SQL] Flink sql version history

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
Situation: Every developer can push code online, but this may cause some issues. I can't find the correct historical version of the code. Therefore, I would like a feature to record the Flink SQL version upon publishing, creating a new version record each time.
Use case
No response
Related issues
No response
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

该功能早已实现，在发布时触发历史版本

该功能早已实现，在发布时触发历史版本

找到了，感谢！


Changing bacticks to (double) quotes

Hi,
Are there any plans to support converting bacticks to quotes when user deletes a variable? I noticed in the gif (see below) from vscode plugin that it has the option to go both ways. Would be great to have both.

Very nice and simple plugin btw, very useful.

Yeah, I'd like to implement this feature, but I need to think more about how to implement it to avoid problems like these: meganrogge/template-string-converter#43

Wasn't aware of those issues. I think there should still be a branch that has it implemented as simple as possible, and have people test it out. Most probably it will not have some of those issues vscode plugin has, but also some other issues might arise.

Awesome, thanks!

@axelvc I tried using the feature but cant manage to make it work. Can you give me a simple explanation or add it to the README? Appreciate a lot your effort 💪🏼

Can you give me a simple explanation or add it to the README?

You need to enable the option in the setup function. That should be enough
require('template-string').setup {
  remove_template_string = true,
}

I made it work by deleting the character with x under normal mode. Is it the way its supposed to be working?

The feature should work in Normal and Insert mode, but there are some cases where the plugin doesn't remove the backticks. You can see them here: https://github.com/axelvc/template-string.nvim/pull/4#issue-1342876268
If you've found a new issue, feel free to report it by opening an issue.


TFLiteGPUDelegate : FirstNLargestPartitions : It would not be very good solution

Issue type
Performance
Have you reproduced the bug with TensorFlow Nightly?
No
Source
source
TensorFlow version
tf 2.4.1
Custom code
Yes
OS platform and distribution
Linux Ubuntu 18.04
Mobile device
Jetson-Xavier nx
Python version
3.6.9
Bazel version
3.1.0
GCC/compiler version
7.5.0
CUDA/cuDNN version
x
GPU model and memory
No response
Current behavior?
Let's suppose that the input tflite model is accelerated using GPUs. If there are incompatible layers for GPU backend (called Fallback layer in tflite) in the middle of the input model, "partition_helper class" divides the input model into delegatable & non-delegatable partition using graph_info class. Then, Apply the FirstNLargestPartitions functions to select the part to be delegated. In FirstNLargestPartitions logic, partitions with many layers are chosen first.  Here, the variable N can be set directly by the user, and the default is 1. In this tflite's gpu delegation policy, there are two major problems, I think.
First, It may not be appropriate to preferentially select a partition with many layers containing it. In most cases, such partitions will have the highest computational amount, but there may be partitions with a small number of layers but a very large amount of computation. For example, a partition with two convolutional layers may have more computational power than a partition with 10 simple computational layers, such as add mul. In such cases, FirstNLargest logic may not see the benefits of acceleration well.
Second, It is inconvenient to have the user set the N value, which is a variable for how many partitions to select and delegate. The user must tune and test one by one to see when the N value can most accelerate the input model. Since there is data exchange overhead between CPU and GPU, in most cases the inference time is fastest when the N value is 1, but depending on the structure of the model, there may be cases where it is not.
As a result, I think the existing delegation policy has room for more efficient change by improving the aforementioned problems. However, it seems that the most recent version of the tflite also uses the policy as it is.
Currently, I conducted an inference performance test with yolov4-tiny by delegating all possible partitions to all combinations. As a result, the more computational partitions were delegated, the better the inference performance.
However, the above trend was not always correct because the larger the N value, the greater the CPU GPU data exchange overhead.
Given this overall tendency, it would be better to choose partitions with a large amount of computation rather than to select partitions with a large number of layers contained, in same  "N" value condition.
In addition, the N value, which is the variable of how many partitions to select and delegate, may vary depending on the performance of the target hardware. I have not yet developed a logic that prevents users from tuning these N values and automatically selects and delegates partitions internally. It seems difficult to find the most appropriate N value by analyzing the performance of the target hardware without going through tasks such as the profiling process.
On the other hand, the method of obtaining an approximate amount of computation for delegatable partitions and delegating large partitions preferentially will be very simple and effective compared to the previous method.
I wonder why tflite still uses FirstNLargestPartitions logic and whether the aforementioned logic is appropriate from an overall perspective.
Standalone code to reproduce the issue
if(strcmp(GetOpName(reg), "CONV_2D") == 0){
          double mac = tensor->dims->data[1] * tensor->dims->data[2] * tensor->dims->data[3] * i_tensor->dims->data[3] * filter * filter;
          flops = 2*mac/1000000;
          tot += flops;
          printf("\033[0;31mFLOPs : %.1f\033[0m\n", flops);
        }
Above code shows roughly calculate amount of computation per layers.
If the contents mentioned in the above current behavior are appropriate, a new delegation policy can be developed based on the above code.

A program to analyze the inference results by delegating delegatable partitions to all possible combinations was conducted at the link below.
[tflite APP code] https://github.com/easyhardhoon/FBF-TF-hoon/tree/hoon/APP_DOT
[tflite source code] https://github.com/easyhardhoon/FBF-TF

Relevant log output
testing yolov4-tiny.tflite
there are seven delegatable partitions by partition helper class.
below log is the result of delegation test in jetson-xavier nx, using my custom tflite application & tflite source.
below log shows that the default gpu delegation policy in tflite is not appropriate.

=== Fallback node number info === :
8 20 32 55 57 60 63 67 69 70 73 75 76 81 86 91 95 97 98 103 105 108 111 117 122 127 132 134 135 138 140 141 144 146 147
=== Delegated_partitions info === :
[0] : 0 1 2 3 4 5 6 7
[1] : 9 10 11 12 13 14 15 16 17 18 19
[2] : 21 22 23 24 25 26 27 28 29 30 31
[3] : 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 102
[4] : 56 59 62 66 72 78 79 80 83 84 85 88 89 90 94 104 107 110 114 115 116 119 120 121 124 125 126 131 137 143
[5] : 58 61 64 65 68 74 82 87 92 93 96 106 109 112 113 118 123 128 129 130 133 139 145
[6] : 71 77 99 100 101 136 142 148 149 150 151
=== Fallback reason info === :
ERROR: Following operations are not supported by GPU delegate:
ADD: tensor type error
MUL: tensor type error
SPLIT: Operation is not supported.
SPLIT_V: Operation is not supported.

N = 1
[0 ]case's latency is 669ms
[1 ]case's latency is 677ms
[2 ]case's latency is 645ms
[3 ]case's latency is 402.00ms  -> Best case
[4 ]case's latency is 632ms   ---> chosen at default delegation.
[5 ]case's latency is 630ms
[6 ]case's latency is 618ms
[END]...Choose_1's average latency is 610.43ms
N = 2
[0 1 ]case's latency is 393ms
[0 2 ]case's latency is 486ms
[0 3 ]case's latency is 293ms
[0 4 ]case's latency is 534ms
[0 5 ]case's latency is 511ms
[0 6 ]case's latency is 510ms
[1 2 ]case's latency is 408ms
[1 3 ]case's latency is 289.00ms
[1 4 ]case's latency is 519ms
[1 5 ]case's latency is 520ms
[1 6 ]case's latency is 519ms
[2 3 ]case's latency is 296ms --> best case
[2 4 ]case's latency is 536ms
[2 5 ]case's latency is 550ms
[2 6 ]case's latency is 534ms
[3 4 ]case's latency is 403ms
[3 5 ]case's latency is 404ms
[3 6 ]case's latency is 408ms
[4 5 ]case's latency is 638ms  --> chosen at default delegation.
[4 6 ]case's latency is 628ms
[5 6 ]case's latency is 635ms
[END]...Choose_2's average latency is 476.86ms
N = 3
[0 1 2 ]case's latency is 280ms
[0 1 3 ]case's latency is 171.00ms
[0 1 4 ]case's latency is 389ms
[0 1 5 ]case's latency is 385ms
[0 1 6 ]case's latency is 391ms
[0 2 3 ]case's latency is 216ms
[0 2 4 ]case's latency is 470ms
[0 2 5 ]case's latency is 481ms
[0 2 6 ]case's latency is 454ms
[0 3 4 ]case's latency is 285ms
[0 3 5 ]case's latency is 287ms
[0 3 6 ]case's latency is 277ms
[0 4 5 ]case's latency is 526ms
[0 4 6 ]case's latency is 546ms
[0 5 6 ]case's latency is 517ms
[1 2 3 ]case's latency is 187ms
[1 2 4 ]case's latency is 407ms
[1 2 5 ]case's latency is 414ms
[1 2 6 ]case's latency is 408ms
[1 3 4 ]case's latency is 292ms
[1 3 5 ]case's latency is 293ms
[1 3 6 ]case's latency is 292ms
[1 4 5 ]case's latency is 529ms
[1 4 6 ]case's latency is 522ms
[1 5 6 ]case's latency is 524ms
[2 3 4 ]case's latency is 298ms
[2 3 5 ]case's latency is 301ms
[2 3 6 ]case's latency is 306ms
[2 4 5 ]case's latency is 535ms
[2 4 6 ]case's latency is 547ms
[2 5 6 ]case's latency is 549ms
[3 4 5 ]case's latency is 406ms
[3 4 6 ]case's latency is 402ms
[3 5 6 ]case's latency is 408ms
[4 5 6 ]case's latency is 640ms
[END]...Choose_3's average latency is 398.14ms
N = 4
[0 1 2 3 ]case's latency is 65.00ms
[0 1 2 4 ]case's latency is 287ms
[0 1 2 5 ]case's latency is 281ms
[0 1 2 6 ]case's latency is 277ms
[0 1 3 4 ]case's latency is 168ms
[0 1 3 5 ]case's latency is 169ms
[0 1 3 6 ]case's latency is 168ms
[0 1 4 5 ]case's latency is 390ms
[0 1 4 6 ]case's latency is 387ms
[0 1 5 6 ]case's latency is 389ms
[0 2 3 4 ]case's latency is 216ms
[0 2 3 5 ]case's latency is 232ms
[0 2 3 6 ]case's latency is 230ms
[0 2 4 5 ]case's latency is 456ms
[0 2 4 6 ]case's latency is 436ms
[0 2 5 6 ]case's latency is 480ms
[0 3 4 5 ]case's latency is 283ms
[0 3 4 6 ]case's latency is 277ms
[0 3 5 6 ]case's latency is 281ms
[0 4 5 6 ]case's latency is 534ms
[1 2 3 4 ]case's latency is 189ms
[1 2 3 5 ]case's latency is 188ms
[1 2 3 6 ]case's latency is 187ms
[1 2 4 5 ]case's latency is 410ms
[1 2 4 6 ]case's latency is 410ms
[1 2 5 6 ]case's latency is 405ms
[1 3 4 5 ]case's latency is 300ms
[1 3 4 6 ]case's latency is 292ms
[1 3 5 6 ]case's latency is 312ms
[1 4 5 6 ]case's latency is 525ms
[2 3 4 5 ]case's latency is 301ms
[2 3 4 6 ]case's latency is 313ms
[2 3 5 6 ]case's latency is 298ms
[2 4 5 6 ]case's latency is 543ms
[3 4 5 6 ]case's latency is 411ms
[END]...Choose_4's average latency is 316.86ms
N = 5
[0 1 2 3 4 ]case's latency is 66ms
[0 1 2 3 5 ]case's latency is 67ms
[0 1 2 3 6 ]case's latency is 64.00ms
[0 1 2 4 5 ]case's latency is 299ms
[0 1 2 4 6 ]case's latency is 285ms
[0 1 2 5 6 ]case's latency is 277ms
[0 1 3 4 5 ]case's latency is 178ms
[0 1 3 4 6 ]case's latency is 175ms
[0 1 3 5 6 ]case's latency is 177ms
[0 1 4 5 6 ]case's latency is 389ms
[0 2 3 4 5 ]case's latency is 193ms
[0 2 3 4 6 ]case's latency is 202ms
[0 2 3 5 6 ]case's latency is 177ms
[0 2 4 5 6 ]case's latency is 462ms
[0 3 4 5 6 ]case's latency is 286ms
[1 2 3 4 5 ]case's latency is 189ms
[1 2 3 4 6 ]case's latency is 190ms
[1 2 3 5 6 ]case's latency is 188ms
[1 2 4 5 6 ]case's latency is 412ms
[1 3 4 5 6 ]case's latency is 299ms
[2 3 4 5 6 ]case's latency is 332ms
[END]...Choose_5's average latency is 233.67ms
N = 6
[0 1 2 3 4 5 ]case's latency is 69ms
[0 1 2 3 4 6 ]case's latency is 67.00ms
[0 1 2 3 5 6 ]case's latency is 68ms
[0 1 2 4 5 6 ]case's latency is 292ms
[0 1 3 4 5 6 ]case's latency is 174ms
[0 2 3 4 5 6 ]case's latency is 225ms
[1 2 3 4 5 6 ]case's latency is 193ms
[END]...Choose_6's average latency is 155.43ms
N = 7
[0 1 2 3 4 5 6 ]case's latency is 70.00ms
[END]...Choose_7's average latency is 70.00ms
Minimum CAES's value : 64.00ms
Minimum CASE's N : 5
Minimum CASE's th : 2
Minimum CASE's combination : [0 1 2 3 6 ]

This issue originally reported by @easyhardhoon has been moved to this dedicated repository for LiteRT to enhance issue tracking and prioritization. To ensure continuity, we have created this new issue on your behalf.
We appreciate your understanding and look forward to your continued involvement.

Hello,
I hope everything is going well with the LiteRT migration.
I previously raised this issue on the TensorFlow Lite GitHub and discussed it with developers @grantjensen @pkgoogle @sawantkumar. I also submitted it to a conference held in Korea.
Cons_of_FirstNLargest.pdf is the poster presented at the time, illustrating inefficiencies in current GPU delegation policy for input models with GPU-incompatible layers (called fallback layers).
As shown in the attached PDF, it is generally desirable to delegate as many computationally intensive partitions as possible to the GPU. However, the performance improvement is not always proportional due to the overhead incurred during this process. Additionally, since this overhead can vary by model and hardware, it is difficult to track using a standardized code, which is likely why developers have created a naive policy.
Of course, this issue is irrelevant if the input model does not have such fallback layers. However, in real-world scenarios, such fallback layers are likely to exist, and the current naive GPU delegation policy (called FirstNLargest) may not achieve optimal user responsiveness, suggesting that improvements are necessary.
Therefore, I propose two solutions.

[ ] A profiling tool

This would perform delegation for all possible combinations in models with fallback layers to find the optimal setup. It has a clear advantage in that it considers all possible combinations, including those that cannot be selected under FirstNLargest, to find the optimal solution. Although profiling introduces additional time overhead, it is a simple method that guarantees optimal responsiveness.

[ ] An advanced GPU delegation policy based on computation

As shown in the attached PDF, FirstNLargest that prioritizes partitions with more layers is inefficient, whereas prioritizing partitions with more computation (called FLOPs) is generally more effective. I'm researching and developing formulas to calculate FLOPs_ for model layers. Once the formula to calculate FLOPs for model layers is implemented, the current GPU delegation policy can be simply replaced with an FLOPs-based priority policy instead of the FirstNLargest .
Although, as mentioned earlier, FLOPs-based priority policy is not always effective, it will undoubtedly lead to higher responsiveness compared to FirstNLargest .
I would appreciate your feedback on these two proposed approaches.
Thank you. @gaikwadrahul8


Comment.body rendered as Markdown, even for plain strings

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.62.0-dev
OS Version: web

Steps to Reproduce:

Using the comments API from an extension, create a CommentThread with a Comment whose body is a plain string that incidentally contains Markdown syntax.
The comment is always rendered with body interpreted as Markdown, resulting in unexpected formatting.

This is relevant in situations where the comments fed into VS Code come from a code review system that either 1) does not support Markdown, meaning all comments are written under the assumption that they are rendered verbatim, or 2) gives the user a choice between writing plain-text comments or Markdown comments, meaning some comments are known to be written with the expectation to have Markdown formatting applied and some comments are known to be written with the expectation of being shown verbatim.
The "always-on" Markdown formatting is unexpected, because Comment.body is of type string | MarkdownString, which leads the user of the API to assume that plain strings will be rendered verbatim.
The current situation is cumbersome, because explicitly creating a MarkdownString from a plain string to trigger Markdown formatting is easy—just make a new object—while escaping all accidental Markdown syntax in a plain string known to not deliberately contain Markdown takes work and can be error-prone.
Expected behaviour:
The situation in 2) above means Markdown vs plain text treatment should not be a single switch on a given CommentController but should instead be configurable for each Comment. Since Comment.body already distinguishes string and MarkdownString on the type level, the more intuitive behaviour would be to require MarkdownString to trigger Markdown formatting—which is of course a breaking change for extensions relying on always-on Markdown at the moment.

The forced conversion to a MarkdownString seems to happen here: https://github.com/microsoft/vscode/blob/adb8450420fee8b22d04c2f808dd4e2caad62b0f/src/vs/workbench/api/common/extHostComments.ts#L639.

This is a bug as it's inconsistent with how string | MarkdownString works everywhere else. I've pushed a fix. I hope no one was relying on this behavior...

Thank you for the speedy fix! 🙏🏻

Verified with
    const ctrl = vscode.comments.createCommentController('idid', 'Hello')

    ctrl.createCommentThread(vscode.Uri.file('/Users/jrieken/Code/_samples/devfest/foo/test.js'),
        new vscode.Range(3, 1, 4, 0),
        [{
            author: { name: 'me' },
            body: 'No _markdown_ **here**',
            mode: vscode.CommentMode.Preview
        }, {
            author: { name: 'me' },
            body: new vscode.MarkdownString('No _markdown_ **here**'),
            mode: vscode.CommentMode.Preview
        }]
    )


lib.d.ts is out of date

Looks like the lib.d.ts in tsserver is out-of-date.  There are some updates like:
getContext(contextId: "2d"): CanvasRenderingContext2D;
getContext(contextId: "experimental-webgl"): WebGLRenderingContext;
Can we pull a fresh lib.d.ts?

Will be updated with the 1.5 release branch soon

Fixed in #247