Are CDS Virtual entities Read-only or Create, Update, Delete

In the past CDS Virtual entities have been documented as read-only.
Do they now support Create, Update, Delete?
Is this this statement on the page accurate? Virtual entities support create, updates and delete of data in the external system.

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

ID: 93f90ab1-ccb0-faab-e37a-d2d6d4f73ac9
Version Independent ID: 41811cb6-a06e-65ef-2873-5e893d097de9
Content: Get started with virtual entities (Common Data Service) - Power Apps
Content Source: powerapps-docs/developer/common-data-service/virtual-entities/get-started-ve.md
Service: powerapps
GitHub Login: @Sunil-Garg
Microsoft Alias: pehecke

@MSIH Yes, virtual entities support create, retrieve, update, and delete operations in the external system. The documentation is correct.

@MSIH Yes, virtual entities support create, retrieve, update, and delete operations in the external system. The documentation is correct.

@phecke - Is there is any sample code on how this can be done, or is this restricted to only first party apps?

@phecke - Is there is any sample code on how this can be done, or is this restricted to only first party apps?

If it is true that full CRUD is now available to us - it is probably the best feature ever to have been released without any buzz whatsoever!
But as @rajyraman asks - where can we find any more details and perhaps even samples?
Thanks!

If it is true that full CRUD is now available to us - it is probably the best feature ever to have been released without any buzz whatsoever!
But as @rajyraman asks - where can we find any more details and perhaps even samples?
Thanks!

Hi Jonas—yes, this has been a bit hush hush 😊
Looping<EMAIL_ADDRESS>who is helping fix a few things we found as gaps during this preview phase and is also working on doc updates. We will circle back with all of you once we have the updates done.
Thanks.
From: Jonas Rapp<EMAIL_ADDRESS>Sent: Thursday, January 21, 2021 11:18 AM
To: MicrosoftDocs/powerapps-docs<EMAIL_ADDRESS>Cc: Sunil Garg<EMAIL_ADDRESS>Assign<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/powerapps-docs] Are CDS Virtual entities Read-only or Create, Update, Delete (#1880)
If it is true that full CRUD is now available to us - it is probably the best feature ever to have been released without any buzz whatsoever!
But as @rajyramanhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Frajyraman&data=04|01|sunilg%40microsoft.com|4fb40ec539264a01a9fa08d8be414cfe|72f988bf86f141af91ab2d7cd011db47|1|0|637468534964121962|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=HwOP3zaQVZl6k1sUn6iUrvSAI6iLLipgf93UbwBAw38%3D&reserved=0 asks - where can we find any more details and perhaps even samples?
Thanks!
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fpowerapps-docs%2Fissues%2F1880%23issuecomment-764876451&data=04|01|sunilg%40microsoft.com|4fb40ec539264a01a9fa08d8be414cfe|72f988bf86f141af91ab2d7cd011db47|1|0|637468534964131956|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=X19Fpe1TmFne%2BVhJX%2BdX8aODDA2SyPi7i5xxawLhZbU%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAHNKDW3XM7QCSKAGFUPPOILS3B4XNANCNFSM4TIZJ3CA&data=04|01|sunilg%40microsoft.com|4fb40ec539264a01a9fa08d8be414cfe|72f988bf86f141af91ab2d7cd011db47|1|0|637468534964131956|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=nB4Td5H7pWSwNKgSbTDMLu4sEmrpX60GEVLgOYwWUk8%3D&reserved=0.

Hi Jonas—yes, this has been a bit hush hush 😊
Looping<EMAIL_ADDRESS>who is helping fix a few things we found as gaps during this preview phase and is also working on doc updates. We will circle back with all of you once we have the updates done.
Thanks.
From: Jonas Rapp<EMAIL_ADDRESS>Sent: Thursday, January 21, 2021 11:18 AM
To: MicrosoftDocs/powerapps-docs<EMAIL_ADDRESS>Cc: Sunil Garg<EMAIL_ADDRESS>Assign<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/powerapps-docs] Are CDS Virtual entities Read-only or Create, Update, Delete (#1880)
If it is true that full CRUD is now available to us - it is probably the best feature ever to have been released without any buzz whatsoever!
But as @rajyramanhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Frajyraman&data=04|01|sunilg%40microsoft.com|4fb40ec539264a01a9fa08d8be414cfe|72f988bf86f141af91ab2d7cd011db47|1|0|637468534964121962|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=HwOP3zaQVZl6k1sUn6iUrvSAI6iLLipgf93UbwBAw38%3D&reserved=0 asks - where can we find any more details and perhaps even samples?
Thanks!
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fpowerapps-docs%2Fissues%2F1880%23issuecomment-764876451&data=04|01|sunilg%40microsoft.com|4fb40ec539264a01a9fa08d8be414cfe|72f988bf86f141af91ab2d7cd011db47|1|0|637468534964131956|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=X19Fpe1TmFne%2BVhJX%2BdX8aODDA2SyPi7i5xxawLhZbU%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAHNKDW3XM7QCSKAGFUPPOILS3B4XNANCNFSM4TIZJ3CA&data=04|01|sunilg%40microsoft.com|4fb40ec539264a01a9fa08d8be414cfe|72f988bf86f141af91ab2d7cd011db47|1|0|637468534964131956|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=nB4Td5H7pWSwNKgSbTDMLu4sEmrpX60GEVLgOYwWUk8%3D&reserved=0.

Hi – As Sunil indicated, I am working through tooling changes to enable full CRUD operation on VE. A quick follow up - is your enquire regarding OData provider or Custom provider?
Thanks,
-Srinath
From: Sunil Garg<EMAIL_ADDRESS>Sent: Thursday, January 21, 2021 11:27 AM
To: MicrosoftDocs/powerapps-docs<EMAIL_ADDRESS>MicrosoftDocs/powerapps-docs<EMAIL_ADDRESS>Srinath Kannan<EMAIL_ADDRESS>Cc: Assign<EMAIL_ADDRESS>Subject: RE: [MicrosoftDocs/powerapps-docs] Are CDS Virtual entities Read-only or Create, Update, Delete (#1880)
Hi Jonas—yes, this has been a bit hush hush 😊
Looping<EMAIL_ADDRESS>who is helping fix a few things we found as gaps during this preview phase and is also working on doc updates. We will circle back with all of you once we have the updates done.
Thanks.
From: Jonas Rapp <notifications<EMAIL_ADDRESS>Sent: Thursday, January 21, 2021 11:18 AM
To: MicrosoftDocs/powerapps-docs <powerapps-docs<EMAIL_ADDRESS>Cc: Sunil Garg <sunilg<EMAIL_ADDRESS>Assign <assign<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/powerapps-docs] Are CDS Virtual entities Read-only or Create, Update, Delete (#1880)
If it is true that full CRUD is now available to us - it is probably the best feature ever to have been released without any buzz whatsoever!
But as @rajyramanhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Frajyraman&data=04|01|Srinath.Kannan%40microsoft.com|9941c1fffbdf421d285308d8be428fbb|72f988bf86f141af91ab2d7cd011db47|1|0|637468540370731742|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=MalAjyQGw4d%2Fjr1SX9%2BmFAsWjry8FI35uq%2BVbOc3z5A%3D&reserved=0 asks - where can we find any more details and perhaps even samples?
Thanks!
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fpowerapps-docs%2Fissues%2F1880%23issuecomment-764876451&data=04|01|Srinath.Kannan%40microsoft.com|9941c1fffbdf421d285308d8be428fbb|72f988bf86f141af91ab2d7cd011db47|1|0|637468540370741735|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=oPFqinPEXJo7w%2BAJ9xUcGFpNUwpgKOgKdU%2BESdkYleU%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAHNKDW3XM7QCSKAGFUPPOILS3B4XNANCNFSM4TIZJ3CA&data=04|01|Srinath.Kannan%40microsoft.com|9941c1fffbdf421d285308d8be428fbb|72f988bf86f141af91ab2d7cd011db47|1|0|637468540370741735|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=eBikYYeusPzZzgCqczFF3D9yhVRhqAU7ruPNZ8k3e70%3D&reserved=0.

Hi – As Sunil indicated, I am working through tooling changes to enable full CRUD operation on VE. A quick follow up - is your enquire regarding OData provider or Custom provider?
Thanks,
-Srinath
From: Sunil Garg<EMAIL_ADDRESS>Sent: Thursday, January 21, 2021 11:27 AM
To: MicrosoftDocs/powerapps-docs<EMAIL_ADDRESS>MicrosoftDocs/powerapps-docs<EMAIL_ADDRESS>Srinath Kannan<EMAIL_ADDRESS>Cc: Assign<EMAIL_ADDRESS>Subject: RE: [MicrosoftDocs/powerapps-docs] Are CDS Virtual entities Read-only or Create, Update, Delete (#1880)
Hi Jonas—yes, this has been a bit hush hush 😊
Looping<EMAIL_ADDRESS>who is helping fix a few things we found as gaps during this preview phase and is also working on doc updates. We will circle back with all of you once we have the updates done.
Thanks.
From: Jonas Rapp <notifications<EMAIL_ADDRESS>Sent: Thursday, January 21, 2021 11:18 AM
To: MicrosoftDocs/powerapps-docs <powerapps-docs<EMAIL_ADDRESS>Cc: Sunil Garg <sunilg<EMAIL_ADDRESS>Assign <assign<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/powerapps-docs] Are CDS Virtual entities Read-only or Create, Update, Delete (#1880)
If it is true that full CRUD is now available to us - it is probably the best feature ever to have been released without any buzz whatsoever!
But as @rajyramanhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Frajyraman&data=04|01|Srinath.Kannan%40microsoft.com|9941c1fffbdf421d285308d8be428fbb|72f988bf86f141af91ab2d7cd011db47|1|0|637468540370731742|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=MalAjyQGw4d%2Fjr1SX9%2BmFAsWjry8FI35uq%2BVbOc3z5A%3D&reserved=0 asks - where can we find any more details and perhaps even samples?
Thanks!
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fpowerapps-docs%2Fissues%2F1880%23issuecomment-764876451&data=04|01|Srinath.Kannan%40microsoft.com|9941c1fffbdf421d285308d8be428fbb|72f988bf86f141af91ab2d7cd011db47|1|0|637468540370741735|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=oPFqinPEXJo7w%2BAJ9xUcGFpNUwpgKOgKdU%2BESdkYleU%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAHNKDW3XM7QCSKAGFUPPOILS3B4XNANCNFSM4TIZJ3CA&data=04|01|Srinath.Kannan%40microsoft.com|9941c1fffbdf421d285308d8be428fbb|72f988bf86f141af91ab2d7cd011db47|1|0|637468540370741735|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=eBikYYeusPzZzgCqczFF3D9yhVRhqAU7ruPNZ8k3e70%3D&reserved=0.

@sndray - I am interested in both. Is there a private preview for this?

@sndray - I am interested in both. Is there a private preview for this?

Regarding provider - any! 😁
Basically mostly curious to see where we are regarding this area, so we know what kind of tech we can consider for our customers.

Regarding provider - any! 😁
Basically mostly curious to see where we are regarding this area, so we know what kind of tech we can consider for our customers.

😊
We will plan for a session as well with all of you to demo and engage in future roadmap discussions to get your inputs.
Thanks again.
From: Jonas Rapp<EMAIL_ADDRESS>Sent: Thursday, January 21, 2021 11:37 AM
To: MicrosoftDocs/powerapps-docs<EMAIL_ADDRESS>Cc: Sunil Garg<EMAIL_ADDRESS>Assign<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/powerapps-docs] Are CDS Virtual entities Read-only or Create, Update, Delete (#1880)
Regarding provider - any! 😁
Basically mostly curious to see where we are regarding this area, so we know what kind of tech we can consider for our customers.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fpowerapps-docs%2Fissues%2F1880%23issuecomment-764887928&data=04|01|sunilg%40microsoft.com|723926139be946526aed08d8be43ee5d|72f988bf86f141af91ab2d7cd011db47|1|0|637468546256951906|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=pS1ab2RMf1zSk8TotFLejd7h2LHwvf%2FYUjUuTs2jo7I%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAHNKDWYRRJGXFFBYJLBDCZTS3B66BANCNFSM4TIZJ3CA&data=04|01|sunilg%40microsoft.com|723926139be946526aed08d8be43ee5d|72f988bf86f141af91ab2d7cd011db47|1|0|637468546256951906|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=njKcA0KGr4XiCNwGBro%2Bot7mUtIr1tnnzwGuxFU7W38%3D&reserved=0.

😊
We will plan for a session as well with all of you to demo and engage in future roadmap discussions to get your inputs.
Thanks again.
From: Jonas Rapp<EMAIL_ADDRESS>Sent: Thursday, January 21, 2021 11:37 AM
To: MicrosoftDocs/powerapps-docs<EMAIL_ADDRESS>Cc: Sunil Garg<EMAIL_ADDRESS>Assign<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/powerapps-docs] Are CDS Virtual entities Read-only or Create, Update, Delete (#1880)
Regarding provider - any! 😁
Basically mostly curious to see where we are regarding this area, so we know what kind of tech we can consider for our customers.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fpowerapps-docs%2Fissues%2F1880%23issuecomment-764887928&data=04|01|sunilg%40microsoft.com|723926139be946526aed08d8be43ee5d|72f988bf86f141af91ab2d7cd011db47|1|0|637468546256951906|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=pS1ab2RMf1zSk8TotFLejd7h2LHwvf%2FYUjUuTs2jo7I%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAHNKDWYRRJGXFFBYJLBDCZTS3B66BANCNFSM4TIZJ3CA&data=04|01|sunilg%40microsoft.com|723926139be946526aed08d8be43ee5d|72f988bf86f141af91ab2d7cd011db47|1|0|637468546256951906|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=njKcA0KGr4XiCNwGBro%2Bot7mUtIr1tnnzwGuxFU7W38%3D&reserved=0.

@sndray , I am interested in both and will love to see a demo. Can you arrange as we are looking to leverage it for an implementation.

@sndray , I am interested in both and will love to see a demo. Can you arrange as we are looking to leverage it for an implementation.

Will do, thanks.
From: Kunal Tripathy<EMAIL_ADDRESS>Sent: Thursday, January 21, 2021 11:43 AM
To: MicrosoftDocs/powerapps-docs<EMAIL_ADDRESS>Cc: Sunil Garg<EMAIL_ADDRESS>Assign<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/powerapps-docs] Are CDS Virtual entities Read-only or Create, Update, Delete (#1880)
@sndrayhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fsndray&data=04|01|sunilg%40microsoft.com|b0ca6b08d9d749542e8908d8be44b52c|72f988bf86f141af91ab2d7cd011db47|1|0|637468549592200763|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=ZbbuKZG3h2FPwoNz431o%2FpXih0R1GSItHDjiKssJYZY%3D&reserved=0 , I am interested in both and will love to see a demo. Can you arrange as we are looking to leverage it for an implementation.

You are receiving this because you were assigned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fpowerapps-docs%2Fissues%2F1880%23issuecomment-764890993&data=04|01|sunilg%40microsoft.com|b0ca6b08d9d749542e8908d8be44b52c|72f988bf86f141af91ab2d7cd011db47|1|0|637468549592210763|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=I0w7YyfZD9Fvok40h6zzd2%2FPON04aYCui1H9IHJK06c%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAHNKDW56FQYITM67BA6I2Y3S3B7S3ANCNFSM4TIZJ3CA&data=04|01|sunilg%40microsoft.com|b0ca6b08d9d749542e8908d8be44b52c|72f988bf86f141af91ab2d7cd011db47|1|0|637468549592210763|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=DHSt1%2FSfXVcOcNi84fLDe7uJkpYwJ08bF7iaRysrmyI%3D&reserved=0.

Will do, thanks.
From: Kunal Tripathy<EMAIL_ADDRESS>Sent: Thursday, January 21, 2021 11:43 AM
To: MicrosoftDocs/powerapps-docs<EMAIL_ADDRESS>Cc: Sunil Garg<EMAIL_ADDRESS>Assign<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/powerapps-docs] Are CDS Virtual entities Read-only or Create, Update, Delete (#1880)
@sndrayhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fsndray&data=04|01|sunilg%40microsoft.com|b0ca6b08d9d749542e8908d8be44b52c|72f988bf86f141af91ab2d7cd011db47|1|0|637468549592200763|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=ZbbuKZG3h2FPwoNz431o%2FpXih0R1GSItHDjiKssJYZY%3D&reserved=0 , I am interested in both and will love to see a demo. Can you arrange as we are looking to leverage it for an implementation.

You are receiving this because you were assigned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fpowerapps-docs%2Fissues%2F1880%23issuecomment-764890993&data=04|01|sunilg%40microsoft.com|b0ca6b08d9d749542e8908d8be44b52c|72f988bf86f141af91ab2d7cd011db47|1|0|637468549592210763|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=I0w7YyfZD9Fvok40h6zzd2%2FPON04aYCui1H9IHJK06c%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAHNKDW56FQYITM67BA6I2Y3S3B7S3ANCNFSM4TIZJ3CA&data=04|01|sunilg%40microsoft.com|b0ca6b08d9d749542e8908d8be44b52c|72f988bf86f141af91ab2d7cd011db47|1|0|637468549592210763|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=DHSt1%2FSfXVcOcNi84fLDe7uJkpYwJ08bF7iaRysrmyI%3D&reserved=0.


feat: introduce java.time variables and methods

This PR introduces java.time alternatives to existing org.threeten.bp.* methods, as well as switching internal variables (if any) to java.time
The main constraint is to keep the changes backwards compatible, so for each existing threeten method "method1(org.threeten.bp.Duration)" we will add an alternative with a Duration (or Timestamp when applicable) suffix: "method1Duration(java.time.Duration)".
For most cases, the implementation will be held in the java.time method and the old threeten method will just delegate the call to it. However, for the case of abstract classes, the implementation will be kept in the threeten method to avoid breaking changes (i.e. users that already overloaded the method in their user code).

@diegomarquezp Can we make sure following in all the files?
import java.time.Duration in all the files and use org.threeten.bp.Duration in obsolete methods. This avoids lot of code changes which is unnecessary. This also provides the standard that java.time.Duration should be used.

@diegomarquezp Can we make sure following in all the files?
import java.time.Duration in all the files(whereever is required) and use org.threeten.bp.Duration directly in obsolete methods. This avoids lot of code changes which is unnecessary. This also provides the standard that java.time.Duration should be used.

@sakthivelmanii Thanks for the review! Before switching to import java.time.Duration I'd like to double check if our rationale for not importing java.time.* seems sound to you: this is mainly to make it clear to the reader that there are two Duration/Instant classes coexisting in the same file and attention should be paid. We deliberately added these changes just to make this differentiation as explicit as possible. We've been doing it this way in other repos (e.g. https://github.com/googleapis/java-pubsub/pull/2271#discussion_r1852395166) (doesn't mean it should be done as in other repos).
Promoting java.time as the standard also makes sense, and it's ultimately the Spanner team's call, but wanted to make sure our approach doesn't come up as a mistake. I'm happy to move forward either way.


Java 14.3: Static Methods in Interfaces

Description
Add audio, documentation, and video regarding the Static Methods in Interfaces.
Location of File to be added
The files should be added inside the Static Methods in Interfaces folder which is inside the Interfaces folder present in the Java main folder. The documentation file can be in the .md/.py/.ipynb format. Audio should be in .mp3 format and to be submitted through a Google drive link. Video can be in any format and should be submitted through a Google Drive link.
Note:

You are required to comment with \assign CONTENT_TYPE, so that other content types can be created at the same time.
Failing to comment in the above manner will lead to the removal of assignment from the issue even if the bot assigns.
You are required to do a PR within 7 days otherwise you will be unassigned and others will be assigned.
Issues will be assigned on a first come first serve basis.

Domain
Java_Domain
Type of Contribution
Audio, Video, Documentation
Code of Conduct

[x]  I follow Contributing Guidelines & Code of conduct of this project.

/assign Documentation

I only have 1 issue that to about to be merged i don't know why is it saying i have three issues. Kindly check it @nandini7637

Even if you have one issue left to be merged, you can't take another. @Harsh-Chaudhary7

/assign documentation

/assign documentation


Issue--How to train this Img2mol model

Hi, OBrink:
When I was testing this model, I met one problem:

I used train model but get wrong predictions.
Do you have any advices to get high accuracy to test these pictures, we want to input these pictures from patents and get right smiles ?
In my personal opinion, it is because there is no such sample when the model is trained, so can I use this Img2mol model that has been trained?

Hi @whkaikai, please have a look @OBrink's detailed answer to your issue in DECIMER. I would simply say that these types of pseudo-molecules are not part of the training set of Img2Mol and could not be expected to be represented by SMILES strings anyhow. I don't think you will have better success with the pre-trained Img2Mol than with DECIMER, but of course, feel free to try.

Thank you very much, it helps a lot.


Add cache mechanism to node

Hi @kandy just curious how does cache help, can you give a usecase?  Wondering because probably won't see the same image twice or am I mistaken

I use Tagger in img2img workflows and I often  modified parameters at end of workflow, so I don't want that tags is recalculated for the same image and workflow start from start

I think this is a valuable PR as currently often tags are re-calculated for the same images (not always, haven't been able to figure why).
I have worked on this node yesterday and figured some other things:

moving the new parameter "cache" to property "optional" of the node's parameters will help to not break legacy workflows not having the new parameter in their JSON, yet
I would recommend to only calculate the hash if cache is True.
what about image batches? Does it work for them as well like it is currently implemented?


Update NPM Package

I just came across polished and would like to use it together with styled components in my current project. It seems like the NPM package hasn't been updated since November 2016 though. Are there any plans for a release anytime soon?

Yep, we're hard at work towards the official release. Should be out within a few weeks!


Try to fix import statements in etcd.go again. Update etcdv3 client.

This seems to fix a panic where duplicate enum is attempted to be
registered with protobuf:
goroutine 1 [running]:
github.com/golang/protobuf/proto.RegisterEnum(...)
        /home/gabrielius/go/pkg/mod/github.com/golang/protobuf@v1.3.3/proto/properties.go:458
github.com/coreos/etcd/auth/authpb.init.0()
        /home/gabrielius/go/pkg/mod/github.com/coreos/etcd@v3.3.13+incompatible/auth/authpb/auth.pb.go:103 +0x1b7

If etcd client is imported twice under different names (go.etcd.io/etcd
and github.com/coreos/etcd).

Issues blocking the 3.5.0 release for easy reference: https://github.com/etcd-io/etcd/milestone/37


Tolerate literal globs (GH-5942 backport to 3.0.x)

If your build environment uses literal globbing characters in its file paths, Cython 3.0 might fail, because find_versioned_file in Utils.py was slapping a * in the path and expecting it to properly glob. This fails in certain large build environments that use, for example, brackets in system paths. Escape paths from sys.path and other sources before looking for different versions of collateral files. This is a backport that works with Python 2.7.
Addresses GitHub issue #5942; see pull request for master.

Closing and reopening to rerun the tests

Thanks


Emails became optional when building; closes #41

Includes very early version of Dockerfile which is wrong;


Example code has use of insecure parameters

Hey,
the README shows the use of 1024 bits RSA keys:
var keyOptions = KeyOptions()..rsaBits = 1024;

1024 is very weak and should be avoided. Most authorities recommend use of at least 2048, better 3072, see https://www.keylength.com/en/

thanks @vanitasvitae I just updated readme


revert "configureNpipeTransport: use winio.DialPipeContext()"

This reverts https://github.com/docker/go-connections/pull/70, as it's possibly causing the failures as seen on https://github.com/moby/moby/pull/41084

Only reverting https://github.com/docker/go-connections/pull/70 isn't enough; tests still fail;
=== FAIL: github.com/docker/docker/integration/build  (0.00s)
[2021-07-26T14:49:21.575Z] failed to get info from daemon: Error response from daemon: client version 1.42 is too new. Maximum supported API version is 1.41
[2021-07-26T14:49:21.575Z] exit status 1


SC-2084 : Post Publish - migration to flink

… PROCESSID is present

@adityagoenka94 - requested changes. Please complete the ASAP.


Understanding hasPrevPage & hasNextPage

Hi!
I've started looking into this library and I'm impressed so far - nice work! Super cool and easy to use with Kysely.
I'm looking into replacing my own custom built cursor-based pagination with this. But I have a question regarding hasPrevPage.
In the following test you have, shouldn't hasPrevPage be true? Since you're basically requesting page 2 of this table?
Essentially I want to know: How should I let the client know that they can go back by sending the startCursor as before?
Or what does undefined mean for these values?
Test for reference:
https://github.com/charlie-hadden/kysely-paginate/blob/ed37a87ad9c940596fc44e6b590d6d9ba6289b8d/test/cursor.test.ts#L102
Thanks again!

Hi there,
The reason I return undefined in that case is mainly a performance one. It is quite easy to check if there's a next page by over-fetching by one result, and discarding it from the returned result set. It is a bit trickier to tell if there are any results before the cursor provided. It might be a nice addition to add an option to support that.
When I use this library myself I'll typically show a previous button in my UI if hasPreviousPage is true, or if an after cursor is provided. This strictly speaking isn't correct as the cursor could point to a non-existent record that would come before the first record in the results, which is why the library returns undefined, but is good enough for most practical use cases. Obviously similar logic applies to the hasNextPage value when paginating backwards with after.
Hopefully that explains it for you but let me know if not.

Hi,
Thanks for the response!

When I use this library myself I'll typically show a previous button in my UI if hasPreviousPage is true, or if an after cursor is provided.

I see, that's quite nifty.
In my own implementation (that I unfortunately made before we started using kysely) I basically have the tie-breaker clause set to fetch the cursor element OR greater (>=) when paginating forward. With a +2 limit you can then figure out if there is a previous page as well.
But I like your approach since it's quite simple.

With that said, it could be cool to have an option where the library handles everything for you without needing to have this client-side or extra server-side logic. I might look into the code a bit too see if it's an easy change

Hey,
I looked into this a bit but I just went with you suggestion instead since it started to get quite messy to get this into the lib.
I'll close this now. I got what I needed, thank you! :)


Fix plutus-metatheory-site nix build script.

The command nix build .#plutus-metatheory-site should convert all the Literate Agda into HTML. There is a script in nix/plutus-metatheory-site.nix that partly works but I have a few problems:

It caches the Agda phase, which sounds good but it doesn't appear to re-run when I edit one or two of the Agda files. This might not be an issue for most people who don't want to re-run Agda every time they rebuild everything, but in my case I am editing the Agda and need to see the changes in a live, hyperlinked document
The jekyll command doesn't seem to index all of the files. The index works and many of the links from there work, but I have found several modules that seem to exist as .md but they don't get converted to html. I'm not sure if jekyll is only descending one level, or if it is based of a list somewhere? Scoped is an example - it is linked from index.html but doesn't get built.

Addressed by https://github.com/IntersectMBO/plutus/pull/5959


examples not working

Did you see that the examples are called by the tests  and that the tests pass ? Maybe it'll help?


Use Go 1.5

Currently Alertmanager does not experience any problems with 1.4.2. There are issues around 1.5 on the other hand. As this possibly introduces problems, we are currently not super motivated to upgrade.
1.5.1 is more realistic.


discord: add libglvnd and fix electron flags

Description of changes
Fixes Discord Canary not launching in Wayland mode when NIXOS_OZONE_WL=1 is set (broken in https://github.com/NixOS/nixpkgs/pull/192659), and errors such as
[2946:1122/160729.555518:ERROR:egl_util.cc(74)] Failed to load GLES library: libGLESv2.so.2: libGLESv2.so.2: cannot open shared object file: No such file or directory

Things done

Built on platform(s)

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

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

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

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Is it related to the issue #159267?

Not entirely sure, I didn't have a black screen before.

i can't reproduce the issue on my amd gpu but there's some vendored libraries in opt/DiscordCanary
$ pwd
/nix/store/k1kcpdbqk7h9ssg2pqsvzc432g1wy2qf-discord-canary-0.0.143/opt/DiscordCanary
$ ls *.so
 libEGL.so   libffmpeg.so   libGLESv2.so   libvk_swiftshader.so

I've tested again and it seems that it only fails to find those libs when building with OpenASAR.
However the Wayland --ozone-platform is wrong either way, and works using this PR.

@Artturin does my comment above address your question? Should we look for alternatives?


User: part of the form was confusing

Question ID
Non-emergency claims

What was confusing
I do not see the new lighting requirements  for shared areas as described in in 105 410.300 (D) (3) for interior lighting and exterior stairway lighting  in residences  with 3 or more dwelling units are described.

Other information

Variable being sought
bad_conditions['Lighting'].claims

Package version
1.12.1

This feedback is referencing the old MADEUptoCode interview, UptoCode sanitary code citations are currently up-to-date.


Add a compiler option for stricter type checking for optional properties

Suggestion
Add a compiler option to prevent Record<string, string> becoming a subtype of { id?: number }. A way to do this is that if there is an optional field in a record then all of it's subtypes needs to have that optional field in the type definition.
🔍 Search Terms
subtype, record, unsafe, type, type system, casting, subtyping, cast, error, compiler, option
✅ Viability Checklist

My suggestion meets these guidelines:

[x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
[x] This wouldn't change the runtime behavior of existing JavaScript code
[x] This could be implemented without emitting different JS based on the types of the expressions
[x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
[x] This feature would agree with the rest of TypeScript's Design Goals.

📃 Motivating Example

To prevent cases like this to happen
const a: Record<string, string> = {
  id: "d4346fda-7480-4e47-a51a-786a431b3272"
};
const fn = (t: { id?: number }) => {
  // Runtime type is `string`
  // Type is `number | undefined` ❌
  console.log(t.id);
};
// Expected error here but got none
fn(a);

Duplicate of https://github.com/microsoft/TypeScript/issues/42719


Create Identity with exported TeamSpeak identity

Hi guys!
I'm curious where you get actually Identity Key. I've tried to get it from TeamSpeak by exporting through GUI and pass identity property from *.ini file.
I'm getting the error Any known methods to decode the key failed with this:
Identity::new_from_str("42VeP4pQAky4r+nmCrlGAUCReG3ZW5zE3lAcHEDfiUae3oBcHJ1ekRvUyR1DS9fKXtIBmF8U1VxSR9UWm0ie2l0Q1NoVnZVVn58LBdjUDYJTixnZgZFIHtCN0IHfHxWNVx1JkZzeEJPTnJLUUloQUxSVlFqNjlDeWRnS0Y5UE5rdVJqMXdLczU2OXdnUHpwZTUyeFhERHVBTDk=")

In your In the example key it is different though. But It's not cleaner is it possible to get this key from TS identity or not.
Thanks!
UPD
Actually, with your key, it doesn't work either. Maybe need to try the latest version

The reason the example key is slightly different is because teampseak stores identities with <counter> 'V' <base64-encoded-private-key>, so in your case the 42 is the counter followed by the constant V and the private key.
I just pushed a fix (d85e08d6e4d088c9d19b9958578aaf7df9cbcbac) which should now just automatically parse this case an gives you the identity object with the private key and counter set.


Changed job priorities to double instead of int

Changed job priorities to double instead of int; this will allow much higher flexibility in assignments.
For example, if there are 10 jobs (set A) that must be assigned and another 500 (set B) that should be assigned if possible, but job capacity is only 20, we want to ensure that set A jobs will be served. We can set priorities for set A jobs = 1.0001 and set B jobs = 10 (smaller value = higher priority). This way there is a much higher chance of all the set A jobs being served.
also updated comparators and tests.

@oblonski
Please consider merging this.

What is the difference between a priority of 1 and one of 1.0001 ?

The difference between a priority of 1 and one of 1.0001 is 0.0001 :-)
The idea is that if I want to assign more than 10 different priorities, I can't do it in the current system. I guess my explanation was not very clear..


Adding Spark unit test

In this PR, an unit test for Spark's dataframe's api is added. Also, RDD support is removed since RDD[Product] doesn't work in Spark due to that class RDD is invariant in type T, and when a case class is passed in, i.e., XYPair <: Product we need to make RDD[T] as RDD[+T] which we can not modify.

+@aishfenton

Current coverage is 69.94% (diff: 100%)

Merging #70 into master will increase coverage by 0.45%

@@             master        #70   diff @@
==========================================
  Files            25         25
  Lines          1763       1760     -3
  Methods        1759       1756     -3
  Messages          0          0
  Branches          4          4
==========================================
+ Hits           1225       1231     +6
+ Misses          538        529     -9
  Partials          0          0

Powered by Codecov. Last update eef177e...556e996

LGTM


vscode_commit

VSCode Version: Code 1.14.2 (cb82febafda0c8c199b9201ad274e25d9a76874e, 2017-07-19T23:34:09.706Z)
OS Version: Windows_NT ia32 10.0.15063
Extensions:

Extension
Author (truncated)
Version

vscode-eslint
dba
1.2.11

sublime-keybindings
ms-
2.9.1

Steps to Reproduce:

Reproduces without extensions: Yes/No

Please provide information about the bug


Failed to load git artifacts in istio-enabled namespace (only in init container phase)

Summary
What happened/what you expected to happen?

Successful GitHub connection was expected to load the
When executing a workflow with git input artifact the artifact loading happens in the init container phase, when istio proxy is not yet running and not even intended to do.
(It's independent from the usual race condition issue which happens in the main container phase, that's already solved by holdApplicationUntilProxyStarts istio configuration)

What version of Argo Workflows are you running?

v3.2.2

Diagnostics

Istio injection is enabled in the namespace where the workflow runs
GitHub connections work fine in other istio-injected pods
GitHub connections work fine in a container/script wrokflow step (in main container)

Example workflow-template part:
apiVersion: argoproj.io/v1alpha1
kind: WorkflowTemplate
metadata:
  name: pipeline-kaniko
spec:
  entrypoint: main
  podMetadata:
    annotations:
      proxy.istio.io/config: '{ "holdApplicationUntilProxyStarts": true }'
  serviceAccountName: workflow
  templates:
  - name: main
    inputs:
      parameters:
        - name: repo
        - name: revision
        - name: container_image_name
    dag:
      tasks:
      - name: build
        templateRef:
          name: common-container-image
          template: build-kaniko-artifact
        arguments:
          artifacts:
            - name: build_context
              path: /workspace
              git:
                repo: "{{inputs.parameters.repo}}"
                revision: "{{inputs.parameters.revision}}"
          parameters:
          - name: target_image_name
            value: "{{inputs.parameters.container_image_name}}"
          - name: target_image_tag
            value: "{{inputs.parameters.revision}}"

What Kubernetes provider are you using?

AKS

What executor are you running? Docker/K8SAPI/Kubelet/PNS/Emissary

PNS

# Workflow Init container logs

time="2021-11-11T22:49:11.530Z" level=info msg="Starting Workflow Executor" executorType=pns version=v3.2.2
time="2021-11-11T22:49:11.536Z" level=info msg="Creating a pns executor"
time="2021-11-11T22:49:11.536Z" level=info msg="Initialized PNS executor (namespace: argo-managed, pod: pipeline-kaniko-5ttgv-4212080228, pid: 6)"
time="2021-11-11T22:49:11.536Z" level=info msg="Executor initialized" deadline="0001-01-01 00:00:00 +0000 UTC" includeScriptOutput=false namespace=argo-managed podName=pipeline-kaniko-5ttgv-4212080228 template="{\"name\":\"build-kaniko-artifact\",\"inputs\":{\"parameters\":[{\"name\":\"target_image_name\",\"value\":\"hello\"},{\"name\":\"target_image_tag\",\"value\":\"master\"}],\"artifacts\":[{\"name\":\"build_context\",\"path\":\"/workspace\",\"git\":{\"repo\":\"https://github.com/zsolt-keseru-epam/argo-combined-app\",\"revision\":\"master\"}}]},\"outputs\":{},\"metadata\":{},\"container\":{\"name\":\"\",\"image\":\"gcr.io/kaniko-project/executor:debug\",\"args\":[\"--context=dir:///workspace\",\"--destination=hello:master\"],\"resources\":{}}}" version="&Version{Version:v3.2.2,BuildDate:2021-10-21T17:18:52Z,GitCommit:8897fff15776f31fbd7f65bbee4f93b2101110f7,GitTag:v3.2.2,GitTreeState:clean,GoVersion:go1.16.9,Compiler:gc,Platform:linux/amd64,}"
time="2021-11-11T22:49:11.536Z" level=info msg="Start loading input artifacts..."
time="2021-11-11T22:49:11.536Z" level=info msg="Downloading artifact: build_context"
time="2021-11-11T22:49:41.539Z" level=error msg="executor error: artifact build_context failed to load: Get \"https://github.com/zsolt-keseru-epam/argo-combined-app/info/refs?service=git-upload-pack\": dial tcp <IP_ADDRESS>:443: i/o timeout"
time="2021-11-11T22:49:41.539Z" level=info msg="Alloc=4840 TotalAlloc=9731 Sys=73297 NumGC=3 Goroutines=3"
time="2021-11-11T22:49:41.539Z" level=fatal msg="artifact build_context failed to load: Get \"https://github.com/zsolt-keseru-epam/argo-combined-app/info/refs?service=git-upload-pack\": dial tcp <IP_ADDRESS>:443: i/o timeout"
stream closed

Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

@zsolt-keseru-epam - can you try by disabling istio?
https://github.com/argoproj/argo-workflows/blob/master/docs/sidecar-injection.md

@zsolt-keseru-epam - can you try by disabling istio?
https://github.com/argoproj/argo-workflows/blob/master/docs/sidecar-injection.md

@whynowy - Unfortunately it's a must-have requirement in my case to have istio, it's a company security constraint.
Otherwise it has been tested with istio turned off, and in that case loading the git artifact works fine.
I have went through the istio-related workflow documentations earlier, including the sidecar-injection.md and I was able to solve all other problems istio caused, except this one.
Is it possible to somehow do the artifact loading in the main container or in a sidecar, instead of the init container?

It could be. I'm not familiar with how ISTIO and init containers work. It could be that the init container starts before ISTIO. Can you look at the pod status?

It could be. I'm not familiar with how ISTIO and init containers work. It could be that the init container starts before ISTIO. Can you look at the pod status?

As to my knowledge istio injects an init container which reconfigures the network stack to redirect all network traffic to the proxy, but the proxy sidecar container only starts when all the init containers have completed.
Here is the pod status of a failed run:
status:
  conditions:
  - lastProbeTime: null
    lastTransitionTime: "2021-11-15T10:42:57Z"
    message: 'containers with incomplete status: [init istio-init]'
    reason: ContainersNotInitialized
    status: "False"
    type: Initialized
  - lastProbeTime: null
    lastTransitionTime: "2021-11-15T10:42:57Z"
    message: 'containers with unready status: [istio-proxy wait main]'
    reason: ContainersNotReady
    status: "False"
    type: Ready
  - lastProbeTime: null
    lastTransitionTime: "2021-11-15T10:42:57Z"
    message: 'containers with unready status: [istio-proxy wait main]'
    reason: ContainersNotReady
    status: "False"
    type: ContainersReady
  - lastProbeTime: null
    lastTransitionTime: "2021-11-15T10:42:56Z"
    status: "True"
    type: PodScheduled
  containerStatuses:
  - image: ***.azurecr.io/istio/proxyv2:1.8.6
    imageID: ""
    lastState: {}
    name: istio-proxy
    ready: false
    restartCount: 0
    started: false
    state:
      waiting:
        reason: PodInitializing
  - image: gcr.io/kaniko-project/executor:debug
    imageID: ""
    lastState: {}
    name: main
    ready: false
    restartCount: 0
    started: false
    state:
      waiting:
        reason: PodInitializing
  - image: ***.azurecr.io/argoproj/argoexec:v3.2.2
    imageID: ""
    lastState: {}
    name: wait
    ready: false
    restartCount: 0
    started: false
    state:
      waiting:
        reason: PodInitializing
  hostIP: <IP_ADDRESS>
  initContainerStatuses:
  - containerID: containerd://e4c31a8092ad35556702b7de19348290f65cc19af9cbbf5107bf59002c9c7dcb
    image: ***.azurecr.io/argoproj/argoexec:v3.2.2
    imageID: ***.azurecr.io/argoproj/argoexec@sha256:bd8ce56bb9dbe7dc641f8d3a605c0e3c508b9efea732aee612549d143dd07c3a
    lastState: {}
    name: init
    ready: false
    restartCount: 0
    state:
      terminated:
        containerID: containerd://e4c31a8092ad35556702b7de19348290f65cc19af9cbbf5107bf59002c9c7dcb
        exitCode: 1
        finishedAt: "2021-11-15T10:43:29Z"
        message: 'artifact build_context failed to load: Get "https://github.com/zsolt-keseru-epam/argo-combined-app/info/refs?service=git-upload-pack":
          dial tcp <IP_ADDRESS>:443: i/o timeout'
        reason: Error
        startedAt: "2021-11-15T10:42:59Z"
  - image: ***.azurecr.io/istio/proxyv2:1.8.6
    imageID: ""
    lastState: {}
    name: istio-init
    ready: false
    restartCount: 0
    state:
      waiting:
        reason: PodInitializing
  phase: Failed
  podIP: <IP_ADDRESS>
  podIPs:
  - ip: <IP_ADDRESS>
  qosClass: Burstable
  startTime: "2021-11-15T10:42:57Z"

I also wonder why other users don't have this problem? Have you tried reming Argo from the loop? I.e. just running a pod with an init container that checks out the files using git clone?

It's reproducible without argo as well:
$ k logs -n argo-managed clone-vbj62 init-clone
Cloning into '/tmp/clone'...
fatal: unable to access 'https://github.com/argoproj/argo-workflows/': Failed to connect to github.com port 443: Connection timed out

While the same succeeds as normal container in the pod.
In the meantime I've seen that the init containers are executed sequentially while I believed they are running in parallel...
The order is:
First my init container (or workflow init-container), then when it's finished istio-init which does the iptables changes.
This would mean from istio side: If there is no egress limitation on the cluster and containers are allowed to connect directly to external addresses, then all init-container before istio-init has connectivity just like without istio (this would be no longer true with istio-cni setup, I think it's not).
So probably that's why it could work for others (who's not using istio-cni yet).
Unfortunately we have egress limitation, so the only way to connect to external addresses is through istio...
Pod description I used for reproducing:
apiVersion: v1
kind: Pod
metadata:
  generateName: clone-
  annotations:
    proxy.istio.io/config: '{ "holdApplicationUntilProxyStarts": true }'
spec:
  initContainers:
  - args:
    - sh
    - -c
    - "git clone https://github.com/argoproj/argo-workflows /tmp/clone && find /tmp/clone"
    image: acraksdanasdeveastus2wi7f.azurecr.io/bitnami/git:2.33.0
    name: init-clone
  containers:
  - args:
    - sh
    - -c
    - "git clone https://github.com/argoproj/argo-workflows /tmp/clone && find /tmp/clone"
    image: acraksdanasdeveastus2wi7f.azurecr.io/bitnami/git:2.33.0
    name: clone
  restartPolicy: Never

This seems to be more like an architectural limitation than a bug, so I've opened an enhancement proposal instead of this with a solution idea.
Maybe I have some time to work on it in the future...
I'm closing this issue.

This seems to be more like an architectural limitation than a bug, so I've opened an enhancement proposal instead of this with a solution idea. Maybe I have some time to work on it in the future...
I'm closing this issue.
@zsolt-keseru-epam Could you please post the link for the enhancement proposal here ?

This seems to be more like an architectural limitation than a bug, so I've opened an enhancement proposal instead of this with a solution idea. Maybe I have some time to work on it in the future...
I'm closing this issue.
@zsolt-keseru-epam Could you please post the link for the enhancement proposal here ?

GitHub has shown the cross-reference to it before my comment.
But let's put the enhancement proposal here for convenience:
https://github.com/argoproj/argo-workflows/issues/7818
I had some additional finding in the meantime, which worth mentioning: if sidecar-free service mesh implementations (Cilium) will land in more widespread service meshes in the future, then the need for this enhancement will significantly drop.


[ios] Show card should collapse on submit action

Platform

iOS

Author or host
Host : MS Teams ios
If you're an author, who are you sending cards to?
1.1
Issue
On submit, show card doesnt close.

@matthidinger can you please comment on this?

Hmm I'm not actually sure any of the renderers do this today. @dclaux can you confirm if the JS renderer has this behavior or an API to handle this? Either way we should document it and make sure all renderers are aligned

This needs to be something configurable by hosts. In Windows toasts, we would want it to stay open... that's because when submission happens, we animate the entire toast out. So if the show card content disappeared, that would look like a choppy and odd experience with that shown section disappearing while the toast is sliding out.


InfluxDB 0.9 Support

I was doing a POC of the InfluxDB 0.9 and had to implement some tweaks to the source. I don't have enough time to do all the necessaries to fork the project, etc. but wanted to share some tweaks I made to the source.
The bulk of the changes were improving the encoding of the data to match the Line Protocol and Line Protocol Write Syntax specification from InfluxDB 0.9.
InfluxDb.cs

        private static string SerializeWriteData(ISeriesPoint data)
        {
            if (data.Fields.Count != data.Values.Count)
            {
                throw new Exception("Invalid field series point - number of fields does not match number of values.");
            }
            var result = data.Name.Replace(",", "\\,").Replace(" ", "\\ ");
            if (data.Tags != null && data.Tags.Count > 0)
            {
                foreach (var kvp in data.Tags)
                {
                    result += "," + kvp.Key + "=" + kvp.Value;
                }
            }
            result += " ";
            var separatorNeeded = false;
            for (int i = 0; i < data.Fields.Count; ++i)
            {
                string strRep;
                var value = data.Values[i];
                if (value == null)
                {
                    continue;
                }
                else if (value is double || value is decimal || value is float || value is Int16 || value is Int32 || value is Int64 || value is UInt16 || value is UInt32 || value is UInt64)
                {
                    strRep = string.Format("{0}", value);
                }
                else if (value is bool)
                {
                    strRep = ((bool)value) ? "t" : "f";
                }
                else
                {
                    strRep = string.Format("\"{0}\"", string.Format("{0}", value).Replace("\"","\\\""));
                }

                if (separatorNeeded)
                {
                    result += ",";
                }
                else
                {
                    separatorNeeded = true;
                }

                result += data.Fields[i] + "=" + strRep;
            }
            if (data.Timestamp.HasValue)
            {
                result += string.Format(" {0}", ToUnixTimeNanoseconds(data.Timestamp.Value));
            }
            return result;
        }

        public static long ToUnixTimeNanoseconds(DateTime date)
        {
            return (date.ToUniversalTime().Ticks -<PHONE_NUMBER>00000000) * 100;
        }

InfluxDb.cs
Add the below to the WriteAsync method to provide better understanding of the errors returned from InfluxDB.
                if (!response.IsSuccessStatusCode)
                {
                    throw new ApplicationException(string.Format("Unable to write series point data. status: {0}, reason: {1}, result: {2}", response.StatusCode, response.ReasonPhrase, await response.Content.ReadAsStringAsync()));
                }

ISeriesPoint.cs
        DateTime? Timestamp { get; }

SeriesPoint.cs
        public DateTime? Timestamp { get; set; }

Feel free to close this but wanted it to be out there should someone else see value in it.

Very good, thanks, added, except that the special formatting I had in there for float/double seems to be necessary as without it "1.0" for example is formatted "1", which causes issues for me with InfluxDB.


Win library prefix

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)

Fixes #3

@conda-forge-admin please rerender

This was failing due to a gap between two different PRs that depended on each other. I've merged the second one now. In a couple hours, you can restart CI and it should pass.

Ah, thanks @h-vetinari ; I just pushed a commit similar to this  since I saw in the Elements chatroom they had the same issue as me. Just unfortunate timing I guess. I'll revert this and will return the CI tomorrow morning.
Thanks a bunch!


file data/a1645191.txt contains UPPERCASE bug – Low Severity Issue

Hello Dave
Thank you for work maintaining this project, it is much appreciated
I seem to have found an issue with the file data/a1645191.txt, there are multiple cases of unnecessary capitalisation in line 11
This error was introduced into the file with commit e271d3ffbc64d5076c11c9c6f4d7c7a8dfff2eb7
Actual:
finish both certainly we. MENTION surface plant XXXXXXX stand information XXXXXXX enter XXXXXXX INTO. group continue CONTINUE since entire. garden physical enjoy activity.
Expected:
finish both certainly we. mention surface plant XXXXXXX stand information XXXXXXX enter XXXXXXX into. group continue continue since entire. garden physical enjoy activity.
I plan to submit a pull request to fix this issue as soon as possible.
Thank you
Deannon

Commit date was 23/9


Fawkes not loading on Mac OS Monterey 12.1

When I download it on my macbook it says "Fawkes Quit Unexpectedly" with options to reopen or ignore which do nothing.
When I restarted it still does not open but now that message is gone. Thanks

Are you running on an Apple M1 chip machine? If so, we do not currently support it.

Fawkes does not work on my Mac: MacBook Pro (13-inch, M1, 2020) | macOS Monterey 12.1.

We currently support M1 now. Pls check the website for the latest update.


add best practices guide for Claude 3 Vision on Bedrock

Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

looks good - the only minor change is that the folder of images is called best_practices, and the best practices notebook is outside
can you change that to either 1) best practices folder has the notebook contained in it; or 2) call that folder images


SFZv1 end= opcode ignored

<region> sample=test.wav offset=1000 end=2000
Expectation is that sample playback stops at sample index 2000. From my tests, it looks like end= is ignored and sample is still played until the end of file.

Yeah, I test this again and I think you're right.
It was working fine, but now it seems broken.
Some bugs maybe...


SQL errors - provide error line number info

Driver version
7.0.0
SQL Server version
Microsoft SQL Server 2016 (SP1) (KB3182545) - 13.0.4001.0 (X64)
Oct 28 2016 18:17:30
Copyright (c) Microsoft Corporation
Express Edition (64-bit) on Windows 10 Home Single Language 6.3  (Build 17134: )
Client Operating System
Windows 10
JAVA/JVM version
java version "9"
Java(TM) SE Runtime Environment (build 9+181)
Java HotSpot(TM) 64-Bit Server VM (build 9+181, mixed mode)
Problem description
Please provide information about error line number in SQLException.
It is already received by tds and stored in StreamError class but then it just never passed to user.
Please provide some way to obtain this info (add special getter in SQLServerException or at least add it in  error messages).

Hi @serge-rider,
Thank you for creating the issue. We will investigate and get back to you soon.

Hi @serge-rider
I created PR #905 to resolve your issue. Let us know your thoughts.

Closing Issue since PR #905 is merged.
The fix shall be available in next Preview Release (v7.1.4)


AdGuard crashes on cdaction.pl

@AdamWr commented on Mon Apr 08 2019
AdGuard crashes everytime I visit this website - https://www.cdaction.pl/
Steps to reproduce

Go to this website - https://www.cdaction.pl/ and wait a moment.

Expected behavior

AdGuard shouldn't crash.
Actual behavior

AdGuard crashes.
Your environment

Adguard version: 3.0.310n (1.3.261cl)
Adguard filtering mode: Local VPN
Device model: Samsung Galaxy S9
Operating system and version: Android 9
Root access: No
Any other apps that can start VPN / Antiviruses / Cleaners etc. installed?: -

It was a sockets bug in 1.3.260, not reproduced in 1.3.267 (AG3.0.311)

Yes, you are right, with 1.3.267 (AG3.0.311) I can't reproduce it too.
Thank you.


make use-context return error when context does not exist

Fixes #10357
➜  kubernetes git:(master) ✗ k config use-context local
➜  kubernetes git:(master) ✗ k config use-context yolo
No context exists with the name. "yolo"

Can you pretty-please add a small test for this in config_test.go?

Updated.

LGTM

@thockin @bgrant0607 for second review

LGTM
I was disappointed to not see yolo in the test


[MM-17111] Limit React Select component to 100 options

Summary
This PR improves the performance of the React Select element by limiting the options to 100 items. This is a much better improvement than the last effort for performance improvement.
The help text for when there are >= 100 items:
There are more than 100 items in your search. Please begin typing to see more.
Ticket Link
https://mattermost.atlassian.net/browse/MM-17605

When there are > 100 items:

When there are <= 100 items:

@aaronrothschild Do we even need that help text to be there, it seems like a common pattern to limit the no of issues, and then allow users to search for issues.

@aaronrothschild I like the help text, but I think it would be better below the drop down.

@cpoile This a better improvement because the dropdown's speed:

no lag when opening dropdown
no lag of updating list while typing
much smoother scrolling in dropdown

The previous improvement made these three metrics better in comparison to without the fix, but now these three issues are resolved by having virtually no lag.


Only a few events are displayed.

Hi tobilg,
I am making use of your project for my school project, already many thanks for making this possible, but I have a little problem.
when entering my city coordinates etc etc, I do only receive 2 events in my whole town, which is not possible, Is this normal or am I doing something wrong?
Looking forward for your reply!
Andres
PS: this is the URL I use.
http://localhost:3000/events?lat=50.8718973&lng=5.516716&distance=150&sort=venue&AccesToken=(my token here)

You only have a radius of 150m. Please choose a bigger one and center it in the center of your city.


Release new crate versions

Mostly to get #615 and #608 out.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license and I agree to the terms of the Developer Certificate of Origin (DCO).

This is the output from Git log for info.
❯ git log mountpoint-s3-client-0.4.0..HEAD -- mountpoint-s3-client
661d0fb (upstream/main, main) Improve logging for ETags and FUSE operation flags (#618)
06a1d7d Add instance and config metadata to user agent (#608)
9a4cfd8 Implement disk-based DataCache with no eviction (#593)
404ba9c Remove unused generic in DataCache (#589)
fa0d516 Add request count tests for FS operations with metadata caching enabled (#567)
7e94711 Refactor signing configuration (#545)

❯ git log mountpoint-s3-crt-0.3.0..HEAD -- mountpoint-s3-crt
7e94711 Refactor signing configuration (#545)
73328cc Silence unnecessary-cast clippy error on linux arm64 (#539)

❯ git log mountpoint-s3-crt-sys-0.3.0..HEAD -- mountpoint-s3-crt-sys
493fc23 Update CRT submodules to latest releases (#604)
9768f31 Update CRT submodules to latest releases (#601)


fix broken link of convolution_2d and convolution_nd document.

links of "See also" part in following documents are broken
http://docs.chainer.org/en/stable/reference/functions.html#convolution-2d
http://docs.chainer.org/en/stable/reference/functions.html#convolution-nd

Thank you for your contribution!


add 'kots upload --deploy --skip-preflights'

Adds --deploy and --skip-preflights flags to kots upload. This enables uploading local changes and immediately deploying them, which is useful for a CLI-only workflow.
Resolves #1201.

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

I'll remove commits from https://github.com/replicatedhq/kots/pull/1313 once I've tested it.

This seems to work as I'd expect.

An alternative would be a separate command to deploy the current latest sequence, with the option to ignore preflight failures.

🤩


Add GrpcCircuitBreakerRule

If a CircuitBreakerRule is built for gRPC clients, users might want to get grpc-status to decide whether a call is a success or not. Normally, grpc-status exists in the HTTP trailers of a response. However, if a call is failed, it could be in the HTTP headers of a trailers-only response. It is a transport-level protocol specification and many users may not know the details.
If we add GrpcCircuitBreakerRule which inherits the existing CircuitBreakerRule and add onGrpcStatus(), users will be able to use circuit breaker with gRPC clients more easily.

@jrhee17 made a good idea to add GrpcRetryRule.

Generally I think adding GrpcCircuitBreakerRule with a onGrpcStatus method is a great idea.
However, it could be even better if the GrpcCircuitBreakerRule has a method onGrpcTrailers(grpcTrailers: HttpHeaders) where grpcTrailers is "trailers" in the context of gRPC. Specifically, grpcTrailers could be either HTTP headers if the response is "trailers-only" or HTTP trailers if the response has 3 parts (HTTP headers, body, and HTTP trailers).
This onGrpcTrailers(grpcTrailers: HttpHeaders) is more generally useful because users get access to the whole gRPC trailer which must contain gRPC status (as promised by the gRPC protocol specification). Another way to think about it would be: what if users want to set up their circuit-break conditions upon other information stored in gRPC trailers other than just gRPC status?
Let me know what you think. Thanks!

it could be even better if the GrpcCircuitBreakerRule has a method onGrpcTrailers(grpcTrailers: HttpHeaders)

Agreed! In addition to onGrpcStatus(), onGrpcTrailers() would be a good extension method for GrpcCircuitBreakerRule and GrpcRetryRule.

Thanks @ikhoon , I wonder when will this GrpcCircuitBreakerRule feature possibly be GA?
Just trying to get a sense of the timeline and you do not need to promise anything. Thanks!

Generally, we try to release a new version every month. However, we are snowed under to participate in LINE internal events, so the next version will be released in the middle of next month.

@Lincong The PR for this issue is up - let me know what you think.

#4535 added AbstractRuleBuilder.onGrpcTrailers() which will be used instead of GrpcCircuitBreakerRule.


any plans to support Metal under the hood?

... in light of Apple dropping Opengl ES support?

Looks like it's gotta happen eventually!

Do you have any sense of the effort? After all, all these APIs are interfaces to the same hardware. How different can they be? :)

It's likely similar to wrapping Metal for OpenGL.  SDL_gpu does rely on some details of OpenGL's state machine that would have to be rethought and reimplemented for Metal.  So I don't have a real sense of the effort, but it's not trivial at least.

It seems hard to know when Apple will truly drop support for OpenGL (e.g., https://www.anandtech.com/show/12894/apple-deprecates-opengl-across-all-oses), but it sounds like it could be relatively soon. Do you have a sense of how much sdl-gpu users care about this? How high is it on your priority list? I'm getting ready to release sdl-gpu-based versions of my iOS games, so this is not a theoretical quandary for me. :)

MoltenVK (Vulkan-to-Metal) might also be a viable option: https://moltengl.com

Unfortunately MoltenVK doesn't come even close to Metal performance-wise. It's still better than Apple OpenGL though.

Ouch, had no idea it was that bad. That said, I'm personally only worried about Apple deprecating OpenGL, so any alternative is fine by me.

MoltenVK is still a good option.  It's more important for code to work than to maximize performance right away.
https://twitter.com/icculus/status/1029052572966051840

Metal would be a lot easier to implement than Vulkan + Moltenvk, and it is officially supported by one major platform.

Does this mean that sdl_gpu doesn't support ios 12 and up?

No. OpenGL is deprecated, not removed.

I don't have a problem at all with incorporating a Metal renderer backend.  I just can't personally provide that implementation before I make a Vulkan one, due to project commitments and time constraints.

It's been a while, but since there are no official C bindings for Metal, I wonder how viable of an option it'd be to use a 3rd party wrapper for this, such as this one: https://github.com/recp/cmt

That can be a useful reference.  You can work with Metal using Objective-C, which is what I would expect to be incorporated into Mac builds of SDL_gpu.


ChatCompletionStream.fromReadableStream errors due to missing finish_reason for choice

Confirm this is a Node library issue and not an underlying OpenAI API issue

[X] This is an issue with the Node library

Describe the bug
When trying to use the API described here https://github.com/openai/openai-node/blob/2242688f14d5ab7dbf312d92a99fa4a7394907dc/examples/stream-to-client-browser.ts
I'm getting the following an error at the following point:

where the actual choices look like this:

Looks like the code expects finish_reason to be populated but the finish details are now in a property called finish_details?
To Reproduce
Setup a server that responds with chat completion streams
Then in the client try to use the ChatCompletionStream.fromReadableStream API, e.g.:
const runner = ChatCompletionStream.fromReadableStream(res.body);
await runner.finalChatCompletion();

Code snippets
No response
OS
Windows
Node version
18.12.1
Library version
4.16.1

I'm seeing this only when using the gpt-4-vision-preview model. Other models still return finish_reason param, it seems.
Here is a workaround patch: https://github.com/petrgazarov/openai-node/commit/093fcbdec38c6f42e05c32130eed5ac66f0c133e. I'm happy to send a PR if the maintainers are interested.

@petrgazarov thanks for looking into this, I am also getting this issue when using gpt-4-vision-preview, didn't think it was relevant so wasn't mentioned initially
I have not got this issue before so I guess that's the key difference

Thanks for reporting, we're investigating.

Is this something that openai needs to fix upstream? This is causing streamed responses using gpt-4-vision-preview and vercel/ai to break

Hey @jonluca ! Yes, this needs to be fixed on the backend. Let me check with the team about this, I'm sorry that's still happening.

I'm still receiving the error when using the openai package

@vitorfdl what is the error you're getting?

const messages =  [
            { role: 'user', content:
                [
                    {
                        type: 'image_url',
                        image_url: 'bla',
                    }
                ]
            }
        ];
    const stream = await openai.beta.chat.completions.stream({
        model,
        messages,
        stream: true,
    });

    stream.on('content', (delta, snapshot) => {
      console.log(delete)
    });

    stream.finalChatCompletion().then( () => {

    } );

I got an error
(node:1824057) UnhandledPromiseRejectionWarning: Error: missing finish_reason for choice 0
    at /node_modules/openai/lib/ChatCompletionStream.mjs:213:23
    at Array.map (<anonymous>)
    at finalizeChatCompletion (/node_modules/openai/lib/ChatCompletionStream.mjs:211:26)
    at ChatCompletionStream._ChatCompletionStream_endRequest (/node_modules/openai/lib/ChatCompletionStream.mjs:107:16)
    at ChatCompletionStream._createChatCompletion (/node_modules/openai/lib/ChatCompletionStream.mjs:58:141)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async ChatCompletionStream._runChatCompletion (/node_modules/openai/lib/AbstractChatCompletionRunner.mjs:312:16)
(Use `electron --trace-warnings ...` to show where the warning was created)

Thanks! Great news, this has been fixed in the API. Please file a new issue if you see any further problems.


Dynamic Client Registration Management

Add support for OAuth 2.0 Dynamic Client Registration Management Protocol
as per https://datatracker.ietf.org/doc/html/rfc7592

add a ClientConfigurationEndpoint
implement (registration) accessToken for client management

Do note that as per https://datatracker.ietf.org/doc/html/rfc7592#section-5 registration access token should NOT expire.

Current implementation already has partial support.
We need to properly handle registration tokens. Full fix depends on #117


end - B1

Name: Zeta159z
Node Id: a309662f0bc535a8
The node launched on October 9. Task " B1 " start 15 Oct. - 14 Nov. end ([Team] Maria Amalia)

confirmed:B1
node:a309662f0bc535a8

Form Submitted at 11:23, GMT+3. (08:23am UTC)


Creating an app when deis remote already exists

'deis create' when a deis remote already exists bubbles up the git error that says the remote called deis already exists.
It'd be nice to have an more clear error/warning like “Existing deis remote already exists. The app was created, but a git remote couldn’t be created. Remove the git remote and add the new one with "

:+1:

:+1: good proposal! Should make it more clear how the user should respond to this error.


B 18313 int updates

Agility ticket
Summary
After merging previous PR for B-18313 the gov wanted to add in a way to force the service member to validate their profile.
The solution is to add a Validate Profile button that, when clicked, enables the Create a Move button.
This PR does the following:

adds in profileValidated state that controls the enablement/disablement of the validate & create a move buttons
moved buttons to the bottom of the page in a section wrapper that will require the service member to scroll all the way down past their profile info
updated tests to reflect changes

How to test

Access MM as customer that has previous moves
Click the Create a Move button on the multi-move dashboard
You'll be directed to the profile screen to review your profile
Scroll to the bottom and you'll see you cannot proceed until you click Validate Profile

Screenshots

Seeing the "oops something went wrong" page when I do this:  Validate profile ->  -> Create move

I'm not sure what to do with that info - that means it has something to do with the move home page and some data is missing. Can you dive into the errors to see what they say? Should say something in console.

Seeing the "oops something went wrong" page when I do this:  Validate profile ->  -> Create move

I'm not sure what to do with that info - that means it has something to do with the move home page and some data is missing. Can you dive into the errors to see what they say? Should say something in console.

Couldn't replicate this - worked for me when testing again. Looks good!


Sync eng/common directory with azure-sdk-tools for PR 2830

Sync eng/common directory with azure-sdk-tools for PR https://github.com/Azure/azure-sdk-tools/pull/2830  See eng/common workflow

/check-enforcer override


Add test for verbosity

Current coverage is 73.20% (diff: 100%)

Merging #111 into master will increase coverage by 2.84%

@@             master       #111   diff @@
==========================================
  Files             4          4
  Lines           415        418     +3
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits            292        306    +14
+ Misses          123        112    -11
  Partials          0          0

Powered by Codecov. Last update 77f2d1b...70c45d9


Build docker image based on version 1.1.0

Is there a change to build fresh docker image based on version 1.1.0. The latest one available on docker hub based on version 1.0.1

I'd double that. Please update image.

I would go a step further and say there needs to be a way for releases to happen semi-automated, be it Docker Images, PyPI or Github releases. Upstream devs are affected by this as well, e.g. linuxserver/docker-faster-whisper, because they rely on published packages or querys to the Github-API for release information.

Docker image has been uploaded to 2.0.0 (see: https://github.com/rhasspy/wyoming-faster-whisper/releases/tag/v2.0.0)


Initial release

Now the initial implementation is finished.  Now starting the example


docs: improve section about Prometheus graceful shutdown.

fixes https://github.com/prometheus/prometheus/issues/13183

cc @beorn7


feat: prettify the test output by listing failed tests

Description
Currently, especially on CI, it's difficult to understand which tests have failed without scrolling through the output. I'd love to see a summary of failed tests in some concise form aside from the typical output. Usually I'm going to rerun them anyway in my IDE to see what exactly failed.
Current output

And at the end:
00:44 +923 -1 ~1: Some tests failed.

Expected Behavior
00:44 +923 -1 ~1: Some tests failed.
Failed tests:
  - test/compare_video/view/compare_video_page_test.dart:237:59 (adds MyVideosRequested to myVideosBloc on pull to refresh on my videos tab)
  - ...

Closed on #397


(Python) Use new-style classes

(See cucumber/gherkin-python#1 for details.)

NOTE: Untested!
I tried to run make after committing my changes, but I got an error:
$ make
cd dotnet && make
rm -f .sln_built_debug
mono --version
make[1]: mono: No such file or directory
make[1]: *** [.sln_built_debug] Error 1
make: *** [dotnet/.compared] Error 2

I’m afraid I don’t know anything about dotnet… :-(
In the meantime, I’ll be waiting for Travis to do its wonderful work.

Okay.  Travis says I need to update my changes to gherkin-parser.razor.  Looking into it…

w00t!  The build passes. :)

@Zearin Thanks for your contribution.


Improve Version Sorting in Snippets

Versions for Deephaven look like 0.28.0, 0.28.1, etc.  That style is not lexicographical sort-able.  For some queries used for generating tables using the Benchmark snippets, sorting by version is important.  Sorting by timestamp is not reliable, because it's possible that a re-run of a specific release will be needed, which would put the timestamps out of order.

Write a function to convert version to something sortable
Add it inline for the version column being sorted (since benchmark data is small, this should not affect performance)
The converted result need not be a string
Related to https://github.com/deephaven/benchmark/issues/228

This ticket has been fulfilled by approaching the problem a different way.  With the change in directory structure, all "set" level directory labels, whether version or date, are lexicographical sort-able.  These are used to sort newest to oldest,  Timestamp is no longer a factor in the benchmark queries.  For example, concerning the nightly category, "last 5 days" means "last 5 sets".  Concerning the release category, "last 5 versions" means "last 5 sets".


Padding input fillers for happier narrow-cell clickbox.

Closes #91
Default TODO list

[X ] Are all notable changes added to the changelog in dev-docs/?
[X ] Are there any manual checks that you did while preparing this release that could be automated and become part of the CI?
[ X] Are any relevant issues to the PR mentioned so that they will be automatically closed when the PR merges?

Gonna self-merge since this is rather trivial.


#32 Microsoft.Data.SqlClient v3.0.0

Based on this PR I assumed that managed identity parameters used for authentication now go through connection string.
I do apologize, but I can't currently check this assumption unfortunately - using my personal Azure subscription it will require spinning up AD domain, and I'm not sure that I have the knowledge (or resource) to do that right now. I will look into possible work-around for this.

@cgillum
After some more source code exploration, I was able to test my assumption, using custom Azure AD domain, Ubuntu 20.04 VM and Azure SQL database. I used this tutorial to setup VM and database.
Here's the code I ran on VM:
using System;
using System.Data.Common;
using Microsoft.Data.SqlClient;

namespace test_prog
{
    class Program
    {
        static void Main(string[] args)
        {
            using (var connection = new SqlConnection("Data Source = durable-sql.database.windows.net; Initial Catalog = DurableDB; Authentication = ActiveDirectoryManagedIdentity"))
            {
                connection.Open();
                using (var cmd = new SqlCommand())
                {
                    cmd.CommandText = "create table test_table(id int);";
                    cmd.Connection = connection;
		    cmd.ExecuteNonQuery();
                }
                Console.WriteLine("Hello World!");
            }
        }
    }
}

Looks like (in the simplest case at least) things like AuthorityHost and TenantId are not required to be provided in connection string (and I'm not sure they can be right now).

Excellent! Thank you for verifying! I'll do a bit more verification as well and then merge this PR. I'm very happy that the SQL client team made it much easier to integrate with managed identities.

Had a chance to do my own testing and everything looks great. I specifically tested locally using Authentication=Active Directory Default which is designed to work both locally and in Azure.
I've updated this PR to include a couple items in CHANGELOG.md. Thanks again for this contribution!!


[BUG] Unable to move past onboarding

As the title says :-

I signed up, asked me a bunch of questions like company name, role etc.
I chose Android as the technology.
Asked me import a design, I selected, " I don't have a design" and so it gave me a choice to select Explore or Template.
I chose explore, selected 1 screen, pressed '+' and clicked on proceed.
On clicking 'Proceed', it said "Application Added Successfully" and then it again goes back to onboarding! Back to step (2) all over again. This seems to be going in an infinite loop.

@ubarua123 I’ve taken a look at it, and identified the issue. Now on to resolving it ASAP!
Meanwhile if you face any more issues, you can always post it on DhiWise's Discord server.


gf watch: ipython functionality and minor fixes

hi @joamatab ,
this MR adds ipython functionality to gf watch and also adds a few minor enhancements and fixes

Fixes issue that dynamically loaded yaml cells appear to vanish from known cells if pdk is switched midway through execution
Adds a convenience show() function to the context of the ipython watcher loop. That is to say, assuming you have a file called TOP.pic.yml somewhere in your file tree you are watching, you can type show('TOP') at the ipython terminal, and it will switch views to that cell for you. This will also work for any other registered python cells or any components you might create at the terminal...

Thank you Troy!


Update the Apps Section in Control Center

Our feedback regarding section 3:
General remark: Not sure if the structure makes sense with having a separate section for active apps and deactivated apps. Now it seems that you only have a “Profile Page” for active apps, and that you can only delete an active app. Also first showing all the actions and possibilities (3.1), and then later explaining what this tab is actually showing (3.1.1) feels like a strange order to me. general remark about the Active/Inactive seems a bit of a strange distinction especially because you're explaining the functionalities for Active and then for Inactive you almost have the same kind of functionalities.
Section 3.1: For the first table about showing options for different types of deployment:

We have both a red cross and “not supported”. What is the difference? -> Kindly requested to change the Not Applicable and Not supported into red crosses.
For the Private Cloud Environment, the option to “Delete a free Mendix Could environment” is marked as “not supported”, but that is confusing to me. Technically, an app that is on private cloud can still have a free environment in the Mendix Cloud (in CP), and you could delete that from CC. Besides that, it might be confusing for the user to talk about free Mendix Cloud environment deletion for a private cloud app.
Is it not worth mentioning SAP cloud as well, maybe there is a reference to private cloud docs that can answer these flavors?, what about IBM?
Is the user aware of a difference between Free Mendix Cloud Environment and No cloud resource? Or are those situations considered the same for the user?

Section 3.1: For the second table showing the consequences:

AFAIK, the team members can also no longer access the code repository when deactivating an app. Should this be mentioned as well? (There is a difference in something being persistent and being accessible. We show the difference for the app project, but not for the repository.)

Section 3.1.1:

Below the image, there is a text saying: "… with options for exporting app details to an .xlsx file, deactivating apps, and deleting apps" .Deleting apps should not be plural, since you can only delete one app at a time.

Section 3.1.2

Maybe move the screenshot of 3.1.2 a bit up after .. it opens with the app profile. Otherwise, you read the explanation and then get the context.
3.1.2 > There are a lot of screenshots, but then for adding yourself to a project there isn't one. I can imagine this is also explained earlier, but then when to show a screenshot a not is a bit random.
The three dots will also show for private/SAP cloud apps, only not for licensed apps in the Mendix (Public) Cloud since we base this on the info we get from CP.
The bullet point “Members” mentions that this tab shows active members, but it also shows deactivated members here.
The bullet point “Environments” mentions that this tab shows all environments, but it is only the Mendix (Public) Cloud environments.


DijkstraOneToMany - isWeightLimitReached

Hi, i found this algo may return NOT_FOUND in case, where desired node is presented in heap and we reached earlier other node with same weight as desired and its weight equals to limit. Also this fix affects other 2 preparation tests.

This should be already fixed due to #362 (?)

Ah, wait you removed the equal sign ...

Yep, please look at new test.

hmm. Maybe if current weight reached limit and equals its, we need check weights array and return "to" if it is contained there?

What do you mean? The current solution seems good to me. Additionally we probably need to change the method name and do this (>) for all other algorithms.

It get slightly more unnecessary iterations, but it is not critical. Ok I'll fix methods and check other algo. Can I rewrite edge counter in broken CH tests?

It get slightly more unnecessary iterations

Yes, but they are necessary :)
I currently investigate and will fix and let you review (as there is some inconsistency for CH and the other bidirectional algos when it comes to the finish and isWeightLimitReached methods)

Okay, would you mind to review the changes? Then I'll merge

Reviewed :)
Thanks!

Thank you :) !


add handler for Google Fit data

Fit/Daily Aggregations csv files -- started appearing in 2017
Fit/Activities/*.tcx and  Fit/Activities/Low Accuracy/*.tcx files -- perhaps worth just having a function to get them, something else should actually handle tcx files
also a bunch of them seems to have disappeared in 2020 (comparing with 2018) -- not sure if it's some sort of retention

for now suppressed it here, quite spammy https://github.com/seanbreckenridge/google_takeout_parser/pull/27


[FormsyText] Add updateImmediately prop & fix handleChange

I believe this resolves the various issues for both use cases. Let me know!
This is based in part on and supersedes @codaholicguy's PR: #103.
If you use onValid / onInvalid to control the submit button, and the last form element before the submit button is a text-field, you should use updateImmediately on that field to provide an error as to why the form can't be submitted without the user having to remove focus from that field.
I increased the timeout slightly, as otherwise the error can come in while still typing for a slower typist.
If you don't control the submit button (or the textfield isn't the last value before the button), the default behaviour is now consistent. onValid / onInvalidupdate immediately, but the error only appears when focus shifts.
Closes #97.

👍

How status of merging this pr?

Works great for me so far, but I think that throttle is better in this case. Otherwise, the form doesn't get re-validated while typing (at rather fast speed) but only after typing.

Agreed that throttle seems to make more sense for this use case. I'd love to see this pull request get merged as I've been dealing with the "last text input in a form not enabling the submit button" issue for quite some time and it really does cause confusion for some users. Is there something I can do to help?

I see. Throttle seems to be better for this case. What is status of this pull request?

@codeaholicguy It needs a rebase after recent merges. I can see pros and cons to throttle vs. debounce, but I'm not yet convinced that throttle would be preferable. I'm open to feedback as to why. With throttle, a slower typist is going to get an error when their going-to-be-valid, but as yet incomplete entry hits the throttle timeout.
With debounce, a fast typist doesnt get an error until they're done, but if they're a fast typist, they can fix thier error quickly. 😄

@jayalfredprufrock

Is there something I can do to help?

When we agree on the best approach, you're welcome to take this PR, fix it up and resubmit it.

@mbrookes I hear ya, and I could certainly be happy with either.
I think the reason this is a tough call is we have two use cases for the updateImmediately prop:

Notifying the user that their input is invalid without requiring them to move to the next field. In this case debounce is preferable to prevent bombarding the user with error messages before they've been given a chance to finish typing.

Notifying the user immediately when their input is valid. In this case, throttle is preferable so the user gets notified as soon as possible, eg. validation errors get cleared, submit buttons enabled, etc.

If I had to choose one, the latter seems more useful. My guess is accomplishing both effects would require some non-trivial internal changes, but perhaps we could provide the two versions separately via two different props?? So updateImmediately would provide a throttled version and another prop, say updateWhenIdle, would provide a debounced version?

Having the choice via a prop would be good, but what should the default be? 😄

Hi,
Any news on this one ?
Many thanks.

@mbrookes can I take responsibility of rebasing this PR?
remote: Permission to mbrookes/formsy-material-ui.git denied to codeaholicguy.
fatal: unable to access 'https://github.com/mbrookes/formsy-material-ui.git/': The requested URL returned error: 403

@codeaholicguy Yes please!!!

@mbrookes I rebased

Thanks!
I'm merging this as is, as I don't have the cycles to review right now, but since this is mostly based on your code, I know it's good!
I think it would be good to get community feedback before we release, so lets hold back on pushing to npm for a bit and see if this throws up any issues.

@mbrookes thank you! Should I merge this PR or wait for you?

Oops - in my haste I forgot to confirm the merge! Done now.

I'm using this updateImmediately option and getting a new error in the browser console.
Unknown prop `updateImmediately` on <input> tag. Remove this prop from the element. For details, see https://fb.me/react-unknown-prop

@rojobuffalo currently, it hasnt been tagged yet, so please use formsy-material-ui direct from github source

Hi, thanks for this PR. Could you explain why you added a debounce? @jayalfredprufrock Could you explain how a user gets bombarded by error messages? Either the input is already invalid, so the message is already shown under the textfield or the input gets invalid, and as soon as this happens I want to know about and not wait for 400ms.

The debounce behavior becomes desirable when you have an input that is guaranteed to fail validation at the first key stroke. Consider a password confirmation field or an email field. It's a little distracting to see the flash of an error message telling you your password is incorrect or email invalid when you just haven't had a chance to finish typing. In a perfect world, the user would be notified immediately when the field becomes valid, but only notified of invalid input after a short idle period. Thi
Earlier I was suggesting some kind of "updateWhenIdle" type functionality where the field can only be invalidated after it has received focus and at least one character, and the user hasn't typed any thing in 400ms. Haven't had a chance to look at the above implementation to know how things are supposed to work now, but it sounds like either way this is a nice improvement to what we had before.

@jayalfredprufrock I like the ideal world ^^, maybe following merge request goes into this direction: https://github.com/mbrookes/formsy-material-ui/pull/155


Same meanr being logged by tb_logger during validation

Hello Fartash,
A small issue that I noticed: there is no meanri for t2i and the same meanr from i2t is being logged by the tb_logger during validation.
https://github.com/fartashf/vsepp/blob/cb5561a5dc745bf495729b261a97e0c93ef0203f/train.py#L209
and
https://github.com/fartashf/vsepp/blob/cb5561a5dc745bf495729b261a97e0c93ef0203f/train.py#L214
Awesome work and hats off to you for still maintaining the repo.
Regards,
Avery

Hi Avery,
Good catch. Thanks. The printed statements were correct but the ones logged using tb_logger were wrong. Commit 7f8ffd55bf4c5f195fcae543f9b8e242e665d839  has fix that. We did not report meanr, meanri in the paper so the change does not concern the numbers in the paper.
Thank you for reporting the issue and using the code.
Fartash


Add Fedora 39 and Fedora 40

Fedora 39 and Fedora 40 have support for s390x, so we should add script support for it as well.

Can I be assigned this issue?

@aarishshahmohsin please send PR if you want to work on it :)

Looks like a PR has been merged which addresses this issue: https://github.com/openmainframeproject/software-discovery-tool/pull/182. Maybe, it can be closed now ?


Getting "undefined" when solution works on CodePen and JSFiddle

My solution works elsewhere, but not on freeCodeCamp. Here is my code:
function sumAll(arr) {

  //Sort the array in ascending order
  arr.sort(function(a, b) {
    return a - b;
  });

  //Assign smallest and largest values to variables
  var firstValue = arr[0];
  var lastValue = arr[1];

  //Count over each number starting with the lowest, and going up to the highest
  for (var i = firstValue; i <= lastValue; i++) {
    var total = 0;
    total = total + i;
  }
}
sumAll([10, 5]);

Your sumAll function never returns a value.
In the future please use the Help Chat and Bonfire Help Chat before filing a bug.
Thanks and happy coding!


Feature/1 feat add welcome api

:tada: This issue has been resolved in version 1.0.0-develop.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 1.1.0-develop.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 1.1.0-develop.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 1.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Why MAX_SERIES = 20

Why do we have this in datasource.ts?
MAX_SERIES = 20

Wanted to keep the responses performant easy to interpret. We only have 20 colors anyway. But feel free to open a PR to remove it.

Is there any way we could remove that limitation ?
There is a limitation on populating graphs(also tables) but at the same time it opt-out full csv results.
Kind regards,
Adrian.

changing that MaxSeries to any value is not affecting graphs at all.
Still getting limit of 20 tables/series. (only on graphs - on csv output - i get all.

Let's make this configurable


"各...次 のステートメント" needs to be replaced with "For Each...Next ステートメント"

https://docs.microsoft.com/ja-jp/office/vba/language/concepts/getting-started/using-for-eachnext-statements

related issues: #858 | #859 | #860

Working on a fix (Bug 3242652)

@hyoshioka0128 The article has been HumanTranslated and published live. Issue is fixed


WFCORE-4162 Incorrect OperationContext.getCapabilityServiceName javadoc

Issue: https://issues.redhat.com/browse/WFCORE-4162

Hello @darranl,
Here https://github.com/wildfly/wildfly-core/blob/master/controller/src/main/java/org/jboss/as/controller/capability/registry/ImmutableCapabilityRegistry.java#L78 it is mentioned it may be {code null} if the user is unconcerned about the validation. And I have also checked API is null safe. For example, here https://github.com/wildfly/wildfly-core/blob/master/controller/src/main/java/org/jboss/as/controller/capability/RuntimeCapability.java#L141 in case user doesn't want the validation and they will pass the serviceType {code null} then it will handle here. Please let me know if my understanding is wrong.
Thanks

I think this should still look at the second interface I linked which has the same restrictions defined, if that implementations of that interface allow null we should update the javadoc there as well.
The reason I am suggesting this is we are relaxing the documented restrictions on an API but not applying the same relaxation to the API likely to be called so anyone implementing the second one could inadvertently require it to not be null as it is documented that way.

Sorry disregard my comment, the second interface doesn't need a change.