WAC - frequent connection errors

Gateway Version: 1.3.2204.19002
To Reproduce
Steps to reproduce the behavior:

Go to 'Server, computer, Cluster or all connections'
Click on any listed machine
Frequently get "Connection Error - Ajax error 400'
sometimes several page refreshes restores ability to connect other times even closing the tab and launching the page does not help

Expected behavior
Consistent and reliable connection to machines

Hello @PeterRoots :)
My name is Rebecca, a Product Manager on Windows Admin Center.
I can't seem to reproduce this issue on my end :(
I understand that this must be a frustrating issue to deal with. Would you like to schedule a call to troubleshoot this?
If so, please send whatever time (as well as your time zone) that would work for you to<EMAIL_ADDRESS>Kind regards!

Hi Rebecca
I am running on BST (GMT+1) at the moment
I work Wed-Fri only between 9:00and 17:00 with a regular meeting on Wednesdays at 14:00-15:30
Happy to have a look at this with you but can be tricky as it an intermittent issue so may or may not show itself on demand :-)
Thanks
Peter
From: RebeccaMbulaMs @.>
Sent: 09 May 2022 10:24
To: MicrosoftDocs/Windows-Admin-Center-Ideas-and-Feedback @.>
Cc: Peter Roots @.>; Mention @.>
Subject: Re: [MicrosoftDocs/Windows-Admin-Center-Ideas-and-Feedback] WAC - frequent connection errors (Issue #173)
NOTE: This message originated outside Barnett Waddingham.

Hello @PeterRootshttps://github.com/PeterRoots :)
My name is Rebecca, a Product Manager on Windows Admin Center.
I can't seem to reproduce this issue on my end :(
I understand that this must be a frustrating issue to deal with. Would you like to schedule a call to troubleshoot this?
If so, please send whatever time (as well as your time zone) that would work for you to<EMAIL_ADDRESS>Kind regards!
—
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/Windows-Admin-Center-Ideas-and-Feedback/issues/173#issuecomment-1120862346, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ARJ7TDREKVVKRHRMT4IVMX3VJDKULANCNFSM5USBBNJA.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>
Protect yourself from cyber fraud.
If you receive an email that appears to come from Barnett Waddingham providing
different bank details or informing of a change of account, it is unlikely to
be genuine. Do not reply to the email or act on any information contained in
it and contact us immediately by phone to check the account details. We will
not accept responsibility if you transfer money into an incorrect account.
Barnett Waddingham LLP is a body corporate with members to whom we refer
as “partners”. A list of members can be inspected at the registered office.
Barnett Waddingham LLP (OC307678), BW SIPP LLP (OC322417), and Barnett
Waddingham Actuaries and Consultants Limited (06498431) are registered in
England and Wales with their registered office at 2 London Wall Place, London,
EC2Y 5AU. Barnett Waddingham LLP is authorised and regulated by the Financial
Conduct Authority. BW SIPP LLP is authorised and regulated by the Financial
Conduct Authority. Barnett Waddingham Actuaries and Consultants Limited is
licensed by the Institute and Faculty of Actuaries in respect of a range of
investment business activities.
This message and any attachments are confidential and are solely for the
individual to whom they are addressed. Any use of, or action taken in reliance
upon this information by any other person is prohibited. If you received this
information in error, please contact the sender immediately and delete the
material from any computer that may contain it and destroy any printed copies
you may have made. We have taken all reasonable precautions to ensure that no
viruses are transmitted with this message. However, we can accept no
responsibility for any loss or damage resulting directly or indirectly from
the use of this e-mail or its contents. Incoming and outgoing e-mails are
subject to scanning and may be intercepted by our e-mail administrators.

Hi Peter!
Thank you so much for reaching out to me about the Ajax error that you are experiencing.
I have been trying to get a software engineer to join in for our troubleshooting/bug discovery call so that we can be more effective.
What would be your best time on Friday?
Kind regards!
From: PeterRoots @.>
Sent: Wednesday, May 11, 2022 12:31 PM
To: MicrosoftDocs/Windows-Admin-Center-Ideas-and-Feedback @.>
Cc: Rebecca Wambua @.>; Comment @.>
Subject: Re: [MicrosoftDocs/Windows-Admin-Center-Ideas-and-Feedback] WAC - frequent connection errors (Issue #173)
Hi Rebecca
I am running on BST (GMT+1) at the moment
I work Wed-Fri only between 9:00and 17:00 with a regular meeting on Wednesdays at 14:00-15:30
Happy to have a look at this with you but can be tricky as it an intermittent issue so may or may not show itself on demand :-)
Thanks
Peter
From: RebeccaMbulaMs<EMAIL_ADDRESS>Sent: 09 May 2022 10:24
To: MicrosoftDocs/Windows-Admin-Center-Ideas-and-Feedback<EMAIL_ADDRESS>Cc: Peter Roots<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/Windows-Admin-Center-Ideas-and-Feedback] WAC - frequent connection errors (Issue #173)
NOTE: This message originated outside Barnett Waddingham.

Hello @PeterRootshttps://github.com/PeterRoots :)
My name is Rebecca, a Product Manager on Windows Admin Center.
I can't seem to reproduce this issue on my end :(
I understand that this must be a frustrating issue to deal with. Would you like to schedule a call to troubleshoot this?
If so, please send whatever time (as well as your time zone) that would work for you to: @.@.mailto:***<EMAIL_ADDRESS>Kind regards!

Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/Windows-Admin-Center-Ideas-and-Feedback/issues/173#issuecomment-1120862346, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ARJ7TDREKVVKRHRMT4IVMX3VJDKULANCNFSM5USBBNJA.
You are receiving this because you were mentioned.Message ID: @.@.mailto:***<EMAIL_ADDRESS>
Protect yourself from cyber fraud.
If you receive an email that appears to come from Barnett Waddingham providing
different bank details or informing of a change of account, it is unlikely to
be genuine. Do not reply to the email or act on any information contained in
it and contact us immediately by phone to check the account details. We will
not accept responsibility if you transfer money into an incorrect account.
Barnett Waddingham LLP is a body corporate with members to whom we refer
as "partners". A list of members can be inspected at the registered office.
Barnett Waddingham LLP (OC307678), BW SIPP LLP (OC322417), and Barnett
Waddingham Actuaries and Consultants Limited (06498431) are registered in
England and Wales with their registered office at 2 London Wall Place, London,
EC2Y 5AU. Barnett Waddingham LLP is authorised and regulated by the Financial
Conduct Authority. BW SIPP LLP is authorised and regulated by the Financial
Conduct Authority. Barnett Waddingham Actuaries and Consultants Limited is
licensed by the Institute and Faculty of Actuaries in respect of a range of
investment business activities.
This message and any attachments are confidential and are solely for the
individual to whom they are addressed. Any use of, or action taken in reliance
upon this information by any other person is prohibited. If you received this
information in error, please contact the sender immediately and delete the
material from any computer that may contain it and destroy any printed copies
you may have made. We have taken all reasonable precautions to ensure that no
viruses are transmitted with this message. However, we can accept no
responsibility for any loss or damage resulting directly or indirectly from
the use of this e-mail or its contents. Incoming and outgoing e-mails are
subject to scanning and may be intercepted by our e-mail administrators.

Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FWindows-Admin-Center-Ideas-and-Feedback%2Fissues%2F173%23issuecomment-1123428931&data=05|01|rwambua%40microsoft.com|3559176594334608eca808da3330e716|72f988bf86f141af91ab2d7cd011db47|1|0|637878582409497330|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=Aeoxvzbx%2Btwmoo22UKguiZ5fUqkpxKuCvOsmk%2FF8kGc%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAW5P2XP25CCO3PO6K5D5BGTVJN43XANCNFSM5USBBNJA&data=05|01|rwambua%40microsoft.com|3559176594334608eca808da3330e716|72f988bf86f141af91ab2d7cd011db47|1|0|637878582409497330|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=p2p3M1WAjP2%2BOc%2Bm95qq0oNaRcHGVFi5w7NrYjw3RgE%3D&reserved=0.
You are receiving this because you commented.Message ID<EMAIL_ADDRESS>

Thanks Rebecca
I start work at 9:00 BST and have a meeting at 10:30 so between them would be good. Otherwise sometime after 14:00 and before I finish work at 17:00
Thanks
Peter
From: RebeccaMbulaMs @.>
Sent: 12 May 2022 07:42
To: MicrosoftDocs/Windows-Admin-Center-Ideas-and-Feedback @.>
Cc: Peter Roots @.>; Mention @.>
Subject: Re: [MicrosoftDocs/Windows-Admin-Center-Ideas-and-Feedback] WAC - frequent connection errors (Issue #173)
NOTE: This message originated outside Barnett Waddingham.

Hi Peter!
Thank you so much for reaching out to me about the Ajax error that you are experiencing.
I have been trying to get a software engineer to join in for our troubleshooting/bug discovery call so that we can be more effective.
What would be your best time on Friday?
Kind regards!
From: PeterRoots<EMAIL_ADDRESS>Sent: Wednesday, May 11, 2022 12:31 PM
To: MicrosoftDocs/Windows-Admin-Center-Ideas-and-Feedback<EMAIL_ADDRESS>Cc: Rebecca Wambua<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/Windows-Admin-Center-Ideas-and-Feedback] WAC - frequent connection errors (Issue #173)
Hi Rebecca
I am running on BST (GMT+1) at the moment
I work Wed-Fri only between 9:00and 17:00 with a regular meeting on Wednesdays at 14:00-15:30
Happy to have a look at this with you but can be tricky as it an intermittent issue so may or may not show itself on demand :-)
Thanks
Peter
From: RebeccaMbulaMs @.<mailto:@.mailto:***<EMAIL_ADDRESS>Sent: 09 May 2022 10:24
To: MicrosoftDocs/Windows-Admin-Center-Ideas-and-Feedback @.<mailto:@.mailto:***<EMAIL_ADDRESS>Cc: Peter Roots @.<mailto:@.mailto:***<EMAIL_ADDRESS>Mention @.<mailto:@.mailto:***<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/Windows-Admin-Center-Ideas-and-Feedback] WAC - frequent connection errors (Issue #173)
NOTE: This message originated outside Barnett Waddingham.

Hello @PeterRoots<https://github.com/PeterRootshttps://github.com/PeterRoots> :)
My name is Rebecca, a Product Manager on Windows Admin Center.
I can't seem to reproduce this issue on my end :(
I understand that this must be a frustrating issue to deal with. Would you like to schedule a call to troubleshoot this?
If so, please send whatever time (as well as your time zone) that would work for you to: @.@.<mailto:@.@.mailto:***@***.******@***.***<mailto:***<EMAIL_ADDRESS>Kind regards!

Reply to this email directly, view it on GitHub<https://github.com/MicrosoftDocs/Windows-Admin-Center-Ideas-and-Feedback/issues/173#issuecomment-1120862346https://github.com/MicrosoftDocs/Windows-Admin-Center-Ideas-and-Feedback/issues/173#issuecomment-1120862346>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ARJ7TDREKVVKRHRMT4IVMX3VJDKULANCNFSM5USBBNJAhttps://github.com/notifications/unsubscribe-auth/ARJ7TDREKVVKRHRMT4IVMX3VJDKULANCNFSM5USBBNJA>.
You are receiving this because you were mentioned.Message ID: @.@.<mailto:@.@.mailto:***@***.******@***.***<mailto:***<EMAIL_ADDRESS>
Protect yourself from cyber fraud.
If you receive an email that appears to come from Barnett Waddingham providing
different bank details or informing of a change of account, it is unlikely to
be genuine. Do not reply to the email or act on any information contained in
it and contact us immediately by phone to check the account details. We will
not accept responsibility if you transfer money into an incorrect account.
Barnett Waddingham LLP is a body corporate with members to whom we refer
as "partners". A list of members can be inspected at the registered office.
Barnett Waddingham LLP (OC307678), BW SIPP LLP (OC322417), and Barnett
Waddingham Actuaries and Consultants Limited (06498431) are registered in
England and Wales with their registered office at 2 London Wall Place, London,
EC2Y 5AU. Barnett Waddingham LLP is authorised and regulated by the Financial
Conduct Authority. BW SIPP LLP is authorised and regulated by the Financial
Conduct Authority. Barnett Waddingham Actuaries and Consultants Limited is
licensed by the Institute and Faculty of Actuaries in respect of a range of
investment business activities.
This message and any attachments are confidential and are solely for the
individual to whom they are addressed. Any use of, or action taken in reliance
upon this information by any other person is prohibited. If you received this
information in error, please contact the sender immediately and delete the
material from any computer that may contain it and destroy any printed copies
you may have made. We have taken all reasonable precautions to ensure that no
viruses are transmitted with this message. However, we can accept no
responsibility for any loss or damage resulting directly or indirectly from
the use of this e-mail or its contents. Incoming and outgoing e-mails are
subject to scanning and may be intercepted by our e-mail administrators.

Reply to this email directly, view it on GitHub<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FWindows-Admin-Center-Ideas-and-Feedback%2Fissues%2F173%23issuecomment-1123428931&data=05|01|rwambua%40microsoft.com|3559176594334608eca808da3330e716|72f988bf86f141af91ab2d7cd011db47|1|0|637878582409497330|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=Aeoxvzbx%2Btwmoo22UKguiZ5fUqkpxKuCvOsmk%2FF8kGc%3D&reserved=0https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FWindows-Admin-Center-Ideas-and-Feedback%2Fissues%2F173%23issuecomment-1123428931&data=05|01|rwambua%40microsoft.com|3559176594334608eca808da3330e716|72f988bf86f141af91ab2d7cd011db47|1|0|637878582409497330|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=Aeoxvzbx%2Btwmoo22UKguiZ5fUqkpxKuCvOsmk%2FF8kGc%3D&reserved=0>, or unsubscribe<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAW5P2XP25CCO3PO6K5D5BGTVJN43XANCNFSM5USBBNJA&data=05|01|rwambua%40microsoft.com|3559176594334608eca808da3330e716|72f988bf86f141af91ab2d7cd011db47|1|0|637878582409497330|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=p2p3M1WAjP2%2BOc%2Bm95qq0oNaRcHGVFi5w7NrYjw3RgE%3D&reserved=0https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAW5P2XP25CCO3PO6K5D5BGTVJN43XANCNFSM5USBBNJA&data=05|01|rwambua%40microsoft.com|3559176594334608eca808da3330e716|72f988bf86f141af91ab2d7cd011db47|1|0|637878582409497330|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=p2p3M1WAjP2%2BOc%2Bm95qq0oNaRcHGVFi5w7NrYjw3RgE%3D&reserved=0>.
You are receiving this because you commented.Message ID: @.@.mailto:***<EMAIL_ADDRESS>—
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/Windows-Admin-Center-Ideas-and-Feedback/issues/173#issuecomment-1124590464, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ARJ7TDREK4HU4CQAT77OAX3VJSR3NANCNFSM5USBBNJA.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

Hey Peter!
I'd like to send you an invite.
Could you please send me an email on<EMAIL_ADDRESS>so that I can send it?
Kind regards

@.***
From: RebeccaMbulaMs @.>
Sent: 12 May 2022 14:11
To: MicrosoftDocs/Windows-Admin-Center-Ideas-and-Feedback @.>
Cc: Peter Roots @.>; Mention @.>
Subject: Re: [MicrosoftDocs/Windows-Admin-Center-Ideas-and-Feedback] WAC - frequent connection errors (Issue #173)
NOTE: This message originated outside Barnett Waddingham.

Hello,
Let me schedule a meeting for 9:00a.m. - 10:30 a.m. BST.
Could you email me your email so that I can share an invite with you?
Kind regards.
From: PeterRoots<EMAIL_ADDRESS>Sent: Thursday, May 12, 2022 11:00 AM
To: MicrosoftDocs/Windows-Admin-Center-Ideas-and-Feedback<EMAIL_ADDRESS>Cc: Rebecca Wambua<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/Windows-Admin-Center-Ideas-and-Feedback] WAC - frequent connection errors (Issue #173)
Thanks Rebecca
I start work at 9:00 BST and have a meeting at 10:30 so between them would be good. Otherwise sometime after 14:00 and before I finish work at 17:00
Thanks
Peter
From: RebeccaMbulaMs @.<mailto:@.mailto:***<EMAIL_ADDRESS>Sent: 12 May 2022 07:42
To: MicrosoftDocs/Windows-Admin-Center-Ideas-and-Feedback @.<mailto:@.mailto:***<EMAIL_ADDRESS>Cc: Peter Roots @.<mailto:@.mailto:***<EMAIL_ADDRESS>Mention @.<mailto:@.mailto:***<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/Windows-Admin-Center-Ideas-and-Feedback] WAC - frequent connection errors (Issue #173)
NOTE: This message originated outside Barnett Waddingham.

Hi Peter!
Thank you so much for reaching out to me about the Ajax error that you are experiencing.
I have been trying to get a software engineer to join in for our troubleshooting/bug discovery call so that we can be more effective.
What would be your best time on Friday?
Kind regards!
From: PeterRoots @.<mailto:@.<mailto:@.%3cmailto:@.mailto:***@***.***<mailto:***@***.***<mailto:***<EMAIL_ADDRESS>Sent: Wednesday, May 11, 2022 12:31 PM
To: MicrosoftDocs/Windows-Admin-Center-Ideas-and-Feedback @.<mailto:@.<mailto:@.%3cmailto:@.mailto:***@***.***<mailto:***@***.***<mailto:***<EMAIL_ADDRESS>Cc: Rebecca Wambua @.<mailto:@.<mailto:@.%3cmailto:@.mailto:***@***.***<mailto:***@***.***<mailto:***<EMAIL_ADDRESS>Comment @.<mailto:@.<mailto:@.%3cmailto:@.mailto:***@***.***<mailto:***@***.***<mailto:***<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/Windows-Admin-Center-Ideas-and-Feedback] WAC - frequent connection errors (Issue #173)
Hi Rebecca
I am running on BST (GMT+1) at the moment
I work Wed-Fri only between 9:00and 17:00 with a regular meeting on Wednesdays at 14:00-15:30
Happy to have a look at this with you but can be tricky as it an intermittent issue so may or may not show itself on demand :-)
Thanks
Peter
From: RebeccaMbulaMs @.<mailto:@.<mailto:@.%3cmailto:@.<mailto:@.%3cmailto:@.%3cmailto:@.%3cmailto:@.mailto:***@***.***<mailto:***@***.***<mailto:***@***.***<mailto:***@***.***<mailto:***@***.***<mailto:***@***.***<mailto:***<EMAIL_ADDRESS>Sent: 09 May 2022 10:24
To: MicrosoftDocs/Windows-Admin-Center-Ideas-and-Feedback @.<mailto:@.<mailto:@.%3cmailto:@.<mailto:@.%3cmailto:@.%3cmailto:@.%3cmailto:@.mailto:***@***.***<mailto:***@***.***<mailto:***@***.***<mailto:***@***.***<mailto:***@***.***<mailto:***@***.***<mailto:***<EMAIL_ADDRESS>Cc: Peter Roots @.<mailto:@.<mailto:@.%3cmailto:@.<mailto:@.%3cmailto:@.%3cmailto:@.%3cmailto:@.mailto:***@***.***<mailto:***@***.***<mailto:***@***.***<mailto:***@***.***<mailto:***@***.***<mailto:***@***.***<mailto:***<EMAIL_ADDRESS>Mention @.<mailto:@.<mailto:@.%3cmailto:@.<mailto:@.%3cmailto:@.%3cmailto:@.%3cmailto:@.mailto:***@***.***<mailto:***@***.***<mailto:***@***.***<mailto:***@***.***<mailto:***@***.***<mailto:***@***.***<mailto:***<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/Windows-Admin-Center-Ideas-and-Feedback] WAC - frequent connection errors (Issue #173)
NOTE: This message originated outside Barnett Waddingham.

Hello @PeterRoots<https://github.com/PeterRootshttps://github.com/PeterRoots<https://github.com/PeterRootshttps://github.com/PeterRoots<https://github.com/PeterRoots<https:/github.com/PeterRootshttps://github.com/PeterRoots<https:/github.com/PeterRoots>>> :)
My name is Rebecca, a Product Manager on Windows Admin Center.
I can't seem to reproduce this issue on my end :(
I understand that this must be a frustrating issue to deal with. Would you like to schedule a call to troubleshoot this?
If so, please send whatever time (as well as your time zone) that would work for you to: @.@.<mailto:@.@.<mailto:@.@.%3cmailto:@.@.<mailto:@.@.%3cmailto:@.@.%3cmailto:@.@.%3cmailto:@.@.mailto:***@***.******@***.***<mailto:***@***.******@***.***<mailto:***@***.******@***.***<mailto:***@***.******@***.***<mailto:***@***.******@***.***<mailto:***@***.******@***.***<mailto:***@***.******@***.***<mailto:***<EMAIL_ADDRESS>Kind regards!

Reply to this email directly, view it on GitHub<https://github.com/MicrosoftDocs/Windows-Admin-Center-Ideas-and-Feedback/issues/173#issuecomment-1120862346https://github.com/MicrosoftDocs/Windows-Admin-Center-Ideas-and-Feedback/issues/173#issuecomment-1120862346<https://github.com/MicrosoftDocs/Windows-Admin-Center-Ideas-and-Feedback/issues/173#issuecomment-1120862346https://github.com/MicrosoftDocs/Windows-Admin-Center-Ideas-and-Feedback/issues/173#issuecomment-1120862346>>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ARJ7TDREKVVKRHRMT4IVMX3VJDKULANCNFSM5USBBNJAhttps://github.com/notifications/unsubscribe-auth/ARJ7TDREKVVKRHRMT4IVMX3VJDKULANCNFSM5USBBNJA<https://github.com/notifications/unsubscribe-auth/ARJ7TDREKVVKRHRMT4IVMX3VJDKULANCNFSM5USBBNJAhttps://github.com/notifications/unsubscribe-auth/ARJ7TDREKVVKRHRMT4IVMX3VJDKULANCNFSM5USBBNJA<https://github.com/notifications/unsubscribe-auth/ARJ7TDREKVVKRHRMT4IVMX3VJDKULANCNFSM5USBBNJA<https:/github.com/notifications/unsubscribe-auth/ARJ7TDREKVVKRHRMT4IVMX3VJDKULANCNFSM5USBBNJAhttps://github.com/notifications/unsubscribe-auth/ARJ7TDREKVVKRHRMT4IVMX3VJDKULANCNFSM5USBBNJA<https:/github.com/notifications/unsubscribe-auth/ARJ7TDREKVVKRHRMT4IVMX3VJDKULANCNFSM5USBBNJA>>>.
You are receiving this because you were mentioned.Message ID: @.@.<mailto:@.@.<mailto:@.@.%3cmailto:@.@.<mailto:@.@.%3cmailto:@.@.%3cmailto:@.@.%3cmailto:@.@.mailto:***@***.******@***.***<mailto:***@***.******@***.***<mailto:***@***.******@***.***<mailto:***@***.******@***.***<mailto:***@***.******@***.***<mailto:***@***.******@***.***<mailto:***@***.******@***.***<mailto:***<EMAIL_ADDRESS>
Protect yourself from cyber fraud.
If you receive an email that appears to come from Barnett Waddingham providing
different bank details or informing of a change of account, it is unlikely to
be genuine. Do not reply to the email or act on any information contained in
it and contact us immediately by phone to check the account details. We will
not accept responsibility if you transfer money into an incorrect account.
Barnett Waddingham LLP is a body corporate with members to whom we refer
as "partners". A list of members can be inspected at the registered office.
Barnett Waddingham LLP (OC307678), BW SIPP LLP (OC322417), and Barnett
Waddingham Actuaries and Consultants Limited (06498431) are registered in
England and Wales with their registered office at 2 London Wall Place, London,
EC2Y 5AU. Barnett Waddingham LLP is authorised and regulated by the Financial
Conduct Authority. BW SIPP LLP is authorised and regulated by the Financial
Conduct Authority. Barnett Waddingham Actuaries and Consultants Limited is
licensed by the Institute and Faculty of Actuaries in respect of a range of
investment business activities.
This message and any attachments are confidential and are solely for the
individual to whom they are addressed. Any use of, or action taken in reliance
upon this information by any other person is prohibited. If you received this
information in error, please contact the sender immediately and delete the
material from any computer that may contain it and destroy any printed copies
you may have made. We have taken all reasonable precautions to ensure that no
viruses are transmitted with this message. However, we can accept no
responsibility for any loss or damage resulting directly or indirectly from
the use of this e-mail or its contents. Incoming and outgoing e-mails are
subject to scanning and may be intercepted by our e-mail administrators.

Reply to this email directly, view it on GitHub<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FWindows-Admin-Center-Ideas-and-Feedback%2Fissues%2F173%23issuecomment-1123428931&data=05|01|rwambua%40microsoft.com|3559176594334608eca808da3330e716|72f988bf86f141af91ab2d7cd011db47|1|0|637878582409497330|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=Aeoxvzbx%2Btwmoo22UKguiZ5fUqkpxKuCvOsmk%2FF8kGc%3D&reserved=0https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FWindows-Admin-Center-Ideas-and-Feedback%2Fissues%2F173%23issuecomment-1123428931&data=05|01|rwambua%40microsoft.com|3559176594334608eca808da3330e716|72f988bf86f141af91ab2d7cd011db47|1|0|637878582409497330|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=Aeoxvzbx%2Btwmoo22UKguiZ5fUqkpxKuCvOsmk%2FF8kGc%3D&reserved=0<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FWindows-Admin-Center-Ideas-and-Feedback%2Fissues%2F173%23issuecomment-1123428931&data=05|01|rwambua%40microsoft.com|3559176594334608eca808da3330e716|72f988bf86f141af91ab2d7cd011db47|1|0|637878582409497330|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=Aeoxvzbx%2Btwmoo22UKguiZ5fUqkpxKuCvOsmk%2FF8kGc%3D&reserved=0https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FWindows-Admin-Center-Ideas-and-Feedback%2Fissues%2F173%23issuecomment-1123428931&data=05|01|rwambua%40microsoft.com|3559176594334608eca808da3330e716|72f988bf86f141af91ab2d7cd011db47|1|0|637878582409497330|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=Aeoxvzbx%2Btwmoo22UKguiZ5fUqkpxKuCvOsmk%2FF8kGc%3D&reserved=0<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FWindows-Admin-Center-Ideas-and-Feedback%2Fissues%2F173%23issuecomment-1123428931&data=05|01|rwambua%40microsoft.com|3559176594334608eca808da3330e716|72f988bf86f141af91ab2d7cd011db47|1|0|637878582409497330|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=Aeoxvzbx%2Btwmoo22UKguiZ5fUqkpxKuCvOsmk%2FF8kGc%3D&reserved=0<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FWindows-Admin-Center-Ideas-and-Feedback%2Fissues%2F173%23issuecomment-1123428931&data=05|01|rwambua%40microsoft.com|3559176594334608eca808da3330e716|72f988bf86f141af91ab2d7cd011db47|1|0|637878582409497330|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=Aeoxvzbx%2Btwmoo22UKguiZ5fUqkpxKuCvOsmk%2FF8kGc%3D&reserved=0https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FWindows-Admin-Center-Ideas-and-Feedback%2Fissues%2F173%23issuecomment-1123428931&data=05|01|rwambua%40microsoft.com|3559176594334608eca808da3330e716|72f988bf86f141af91ab2d7cd011db47|1|0|637878582409497330|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=Aeoxvzbx%2Btwmoo22UKguiZ5fUqkpxKuCvOsmk%2FF8kGc%3D&reserved=0<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FWindows-Admin-Center-Ideas-and-Feedback%2Fissues%2F173%23issuecomment-1123428931&data=05|01|rwambua%40microsoft.com|3559176594334608eca808da3330e716|72f988bf86f141af91ab2d7cd011db47|1|0|637878582409497330|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=Aeoxvzbx%2Btwmoo22UKguiZ5fUqkpxKuCvOsmk%2FF8kGc%3D&reserved=0>>>, or unsubscribe<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAW5P2XP25CCO3PO6K5D5BGTVJN43XANCNFSM5USBBNJA&data=05|01|rwambua%40microsoft.com|3559176594334608eca808da3330e716|72f988bf86f141af91ab2d7cd011db47|1|0|637878582409497330|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=p2p3M1WAjP2%2BOc%2Bm95qq0oNaRcHGVFi5w7NrYjw3RgE%3D&reserved=0https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAW5P2XP25CCO3PO6K5D5BGTVJN43XANCNFSM5USBBNJA&data=05|01|rwambua%40microsoft.com|3559176594334608eca808da3330e716|72f988bf86f141af91ab2d7cd011db47|1|0|637878582409497330|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=p2p3M1WAjP2%2BOc%2Bm95qq0oNaRcHGVFi5w7NrYjw3RgE%3D&reserved=0<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAW5P2XP25CCO3PO6K5D5BGTVJN43XANCNFSM5USBBNJA&data=05|01|rwambua%40microsoft.com|3559176594334608eca808da3330e716|72f988bf86f141af91ab2d7cd011db47|1|0|637878582409497330|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=p2p3M1WAjP2%2BOc%2Bm95qq0oNaRcHGVFi5w7NrYjw3RgE%3D&reserved=0https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAW5P2XP25CCO3PO6K5D5BGTVJN43XANCNFSM5USBBNJA&data=05|01|rwambua%40microsoft.com|3559176594334608eca808da3330e716|72f988bf86f141af91ab2d7cd011db47|1|0|637878582409497330|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=p2p3M1WAjP2%2BOc%2Bm95qq0oNaRcHGVFi5w7NrYjw3RgE%3D&reserved=0<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAW5P2XP25CCO3PO6K5D5BGTVJN43XANCNFSM5USBBNJA&data=05|01|rwambua%40microsoft.com|3559176594334608eca808da3330e716|72f988bf86f141af91ab2d7cd011db47|1|0|637878582409497330|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=p2p3M1WAjP2%2BOc%2Bm95qq0oNaRcHGVFi5w7NrYjw3RgE%3D&reserved=0<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAW5P2XP25CCO3PO6K5D5BGTVJN43XANCNFSM5USBBNJA&data=05|01|rwambua%40microsoft.com|3559176594334608eca808da3330e716|72f988bf86f141af91ab2d7cd011db47|1|0|637878582409497330|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=p2p3M1WAjP2%2BOc%2Bm95qq0oNaRcHGVFi5w7NrYjw3RgE%3D&reserved=0https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAW5P2XP25CCO3PO6K5D5BGTVJN43XANCNFSM5USBBNJA&data=05|01|rwambua%40microsoft.com|3559176594334608eca808da3330e716|72f988bf86f141af91ab2d7cd011db47|1|0|637878582409497330|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=p2p3M1WAjP2%2BOc%2Bm95qq0oNaRcHGVFi5w7NrYjw3RgE%3D&reserved=0<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAW5P2XP25CCO3PO6K5D5BGTVJN43XANCNFSM5USBBNJA&data=05|01|rwambua%40microsoft.com|3559176594334608eca808da3330e716|72f988bf86f141af91ab2d7cd011db47|1|0|637878582409497330|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=p2p3M1WAjP2%2BOc%2Bm95qq0oNaRcHGVFi5w7NrYjw3RgE%3D&reserved=0>>>.
You are receiving this because you commented.Message ID: @.@.<mailto:@.@.<mailto:@.@.%3cmailto:@.@.mailto:***@***.******@***.***<mailto:***@***.******@***.***<mailto:***@***.******@***.***<mailto:***<EMAIL_ADDRESS>

Reply to this email directly, view it on GitHub<https://github.com/MicrosoftDocs/Windows-Admin-Center-Ideas-and-Feedback/issues/173#issuecomment-1124590464https://github.com/MicrosoftDocs/Windows-Admin-Center-Ideas-and-Feedback/issues/173#issuecomment-1124590464>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ARJ7TDREK4HU4CQAT77OAX3VJSR3NANCNFSM5USBBNJAhttps://github.com/notifications/unsubscribe-auth/ARJ7TDREK4HU4CQAT77OAX3VJSR3NANCNFSM5USBBNJA>.
You are receiving this because you were mentioned.Message ID: @.@.<mailto:@.@.mailto:***@***.******@***.***<mailto:***<EMAIL_ADDRESS>

Reply to this email directly, view it on GitHub<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FWindows-Admin-Center-Ideas-and-Feedback%2Fissues%2F173%23issuecomment-1124656724&data=05|01|rwambua%40microsoft.com|a3461637e63a4aacac2b08da33ed67f1|72f988bf86f141af91ab2d7cd011db47|1|0|637879392019228792|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=iBO8G3oetcmAW06yQI%2BUtQNCcd6ZUYat17tHA8S1xPk%3D&reserved=0https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FWindows-Admin-Center-Ideas-and-Feedback%2Fissues%2F173%23issuecomment-1124656724&data=05|01|rwambua%40microsoft.com|a3461637e63a4aacac2b08da33ed67f1|72f988bf86f141af91ab2d7cd011db47|1|0|637879392019228792|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=iBO8G3oetcmAW06yQI%2BUtQNCcd6ZUYat17tHA8S1xPk%3D&reserved=0>, or unsubscribe<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAW5P2XLVKJD5LD733QKYMYLVJS27ZANCNFSM5USBBNJA&data=05|01|rwambua%40microsoft.com|a3461637e63a4aacac2b08da33ed67f1|72f988bf86f141af91ab2d7cd011db47|1|0|637879392019228792|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=1RC47x155IBFB9lg1wBrji4jRrmTXQao%2FK7mSmuT%2FRk%3D&reserved=0https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAW5P2XLVKJD5LD733QKYMYLVJS27ZANCNFSM5USBBNJA&data=05|01|rwambua%40microsoft.com|a3461637e63a4aacac2b08da33ed67f1|72f988bf86f141af91ab2d7cd011db47|1|0|637879392019228792|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=1RC47x155IBFB9lg1wBrji4jRrmTXQao%2FK7mSmuT%2FRk%3D&reserved=0>.
You are receiving this because you commented.Message ID: @.@.mailto:***<EMAIL_ADDRESS>—
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/Windows-Admin-Center-Ideas-and-Feedback/issues/173#issuecomment-1124975623, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ARJ7TDSOQ35FAFQU7P5QYMTVJT7OVANCNFSM5USBBNJA.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>


chore(main): release 0.18.0

:robot: I have created a release beep boop
0.18.0 (2023-02-28)
Features

Workspaces: Create Workspace Notebooks (#216) (f4bf585)
Workspaces: workspace database exploration (#200) (c1036cd)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/BLSQ/openhexa-frontend/releases/tag/0.18.0 :sunflower:


[Search] extern search input

Issue description
Issue description
I would like to use the search-component with an extern search value. In our example the search term will come as url-parameter from another component. In our case the first result of the search, should be choosen and trigger the onSelect function as usual.
Discussion
We can implement the feature but there seem to be multple options for the general use case, that should be discussed:

If there is just a single result:

Just trigger onSelect for this

If there are multple results:

Just take the first result of the search and trigger onSelect
Do nothing
Show a warning
Show a warning, but still use the first result
Modify SearchSelectEvent  and return an Array of SearchResult with onSelect

If there is no result:

Do nothing
Show a warning
Modify SearchSelectEvent  and let SearchResult be null or an empty Array

And maybe there is an other case, that i didn't think of :)
I think modifying SearchSelectEvent to an SearchResult-Array would give the developer the most freedom, but would also be a breaking change.
Validations

[X] Read and follow our code of conduct
[X] Read the contributing guidelines
[X] Check that there isn't already a similar issue

We have the same requirement for another project.
Here are my thoughts:
I am not sure if we should trigger onSelect automatically since generally we don't know what the expected behavior might be.
Instead I would introduce onSearchCompleted which provides the search results and the developer can use it as it is desired.
Alternatively we could even introduce onSearchStateChanged => (searchState: FullSearchState) => void;.
Then the developer could react on every change. That would basically supersede the existing onSelect (and onInputChanged that we might introduce). But I think this would

be a big change to the current API
trigger many events (e.g. every time the user types in a single character) that might be hard to handle for the developer.


Issue when parsing long user identifiers. So users with long identifier 64-bit integer can't work with the bot.

[ 4][t 1][1638944335.698203086][HttpReader.cpp:625][#1171565679][!Connect:3840] Parse JSON parameters: "{"timestamp":"2021-12-08T06:18:55.696+0000","status":400,"error":"Bad Request","message":"JSON parse error: Numeric value<PHONE_NUMBER>) out of range of int (-2147483648 -<PHONE_NUMBER>); nested exception is com.fasterxml.jackson.databind.JsonMappingException: Numeric value<PHONE_NUMBER>) out of range of int (-2147483648 -<PHONE_NUMBER>)\n at [Source: (PushbackInputStream); line: 2, column: 46] (through reference chain: org.telegram.telegrambots.meta.api.objects.Update["message"]->org.telegram.telegrambots.meta.api.objects.Message["from"]->org.telegram.telegrambots.meta.api.objects.User["id"])","path":"/callback"}"

This is response of your server to a webhook request by Bot API. The exception happened in your code, so the code needs to be fixed. There are no issues in TDLib or Bot API.

Understand. Thanks.


Theory: Machine Learning

Just a small chapter, giving a general description of what machine learning is.


perf: Use babel-plugin-transform-runtime to reduce size

With this change, the cjs and es builds will refer to babel-runtime package to import the needed polyfills instead of inlining them on each file.
This adds babel-runtime as additional dependency, but I don't think we should be worried because the final size is going to be smaller than when we didn't rely on it.
Example of transpiled file before:
var _extends = Object.assign || function (target) { for (var i = 1; i < arguments.length; i++) { var source = arguments[i]; for (var key in source) { if (Object.prototype.hasOwnProperty.call(source, key)) { target[key] = source[key]; } } } return target; };

var _createClass = function () { function defineProperties(target, props) { for (var i = 0; i < props.length; i++) { var descriptor = props[i]; descriptor.enumerable = descriptor.enumerable || false; descriptor.configurable = true; if ("value" in descriptor) descriptor.writable = true; Object.defineProperty(target, descriptor.key, descriptor); } } return function (Constructor, protoProps, staticProps) { if (protoProps) defineProperties(Constructor.prototype, protoProps); if (staticProps) defineProperties(Constructor, staticProps); return Constructor; }; }();

function _classCallCheck(instance, Constructor) { if (!(instance instanceof Constructor)) { throw new TypeError("Cannot call a class as a function"); } }

function _possibleConstructorReturn(self, call) { if (!self) { throw new ReferenceError("this hasn't been initialised - super() hasn't been called"); } return call && (typeof call === "object" || typeof call === "function") ? call : self; }

function _inherits(subClass, superClass) { if (typeof superClass !== "function" && superClass !== null) { throw new TypeError("Super expression must either be null or a function, not " + typeof superClass); } subClass.prototype = Object.create(superClass && superClass.prototype, { constructor: { value: subClass, enumerable: false, writable: true, configurable: true } }); if (superClass) Object.setPrototypeOf ? Object.setPrototypeOf(subClass, superClass) : subClass.__proto__ = superClass; }

import React, { Component } from "react";
import createContext from "create-react-context";

and after:
import _extends from "babel-runtime/helpers/extends";
import _Object$getPrototypeOf from "babel-runtime/core-js/object/get-prototype-of";
import _classCallCheck from "babel-runtime/helpers/classCallCheck";
import _createClass from "babel-runtime/helpers/createClass";
import _possibleConstructorReturn from "babel-runtime/helpers/possibleConstructorReturn";
import _inherits from "babel-runtime/helpers/inherits";
import React, { Component } from "react";
import createContext from "create-react-context";

For sake of simplicity, the browser (umd) bundle is not going to require the babel-runtime dependency.

This looks great! 👍🎉This was just added to react-measure as well to reduce the bundle.


Debug impl changes

This is a common Debug implementation with a lot less codegen per enum required. You can now use format specifiers like {:02x?} to get BitFlags<T>(03, A | B), and custom Debug impls for the enum will be used in place of A or B if used.
Maybe we should explicitly add a 0x prefix for the hex case?
The internal BitFlagsFmt trait has been removed and replaced with a bitflags_type_name() method to get the same old BitFlags<T>(...) behaviour. A consequence of this is that the enum types must now be explicitly annotated with #[derive(Debug)] in order for debug to work.
This is partially based on #4 like most of my PRs to reduce conflicts/noise/etc, will rebase them all once that lands in some form.

Yeah, that part is ugly and will need more explanation. The story is basically:

The relevant RFC that introduced debug hex formatters proposed an API for it
Implementation of that API was punted off with a fixme pointing to a closed tracking issue
The PR implementing it states some of the reasons the API wasn't introduced

Which leaves the only decent stable way I know of determining the formatter used to be the flags() field with bits set by the discriminator of the FlagV1 enum.

Moved the strangeness into its own formatter struct so it's fairly isolated and documented. I wish it were possible to do things a bit better/neater, but the Formatter API is pretty inflexible. This is yet another case of std not dogfooding and just resorting to mutating private fields to achieve desired behaviour, which disadvantages external types since they obviously can't mimic the same approach.
Also implemented the binary/hex/etc. formatters for BitFlags, since it seems pretty reasonable to expect the bits to be explicitly formatted. I'm holding off on Display because I'm not sure there's much value in just formatting them as a decimal? I feel like this is actually a case where it'd be a good idea to bring back BitFlagsFmt as a public API to allow the downstream enum itself to impl Display however it wishes.

Good job! I don't see anything to improve here, making this perfect by at least one measure :)
By the way, would you like to add yourself to authors in Cargo.toml? Across the no_std support and this Debug implementation, you've done what feels like more work than I have since I started maintaining this crate.


question about Jquery Mobile

Is there a way to tweak this for use with jQuery mobile to keep the checkbox state?  Thank you!

Only the checkbox element's state (checked or not) will be cached. If you use a checkbox component, you may toggle its state manually.


Added option to retrieve the colors used in the QR code from the image.

Implementation for #73.

Awesome work on the PR. It's been a pretty busy week for me, but I'll give it a look soon.
Meanwhile in #77 I've added the options object for another option we needed to add, so you may be able to leverage some of the work there.

If you want faster iteration on this lint stuff you can just run npm run-script lint locally.

@cozmo It looks like the tests are failing due to how the objects are getting serialized? Not sure how to fix that...

Yeah, I'm not sure how to fix that. it seems to be caused by data type issues...

Those all sound good, I'll update all that soon. Changing the (QR)Color interface should fix the tests but, to confirm, you're OK with the way I implemented them?

For testing I added some checks for the color space transformations and effectively end-to-end-tests.ts but that only looks at color. For populating the test data I just added on to generate-test-data.ts but that might want to be broken out into a separate script.

Just left one final comment since I tried to merge this. but realized the conversions tests weren't actually doing anything. Right now there's a merge conflict on master, but feel free to ignore that, I'll handle it since I caused it. That said not really sure how best to fix these tests so would rather defer to you.

@cozmo Sorry for disappearing for so long! It's been a busy school year... If I finish up this pull request (I think I had more to do even though you approved it...), still up for merging it?


add more communications data into payload

DCWC-836 (Jira Issue)
Description
List of proposed changes:

added more communications data into payload

What to test for/How to test
no test needed
Addtional Notes

renaming branch

renaming branch


LSP formatters not used as fallback?

With elentok-format-on-save.nvim, I'm using:
return {
  "elentok/format-on-save.nvim",
  event = { "BufReadPre", "BufNewFile" },
  config = function()
    local format_on_save = require("format-on-save")
    local formatters = require("format-on-save.formatters")

    format_on_save.setup({
        c = formatters.lsp,
        cpp = formatters.lsp,
        json = formatters.lsp,
        jsonc = formatters.lsp,
        lua = formatters.lsp,
    })
  end,
}

and my files with these filetypes are formatted on saving.
The LSP I'm using:

Filetype
LSP

c, cpp
clangd

json, jsonc
json-lsp

lua
lua-language-server

For lua, I guess it's using CppCXY/EmmyLuaCodeStyle, which is the formatter from lua-language-server, as mentioned here.
With conform.nvim, when saving in a c, cpp, json, jsonc or lua file, no formatting is applied at all. My config:
return {
  "stevearc/conform.nvim",
  event = { "BufReadPre", "BufNewFile" },
  config = function()
    require("conform").setup({
    formatters_by_ft = {
      css = { "prettierd" },
      javascript = { "prettierd" },
      markdown = { "prettierd" },
      sh = { "shfmt" },
      yaml = { "yamlfmt" },
    },
    format_on_save = {
        timeout_ms = 500,
        lsp_fallback = true,
    },
    })
  end
}

Am I missing something? I would expect lsp_fallback = true to use the formatter from the relevant LSP like elentok-format-on-save.nvim does.

I'm actually going to keep this open. I agree that this is surprising behavior, and I think I may want to refactor some things to make it more predictable.


convert pipeline query result to JSON?

If I use aggregation pipeline. query result comes back as a dictionary instead of a mongo document object.
Is there a way to convert that dict result to goodjson format? because using bson.dumps produces inconsistent results with current goodjson format.

Unfortunately, there's no method atm, but I'm interested in implementing it.

thanks. I'll go through the code and see if I can contribute for that.

Hi guys, is there any updates about this ?
Thanks

Any updates?

any updates on this?


Restore MARL Benchmark

Restore MARL benchmark on the main branch.

[ ] Address #1131

TraCI connection error contributes to fixing the benchmark: #295

Can this issue be closed given that MARL benchmark code has been removed from the main SMARTS repository?


Fix s3 open()

"file exist" operation now is performed with boto3's head_object
before it was using list_object, that by default returns 1000 objects at maximum. The requested (existing) key may not be in the returned list. In any case the maximum number of objects must be known in advance, and listing all objects is a waste of resources.
solves https://github.com/sphuber/aiida-s3/issues/11
Some points to discuss on my side:

call or not call super().open(key)? In principle I think it should be called, but the additional test on file existence is a waste of communication. If this line is removed this implementation works in the same way and is more efficient.
we can possibly find a way to implement list_objects to list all the objects in the bucket, but this may be useless and expensive for the server. Is this feature needed anywhere?

Thank you @sphuber for the explanation. I agree on everything. If the method list_objects is used we should definitevely find a better solution.
Anyway I rebased on master, removed the modification to has_files, and checked that everything worked as expected for my workflow that triggered this issue.

Thanks a lot for your contribution @rikigigi ! Much appreciated


Binary Image Gets Corrupted When PUT Over FTP

Every image I PUT() to a server using FTP client gets corrupted.  I've tested with jpeg and png, all are damaged during transfer.  Some characters are missing and some are displaced:
    async sendImage(image) {         try {             const credentials = await getFtpCredentials(this.platform);             console.log('Sending files via FTP client');             return new Promise((resolve, reject) => {                 let ftpClient = new ftp();                 ftpClient.on('ready', () => {                     console.log(Putting ${image.path} onto server);                     // Set transfer type to binary                     ftpClient.binary(err => {                         if(err)                             reject(err);                         else                             // image.content is binary string data                             ftpClient.put(image.content, image.path, (err) => {                                 if (err) {                                     reject(err);                                 }                                 console.log('Closing FTP connection');                                 ftpClient.end();                                 resolve(FTP PUT for ${image.path} successful!`);
});
                });
            });
            console.log('Connecting to FTP server');
            ftpClient.connect(credentials);
        });

`
Here's a copy of the image before sending over FTP and here's a corrupted copy after.  Please compare the two using a binary editor or regular notepad.  I hope this issue can be resolved as I like this library!
Thanks!

Have you found a workaround?

@besserwisser No, I'm using the basic-ftp library instead.


Add UserInfo claims to User.Claims

Would it be useful add an option that makes the middleware fetch the UserInfo endpoint and add these claims to the principal claims collection?
Many of my APIs are already doing this but on a whole new step.
I am willing to contribute if you thing this is relevant to the project and if I'm doing this the right way.

Userinfo is not for an API to consume. It's meant for a client to consume.

Please, help me understand the whole picture:
Why wouln't be appropriate for an API to consume the UserInfo endpoint?
How are the APIs suppose fetch the info about the token's user?

Please, help me understand the whole picture:

You will have to spend the time and read the specs, unless you're looking to hire us for consulting.

How are the APIs suppose fetch the info about the token's user?

Introspection or the claims are in the token itself.

I am realizing that I shouldn't call the UserInfo endpoint from the API, but rather configure my API's scope to include some the claims I want to know about.
Thanks


chore: update requirements.txt to run on m1 w/pip

this is similar to #334, which updates numpy and opencv-python similarly. however, there are several additional and necessary changes: updating torch to 1.12 (which adds support for mps, the whole point of this), and updating the k-diffusion repo to point to the mps fork

Confirmed this has helped me pass the pip install -r requirements.txt step on a M1 Mac; thank you!

Merged into development.


[Do not review] Fix failover test for swarm nodes

Trying to fixes issue #1505
Need to investigate the issue as we see failure only on CI.
Not able to repro the issue locally.
Have added more logging to help in debugging.

Closing this PR as this is dupicate of PR #1585 .


fix: srv binary missing message, add more detail

- What I did
Closes #950
- How I did it
- How to verify it
- Description for the changelog
fix: srv binary missing message, add more detail

Related: #745


Update the link of OWASP Top 10 list in security.txt

The latest version of OWASP Top 10 list is 2021, and OWASP has a page for this project. So referring to the project homepage is better than a specific version of it.

@grammy-jiang Thanks :+1: What do you think about using https://owasp.org/Top10/ instead?

Hi, @felixxm, both of them are okay to me:

from the url, both of them are not limited to only one yearly report
from the context in the document, readers will expect the page list some pullet points about security issues, and both of urls have these pullet points

So, if you prefer https://owasp.org/Top10/, I am okay to turn to this link.

Hi, @felixxm, updated!

@grammy-jiang Thanks :+1: Welcome aboard :boat:


Improve MITM detection during session establishment:

Even with TLS encrypted connections, it is possible for a determined attacker to mount certain types of relatively easy man-in-the-middle attacks which, if successful, could allow an attacker to tamper with messages exchanged between endpoints.
The risk can be mitigated if each side has a certificate issued by a CA that the other side trusts. In the context of a decentralized and permissionless network, this is neither reasonable nor desirable.
To prevent this problem all we need is to allow the two endpoints, A and B, to be able to independently verify that they are connected to each other over a single end-to-end TLS session, instead of separate TLS sessions with the attacker bridges.
The protocol level handshake implements this security check by using digital signatures: each endpoint derives a fingerprint from the TLS session, which it signs with the private key associated with its own node identity. This strongly binds the TLS session to the identities of the two endpoints of the session.
This commit introduces a new fingerprint derivation that uses modern and standardized TLS exporter functionality, instead of the existing derivation whch uses OpenSSL APIs that are non-standard.
The change is backwards compatible and servers with this commit will still generate and verify old-style fingerprints, in addition to the new style fingerprints.
For a fuller discussion on this topic, please see:
https://github.com/openssl/openssl/issues/5509
https://github.com/ripple/rippled/issues/2413
This commit was previously introduced as #3929, which was closed. If merged, it also fixes #2413 (which had been closed as a 'WONTFIX').

High Level Overview of Change

Context of Change

Type of Change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Refactor (non-breaking change that only restructures code)
[ ] Tests (You added tests for code that already exists, or your new feature included in this PR)
[ ] Documentation Updates
[ ] Release

Test Plan
Running this against servers with and without this change and verifying that peer connections are established (e.g. by using the peers command) should be sufficient. Ideally, in addition to Linux, this should also be tested against servers running on the "compiles-on-but-it's-not supported" platforms: MacOS and Windows.

Testable: See Test Plan in the PR description.

Updated this branch to introduce directional cookies and to strongly bind the Instance-Cookie. It's ready for a review and, if approved, merging.

LGTM. There's the reference to a renamed section by the old section name and the line of debug code that got left in, but other than that, no issues except:
This code currently violates RFC 5705:

Label values beginning with "EXPERIMENTAL" MAY be used for private use without registration.  All other label values MUST be registered via Specification Required as described by RFC 5226

We can register our two labels, use experimental labels, or use existing registered labels whose uses do not conflict with ours.

@nbougalis at your convenience, please respond to the suggestions by ximinez


Haptic feedback on Android not working, vibration only

Describe the issue
Haptic feedback on Android is vibration and doesn't feel like Haptic.
Checked on Samsung devices mostly (a few Android versions same result).
Also, the Selection type isn't working at all.
Checked with React Native 0.71.12 and react-native-haptic-feedback versions 2.2.0 & 1.1.0.
Expected behavior
When trigger haptic feedback to get haptic and not vibration.
It's feels like react-native Vibration.
Expected to get result as on IOS devices.

I've also noticed this. I'm unable to to achieve the same Haptic feel on Android.


Submit is triggered when clicking on buttom to upload image... drag and drop does not trigger the submission

How can I ensure a submission is not trigged while uploading an image on click

<button
type="button"
className="custom-file-upload"
style={isDragging ? { color: 'red' } : undefined}
onClick={onImageUpload}
{...dragProps}
>

add type="button" to not trigger submission


fromRep for Any

The fromRep implementation for Any is incorrect. Getting it right is pretty important for the client part of ble, so I've been thinking about it, but I don't think it's possible without restricting it to some universe...

The client implementation goes via a different route now, so closing.


Implement an interface for configuration and metrics

We should implement some kind REST API to adjust the configuration (write the configuration file) and to show some metrics such as:

How much data has been transferred
System status
other...?

Feel free to assign to me.  I have some spare time now. Please point out a notion.so group for sharing the design. My idea is to use the simpler: https://github.com/julienschmidt/httprouter
HttpRouter and over there map the api. It's less 'invasive' than gogin.

It wouldb e really useful if we collect some statistics about the system, such as:

Status (if it is running, idle...)
amount of data transferred, this can be done with a counter in the MoveData function (this can be partial, like hourly or total)
It would be great to measure performance, such as the time spent in moving data
Don't know if we can also get info about the cpu time...

Here the initial design, please review it:
https://scrawny-newsstand-bd9.notion.site/REST-API-Metrics-fcf6e7f4cb6146e6b6bc9c0afc64fba0


Plugin Version Info + upgrade hooks

Provide a way to include something like package.json in the plugin sourceball so ExtPlug can show that info, and plugins can run code when a new version is run for the first time.
This probably requires more assumptions about plugin module names. (Related #13)

Obsolete as of 26c3afe.


refactor(contracts): Big refactor to avoid duplication moving forwards

This PR represents a pretty significant refactor to how we structure farmbots. I racked my brain for a while trying to figure out the "best" way to structure things to be able to support the widest possible set of underlying farms as possible, and couldn't quite get there. This refactor definitely isn't the best or most general way to structure things, but I think it's at least an improvement over the current setup.
The general idea is as follows:
RevoFarmBot is the base-most abstract class that all farmbots must implement. It, maybe surprisingly, does not define a virtual compound function, since compound may require different parameters from the caller depending on the underlying implementation. This class makes no assumptions about the underlying farm, or how swapping/minting liquidity occurs (or if it even occurs at all). The only real assumptions it makes is that the farm pays out some number of ERC20 reward tokens in exchange for staking an ERC20 token.
RevoUniswapStakingTokenStrategy narrows RevoFarmBot to supporting yield farms whose stakingToken is a typical IUniswapV2Pair. It both exchanges the reward tokens for LP constituent tokens, and mints LP, through an IUniswapV2Router02 contract, though not necessarily the same one for each operation. This class is still abstract, in that it makes no assumptions about the underlying farm beyond those made by RevoFarmBot. The value of having this intermediate abstract class is that this ought to be a relatively common pattern. It will work for all manner of Ubeswap farms, and should work for Sushiswap as well.
RevoUbeswapFarmBot is a farmbot that supports Ubeswap yield farms that use an IMoolaStakingRewards contract to stake LP and issue rewards. This inherits from RevoUniswapStakingTokenStrategy, and provides basically no new code(!) except for what is required to deposit, withdraw, and claim rewards from the underlying farm.
Another new feature is the placement of certain code into libraries. library/UniswapRouter.sol contains library code that performs Revo-specific operations against IUniswapV2Router02 contracts. library/MoolaStakingRewards.sol performs an identical role, but against IMoolaStakingRewards contracts. This should be helpful if we ever need to create farms out of new combinations of routers/liquidity-minting-contracts/underlying farms; there should be little-to-no duplication of code that interacts with these "underlying" contracts.
The file structure was also reorganized to be a bit cleaner, and a couple of files have been re-named. Note that this PR does not contain updated tests/mocks. I wanted to get some feedback that this all looks good before committing to changing the tests around.

btw, do tests still pass? and do the helper scripts still work? I'm ok with these getting fixed in a fast follow, but we shouldn't let them fall by the wayside


Update example.application.yml raw to new link of Lavalink github

Description

Checklist for all submissions

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
[x] Have you tested and reviewed your changes with confidence that everything works?
[x] Did you branch your changes and PR from that branch and not from your master branch?

If not, why?:

[ ] You verify that the start command applied does not use a shell script

[ ] If some script is needed then it is part of a current yolk or a PR to add one

[ ] The egg was exported from the panel

can be closed, because its outdated with this:
https://github.com/pelican-eggs/software/pull/9

overwritten by #9


Implement error handling

This PR adds error handling via failure. This implementation does however need some work on it as the generated errors doesn't seem matchable in it's current state.
TODO

Change fn(...) -> Result<_,Error> into fn(...) -> Result<_,FnSpecificError>
This should fix item 2, but I'm not sure.
Make matching more ergonomic and always possible
Add more tests

Part of #46 and #18

I'm not 💯 on implementing errors yet, but would the solution to match be to expose an SVDError enum to use that collects the implemented error types?

This may all be due to bad usage of failure, but an example of not being able to match on errors is this ignored test.
I am currently looking into implementing failure::Error manually instead of using the #[derive(Fail)].

Work is being reimplemented in the refactor branch


News 36: typo fix: s/FindAndReplace/FindAndDelete/

This newsletter correctly calls the function FindAndDelete() in most places, but for some reason I used the wrong name in three other places.
Just to make sure I hadn't forgotten something I knew during the writing of the newsletter, I checked both the Bitcoin Core source code and bip-cleanup to confirm that neither mentions a FindAndReplace() function.

ACK


There is a lack of clarity on using virtualenvs with the app directory structure

Python azure function apps have a recommended structure that leaves it unclear where the python virtual environment should live.  Python projects usually have it in the project root, but that doesn't seem to work seamlessly for a Python Function App.  See details below.
The recommended structure is:
__app__
  - my_first_function
  - my_second_function
  - shared_code
  - host.json
  - requirements.txt
- tests

If I do the following:

python -m venv .venv
./.venv/bin/activate
cd __app__
Start debugger

Error:
> Executing task: .venv/bin/python -m pip install -r requirements.txt <
/bin/bash: .venv/bin/python: No such file or directory
The terminal process terminated with exit code: 127

Basically, that debug task seems to expect the .venv to exist in __app__ directory and fails without it.  Note - running func host start from within __app__ works ok, but not the debugger.
Putting the virtual env in __app__ works, although it's a bit awkward to not have it in the project root.  It's especially confusing, since we'll have requirements-dev.txt at the root level still.
Regardless, since python function apps depend on requirements.txt, it'd be useful to have a clear recommendation around how to manage the virtual environment alongside it.
Thanks!

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

ID: d955d169-8fb8-c511-8911-3e49f95c5ce6
Version Independent ID: 8a3d927c-51ce-d7d4-e5d1-acd928826db2
Content: Python developer reference for Azure Functions
Content Source: articles/azure-functions/functions-reference-python.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: glenga

@jeffthink Thank you for your feedback! We will review and update as appropriate.

Hi @jeffthink,
We recently updated the documentation on Python folder structure which no longer requires app namespace. Please try it out https://docs.microsoft.com/en-us/azure/azure-functions/functions-reference-python#folder-structure.


Kernel32: Add more functions

The main additions here are:

Checking to see if a process is a 32-bit process running on 64-bit windows
Getting and setting thread priorities and boosts
Checking to see if the boot drive is virtualized (Only on recent releases? I've never seen it before)
A few random additions that weren't too hard

@retep998 Updated :) Could you also please bump kernel32 when you have time?


Fix messedup pagination links

Summarize
Pagination links before

after

closes #598

Testing 597

its not fixed yet

tested and looks good to me

Working fine

last link

all  scenarios works fine. (Y)

LGTM. Working on both desktop and mobile.


Ability to clear current response

Tell us about the task you want to perform and are unable to do so because the feature is not available
There should be a small recycle bin or clear button in the response section to clear the current response.

Hi @animator
I have implemented this functionality (have attached a demo video of it).
Below is the implementation of the ClearResponseButton. Unlike all the other buttons, it extends ConsumerWidget instead of Stateless/Stateful Widget. Before I open a PR, I wanted to confirm whether the this is allowed or not.
Thanks in advance
class ClearResponseButton extends ConsumerWidget {
  const ClearResponseButton({super.key});

  @override
  Widget build(BuildContext context, WidgetRef ref) {
    var sm = ScaffoldMessenger.of(context);
    return SizedBox(
      child: TextButton(
        style: TextButton.styleFrom(minimumSize: const Size(40, 40)),
        onPressed: () {
          final selectedId = ref.watch(selectedIdStateProvider);
          ref
              .read(collectionStateNotifierProvider.notifier)
              .clearResponse(selectedId!);
          sm.hideCurrentSnackBar();
          sm.showSnackBar(
            SnackBar(
              content: const Text('Response cleared'),
              action: SnackBarAction(
                label: 'Undo',
                onPressed: () {},
              ),
            ),
          );
        },
        child: const Icon(
          Icons.delete,
          size: 20,
        ),
      ),
    );
  }
}

https://github.com/foss42/apidash/assets/59914433/63de8050-1c73-478a-b97a-8580e9aa97c8

@mdmohsin7 Please open a PR for review.


Sticky scroll stops working when deleting all and undoing

Testing #156175
Repro steps:

Select all of the text in the file and delete it all
No sticky scroll persists, as expected.
CTRL+Z to undo. Sticky scroll didn't come back. :bug:

Fixed with: https://github.com/microsoft/vscode/pull/156306/commits/2cc280494ed8fd2429afff8b5ad2ec18ab1d1dc7


Suggestion: Translate "migliaia" to "mila" in Italian

In Italian, to say 10 thousand, we say "10mila" (diecimila).
It would be great to have that translation. Also, is there a way to have your humanize.po in your project folder and use that file for translations?
What versions are you using?

OS: Windows 11
Python: 3.11.4
Humanize: 4.7.0

"migliaia" was added in https://github.com/python-humanize/humanize/pull/97 by @aborruso, would you like to agree together what it should be and create a new PR if needed?

Also, is there a way to have your humanize.po in your project folder and use that file for translations?

Yes, see the instructions at https://github.com/python-humanize/humanize#localization to do something like humanize.i18n.activate("pt_BR", path="path/to/my/own/translation/").

Yes, see the instructions at https://github.com/python-humanize/humanize#localization to do something like humanize.i18n.activate("pt_BR", path="path/to/my/own/translation/").
The only thing that isn't clear to me is: how do I define a new translation, in which file extension/format?

We start with .po files (in https://github.com/python-humanize/humanize/tree/main/src/humanize/locale) and then during release run scripts/generate-translation-binaries.sh, which essentially runs this command to compile binary .mo files:
msgfmt --check -o path/to/humanize{.mo,.po}

Any more questions for this?


#1227 warning fix transfer

Thank you for your contribution to the KodaDot NFT gallery.
👇  _ Do a quick check before the merge.
PR type

[x] Bugfix
[ ] Feature
[ ] Refactoring

Before submitting Pull Request, please make sure:

[x] My contribution builds clean without any errors or warnings
[x] I've merged recent default branch -- main and I've no conflicts
[x] I've tried respect high code quality standards
[x] I've didn't break any original functionality
[ ] I've posted screenshot of demonstrated change in this PR

Optional

[x] I've tested it at </rmrk/collection/26902bc2f7c20c546a-1FVG7>
[ ] I've tested PR on mobile and everything works
[ ] I found edge cases

What's new?

[x] PR closes #1227
[x] Added a default value when store has empty values

Had issue bounty label ?

[x] Fill up your KSM address:
Payout

Community participation

[x] Are you at KodaDot Discord?

Screenshot

[ ] My fix has changed something on UI, a screenshot for others, is best to understand changes.

isAddressValid

@vikiival the address is correct tho, the issue is with this.chainProperties?.ss58Format , chainProperties is undefined during initialization

isAddressValid

@vikiival the address is correct tho, the issue is with this.chainProperties?.ss58Format , chainProperties is undefined during initialization

yeah because it's waiting for a connection. Is it possible to skip it, put the transaction into queue and dispatch once it's connected?

continue to #1263


hey

How to further filter based on the minimum number of likes when searching

There is not such possibility


Deoplete Source

I found a couple of projects to make deoplete work with Omnisharp:

Robzz/deoplete-omnisharp
gitlab.com/mixedCase/deoplete-omnisharp

The first one can't connect to the omnisharp server and the second one is slower that it should, also is unmaintained, a official support would be nice

Could you share you'r vimrc config?

Actually, I think I might be in the same boat as the links you mentioned. It's probably not optimal because I'm using omni func. This is my entire deoplete config.
Plug 'Shougo/deoplete.nvim', { 'do': ':UpdateRemotePlugins' }
"{{{
    let g:deoplete#enable_at_startup = 1

    let g:deoplete#sources = {}
    let g:deoplete#sources._=['buffer', 'ultisnips', 'file', 'dictionary']
    "let g:deoplete#sources.clojure=['omni', 'file']
    let g:deoplete#sources.clojure=['async_clj', 'file', 'dictionary', 'ultisnips']
    let g:deoplete#sources.cs = ['omni', 'file', 'buffer', 'ultisnips']

    let g:deoplete#omni#input_patterns = {}
    let g:deoplete#omni#input_patterns.cs = ['\w*']
    "let g:deoplete#omni#input_patterns.clojure = ['\w*']

    let g:deoplete#keyword_patterns = {}
    let g:deoplete#keyword_patterns.clojure =<EMAIL_ADDRESS>
    " Use smartcase.
    let g:deoplete#enable_smart_case = 1

    " <TAB>: completion.
    inoremap <expr><TAB>  pumvisible() ? "\<C-n>" : "\<TAB>"
    inoremap <expr><S-TAB>  pumvisible() ? "\<C-p>" : "\<TAB>"
    " <C-h>, <BS>: close popup and delete backword char.
    inoremap <expr><C-h> deoplete#smart_close_popup()."\<C-h>"
    inoremap <expr><BS>  deoplete#smart_close_popup()."\<C-h>"

    " <CR>: close popup and save indent.
    inoremap <silent> <CR> <C-r>=<SID>my_cr_function()<CR>
    function! s:my_cr_function() abort
      return deoplete#close_popup() . "\<CR>"
    endfunction
"}}}

And I also have this:
autocmd FileType cs setlocal omnifunc=OmniSharp#Complete

I think you are right though, out of the box support for sources would be better.

An out-of-the-box deoplete source was added by @stevearc in #392


Invalid entity errors during shift upload

All of a sudden we are getting multiple errors in the log that look like this:
Temporary error on shift item #21, will retry later: webhook_transfer.py, 67: HTTPError('422 Client Error: Unprocessable Entity for url: https://api.airtable.com/v0/appQ5XIu4UyWmXWAj/tblXentRNTHB13B39', '422 Client Error: Unprocessable Entity for url: https://api.airtable.com/v0/appQ5XIu4UyWmXWAj/tblXentRNTHB13B39 [Error: {\'type\': \'INVALID_VALUE_FOR_COLUMN\', \'message\': \'Field "email" cannot accept the provided value\'}]')

This looks to be due to someone changing the field type of the email field in the Shifts table to be a plain text field rather than a link field.  But debugging this led to noticing errors in the cache, reported as #64.


Build failure when pulled in via cargo-outdated

I try do define a Rust base image to be used in several CI pipelines. This is what a MWE looks like:
ARG RUST_VERSION
FROM rust:${RUST_VERSION}-slim-bullseye

# The Rust base images seem to be created only once. Thus, in order to prevent
# using outdated packages, we need to update the image.
RUN apt update \
    && apt full-upgrade -y \
    && apt install -y curl git libssl-dev pkg-config \
    && apt clean \
    && rm -rf /var/lib/apt/lists/*

RUN cargo install cargo-outdated

Note that I install curl and git via apt. Before adding curl the container build fine. After adding curl I got the following error message:
100.7    Compiling git2-curl v0.19.0
101.6 error[E0425]: cannot find value `__deserializer` in this scope
101.6    --> /usr/local/cargo/registry/src/index.crates.io-6f17d22bba15001f/cargo-0.76.0/src/cargo/core/features.rs:734:32
101.6     |
101.6 734 |     #[serde(deserialize_with = "deserialize_build_std")]
101.6     |                                ^^^^^^^^^^^^^^^^^^^^^^^ not found in this scope
101.6
108.8 For more information about this error, try `rustc --explain E0425`.
108.8 error: could not compile `cargo` (lib) due to 1 previous error
108.9 error: failed to compile `cargo-outdated v0.15.0`, intermediate artifacts can be found at `/tmp/cargo-installMAtqaR`.
108.9 To reuse those artifacts with a future compilation, set the environment variable `CARGO_TARGET_DIR` to that path.
------
Dockerfile:12
--------------------
  10 |         && rm -rf /var/lib/apt/lists/*
  11 |
  12 | >>> RUN cargo install cargo-outdated
  13 |
--------------------
ERROR: failed to solve: process "/bin/sh -c cargo install cargo-outdated" did not complete successfully: exit code: 101

I find that puzzling and wanted to report the bug here. If you think the responsibility is with cargo-outdated, let me know. I'll open the ticket there.

Which version of

curl
Rust toolchain
cargo-outdated
you were using or installing?

This does not look related to git2. The error is coming from building cargo-0.76.0 (which is quite an old version).

Thank you for the replies so far.
How can cargo be outdated if I am using the most recent Rust image? 1.82-slim-bullseye was published only four days ago.

Thank you for the hint. I will move this to cargo-outdated.


Help and input validation

allow for help from --help.
validate that the user provides --input and --output.  Don't use defaults here.

Thanks!
I would use "--input SOURCE --output DESTINATION" in the help message though, as brackets signify optional parameters.


BN_zero() is void and can't fail

This will break the build with LibreSSL 3.7.1 and later. In OpenSSL, BN_zero() only has a return value if OPENSSL_API_COMPAT < 0x00908000L, which is prehistoric.

This will break the build in the upcoming libcrypto bump that will happen within the next few days. If you update the port, then I don't need to patch it.


arm build please?

Raspberry Pi can't use :(

web3py install fails in raspberry pi due to this package not being available in Raspberry Pi.

I'm afraid I don't know how to support ARM builds right now. I build binaries through GitHub Actions. If anyone knows how to add Arm support I would be happy to merge such a PR.
This would be the place to start looking into I guess
https://github.com/cburgdorf/rusty-rlp/blob/41af02048f60a8ce4f4193a03c4b8f3a04b4491f/.github/workflows/main.yml#L44-L46
In the meantime, there is work under way to fall back to the slower Python based implementation for environments where this library is not available.
https://github.com/ethereum/pyrlp/pull/127

Hello @cburgdorf, I've been following up with your work on ethereum/pyrlp#127 and this is a real life saver. Thanks!
But when I try to install web3 from pip, it still gets the older version. I guess that's probably because web3 repo has not been updated for that yet. Do you suggest any quick, maybe dirty, solution for that?

@cburgdorf Thanks I really appreciate it. Will be waiting for that.

@Naheel-Azawy Can you try again. I think the error should be gone.

@cburgdorf Yep, I do confirm that web3 py was installed on my raspberry pi zero w with no errors using pyrlp. Thank you!
I was trying to perform some actual work with it but I'm now getting a ConnectionRefusedError. It works well on my localhost though. But anyway, I doubt this is related to our issue here. What I'm trying to say is that I couldn't actually test it in a real scenario yet. Will update you once I figure out what's going wrong.

@Naheel-Azawy Sounds good. Yes, the other error is most likely unrelated. This library is now entirely optional for py-rlp and needs to be explicitly installed via an extra (e.g. rlp[rust-backend]) and pretty much nothing else changed about the py-rlp from the previous version.


Sequence coverage Quality visualization doesn't display when launching from Mosaic using a single gene

Launch https://mosaic.chpc.utah.edu/#/projects/536/samples/ using the gene AIFM1 - gene should default to the X-linked recessive missense variant chrX:130140554 C->T
However, the Quality doesn't display

Click to a different variant in the gene and then click back to the X-linked variant and the visualization does display now

The visualization loads fine when launching gene.iobio from Mosaic using a gene list (can use Skeletal dysplasia panel gene list - which contains AIFM1)

Also, notice the coverage calculated is different depending on the mode launched... which is also not great

I just launched and the coverage visual seems to be fixed.
But there remains a difference between the coverage shown in the different panels. This is a clear error and needs to be fixed.

This is quite important to understand how the coverage value is inconsistent.

@AlistairNWard, the 55x showing in the coverage depth area chart in the Variants card is the bam depth. The 61x showing in the variant inspect card is the variant read count (alt + ref) in the vcf, reported by the variant caller.

But something strange happens. If I click on the variant symbol in the Variants card, the QC now shows the bam depth, not the total read count.


delve and go on grafana codebase error - decoding dwarf section info at offset 0x0: too short

Please answer the following before submitting your issue:
Note: Please include any substantial examples (debug session output,
stacktraces, etc) as linked gists.

What version of Delve are you using (dlv version)? 1.0.0-rc.2, Build: $Id: 5c7676404d10d52e16be57fea744a7312b831f0c
What version of Go are you using? (go version)? go1.9.2 darwin/amd64
What operating system and processor architecture are you using? macOS Sierra
What did you do? Trying to debug grafana codebase by executing command - dlv debug ./pkg/cmd/grafana-server/
What did you expect to see? expect to start the debugger
What did you see instead? Error - could not launch process: decoding dwarf section info at offset 0x0: too short

I have setup grafana and delve successfully and tried to debug, exec and attach delve to the process but the same error.
 Either stop stripping the debug symbols (flags -w and -s) or use an assembly level debugger.

@aarzilli
Now I built like below:
go build -o ./bin/grafana-server ./pkg/cmd/grafana-server
This would stop stripping debug symbols, right ?
dlv exec ./bin/grafana-server
could not launch process: decoding dwarf section info at offset 0x0: too short
Still getting same error. Please suggest how can I build to use the debugger.

Can you upload bin/grafana-server somewhere so I can take a look?

@aarzilli sorry for late reply. grafana-server is a binary file, not sure if that would be helpful. Can you please reopen this issue ?

grafana-server is a binary file, not sure if that would be helpful

it would. Or you can verify yourself if it has all the debug sections with readelf or gnu objdump. It should have __debug_info, __debug_line, __debug_abbrev and __debug_frame. If it doesn't it has been stripped.

I opened file using the command "gobjdump -x grafana-server".
I didn't find any of the words mentioned above (__debug_info, __debug_line, __debug_abbrev and __debug_frame) so seems that the debug info is stripped off.
I am trying to find if there is another way to compile the go code so that I can use delve debugger.
I am building the grafana master branch from here. I appreciate if you could do the same by following instructions and debug using the dlv, please do let me know.
I can't attach executables.
In the meanwhile, can you please point me to github GO project that works with dlv?

build.go:415 comment out b.WriteString("-w"). In the build function you will also want to append -gcflags=-N -l to args.

I am building with below command:
go build -gcflags="-N -l" -o ./bin/grafana-server ./pkg/cmd/grafana-server
still not working

strange, it should work

Do you mind, checking out the code base and doing it yourself. May be I am doing something wrong

May be this helps in debugging the issue:
gobjdump -x ./bin/grafana-server > a.txt
PFA a.txt
a.txt

@aarzilli any updates ?

Checked out grafana, I can confirm that building with go build -gcflags '-N -l' -o bin/grafana-server ./pkg/cmd/grafana-server does not produce a stripped executable (unlike the one you have).
This is what the start of gobjdump -x bin/grafana-server looks like for me:
./grafana-server:     file format mach-o-x86-64
./grafana-server
architecture: i386:x86-64, flags 0x00000012:
EXEC_P, HAS_SYMS
start address 0x000000000405eef0

Sections:
Idx Name          Size      VMA               LMA               File off  Algn
  0 __TEXT.__stubs 00000288<PHONE_NUMBER>001c40<PHONE_NUMBER>001c40  00001c40  2**1
                  CONTENTS, ALLOC, LOAD, READONLY, CODE
  1 __TEXT.__stub_helper 00000448<PHONE_NUMBER>001ec8<PHONE_NUMBER>001ec8  00001ec8  2**2
                  CONTENTS, ALLOC, LOAD, READONLY, CODE
  2 .text         00de4828<PHONE_NUMBER>002310<PHONE_NUMBER>002310  00002310  2**4
                  CONTENTS, ALLOC, LOAD, CODE
  3 __TEXT.__rodata 004958e9<PHONE_NUMBER>de6b40<PHONE_NUMBER>de6b40  00de6b40  2**5
                  CONTENTS, ALLOC, LOAD, READONLY, CODE
  4 __TEXT.__typelink 0000d7cc<PHONE_NUMBER>27c440<PHONE_NUMBER>27c440  0127c440  2**5
                  CONTENTS, ALLOC, LOAD, READONLY, CODE
  5 __TEXT.__itablink 00001be8<PHONE_NUMBER>289c10<PHONE_NUMBER>289c10  01289c10  2**3
                  CONTENTS, ALLOC, LOAD, READONLY, CODE
  6 __TEXT.__gosymtab 00000000<PHONE_NUMBER>28b7f8<PHONE_NUMBER>28b7f8  0128b7f8  2**0
                  CONTENTS, ALLOC, LOAD, READONLY, CODE
  7 __TEXT.__gopclntab 0065cfcd<PHONE_NUMBER>28b800<PHONE_NUMBER>28b800  0128b800  2**5
                  CONTENTS, ALLOC, LOAD, READONLY, CODE
  8 .cstring      0000614d<PHONE_NUMBER>8e87d0<PHONE_NUMBER>8e87d0  018e87d0  2**4
                  CONTENTS, ALLOC, LOAD, READONLY, DATA
  9 .const        00003c62<PHONE_NUMBER>8ee920<PHONE_NUMBER>8ee920  018ee920  2**4
                  CONTENTS, ALLOC, LOAD, READONLY, DATA
 10 __TEXT.__unwind_info 00000a6c<PHONE_NUMBER>8f2584<PHONE_NUMBER>8f2584  018f2584  2**2
                  CONTENTS, ALLOC, LOAD, READONLY, CODE
 11 __DATA.__got  00000020<PHONE_NUMBER>8f3000<PHONE_NUMBER>8f3000  018f3000  2**3
                  CONTENTS, ALLOC, LOAD, DATA
 12 __DATA.__nl_symbol_ptr 00000010<PHONE_NUMBER>8f3020<PHONE_NUMBER>8f3020  018f3020  2**3
                  CONTENTS, ALLOC, LOAD, DATA
 13 __DATA.__la_symbol_ptr 00000360<PHONE_NUMBER>8f3030<PHONE_NUMBER>8f3030  018f3030  2**3
                  CONTENTS, ALLOC, LOAD, DATA
 14 .const_data   00002170<PHONE_NUMBER>8f3390<PHONE_NUMBER>8f3390  018f3390  2**4
                  CONTENTS, ALLOC, LOAD, DATA
 15 __DATA.__noptrdata 0003f0e1<PHONE_NUMBER>8f5500<PHONE_NUMBER>8f5500  018f5500  2**5
                  CONTENTS, ALLOC, LOAD, DATA
 16 .data         00012f70<PHONE_NUMBER>934600<PHONE_NUMBER>934600  01934600  2**5
                  CONTENTS, ALLOC, LOAD, DATA
 17 .bss          001a4198<PHONE_NUMBER>947580<PHONE_NUMBER>947580  00000000  2**5
                  ALLOC
 18 __DATA.__noptrbss 00003f18<PHONE_NUMBER>aeb720<PHONE_NUMBER>aeb720  00000000  2**5
                  ALLOC
 19 __DATA.__common 00000010<PHONE_NUMBER>aef638<PHONE_NUMBER>aef638  00000000  2**3
                  ALLOC
 20 .debug_line   001f5d2b<PHONE_NUMBER>e38000<PHONE_NUMBER>e38000  01948000  2**0
                  CONTENTS, DEBUGGING
 21 .debug_pubnames 002d2d4d<PHONE_NUMBER>02dd2b<PHONE_NUMBER>02dd2b  01b3dd2b  2**0
                  CONTENTS, DEBUGGING
 22 .debug_pubtypes 000e8624<PHONE_NUMBER>300a78<PHONE_NUMBER>300a78  01e10a78  2**0
                  CONTENTS, DEBUGGING
 23 .debug_ranges 0004d1a0<PHONE_NUMBER>3e909c<PHONE_NUMBER>3e909c  01ef909c  2**0
                  CONTENTS, DEBUGGING
 24 .debug_aranges 00071c20<PHONE_NUMBER>43623c<PHONE_NUMBER>43623c  01f4623c  2**0
                  CONTENTS, DEBUGGING
 25 .debug_info   003ab18c<PHONE_NUMBER>4a7e5c<PHONE_NUMBER>4a7e5c  01fb7e5c  2**0
                  CONTENTS, DEBUGGING
 26 .debug_frame  001484f4<PHONE_NUMBER>852fe8<PHONE_NUMBER>852fe8  02362fe8  2**0
                  CONTENTS, DEBUGGING
 27 .debug_loc    0018284c<PHONE_NUMBER>99b4dc<PHONE_NUMBER>99b4dc  024ab4dc  2**0
                  CONTENTS, DEBUGGING
 28 .debug_abbrev 000008f2<PHONE_NUMBER>b1dd28<PHONE_NUMBER>b1dd28  0262dd28  2**0
                  CONTENTS, DEBUGGING
 29 .debug_str    0038642f<PHONE_NUMBER>b1e61a<PHONE_NUMBER>b1e61a  0262e61a  2**0
                  CONTENTS, DEBUGGING
 30 __DWARF.__apple_names 00104e94<PHONE_NUMBER>ea4a49<PHONE_NUMBER>ea4a49  029b4a49  2**0
                  CONTENTS, ALLOC, LOAD, DATA
 31 __DWARF.__apple_namespac 00000024<PHONE_NUMBER>fa98dd<PHONE_NUMBER>fa98dd  02ab98dd  2**0
                  CONTENTS, ALLOC, LOAD, DATA
 32 __DWARF.__apple_types 000629d6<PHONE_NUMBER>fa9901<PHONE_NUMBER>fa9901  02ab9901  2**0
                  CONTENTS, ALLOC, LOAD, DATA
 33 __DWARF.__apple_objc 00000024<PHONE_NUMBER>00c2d7<PHONE_NUMBER>00c2d7  02b1c2d7  2**0
                  CONTENTS, ALLOC, LOAD, DATA

Can not reproduce and even if I could it wouldn't be a delve bug.
If you do manage to build note that this program is also affected by #852.

@komalvmehta Did you work out what was doing this?

No I didn't. Seemed like a bug because of my OS.

But when I downupgrade the go version to 1.9.4 , it could debug normally. Go version 1.10 does not work

@komalvmehta
I am facing exact same issue and I am on macOS Sierra. Did you find out the resolution for the "decoding dwarf section info at offset 0x0: too short" issue?

I have spent lot of time to get it work on grafana 4.4.3.. but nothing
worked... I am upgrading to grafana V5.. will try it out later
On Sat, Mar 31, 2018 at 3:34 AM, prathibha-cb<EMAIL_ADDRESS>wrote:

@komalvmehta https://github.com/komalvmehta
I am facing exact same issue and I am on macOS Sierra. Did you find out
the resolution for the "decoding dwarf section info at offset 0x0: too
short" issue?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/derekparker/delve/issues/1006#issuecomment-377683448,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFE9rSHy4xKfNKTNnQVcaooId0pLWervks5tj1uygaJpZM4QQTXU
.


AWS Lambda not reporting URL

Using SDK with Django.
The lambda function traces don't report the URL on the top level segment, looking at the raw data it seems that the URL is being set in the subsegments. Is there any way to call put_http_meta on the root Lambda segment through application code?
I tried extending the middleware, grabbing the current segment and setting the http metadata, but this returns the facade segment, which can't be mutated.

Hi @rajbeard
Thanks for bringing up this issue. The Lambda root segment is indeed immutable. There is no way to modify it. The only place to put http metadata is on the custom subsegment. It is indexed and queryable as same. Would you mind sharing your use case that only works on segment level?

Hey @shengxil
We manage multiple content oriented websites. It's useful for us to be able to quickly see which pages are causing poor performance, so that we can identify common chokepoints and make tweaks.
The XRay console is not reporting the URLs (or any of the other metadata) for each page. Instead, they are just blank. Locally, the URLs are correctly displayed inside of the console. Looking at the data payloads, the difference seems to be because the top level segment has that metadata in local development environments.

Hi rajbeard, that is indeed a valid concern. Unfortunately at this moment we don't have any workaround to put HTTP URL at the Lambda root segment. We will work with AWS Lambda team to address and solve this issue. Please stay tuned with us.

@shengxil Any updates on this? Thanks.

Hi!
As a workaround for the Lambda root segment immutability, I was able to manually create segments referencing the root segment I receive in an SQS message (attributes).
This SDK seems to prohibit using xray_recorder.begin_segment to start a segment if being called inside a Lambda (as shown here).
Is there a workaround that could be used here or should I use boto / direct API calls?
Thanks.

Recently we migrate our application to Lambda Urls and stop using API Gateways, and find out xray stop showing Method and Url for traces.

Active tracing is enabled
The IAM role has xray:* permission
We can see Method and URL at the service segment after we open the trace (aws-xray-sdk-python added them)
The Method and URL is empty on the trace list
We can't filter traces by method or url

Looks like AWS Lambda Urls did not report Method and URL to XRay like what API Gateways did, and there is noway to call put_http_meta on the root segment.
One solution is adding annotation like #348 and use it instead of http meta, but it's not very convenient.
If you know any workround please tell us.

Thanks for raising this issue. If you can provide the xray trace raw data after using Lambda URL it would be great helpful.
We can investigate whether there is workaround or X-Ray should improve trace summary.

Thanks for raising this issue. If you can provide the xray trace raw data after using Lambda URL it would be great helpful. We can investigate whether there is workaround or X-Ray should improve trace summary.

Hello, this is the raw data of our http server using lambda urls standalone, some information are masked.
xray-lambda-urls.txt
There are URL and HTTP Method metadata in the Invocation segment, it's added from aws-xray-sdk-python, the root segment has none http metadata. And the trace list only recognize http metadata in root segment.

We have raised a ticket to AWS support last week, they confirm Lambda URLs did not report http metadata currently, but they will add this to their feature request list.

Forward this question to AWS Lambda monitoring.
Currently user can only filter resource_arn instead.

Hello, do you have any update on this? Working with lambdas behind HTTP API Gateway is difficult without this.
Thanks

Similarily it's betty annoying when working with Lambda Function URLs, as we can not see the called path from the overview page.


Migrate code structure to kubebuilder v1.0.x

kubebuilder 1.0.0 introduces big architectural change in the project/code structure. 1.0.0 projects uses client and controller libraries developed under controller-runtime repo. It uses tools from controller-tools repo for scaffolding and manifests (CRD/RBAC) generation.
1.0.0 will continue to support projects generated using older version (pre 1.0.0 version) of Kubebuilder, but we would highly recommend migrating to newer version. Follow instructions for migration your project to 1.0.0 version.

I know this is not a urgent issue for us as of now. just adding it to backlog.
/cc @marun @gyliu513 @kubernetes-sigs/federation-wg

Thanks @shashidharatd .
There is a WIP PR here https://github.com/kubernetes-sigs/federation-v2/pull/148 , hope we can get more comments from @marun to see when we can do the migration.

@gyliu513 Upgrading the binaries is fine.  Migrating to the new client-less framework should wait until after #60, which I'll be tackling after #216 is complete.

@marun yes, I only created PR https://github.com/kubernetes-sigs/federation-v2/pull/250 to update binaries based on your comments.

I think the next steps for this issue are:

Replacing all calls to the generated clients with equivalent calls to the controller-runtime generic client
Removing the generated clients (and the +genclient annotation on the types to prevent regeneration)

Here is an example of a call to a generated client:
fedClient := fedclientset.NewForConfigOrDie(kubeConfig).
typeConfig, err := fedClient.CoreV1alpha1().FederatedTypeConfigs(namespace).Get(name, metav1.GetOptions{})

Here is an equivalent call with the generic client:
// Assumes import of:
//    - "context"
//    - "sigs.k8s.io/controller-runtime/pkg/client"

genericClient, err := client.New(kubeConfig, client.Options{})
if err != nil {
...
}
typeConfig := &fedv1a1.FederatedTypeConfig{}
key := client.ObjectKey{Name: name, Namespace: namespace}
err := genericClient.Get(context.Background(), key, typeConfig)

This is addressed with https://github.com/kubernetes-sigs/federation-v2/pull/716


Don't use smartquotes in localized error messages

TypeScript Version:  2.6.0-dev.2016
Code
// @ts-check
function foo() {
    var a = 1
    a = '123'
}

Start tsserver with --local chs
Bug:
Here's the error in english:

and here's the localized one:

Notice that this one replaces the single quote ' with a double quote ". The double quotes are also  smart quotes instead of regular ascii double quotes, which is odd looking in this context. I'm not sure if this was by design

That is what the localizes for this language chose to put in there. we really have no control over that. @danyeh any thoughts here?

@mjbvz @mhegazy , from pure linguistic perspective, these double quotes are right which match language style and usage. Does this break functionality or break intended meaning? If so, we can revert back to be same as English. Let us know.
@janbaltus @joinliu2016, we may need to change translation based on the answer.

Does this break functionality or break intended meaning?

I do not think so. I beleive this is @mjbvz stylistic observation.

Just to be clear. @danyeh you know best. if you believe this is the right quote style for the language then there is nothing we need to change here.

Then it is by design. For information, here is where to download language style guide. https://www.microsoft.com/en-us/language/StyleGuides

thanks!

Thanks for the additional info. My concern was that, in english at least, smartquotes are more for text. They are not used often in code and will break some languages if you try to use them in place of ascii double quotes


Hi @pviswanathan  The extension (Auto Text Expander for Google Chrome Official

Hi @pviswanathan  The extension (Auto Text Expander for Google Chrome Official
1.10.4) was just marked with malware again, and it's not reverting back by just leaving it there. I have also lost my information. Please help.

I’m terribly sorry that you are seeing this message. We are in the process of resolving this with Google. We should be back in the store, I request you to not delete the app in the meantime as your data will unfortunately be lost if you do so.

Hi @pviswanathan It seems to be back up and working now. Thank you for your help :-)


Update main.js

As of Redux 4.2. 0, which was released April 2022, Redux has deprecated its createStore API.
Instead one can import legacy_createStore as createStore for the application to run in harmony without any additional warnings or polyfills

Kindly approve the PR, so that the future learner will face no issues while trying the demonstration in the official documentation