error: 'Stop timeout' requires API version 1.25, but the Docker Daemon API is version 1.24

Question:
I am running Portainer-docker v2.00. I pulled the image yesterday.
I am trying to 'create a stack' using the internal web editor. I pasted my docker-compose.yaml into the editor and hit 'deploy the stack'.
I get the error: 'Stop timeout' requires API version 1.25, but the Docker Daemon API is version 1.24.
I am running it on debian buster.
docker version
Client: Docker Engine - Community
Version:           20.10.1
API version:       1.41
Go version:        go1.13.15
Git commit:        831ebea
Built:             Tue Dec 15 04:34:48 2020
OS/Arch:           linux/amd64
Context:           default
Experimental:      true
Server: Docker Engine - Community
Engine:
Version:          20.10.1
API version:      1.41 (minimum version 1.12)
Go version:       go1.13.15
Git commit:       f001486
Built:            Tue Dec 15 04:32:45 2020
OS/Arch:          linux/amd64
Experimental:     false
containerd:
Version:          1.4.3
GitCommit:        269548fa27e0089a8b8278fc4fc781d7f65a939b
runc:
Version:          1.0.0-rc92
GitCommit:        ff819c7e9184c13b7c2607fe6c30ae19403a7aff
docker-init:
Version:          0.19.0
GitCommit:        de40ad0
PS
Come chat with us on Slack http://portainer.io/slack/
This leads nowhere...

did you get a fix for that ?

did you get a fix for that ?

yeah, I removed the offending line from the docker-compose.yaml. "stop_grace_period: 30s"
I think, with no evidence that portainer does not like being run as a non-root user.

Ticket update by Amet Doohan<EMAIL_ADDRESS>Hi @tserversbfs,
can you show me your docker-compose.yml ? if it's fixed, can you show us for
workaround this?

Ticket update by Amet Doohan<EMAIL_ADDRESS>Hi @tserversbfs,
can you show me your docker-compose.yml ? if it's fixed, can you show us for
workaround this?

i just remove the "stop_grace_period: 30s" line as well

i just remove the "stop_grace_period: 30s" line as well

Sorry, but I do not have that config file anymore, but the command at issue was:
https://docs.docker.com/compose/compose-file/compose-file-v2/#stop_grace_period
As I said in my original message: I removed the line and the problem went away.

Sorry, but I do not have that config file anymore, but the command at issue was:
https://docs.docker.com/compose/compose-file/compose-file-v2/#stop_grace_period
As I said in my original message: I removed the line and the problem went away.

Ticket update by Amet Doohan<EMAIL_ADDRESS>Thanks @tserversbfs , will close this issue with workaround remove the
"stop_grace_period: 30s" line

Ticket update by Amet Doohan<EMAIL_ADDRESS>Thanks @tserversbfs , will close this issue with workaround remove the
"stop_grace_period: 30s" line

Ticket update by Microsoft Outlook<EMAIL_ADDRESS>[https://products.office.com/en-us/CMSImages/Office365Logo_Orange.png?version=b8d100a9-0a8b-8e6a-88e1-ef488fee0470]
Your message to<EMAIL_ADDRESS>couldn't be delivered.
tserversbfs wasn't found at github.com.
hello   Office 365      tserversbfs
Action Required                 Recipient
Unknown To address
How to Fix It
The address may be misspelled or may not exist. Try one or more of the following:

Send the message again following these steps: In Outlook, open this non-delivery report (NDR) and choose Send Again from the Report ribbon. In Outlook on the web, select this NDR, then select the link "To send this message again, click here." Then delete and retype the entire recipient address. If prompted with an Auto-Complete List suggestion don't select it. After typing the complete address, click Send.
Contact the recipient (by phone, for example) to check that the address exists and is correct.
The recipient may have set up email forwarding to an incorrect address. Ask them to check that any forwarding they've set up is working correctly.
Clear the recipient Auto-Complete List in Outlook or Outlook on the web by following the steps in this article: Fix email delivery issues for error code 5.1.1 in Office 365https://go.microsoft.com/fwlink/?LinkId=389363, and then send the message again. Retype the entire recipient address before selecting Send.

If the problem continues, forward this message to your email admin. If you're an email admin, refer to the More Info for Email Admins section below.
Was this helpful? Send feedback to Microsofthttps://go.microsoft.com/fwlink/?LinkId=525920.

More Info for Email Admins
Status code: 550 5.1.1
This error occurs because the sender sent a message to an email address outside of Office 365, but the address is incorrect or doesn't exist at the destination domain. The error is reported by the recipient domain's email server, but most often it must be fixed by the person who sent the message. If the steps in the How to Fix It section above don't fix the problem, and you're the email admin for the recipient, try one or more of the following:
The email address exists and is correct - Confirm that the recipient address exists, is correct, and is accepting messages.
Synchronize your directories - If you have a hybrid environment and are using directory synchronization make sure the recipient's email address is synced correctly in both Office 365 and in your on-premises directory.
Errant forwarding rule - Check for forwarding rules that aren't behaving as expected. Forwarding can be set up by an admin via mail flow rules or mailbox forwarding address settings, or by the recipient via the Inbox Rules feature.
Mail flow settings and MX records are not correct - Misconfigured mail flow or MX record settings can cause this error. Check your Office 365 mail flow settings to make sure your domain and any mail flow connectors are set up correctly. Also, work with your domain registrar to make sure the MX records for your domain are configured correctly.
For more information and additional tips to fix this issue, see Fix email delivery issues for error code 550 5.1.1 in Office 365https://go.microsoft.com/fwlink/?LinkId=389363.
Original Message Details
Created Date:   1/18/2021 4:01:07 AM
Sender Address<EMAIL_ADDRESS>Recipient Address<EMAIL_ADDRESS>Subject:        Re: error: 'Stop timeout' requires API version 1.25, but the Docker Daemon API is version 1.24. #QUE00000271
Error Details
Reported error: 550-5.1.1 The email account that you tried to reach does not exist. Please try 550-5.1.1 double-checking the recipient's email address for typos or 550-5.1.1 unnecessary spaces. Learn more at 550 5.1.1 https://support.google.com/mail/?p=NoSuchUser mp17si19061762pjb.26 - gsmtp
DSN generated by:       ME2PR01MB5684.ausprd01.prod.outlook.com
Remote server:  mx.google.com
Message Hops
HOP     TIME (UTC)      FROM    TO      WITH    RELAY TIME
1       1/18/2021
4:01:07 AM      ip-10-10-18-71.happyfox v2app8.mail.happyfox.com        ESMTPS  *
2       1/18/2021
4:01:15 AM      v2app8.mail.happyfox.com MW4PR03CA0410.namprd03.prod.outlook.com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384)    8 sec
3       1/18/2021
4:01:15 AM      MEAPR01MB2631.ausprd01.prod.outlook.com MEAPR01MB2631.ausprd01.prod.outlook.com mapi    *
4       1/18/2021
4:01:15 AM      MEAPR01MB2631.ausprd01.prod.outlook.com ME2PR01MB5684.ausprd01.prod.outlook.com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384)    *
Original Message Headers
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none;
b=SGU+JqvzUy6Noiu8Csj/p+p1w9Ptkxyvs3zcf0QxGEbQ95DxJjH8K3V01zkNs3uRV1lmInfQPXVXp2nEc6ODkzzuY+tJlp/+VtG9JAoL9lnU6fIQskT+TnNniIGMz8TcIJO0P7RWBRJAlAIp0Ul7RhLRb36Pt2X7n8DXfBjMOTm4GxtsqSZ/glEABAeraGgC3rXnrPznCba+PCFPHEsgiD2coJxDZfKQdvJU8jlpwXWt6v6sqMr/2+fmUkANu2SZrihwnaiC2db3tvctJzQ//PxtH8vkGjwbUogvWfsnrkAZpnTuFQ+jNH/7maN6Lf1mPNNOcLq2kgfcIRROpNOqyg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;
s=arcselector9901;
h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;
bh=VIaufhxn9k6I2YZW3zovcSFqldTdOTAabIDHjuoqD5Y=;
b=gwN3SqOUM8H6z3Cc8yMCS/X3FnV/FJwbAxzFkd6iGTQl1pGrjR8Jc273LWn1eMUN7/99jbRvlLwgGVYPMdfZCH4VuiIpFcEOle9abqdjlA6mUUuUYKKd7NkYWWzOGQFU9VFHZ3xzDpghOPZUAFEL9+uWKKMJZ7KX/IMpdlcVpVGrjh0uVwI2xJNHQwurPmYaewDzzvFs/wHDLSq+v0rsG3VBjLPtlQ+S0j9xF3He9dxJueMHFqB0WCzhM+xxWuL46g+72YHcCV9Ns2nG6+r9H0yzHNhTbfsjZJjr0GcBY+62lRIC1m9H9BP2n0utZNtYB1T0qTtRw0dko0/Ntwx3YA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass
smtp.mailfrom=portainer.io; dmarc=pass action=none header.from=portainer.io;
dkim=pass header.d=portainer.io; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=portainer.io;
s=selector1;
h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;
bh=VIaufhxn9k6I2YZW3zovcSFqldTdOTAabIDHjuoqD5Y=;
b=xiOwlMTOQ3fil0wWlCo8DK2lBDprM+qwXTlQPdsLLbfJcIHVK90v3hxlm2TKneYImOZydPCTak8kuiRcpgRrExatxa9pnAg51zAAygEDNQ5IEBO8FDCNUHlnv69t0g12iYZBJSyVr/JRI/izqos0abNHDOJZeDNUR3u5pchuQvM=
Authentication-Results: github.com; dkim=none (message not signed)
header.d=none;github.com; dmarc=none action=none header.from=portainer.io;
Received: from MEAPR01MB2631.ausprd01.prod.outlook.com (2603:10c6:201:b::15)
by ME2PR01MB5684.ausprd01.prod.outlook.com (2603:10c6:220:d3::9) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3763.11; Mon, 18 Jan
2021 04:01:15 +0000
Received: from MEAPR01MB2631.ausprd01.prod.outlook.com
([fe80::cd2a:fba6:c086:163]) by MEAPR01MB2631.ausprd01.prod.outlook.com
([fe80::cd2a:fba6:c086:163%7]) with mapi id 15.20.3763.014; Mon, 18 Jan 2021
04:01:15 +0000
Content-Type: multipart/alternative;
boundary="===============0336705965927718082=="
Subject: Re: error: 'Stop timeout' requires API version 1.25,
but the Docker Daemon API is version 1.24. #QUE00000271
From: "Amet Doohan"<EMAIL_ADDRESS>To<EMAIL_ADDRESS>Date: Mon, 18 Jan 2021 04:01:07 -0000
Reply-To: "Amet Doohan"<EMAIL_ADDRESS>References<EMAIL_ADDRESS>Message-ID<EMAIL_ADDRESS>X-Originating-IP: [<IP_ADDRESS>]
X-ClientProxiedBy: MW4PR03CA0410.namprd03.prod.outlook.com
(2603:10b6:303:115::25) To MEAPR01MB2631.ausprd01.prod.outlook.com
(2603:10c6:201:b::15)
Return-Path<EMAIL_ADDRESS>MIME-Version: 1.0
X-MS-Exchange-MessageSentRepresentingType: 1
Received: from v2app8.mail.happyfox.com (<IP_ADDRESS>) by MW4PR03CA0410.namprd03.prod.outlook.com (2603:10b6:303:115::25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3763.10 via Frontend Transport; Mon, 18 Jan 2021 04:01:15 +0000
Received: from ip-10-10-18-71.happyfox (ip6-localhost [<IP_ADDRESS>])      by v2app8.mail.happyfox.com (Postfix) with ESMTPS id 63AB61E33C9        for<EMAIL_ADDRESS>Mon, 18 Jan 2021 04:01:07 +0000 (UTC)
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: f98123d7-457a-4694-e990-08d8bb65b3b5
X-MS-TrafficTypeDiagnostic: ME2PR01MB5684:
X-Microsoft-Antispam-PRVS:
<EMAIL_ADDRESS>X-MS-Oob-TLC-OOBClassifiers: OLM:6430;
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info:
ybwFv+s+7hxPjkhnly+9QR880XbRbY4pBLvmQuFW3c8yMMnTUejs8ab9E+E/HbumbGE/0ym1qbNBV58vMbGwOB6qSoWzJOlcz9dkwFJDrYF9ljDhnRALHF73xfQVNH21TD1ZL3xHqRGHG+/RTpSefLbttX1mRhXbNiXFlB9bKkdgCq3gSnuBrql8tzH226De9joX6uvz+xwI92XFDR3AyPb6Q2kcGg89GPqJ342Epl6Lfa0ECEffU9jWEK/r0WwMgxQli/Kqb3Su4n9hr0O0zMRVyTc9iPSFq+kmdJ+9RUy0QhUq8fwuXtbaZM9azOMie0JaVxvNgRE1LgxFaAsIlB1Sm8PCxCb3dEgQCY0120Gmt6XMjzLvnFpcogR8WvyDODv1HsbX3dE3mdPRvMewtQ==
X-Forefront-Antispam-Report:
CIP:<IP_ADDRESS>;CTRY:;LANG:en;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:MEAPR01MB2631.ausprd01.prod.outlook.com;PTR:;CAT:NONE;SFS:(4636009)(39830400003)(366004)(346002)(136003)(376002)(396003)(66476007)(8676002)(86362001)(66556008)(66946007)(8936002)(478600001)(2906002)(3450700001)(6266002)(186003)(316002)(55236004)(83380400001)(33964004)(9686003)(52116002)(7126003)(103116003)(26005)(36756003)(5660300002)(6916009);DIR:OUT;SFP:1102;
X-MS-Exchange-AntiSpam-MessageData:
=?us-ascii?Q?+6mE7fGPCWmdfY3qrovZhhOH6sxGl3WiGk5Q9dyTN+Xc0Q3AGIVY5/6wkF38?=
=?us-ascii?Q?tW9whYZuH6Okn2g924sl50DiU89w76Jf+uE18H/zCOhSobW7rjoUhtf/xo6n?=
=?us-ascii?Q?X765cou6MkAWHyFFrklqZWgvDBOcgtZGVRIPGV+5v/PrP4GHNDCVWFCMZLof?=
=?us-ascii?Q?/NoaUbijlA/0TkJOkkYyhJRqe5Y4LsulW6kAr0b//FNsdIk1LjaG6+stRysN?=
=?us-ascii?Q?f25LL0yhN708XrMNB9LLxXNzSYwIkwMW1IwRNuuX0Y35AQiGMXuxp1FieaFL?=
=?us-ascii?Q?EmeyVwBPH8kK1bZcNEZmm2RiCvir1fJSuJ9PpBdKxi6MLUvO/JW0GJCC5FrV?=
=?us-ascii?Q?FWp9sCIRt8MwmzFywEggIgTYRoNLWSmZyAqx4LtK/7J3ExL9btTFHrGbmI3s?=
=?us-ascii?Q?s1PlyZwvhb7hj3WYnfjAJZFONalJFKoL362xO/Fa983zzxAjz7uBi756CJTZ?=
=?us-ascii?Q?yIUpTcTvxfRFS17U147s7BCoN3YHPWyR3Fz6iu8WmOpsg62+tCXESIO9dEYn?=
=?us-ascii?Q?abYv7av+GYAG0otSv3v8tNbR9YGzQ+HC/4iXMk+uKiFXaeXy2WTgQ/21M4C7?=
=?us-ascii?Q?qcC5seUF9u6MSrpeLr86L4Ol0KXqCV0q63nlglsJyBDcaUtSui9rA8fTdpmI?=
=?us-ascii?Q?al1Z7CwBWblzdcoasJBPDxHyIgetFJ5cLJlT57DLtMoPtoNnBqoCV9XzH3mM?=
=?us-ascii?Q?qTT31ijX+JP9tui6r9KbHhq7eyEuwr5WBaNk277uL62AqTjVMz+Yb577KAXg?=
=?us-ascii?Q?7R0Cj7QGVfDtaNWu9DVA2nR0Fl/VSHNf1WNSxUFrLpNEPxLMs5CkuMTwOVjk?=
=?us-ascii?Q?fAlxcXyhOUJFqMyDu54eV4kbcnwXhbTkWOLoyMVRHJ1KwsSmC4ZQguGYNEOo?=
=?us-ascii?Q?kpHozPj+ZtreGe6JYXIs1Eq0FFQezObmcigQfLhaGGPsP9AG1RsjTE1wj78G?=
=?us-ascii?Q?hMj1uQ773FrqSC0HTFxhAwnVCLTMNi9GnZw4v/FUgo3M6mZDMwDNIM34QfUC?=
=?us-ascii?Q?jJEY?=
X-OriginatorOrg: portainer.io
X-MS-Exchange-CrossTenant-Network-Message-Id: f98123d7-457a-4694-e990-08d8bb65b3b5
X-MS-Exchange-CrossTenant-AuthSource: MEAPR01MB2631.ausprd01.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 18 Jan 2021 04:01:15.7937
(UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: 34d4c73d-4fff-4352-9ce2-df14c8d839f5
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: 5uAPiJZAzs0RhaTI+bTk+3PnIgomaaQjJ+T5O9b/aq07JZjcMZk/kDe14Mac6XXpzQ+31thMkCotZ+5LBDiNsw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: ME2PR01MB5684
New reply for the ticket #QUE00000271
Thanks @tserversbfs , will close this issue with workaround remove the
"stop_grace_period: 30s" line
Amet Doohan
Reply to this email to submit an update.

Ticket update by Microsoft Outlook<EMAIL_ADDRESS>[https://products.office.com/en-us/CMSImages/Office365Logo_Orange.png?version=b8d100a9-0a8b-8e6a-88e1-ef488fee0470]
Your message to<EMAIL_ADDRESS>couldn't be delivered.
tserversbfs wasn't found at github.com.
hello   Office 365      tserversbfs
Action Required                 Recipient
Unknown To address
How to Fix It
The address may be misspelled or may not exist. Try one or more of the following:

Send the message again following these steps: In Outlook, open this non-delivery report (NDR) and choose Send Again from the Report ribbon. In Outlook on the web, select this NDR, then select the link "To send this message again, click here." Then delete and retype the entire recipient address. If prompted with an Auto-Complete List suggestion don't select it. After typing the complete address, click Send.
Contact the recipient (by phone, for example) to check that the address exists and is correct.
The recipient may have set up email forwarding to an incorrect address. Ask them to check that any forwarding they've set up is working correctly.
Clear the recipient Auto-Complete List in Outlook or Outlook on the web by following the steps in this article: Fix email delivery issues for error code 5.1.1 in Office 365https://go.microsoft.com/fwlink/?LinkId=389363, and then send the message again. Retype the entire recipient address before selecting Send.

If the problem continues, forward this message to your email admin. If you're an email admin, refer to the More Info for Email Admins section below.
Was this helpful? Send feedback to Microsofthttps://go.microsoft.com/fwlink/?LinkId=525920.

More Info for Email Admins
Status code: 550 5.1.1
This error occurs because the sender sent a message to an email address outside of Office 365, but the address is incorrect or doesn't exist at the destination domain. The error is reported by the recipient domain's email server, but most often it must be fixed by the person who sent the message. If the steps in the How to Fix It section above don't fix the problem, and you're the email admin for the recipient, try one or more of the following:
The email address exists and is correct - Confirm that the recipient address exists, is correct, and is accepting messages.
Synchronize your directories - If you have a hybrid environment and are using directory synchronization make sure the recipient's email address is synced correctly in both Office 365 and in your on-premises directory.
Errant forwarding rule - Check for forwarding rules that aren't behaving as expected. Forwarding can be set up by an admin via mail flow rules or mailbox forwarding address settings, or by the recipient via the Inbox Rules feature.
Mail flow settings and MX records are not correct - Misconfigured mail flow or MX record settings can cause this error. Check your Office 365 mail flow settings to make sure your domain and any mail flow connectors are set up correctly. Also, work with your domain registrar to make sure the MX records for your domain are configured correctly.
For more information and additional tips to fix this issue, see Fix email delivery issues for error code 550 5.1.1 in Office 365https://go.microsoft.com/fwlink/?LinkId=389363.
Original Message Details
Created Date:   1/18/2021 4:01:07 AM
Sender Address<EMAIL_ADDRESS>Recipient Address<EMAIL_ADDRESS>Subject:        Re: error: 'Stop timeout' requires API version 1.25, but the Docker Daemon API is version 1.24. #QUE00000271
Error Details
Reported error: 550-5.1.1 The email account that you tried to reach does not exist. Please try 550-5.1.1 double-checking the recipient's email address for typos or 550-5.1.1 unnecessary spaces. Learn more at 550 5.1.1 https://support.google.com/mail/?p=NoSuchUser mp17si19061762pjb.26 - gsmtp
DSN generated by:       ME2PR01MB5684.ausprd01.prod.outlook.com
Remote server:  mx.google.com
Message Hops
HOP     TIME (UTC)      FROM    TO      WITH    RELAY TIME
1       1/18/2021
4:01:07 AM      ip-10-10-18-71.happyfox v2app8.mail.happyfox.com        ESMTPS  *
2       1/18/2021
4:01:15 AM      v2app8.mail.happyfox.com MW4PR03CA0410.namprd03.prod.outlook.com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384)    8 sec
3       1/18/2021
4:01:15 AM      MEAPR01MB2631.ausprd01.prod.outlook.com MEAPR01MB2631.ausprd01.prod.outlook.com mapi    *
4       1/18/2021
4:01:15 AM      MEAPR01MB2631.ausprd01.prod.outlook.com ME2PR01MB5684.ausprd01.prod.outlook.com Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384)    *
Original Message Headers
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none;
b=SGU+JqvzUy6Noiu8Csj/p+p1w9Ptkxyvs3zcf0QxGEbQ95DxJjH8K3V01zkNs3uRV1lmInfQPXVXp2nEc6ODkzzuY+tJlp/+VtG9JAoL9lnU6fIQskT+TnNniIGMz8TcIJO0P7RWBRJAlAIp0Ul7RhLRb36Pt2X7n8DXfBjMOTm4GxtsqSZ/glEABAeraGgC3rXnrPznCba+PCFPHEsgiD2coJxDZfKQdvJU8jlpwXWt6v6sqMr/2+fmUkANu2SZrihwnaiC2db3tvctJzQ//PxtH8vkGjwbUogvWfsnrkAZpnTuFQ+jNH/7maN6Lf1mPNNOcLq2kgfcIRROpNOqyg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;
s=arcselector9901;
h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;
bh=VIaufhxn9k6I2YZW3zovcSFqldTdOTAabIDHjuoqD5Y=;
b=gwN3SqOUM8H6z3Cc8yMCS/X3FnV/FJwbAxzFkd6iGTQl1pGrjR8Jc273LWn1eMUN7/99jbRvlLwgGVYPMdfZCH4VuiIpFcEOle9abqdjlA6mUUuUYKKd7NkYWWzOGQFU9VFHZ3xzDpghOPZUAFEL9+uWKKMJZ7KX/IMpdlcVpVGrjh0uVwI2xJNHQwurPmYaewDzzvFs/wHDLSq+v0rsG3VBjLPtlQ+S0j9xF3He9dxJueMHFqB0WCzhM+xxWuL46g+72YHcCV9Ns2nG6+r9H0yzHNhTbfsjZJjr0GcBY+62lRIC1m9H9BP2n0utZNtYB1T0qTtRw0dko0/Ntwx3YA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass
smtp.mailfrom=portainer.io; dmarc=pass action=none header.from=portainer.io;
dkim=pass header.d=portainer.io; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=portainer.io;
s=selector1;
h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck;
bh=VIaufhxn9k6I2YZW3zovcSFqldTdOTAabIDHjuoqD5Y=;
b=xiOwlMTOQ3fil0wWlCo8DK2lBDprM+qwXTlQPdsLLbfJcIHVK90v3hxlm2TKneYImOZydPCTak8kuiRcpgRrExatxa9pnAg51zAAygEDNQ5IEBO8FDCNUHlnv69t0g12iYZBJSyVr/JRI/izqos0abNHDOJZeDNUR3u5pchuQvM=
Authentication-Results: github.com; dkim=none (message not signed)
header.d=none;github.com; dmarc=none action=none header.from=portainer.io;
Received: from MEAPR01MB2631.ausprd01.prod.outlook.com (2603:10c6:201:b::15)
by ME2PR01MB5684.ausprd01.prod.outlook.com (2603:10c6:220:d3::9) with
Microsoft SMTP Server (version=TLS1_2,
cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3763.11; Mon, 18 Jan
2021 04:01:15 +0000
Received: from MEAPR01MB2631.ausprd01.prod.outlook.com
([fe80::cd2a:fba6:c086:163]) by MEAPR01MB2631.ausprd01.prod.outlook.com
([fe80::cd2a:fba6:c086:163%7]) with mapi id 15.20.3763.014; Mon, 18 Jan 2021
04:01:15 +0000
Content-Type: multipart/alternative;
boundary="===============0336705965927718082=="
Subject: Re: error: 'Stop timeout' requires API version 1.25,
but the Docker Daemon API is version 1.24. #QUE00000271
From: "Amet Doohan"<EMAIL_ADDRESS>To<EMAIL_ADDRESS>Date: Mon, 18 Jan 2021 04:01:07 -0000
Reply-To: "Amet Doohan"<EMAIL_ADDRESS>References<EMAIL_ADDRESS>Message-ID<EMAIL_ADDRESS>X-Originating-IP: [<IP_ADDRESS>]
X-ClientProxiedBy: MW4PR03CA0410.namprd03.prod.outlook.com
(2603:10b6:303:115::25) To MEAPR01MB2631.ausprd01.prod.outlook.com
(2603:10c6:201:b::15)
Return-Path<EMAIL_ADDRESS>MIME-Version: 1.0
X-MS-Exchange-MessageSentRepresentingType: 1
Received: from v2app8.mail.happyfox.com (<IP_ADDRESS>) by MW4PR03CA0410.namprd03.prod.outlook.com (2603:10b6:303:115::25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3763.10 via Frontend Transport; Mon, 18 Jan 2021 04:01:15 +0000
Received: from ip-10-10-18-71.happyfox (ip6-localhost [<IP_ADDRESS>])      by v2app8.mail.happyfox.com (Postfix) with ESMTPS id 63AB61E33C9        for<EMAIL_ADDRESS>Mon, 18 Jan 2021 04:01:07 +0000 (UTC)
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-Correlation-Id: f98123d7-457a-4694-e990-08d8bb65b3b5
X-MS-TrafficTypeDiagnostic: ME2PR01MB5684:
X-Microsoft-Antispam-PRVS:
<EMAIL_ADDRESS>X-MS-Oob-TLC-OOBClassifiers: OLM:6430;
X-MS-Exchange-SenderADCheck: 1
X-Microsoft-Antispam: BCL:0;
X-Microsoft-Antispam-Message-Info:
ybwFv+s+7hxPjkhnly+9QR880XbRbY4pBLvmQuFW3c8yMMnTUejs8ab9E+E/HbumbGE/0ym1qbNBV58vMbGwOB6qSoWzJOlcz9dkwFJDrYF9ljDhnRALHF73xfQVNH21TD1ZL3xHqRGHG+/RTpSefLbttX1mRhXbNiXFlB9bKkdgCq3gSnuBrql8tzH226De9joX6uvz+xwI92XFDR3AyPb6Q2kcGg89GPqJ342Epl6Lfa0ECEffU9jWEK/r0WwMgxQli/Kqb3Su4n9hr0O0zMRVyTc9iPSFq+kmdJ+9RUy0QhUq8fwuXtbaZM9azOMie0JaVxvNgRE1LgxFaAsIlB1Sm8PCxCb3dEgQCY0120Gmt6XMjzLvnFpcogR8WvyDODv1HsbX3dE3mdPRvMewtQ==
X-Forefront-Antispam-Report:
CIP:<IP_ADDRESS>;CTRY:;LANG:en;SCL:1;SRV:;IPV:NLI;SFV:NSPM;H:MEAPR01MB2631.ausprd01.prod.outlook.com;PTR:;CAT:NONE;SFS:(4636009)(39830400003)(366004)(346002)(136003)(376002)(396003)(66476007)(8676002)(86362001)(66556008)(66946007)(8936002)(478600001)(2906002)(3450700001)(6266002)(186003)(316002)(55236004)(83380400001)(33964004)(9686003)(52116002)(7126003)(103116003)(26005)(36756003)(5660300002)(6916009);DIR:OUT;SFP:1102;
X-MS-Exchange-AntiSpam-MessageData:
=?us-ascii?Q?+6mE7fGPCWmdfY3qrovZhhOH6sxGl3WiGk5Q9dyTN+Xc0Q3AGIVY5/6wkF38?=
=?us-ascii?Q?tW9whYZuH6Okn2g924sl50DiU89w76Jf+uE18H/zCOhSobW7rjoUhtf/xo6n?=
=?us-ascii?Q?X765cou6MkAWHyFFrklqZWgvDBOcgtZGVRIPGV+5v/PrP4GHNDCVWFCMZLof?=
=?us-ascii?Q?/NoaUbijlA/0TkJOkkYyhJRqe5Y4LsulW6kAr0b//FNsdIk1LjaG6+stRysN?=
=?us-ascii?Q?f25LL0yhN708XrMNB9LLxXNzSYwIkwMW1IwRNuuX0Y35AQiGMXuxp1FieaFL?=
=?us-ascii?Q?EmeyVwBPH8kK1bZcNEZmm2RiCvir1fJSuJ9PpBdKxi6MLUvO/JW0GJCC5FrV?=
=?us-ascii?Q?FWp9sCIRt8MwmzFywEggIgTYRoNLWSmZyAqx4LtK/7J3ExL9btTFHrGbmI3s?=
=?us-ascii?Q?s1PlyZwvhb7hj3WYnfjAJZFONalJFKoL362xO/Fa983zzxAjz7uBi756CJTZ?=
=?us-ascii?Q?yIUpTcTvxfRFS17U147s7BCoN3YHPWyR3Fz6iu8WmOpsg62+tCXESIO9dEYn?=
=?us-ascii?Q?abYv7av+GYAG0otSv3v8tNbR9YGzQ+HC/4iXMk+uKiFXaeXy2WTgQ/21M4C7?=
=?us-ascii?Q?qcC5seUF9u6MSrpeLr86L4Ol0KXqCV0q63nlglsJyBDcaUtSui9rA8fTdpmI?=
=?us-ascii?Q?al1Z7CwBWblzdcoasJBPDxHyIgetFJ5cLJlT57DLtMoPtoNnBqoCV9XzH3mM?=
=?us-ascii?Q?qTT31ijX+JP9tui6r9KbHhq7eyEuwr5WBaNk277uL62AqTjVMz+Yb577KAXg?=
=?us-ascii?Q?7R0Cj7QGVfDtaNWu9DVA2nR0Fl/VSHNf1WNSxUFrLpNEPxLMs5CkuMTwOVjk?=
=?us-ascii?Q?fAlxcXyhOUJFqMyDu54eV4kbcnwXhbTkWOLoyMVRHJ1KwsSmC4ZQguGYNEOo?=
=?us-ascii?Q?kpHozPj+ZtreGe6JYXIs1Eq0FFQezObmcigQfLhaGGPsP9AG1RsjTE1wj78G?=
=?us-ascii?Q?hMj1uQ773FrqSC0HTFxhAwnVCLTMNi9GnZw4v/FUgo3M6mZDMwDNIM34QfUC?=
=?us-ascii?Q?jJEY?=
X-OriginatorOrg: portainer.io
X-MS-Exchange-CrossTenant-Network-Message-Id: f98123d7-457a-4694-e990-08d8bb65b3b5
X-MS-Exchange-CrossTenant-AuthSource: MEAPR01MB2631.ausprd01.prod.outlook.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 18 Jan 2021 04:01:15.7937
(UTC)
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: 34d4c73d-4fff-4352-9ce2-df14c8d839f5
X-MS-Exchange-CrossTenant-MailboxType: HOSTED
X-MS-Exchange-CrossTenant-UserPrincipalName: 5uAPiJZAzs0RhaTI+bTk+3PnIgomaaQjJ+T5O9b/aq07JZjcMZk/kDe14Mac6XXpzQ+31thMkCotZ+5LBDiNsw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: ME2PR01MB5684
New reply for the ticket #QUE00000271
Thanks @tserversbfs , will close this issue with workaround remove the
"stop_grace_period: 30s" line
Amet Doohan
Reply to this email to submit an update.


NameError("name 'call' is not defined",)

Hello
I got this error when I ran the 'Pythonic interface (Experimental)' example.
Is it because I am missing something?
Thanks
py3.6
swipl1.6.4
Traceback (most recent call last):
File "D:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\Microsoft\Python\Core\ptvsd_launcher.py", line 111, in
vspd.debug(filename, port_num, debug_id, debug_options, run_as)
File "D:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\Microsoft\Python\Core\Packages\ptvsd\debugger.py", line 36, in debug
run(address, filename, *args, **kwargs)
File "D:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\Microsoft\Python\Core\Packages\ptvsd_main.py", line 47, in run_file
run(argv, addr, **kwargs)
File "D:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\Microsoft\Python\Core\Packages\ptvsd_main.py", line 98, in _run
_pydevd.main()
File "D:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\Microsoft\Python\Core\Packages\ptvsd\pydevd\pydevd.py", line 1628, in main
globals = debugger.run(setup['file'], None, None, is_module)
File "D:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\Microsoft\Python\Core\Packages\ptvsd\pydevd\pydevd.py", line 1035, in run
pydev_imports.execfile(file, globals, locals)  # execute the script
File "D:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\Extensions\Microsoft\Python\Core\Packages\ptvsd\pydevd_pydev_imps_pydev_execfile.py", line 25, in execfile
exec(compile(contents+"\n", file, 'exec'), glob, loc)
File "D:\Project\AI_NLP\AI_NLP\test.py", line 9, in
call(assertz(father("michael","john")))
NameError: name 'call' is not defined

maybe you can try to add one line like 'from pyswip import call'.  and you may still encounter another error, then you should modify the one line of code to 'assertz = Functor("assertz", 1)'

@XUEZIJIAN @GraceGay 's fix is correct, I've updated the README.


Convert RunString to lambda function in compiler

Fixes #1150
As far as I can tell everything will work the same, only difference is things like math.huge should be handled correctly. The InstrSTR should work the same, and did in my testing, though if someone else could do the same to confirm.
If you want I can also add the math.huge constant as an extra commit here, though I figured it'd be better in a separate pr.

I'm not so sure about InstrNUM behaving the same way before and after your change

Why's that?

x = tonumber(x) is not the same as RunString("x="..x)

It's being treated practically the same here. In the case of binary and hexadecimal literals, they're converted to numbers in the tokenizer. So the only numbers it receives in string form are normal decimal numbers, which as far as I can tell interrupted the same way.

Looked into how Lua did tonumber as well as how a number is interrupted. Both rely on strtod, so output will be the same. As for InstrSTR, it will also act the same as all %q did was make the string safe in order to be read correctly.

Tokenizer:NextSymbol() is responsible for getting the tokendata, and it sometimes spits out a number and sometimes a string. Parser:Expr17() is then responsible for maybe doing a bit more parsing of the number and then calling the right instruction. The instruction is then implicitly in charge of reparsing the already-parsed tokendata by putting it in a string which is then interpreted as Lua. This isn't a very nice system.
I think it'd be more principled and easier to understand the logic if all the parsing was done in the tokenizer (and then tokendata would always be a number, or a {number, 'i'/'j'/'k'}) or in the parser (and then tokendata would be the original string, and the parser would fully parse it and always call self:Instruction with a number argument). In fact, there's no need for separate NUM/NUMI/NUMJ/NUMK/STR instructions - just have a single instruction for all literal values.

@bigdogmat all of the changes in this are now in master, except the InstrVAR change. Do you want to update this PR to be just that change, or should I?

@AbigailBuccaneer The main point of this was just to fix up the constant handling, however seen as it's probably a good idea to remove the RunString'd stuff anyway this'll do fine.


Figure out attribution

I created this repo by copying nearly verbatim from https://github.com/broadinstitute/pooled-cell-painting-profiling-template. We should figure out how to attribute this work to the author (@gwaygenomics) and related discussions (https://github.com/broadinstitute/pooled-cell-painting-profiling-recipe/issues/3)

We have this in the README:

(Derived from this template)


Fix Typo

1. Why is this change necessary?
For perfection.
2. What does this change do, exactly?
It fixes a typo
3. Describe each step to reproduce the issue or behaviour.
Just look at the the admin panel, customer scope card
5. Checklist

[x] I have rebased my changes to remove merge conflicts
[nope] I have written tests and verified that they fail without my change
[x] I have created a changelog file with all necessary information about my changes
[nope] I have written or adjusted the documentation according to my changes
[nope] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/NEXT-24792
Please use this issue to track the state of your pull request.

Thank you, @amenk, for your contribution. 💙


[KYUUBI #381] Release session if shared level is CONNECTION

      ❨?❩

Why are the changes needed?

In CONNECTION level, it's better to release session if the connection is closed.
How was this patch tested?

[ ] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[ ] Run test locally before make a pull request

cc @yaooqinn @pan3793

The change LGTM, and I'm considering is there possible to make Kyuubi support dynamic Shard Level?
Currently, I deploy 2 kyuubi servers, one for ad-hoc query with user shard level, and one for batch with connection shard level and set idle timeout = 1min.

@pan3793 I believe you can set config during create connection.
jdbc:hive2://localhost:10009/;#spark.master=yarn;kyuubi.session.engine.share.level=CONNECTION

jdbc:hive2://localhost:10009/;#spark.master=yarn;kyuubi.session.engine.share.level=USER

Thanks @ulysses-you , I just found that jdbc url in beeline must be quota with "
beeline -u "jdbc:hive2://kyuubi10009/;#kyuubi.session.engine.share.level=CONNECTION"

beeline -u jdbc:hive2://kyuubi:10009/;#kyuubi.session.engine.share.level=CONNECTION

The first works but the second not.

Just share my thoughts:

the config is useless to me, as it brings extra lifecycle for the engine
for tests, we can add some tests in KyuubiOperationPerConnectionSuite. the new tests here seem not to work after you call sys.exit(0)

Thanks @ulysses-you , I just found that jdbc url in beeline must be quota with "
beeline -u "jdbc:hive2://kyuubi10009/;#kyuubi.session.engine.share.level=CONNECTION"

beeline -u jdbc:hive2://kyuubi:10009/;#kyuubi.session.engine.share.level=CONNECTION

The first works but the second not.

It looks like the current document is not good enough even for committers 🙂

interesting .. my local env can pass the test
Discovery starting.
Discovery completed in 1 second, 150 milliseconds.
Run starting. Expected test count is: 1
SessionSuite:
- release session if shared level is CONNECTION
Run completed in 45 seconds, 962 milliseconds.
Total number of tests run: 1
Suites: completed 2, aborted 0
Tests: succeeded 1, failed 0, canceled 0, ignored 0, pending 0
All tests passed.

thanks merging to master for 1.1.0


[MB-1970] Update to Android UA SDK 8.2.2

Updates to use Android SDK 8.2.2
Changes:

Update dependency versions
Bindings for SDK 8.2.2
Add Class to any class that conflicts with the namespace (AnalyticsClass, MessageCenterClass, etc..)

Looks like the latest Xamarin update fixed the crash - https://releases.xamarin.com/stable-release-cycle-8-service-release-0/
However we need unreleased versions of v4 and GCM:

https://www.nuget.org/packages/Xamarin.Android.Support.v4
https://www.nuget.org/packages/Xamarin.GooglePlayServices.Gcm

Holding off on the release until then.

🍊  after reviewing a question/comment above ^

:boat:


GPL-407 Store sample data from external sites

User story
As a dev team we would like a service to store sample data from external sites. This data arrives as CSV files on an internal SFTP server.
Who the primary contacts are for this story
Philip
Acceptance criteria
To be considered successful the solution must allow:

connect to and download the latest CSV files for a site
update (drop and recreate) the sample data for that site

Additional context
Add any other context or screenshots about the feature request here.

David M (Alderley park) wrote
Wednesday, 22 April 2020 at 00:23
"For the old temporary RNA plate barcode, I don’t think we have any left. The format is RNA_xxxx
I can photograph a new barcode which will be our standard moving forward"
First plate maps expected from Alderley park on 22nd.

New file every Monday
Whole LIMS export (not incremental)
Date in file name


Windows build failure (merge)

The Windows Egeria Merge build is failing
https://github.com/odpi/egeria/actions/workflows/windows-daily.yml
For example for one specific log:
See https://github.com/odpi/egeria/runs/2126504680?check_suite_focus=true
This looks like an issue with launching the chassis for FVT tests. I made changes in this area recently under #4896
Linux/macOS are fine

Trying to debug this I also hit build problems in the conformance suite, which seemed to be caused by symbolic links .
Will add notes to readme for 2.9 & leave to future release

One option is to consider whether we advise windows users to work within WSL2 (the linux environment supported in windows which can run a full ubuntu etc environment) to avoid these platform specific issues and improve performance 3x
The one gotcha will be around IDE integration.
Are there any windows based developers that would like to take this issue on to work out what works best? Most of the core team are using MacOS and/or Linux

Building on a clean machine, the first issue hit is in the conformance suite:
[INFO]
[INFO] --- apache-rat-plugin:0.13:check (rat-check) @ open-metadata-conformance-suite ---
[INFO] Added 3 additional default licenses.
[INFO] Enabled default license matchers.
[INFO] Added 2 custom approved licenses.
[INFO] Will parse SCM ignores for exclusions...
[INFO] Finished adding exclusions from SCM ignore files.
[INFO] 66 implicit excludes (use -debug for more details).
[INFO] 46 explicit excludes (use -debug for more details).
[INFO] 176 resources included (use -debug for more details)
[INFO] Rat check: Summary over all files. Unapproved: 29, unknown: 29, generated: 0, approved: 147 licenses.

The rat report shows :
29 Unknown Licenses

*****************************************************

Files with unapproved licenses:

  C:/Users/nigel/IdeaProjects/egeria/open-metadata-conformance-suite/docs/performance-workbench/test-cases/repository-classification-search-performance-test-case.md
  C:/Users/nigel/IdeaProjects/egeria/open-metadata-conformance-suite/docs/performance-workbench/test-cases/repository-classification-update-performance-test-case.md
  C:/Users/nigel/IdeaProjects/egeria/open-metadata-conformance-suite/docs/performance-workbench/test-cases/repository-entity-classification-performance-test-case.md
  C:/Users/nigel/IdeaProjects/egeria/open-metadata-conformance-suite/docs/performance-workbench/test-cases/repository-entity-creation-performance-test-case.md
  C:/Users/nigel/IdeaProjects/egeria/open-metadata-conformance-suite/docs/performance-workbench/test-cases/repository-entity-declassification-performance-test-case.md
  C:/Users/nigel/IdeaProjects/egeria/open-metadata-conformance-suite/docs/performance-workbench/test-cases/repository-entity-delete-performance-test-case.md
  C:/Users/nigel/IdeaProjects/egeria/open-metadata-conformance-suite/docs/performance-workbench/test-cases/repository-entity-history-retrieval-performance-test-case.md
  C:/Users/nigel/IdeaProjects/egeria/open-metadata-conformance-suite/docs/performance-workbench/test-cases/repository-entity-purge-performance-test-case.md
  C:/Users/nigel/IdeaProjects/egeria/open-metadata-conformance-suite/docs/performance-workbench/test-cases/repository-entity-re-home-performance-test-case.md
  C:/Users/nigel/IdeaProjects/egeria/open-metadata-conformance-suite/docs/performance-workbench/test-cases/repository-entity-restore-performance-test-case.md
  C:/Users/nigel/IdeaProjects/egeria/open-metadata-conformance-suite/docs/performance-workbench/test-cases/repository-entity-retrieval-performance-test-case.md
  C:/Users/nigel/IdeaProjects/egeria/open-metadata-conformance-suite/docs/performance-workbench/test-cases/repository-entity-search-history-performance-test-case.md
  C:/Users/nigel/IdeaProjects/egeria/open-metadata-conformance-suite/docs/performance-workbench/test-cases/repository-entity-search-performance-test-case.md
  C:/Users/nigel/IdeaProjects/egeria/open-metadata-conformance-suite/docs/performance-workbench/test-cases/repository-entity-undo-performance-test-case.md
  C:/Users/nigel/IdeaProjects/egeria/open-metadata-conformance-suite/docs/performance-workbench/test-cases/repository-entity-update-performance-test-case.md
  C:/Users/nigel/IdeaProjects/egeria/open-metadata-conformance-suite/docs/performance-workbench/test-cases/repository-graph-history-query-performance-test-case.md
  C:/Users/nigel/IdeaProjects/egeria/open-metadata-conformance-suite/docs/performance-workbench/test-cases/repository-graph-query-performance-test-case.md
  C:/Users/nigel/IdeaProjects/egeria/open-metadata-conformance-suite/docs/performance-workbench/test-cases/repository-performance-environment-test-case.md
  C:/Users/nigel/IdeaProjects/egeria/open-metadata-conformance-suite/docs/performance-workbench/test-cases/repository-relationship-creation-performance-test-case.md
  C:/Users/nigel/IdeaProjects/egeria/open-metadata-conformance-suite/docs/performance-workbench/test-cases/repository-relationship-delete-performance-test-case.md
  C:/Users/nigel/IdeaProjects/egeria/open-metadata-conformance-suite/docs/performance-workbench/test-cases/repository-relationship-history-retrieval-performance-test-case.md
  C:/Users/nigel/IdeaProjects/egeria/open-metadata-conformance-suite/docs/performance-workbench/test-cases/repository-relationship-purge-performance-test-case.md
  C:/Users/nigel/IdeaProjects/egeria/open-metadata-conformance-suite/docs/performance-workbench/test-cases/repository-relationship-re-home-performance-test-case.md
  C:/Users/nigel/IdeaProjects/egeria/open-metadata-conformance-suite/docs/performance-workbench/test-cases/repository-relationship-restore-performance-test-case.md
  C:/Users/nigel/IdeaProjects/egeria/open-metadata-conformance-suite/docs/performance-workbench/test-cases/repository-relationship-retrieval-performance-test-case.md
  C:/Users/nigel/IdeaProjects/egeria/open-metadata-conformance-suite/docs/performance-workbench/test-cases/repository-relationship-search-history-performance-test-case.md
  C:/Users/nigel/IdeaProjects/egeria/open-metadata-conformance-suite/docs/performance-workbench/test-cases/repository-relationship-search-performance-test-case.md
  C:/Users/nigel/IdeaProjects/egeria/open-metadata-conformance-suite/docs/performance-workbench/test-cases/repository-relationship-undo-performance-test-case.md
  C:/Users/nigel/IdeaProjects/egeria/open-metadata-conformance-suite/docs/performance-workbench/test-cases/repository-relationship-update-performance-test-case.md

If we take an example of one of these files, they contain a simple stub ie:
../profiles/classification-search/README.md

which seems to indicate the target of the link, but the rat check doesn't understand that ...
Running a query on a linux environment shows the same list of files are symbolic links checked into git
➜  egeria git:(master) git ls-files -s | awk '/120000/{print $4}'
open-metadata-conformance-suite/docs/performance-workbench/test-cases/repository-classification-search-performance-test-case.md
open-metadata-conformance-suite/docs/performance-workbench/test-cases/repository-classification-update-performance-test-case.md
open-metadata-conformance-suite/docs/performance-workbench/test-cases/repository-entity-classification-performance-test-case.md
open-metadata-conformance-suite/docs/performance-workbench/test-cases/repository-entity-creation-performance-test-case.md
open-metadata-conformance-suite/docs/performance-workbench/test-cases/repository-entity-declassification-performance-test-case.md
open-metadata-conformance-suite/docs/performance-workbench/test-cases/repository-entity-delete-performance-test-case.md
open-metadata-conformance-suite/docs/performance-workbench/test-cases/repository-entity-history-retrieval-performance-test-case.md
open-metadata-conformance-suite/docs/performance-workbench/test-cases/repository-entity-purge-performance-test-case.md
open-metadata-conformance-suite/docs/performance-workbench/test-cases/repository-entity-re-home-performance-test-case.mdopen-metadata-conformance-suite/docs/performance-workbench/test-cases/repository-entity-restore-performance-test-case.mdopen-metadata-conformance-suite/docs/performance-workbench/test-cases/repository-entity-retrieval-performance-test-case.md
open-metadata-conformance-suite/docs/performance-workbench/test-cases/repository-entity-search-history-performance-test-case.md
open-metadata-conformance-suite/docs/performance-workbench/test-cases/repository-entity-search-performance-test-case.md
open-metadata-conformance-suite/docs/performance-workbench/test-cases/repository-entity-undo-performance-test-case.md
open-metadata-conformance-suite/docs/performance-workbench/test-cases/repository-entity-update-performance-test-case.md
open-metadata-conformance-suite/docs/performance-workbench/test-cases/repository-graph-history-query-performance-test-case.md
open-metadata-conformance-suite/docs/performance-workbench/test-cases/repository-graph-query-performance-test-case.md
open-metadata-conformance-suite/docs/performance-workbench/test-cases/repository-performance-environment-test-case.md
open-metadata-conformance-suite/docs/performance-workbench/test-cases/repository-relationship-creation-performance-test-case.md
open-metadata-conformance-suite/docs/performance-workbench/test-cases/repository-relationship-delete-performance-test-case.md
open-metadata-conformance-suite/docs/performance-workbench/test-cases/repository-relationship-history-retrieval-performance-test-case.md
open-metadata-conformance-suite/docs/performance-workbench/test-cases/repository-relationship-purge-performance-test-case.md
open-metadata-conformance-suite/docs/performance-workbench/test-cases/repository-relationship-re-home-performance-test-case.md
open-metadata-conformance-suite/docs/performance-workbench/test-cases/repository-relationship-restore-performance-test-case.md
open-metadata-conformance-suite/docs/performance-workbench/test-cases/repository-relationship-retrieval-performance-test-case.md
open-metadata-conformance-suite/docs/performance-workbench/test-cases/repository-relationship-search-history-performance-test-case.md
open-metadata-conformance-suite/docs/performance-workbench/test-cases/repository-relationship-search-performance-test-case.md
open-metadata-conformance-suite/docs/performance-workbench/test-cases/repository-relationship-undo-performance-test-case.md
open-metadata-conformance-suite/docs/performance-workbench/test-cases/repository-relationship-update-performance-test-case.md

Given that the windows git client doesn't properly handle symlinks I think we need to avoid using them if possible. Or we could skip certain areas on windows, or agreeing not to support. It's unfortunate since windows/NTFS does support a variety of links - hardlinks, symbolic links, and junction
cc: @cmgrote

Will continue checking for other issues...

It looks like the config setting 'core.symlinks=true' may help assuming the user is using WIndows 10, NTFS or another fs with symlink support, AND is in developer mode ???
Will retry (after next tests of FVT -- windows build is very slow). If that works then I'm inclined to add docs to the project and not revert the symlink change.
Additionally it's worth noting that intellij now supports IDE usage on windows where the actual build/file management is run under WLS2 (linux kernel) which should avoid all of these kind of issues. this may also be worth recommending.

The following does not work

set core.symlinks.true globally
clone repo
.. and it can't be set after as by then the links are created
since git tries to detect whether a supported scenario is being used

It only seems to work if, as documented, WIndows 'developer mode' is enabled.
Will repeat a build...

With that change, the conformance test build completes. I will later raise a PR to add notes to the windows setup documentation.
The build now fails with:
[INFO] --- process-exec-maven-plugin:0.9:start (chassis-start) @ asset-consumer-fvt ---
[INFO] arg: java
[INFO] arg: -Dserver.port=10443
[INFO] arg: -Dloader.path=../../../../../../open-metadata-distribution/open-metadata-assemblies/target/egeria-2.9-SNAPSHOT-distribution/egeria-omag-2.9-SNAPSHOT/server/lib
[INFO] arg: -Dspringdoc.api-docs.enabled=false
[INFO] arg: -Djavax.net.ssl.trustStore=../../../../../../open-metadata-distribution/open-metadata-assemblies/target/egeria-2.9-SNAPSHOT-distribution/egeria-omag-2.9-SNAPSHOT/truststore.p12
[INFO] arg: -Dserver.ssl.trust-store=../../../../../../open-metadata-distribution/open-metadata-assemblies/target/egeria-2.9-SNAPSHOT-distribution/egeria-omag-2.9-SNAPSHOT/truststore.p12 [INFO] arg: -jar
[INFO] arg: ../../../../../../open-metadata-distribution/open-metadata-assemblies/target/egeria-2.9-SNAPSHOT-distribution/egeria-omag-2.9-SNAPSHOT/server/server-chassis-spring-2.9-SNAPSHOT.jar
[INFO] Full command line: java -Dserver.port=10443 -Dloader.path=../../../../../../open-metadata-distribution/open-metadata-assemblies/target/egeria-2.9-SNAPSHOT-distribution/egeria-omag-2.9-SNAPSHOT/server/lib -Dspringdoc.api-docs.enabled=false -Djavax.net.ssl.trustStore=../../../../../../open-metadata-distribution/open-metadata-assemblies/target/egeria-2.9-SNAPSHOT-distribution/egeria-omag-2.9-SNAPSHOT/truststore.p12 -Dserver.ssl.trust-store=../../../../../../open-metadata-distribution/open-metadata-assemblies/target/egeria-2.9-SNAPSHOT-distribution/egeria-omag-2.9-SNAPSHOT/truststore.p12 -jar ../../../../../../open-metadata-distribution/open-metadata-assemblies/target/egeria-2.9-SNAPSHOT-distribution/egeria-omag-2.9-SNAPSHOT/server/server-chassis-spring-2.9-SNAPSHOT.jar
[INFO] Starting process: chassis-start
[INFO] Using working directory for this process: C:\Users\nigel\IdeaProjects\egeria\open-metadata-test\open-metadata-fvt\access-services-fvt\asset-consumer-fvt\target\classes
[ERROR] Error: Unable to access jarfile ../../../../../../open-metadata-distribution/open-metadata-assemblies/target/egeria-2.9-SNAPSHOT-distribution/egeria-omag-2.9-SNAPSHOT/server/server-chassis-spring-2.9-SNAPSHOT.jar
[INFO] Started process: chassis-start
[INFO]
[INFO] --- groovy-maven-plugin:2.1.1:execute (server-start) @ asset-consumer-fvt ---
=== Checking platform at https://localhost:10443 is available (12 attempts remaining) ===
=== Checking platform at https://localhost:10443 is available (11 attempts remaining) ===
=== Checking platform at https://localhost:10443 is available (10 attempts remaining) ===
=== Checking platform at https://localhost:10443 is available (9 attempts remaining) ===
[INFO] Stopping all processes ...
[INFO] Stopping process: chassis-start
[INFO] Stopped process: chassis-start

This looks as if it may be some kind of path length/parsing issue ie
nigel@MEGA C:\Users\nigel\IdeaProjects\egeria\open-metadata-test\open-metadata-fvt\access-services-fvt\asset-consumer-fvt\target\classes
$ dir ..\..\..\..\..\..\open-metadata-distribution\open-metadata-assemblies\target\egeria-2.9-SNAPSHOT-distribution\egeria-omag-2.9-SNAPSHOT
 Volume in drive C is Win10
 Volume Serial Number is 765D-6B1A

 Directory of C:\Users\nigel\IdeaProjects\egeria\open-metadata-distribution\open-metadata-assemblies\target\egeria-2.9-SNAPSHOT-distribution

2021-04-15  18:48    <DIR>          egeria-omag-2.9-SNAPSHOT
               0 File(s)              0 bytes
               1 Dir(s)  23,115,759,616 bytes free

nigel@MEGA C:\Users\nigel\IdeaProjects\egeria\open-metadata-test\open-metadata-fvt\access-services-fvt\asset-consumer-fvt\target\classes
$ dir ..\..\..\..\..\..\open-metadata-distribution\open-metadata-assemblies\target\egeria-2.9-SNAPSHOT-distribution\egeria-omag-2.9-SNAPSHOT\*
The system cannot find the path specified.

nigel@MEGA C:\Users\nigel\IdeaProjects\egeria\open-metadata-test\open-metadata-fvt\access-services-fvt\asset-consumer-fvt\target\classes
$ dir ..\..\..\..\..\..\open-metadata-distribution\open-metadata-assemblies\target\egeria-2.9-SNAPSHOT-distribution\egeria-omag-2.9-SNAPSHOT\
The system cannot find the path specified.

nigel@MEGA C:\Users\nigel\IdeaProjects\egeria\open-metadata-test\open-metadata-fvt\access-services-fvt\asset-consumer-fvt\target\classes
$ dir ..\..\..\..\..\..\open-metadata-distribution\open-metadata-assemblies\target\egeria-2.9-SNAPSHOT-distribution\egeria-omag-2.9-SNAPSHOT
 Volume in drive C is Win10
 Volume Serial Number is 765D-6B1A

 Directory of C:\Users\nigel\IdeaProjects\egeria\open-metadata-distribution\open-metadata-assemblies\target\egeria-2.9-SNAPSHOT-distribution

2021-04-15  18:48    <DIR>          egeria-omag-2.9-SNAPSHOT
               0 File(s)              0 bytes
               1 Dir(s)  23,115,759,616 bytes free

nigel@MEGA C:\Users\nigel\IdeaProjects\egeria\open-metadata-test\open-metadata-fvt\access-services-fvt\asset-consumer-fvt\target\classes
$ cd  ..\..\..\..\..\..\open-metadata-distribution\open-metadata-assemblies\target\egeria-2.9-SNAPSHOT-distribution

nigel@MEGA C:\Users\nigel\IdeaProjects\egeria\open-metadata-distribution\open-metadata-assemblies\target\egeria-2.9-SNAPSHOT-distribution
$ dir egeria-omag-2.9-SNAPSHOT
 Volume in drive C is Win10
 Volume Serial Number is 765D-6B1A

 Directory of C:\Users\nigel\IdeaProjects\egeria\open-metadata-distribution\open-metadata-assemblies\target\egeria-2.9-SNAPSHOT-distribution\egeria-omag-2.9-SNAPSHOT

2021-04-15  18:48    <DIR>          .
2021-04-15  18:48    <DIR>          ..
2021-04-15  18:48    <DIR>          conformance-suite
2021-04-15  18:48    <DIR>          content-packs
2021-04-15  18:14            11,689 LICENSE
2021-04-15  18:14               276 NOTICE
2021-04-15  18:48    <DIR>          sample-data
2021-04-15  18:48    <DIR>          samples
2021-04-15  18:48    <DIR>          server
2021-04-15  18:14             1,866 truststore.p12
2021-04-15  18:48    <DIR>          user-interface
2021-04-15  18:48    <DIR>          utilities
               3 File(s)         13,831 bytes
               9 Dir(s)  23,115,759,616 bytes free

nigel@MEGA C:\Users\nigel\IdeaProjects\egeria\open-metadata-distribution\open-metadata-assemblies\target\egeria-2.9-SNAPSHOT-distribution
$

Note that the attempt to access the contents of the directory by relative path failed -- not found, yet a 'cd' then trying to list the remainder of the path worked ok....

This could be a limt of 260 chars in path - see https://www.howtogeek.com/266621/how-to-make-windows-10-accept-file-paths-over-260-characters/
To fix this -> https://www.howtogeek.com/266621/how-to-make-windows-10-accept-file-paths-over-260-characters/
ie edit HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem\LongPathsEnabled to 1

After that change the file can be accessed at the CLI, but the windows java process still fails ie
$ dir "../../../../../../open-metadata-distribution/open-metadata-assemblies/target/egeria-2.9-SNAPSHOT-distribution/egeria-omag-2.9-SNAPSHOT/server/server-chassis-spring-2.9-SNAPSHOT.jar"
 Volume in drive C is Win10
 Volume Serial Number is 765D-6B1A

 Directory of C:\Users\nigel\IdeaProjects\egeria\open-metadata-distribution\open-metadata-assemblies\target\egeria-2.9-SNAPSHOT-distribution\egeria-omag-2.9-SNAPSHOT\server

2021-04-15  18:35       144,336,410 server-chassis-spring-2.9-SNAPSHOT.jar
               1 File(s)    144,336,410 bytes
               0 Dir(s)  23,115,759,616 bytes free

nigel@MEGA C:\Users\nigel\IdeaProjects\egeria\open-metadata-test\open-metadata-fvt\access-services-fvt\asset-consumer-fvt\target\classes
$ java -jar "../../../../../../open-metadata-distribution/open-metadata-assemblies/target/egeria-2.9-SNAPSHOT-distribution/egeria-omag-2.9-SNAPSHOT/server/server-chassis-spring-2.9-SNAPSHOT.jar"
Error: Unable to access jarfile ../../../../../../open-metadata-distribution/open-metadata-assemblies/target/egeria-2.9-SNAPSHOT-distribution/egeria-omag-2.9-SNAPSHOT/server/server-chassis-spring-2.9-SNAPSHOT.jar

I'm inclined to suggest windows users build under WSL2 which will behave similarly to linux and macOS. If a native windows build is desired then pull requests to fix issues can be submitted.
Any readers care to comment on this idea?

^ @mandy-chessell

See https://github.com/odpi/egeria/pull/5084 which proposes use of WSL2 only to address this issue


crop resized images that get bigger beyond the bounds  parameter

This can happen specifically when using UIViewContentModeScaleAspectFill, and at least one of the dimensions is larger than the specified bounds. Since it's aspect fill, this center crops the resized image to the given bounds' dimensions.

Apologies for leaving this open for so long! As you can guess, I no longer use this code in any of my current projects. If you’re still interested in this PR, could you verify it’s compatible with Xcode 7 and provide a test image to demonstrate the issue? Thanks, and I apologize for not responding before!


dev container schemas: use unevaluatedProperties

See also https://github.com/devcontainers/spec/pull/167


Possibility to create two sets of clamps

Hi!
Thanks for amazing plugin, concept of fluid font-sizes are the best, very useful.
In my recent project, I found that I need to create two different sets of clamps, e.g. one for sizes from 320 to 768, and another for sizes 768 to 1440, but it is impossible, because plugin creates only one set (using last clamp)
It is possible to update plugin code to process all rules, instead of last one?
:root {
  @utopia clamps({
    minWidth: 320,
    maxWidth: 768,
    pairs: [
      [16, 24],
    ],
    prefix: "fluid-sm",
    usePx: true,
  });

  @utopia clamps({
    minWidth: 768,
    maxWidth: 1440,
    pairs: [
      [24, 96],
    ],
    prefix: "fluid-md",
    usePx: true,
  });
}

Hey @yagee - thanks for the message. Strange, it appears to be working for me:
Input
.test{
  @utopia clamps({
    minWidth: 320,
    maxWidth: 768,
    pairs: [
      [16, 24],
    ],
    prefix: "fluid-sm",
    usePx: true,
  });

  @utopia clamps({
    minWidth: 768,
    maxWidth: 1440,
    pairs: [
      [24, 96],
    ],
    prefix: "fluid-md",
    usePx: true,
  });
}

Output
.test {
  --fluid-sm-16-24: clamp(16px, 10.2857px + 1.7857vi, 24px);
  --fluid-md-24-96: clamp(24px, -58.2857px + 10.7143vi, 96px);
}

This was tested with PostCSS 8.4.33.
Are you getting a different result, or am I misunderstanding the problem?! Let me know 😄

It seems problem appears only using Astro.
Sorry for bothering you!
Have a nice day :)

@yagee interesting! I'll try and do some digging to see what differs in that environment


[Feature] Use mmeval.Accuracy

TBD

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


Suggestion: Filter for spawner spawned entities

A filter to determine if an entity came from a spawner would be extremely helpful.

Coming in next update - for future reference, this issue should be opened in libreforge, not eco


User Filter Autocomplete

building on #117 with an autocomplete for users...

blocked UPSTREAM https://github.com/LemmyNet/lemmy/issues/4146

https://github.com/tgxn/lemmy-modder/issues/47 <- this can use the same user search component

I'll get this in in the current state, but it would be nice to limit by local users only.

I'm gonna merge this in, since it's possible to search for users,


replace Travis CI by Github Actions

This is factored out of my other PR #271. I've tested this PR on my fork (see https://github.com/greimel/QuantEcon.jl/runs/6448797672?check_suite_focus=true)
@sglyon, please enable workflows for this PR (this is necessary for all first time contributors)
You will see that this one test is passing on 1.6 but failing on 1.7
The test depends on generated random numbers and these are unstable across Julia versions.

One way to fix this would be using https://github.com/JuliaRandom/StableRNGs.jl but I have no bandwidth to implement this.
Another option would be to allow a failure on this test, open an issue and fix this in the future.

@greimel Thank you for the PR!
I think the package should be tested also against the current version (= 1.7) (and nightly also), even if some tests fail.

Thanks for the feedback @oyamad!
I've updated the PR. Could you please approve the CI run again?

Thanks for approving the CI run! As you can see, there is one failing test on latest and nightly

I think this should be fixed in a separate PR. Would you mind merging this?

@greimel Thanks! Merging.


Bubble not moving

Hi i am trying to move the bubble via drag and also by providing absolute position but it is stick with bottom left corner.
Your github code version is 1.0.14 in pacakge.json.
while on the npm it is 1.1.1. I have tried both but not working moving option.
Can you please also share a sample app code that is using this package?

Hi, we removed option for making bubble draggable. There were some problems with it and we decided to remove it.
But, we were using this module for it: https://github.com/venits/react-native-movable-view
Usage of it is very simple:
<MovableView>
   <LiveChat/>
</MovableView>

That should be it ;)


bintools-wrapper: skip dynamic linker for static binaries

Currently we set dynamic-linker unconditionally. This breaks
however some static binaries i.e. rust binaries linked against musl.
There is no reason we should set an elf interpreter for static binaries
hence this is skipped if -static or -static-pie is either passed to
our cc or ld wrapper.

Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Tested with glibc and musl:
$ nix-build -A pkgsMusl.tests.cc-wrapper -A pkgsMusl.tests.cc-wrapper-clang -A tests.cc-wrapper -A tests.cc-wrapper-clang

This is now passing -dynamic-linker on darwin where it's not supported. See comment / thread: https://github.com/NixOS/nixpkgs/pull/107086#issuecomment-748849140

This PR was reverted in 363175cd (for now).  Unfortunately it isn't possible to reopen the original PR, but you can create a new one.

reopened: https://github.com/NixOS/nixpkgs/pull/107596


Test updated wasi-types.

The purpose of this veracruz PR is to test a wasi-types PR: https://github.com/veracruz-project/wasi-types/pull/6

The wasi-types PR has been merged.


remove serviceclassHolder and also fix the issue #2637

Fix the issue #2606

Codecov Report

Merging #2607 into 2.6.x will decrease coverage by <.01%.
The diff coverage is 60%.

@@             Coverage Diff              @@
##              2.6.x    #2607      +/-   ##
============================================
- Coverage     47.53%   47.53%   -0.01%
+ Complexity     4303     4302       -1
============================================
  Files           557      556       -1
  Lines         24433    24401      -32
  Branches       4349     4327      -22
============================================
- Hits          11615    11598      -17
+ Misses        11021    11000      -21
- Partials       1797     1803       +6

Impacted Files
Coverage Δ
Complexity Δ

.../main/java/com/alibaba/dubbo/common/Constants.java
88.88% <ø> (ø)
1 <0> (ø)
:arrow_down:

...n/java/com/alibaba/dubbo/config/ServiceConfig.java
48.37% <100%> (ø)
64 <0> (ø)
:arrow_down:

.../alibaba/dubbo/rpc/protocol/rest/RestProtocol.java
64.75% <100%> (ø)
14 <0> (ø)
:arrow_down:

...va/com/alibaba/dubbo/common/utils/ConfigUtils.java
71.42% <33.33%> (-0.3%)
45 <1> (+1)

...dubbo/common/status/support/LoadStatusChecker.java
50% <0%> (-10%)
2% <0%> (ø)

...mmon/threadpool/support/fixed/FixedThreadPool.java
80% <0%> (-7.5%)
3% <0%> (ø)

.../threadpool/support/limited/LimitedThreadPool.java
83.33% <0%> (-5.56%)
3% <0%> (ø)

...on/threadpool/support/cached/CachedThreadPool.java
85.71% <0%> (-4.29%)
3% <0%> (ø)

...ba/dubbo/remoting/transport/netty/NettyServer.java
67.85% <0%> (-3.58%)
8% <0%> (-1%)

...a/dubbo/remoting/transport/netty4/NettyClient.java
64.4% <0%> (-3.39%)
11% <0%> (-1%)

... and 16 more

Continue to review full report at Codecov.

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


Exposing the configuration for the BGP passive mode

https://redocly.github.io/redoc/?url=https://raw.githubusercontent.com/open-traffic-generator/models/bgp-passive-mode/artifacts/openapi.yaml&nocors
This PR is for a sub-part of RT-1.9: BGP Transport Parameters test.
Exposed passive_mode under BGP peer advanced configuration.
If set to true, the local BGP peer will wait for the remote peer to initiate the BGP session by establishing the TCP connection, rather than initiating sessions from the local peer.
Configuration snippet:
bgpIpv4Interface := device.Bgp().Ipv4Interfaces().
                            Add().
                            SetIpv4Name(ipv4Name)
bgpPeer := bgpIpv4Interface.Peers().
                    Add().
                    SetAsNumber(uint32(ixiaAs)).
                    SetAsType(gosnappi.BgpV4PeerAsType.IBGP).
                    SetPeerAddress(peerRemoteIp).
                    SetName(peerName)

**bgpPeer.Advanced().SetPassiveMode(true)**

Merging BGP Passive Mode changes to master


Activate crawler task based on a list of recent syncer obtain/extend lengths

Motivation
We want to control when we activate the network crawler task that will help us to populate the mempool. We want to be able to do this both for testing purposes as well as when zebra reaches the chain tip.
We also want to stop the mempool crawler if the syncer starts syncing large numbers of blocks again.
Specifications
Designs
Mempool Design diagram
Related Work
#2592

The crawler will receive a latest_sync_heights: watch::Receiver<Vec<usize>> to use to determine if it should be enabled or not, and the crawler should stop if that endpoint is closed.

Closed by #2667.


build(deps): update various dependencies

Update various dependencies

Bumps cryptography from 2.9.2 to 3.2, closes #31 and closes #32

Alphabetized Pipfiles to make them easier to update (pipenv update just updates Pipfile.lock)

Yes, functionality has been tested in a dev environment.


⚠ Samsung has degraded performance

In 9019b52, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2308 ms

Resolved: Samsung performance has improved in b06776f.


Port unwind tests to new x64 backend

In #2411, we discovered that unwind tests for the x86 backend are running even when the new x64 backend is enabled, resulting in test failures (due to the mismatch of implementation internals). In that PR, we disabled the old tests on the new configuration; but before we remove the old backend entirely, we need to preserve the test coverage by porting the tests over. This should largely be mechanical, with just some updates to the expected unwind info if the prologues/epilogues differ slightly.

I think all unwinding bits and pieces for the new backend are now in place, so I figure this can be closed.


Allow subclass constructors without super() call

TypeScript Version:
1.8.0
Code
Custom element classes often have constructors that just return document.createElement(), since HTMLElement doesn't have a callable constructor, but this generates an error in TypeScript:
class MyElement extends HTMLElement {
  constructor() {
    return document.createElement('my-element');
  }
}

In general, it is completely valid ES2015 to not call super(), as long as you don't access this.

Something similar was discussed in #5910

I know this is a very ugly solution but It works.
class MyElement extends HTMLElement {

	constructor() {
		try{
			super();
		}catch(e){
		}finally{
			return document.createElement('my-element');
		}
	}
}

Apparently TS's super() check isn't too robust, so I just did this:
constructor() {
  if (1 > 0) {
    super();
  }
  return document.createElement('my-element');
}

I think that code will beacome deprecated when unreachable code detection improves.
this does not work

class MyElement extends HTMLElement {
    constructor(element : string) {
        if (false){
		  super();
		}
		return document.createElement(element);
    }
}

this it does
class MyElement extends HTMLElement {
    constructor(element : string) {
        if (0){
		  super();
		}
		return document.createElement(element);
    }
}

Oops, I meant the other way! Editing...

@xLama there will always be some way to beat compile-time evaluation... it'll just get uglier over time.

What's the use of a class like this? Why not just have a factory function?
It seems crazy to have MyElement such that (new MyElement()) instanceof MyElement is false

(new MyElement()) instanceof MyElement will be true. document.createElement('my-element') will create an instance of MyElement.
The use, in this case, is that users want constructors, even before the built-in HTMLElement subclasses get callable constructors.
In other cases, a constructor could return a subtype, or return a cached instance.

That's not what I'm seeing in Firefox nightly -- maybe a bug on their side?

Firefox custom element support is behind a flag. You need to enable dom.webcomponents.enabled in about:config. Or try on Chrome.

Here's an example that works in Chrome: http://jsbin.com/xivutarobo/edit?html,console,output
With polyfills is also works on other browsers without flags.

Adding the code here, for convenience:
    class MyElement extends HTMLElement {
      constructor() {
        return document.createElement('my-element');
      }

      createdCallback() {
        console.log('created my-element');
      }
    }
    document.registerElement('my-element', MyElement);
    let el = new MyElement();
    console.log(el instanceof MyElement); // true

Is more info still needed, or was this enough?

I think this is enough.
For the vast majority of ES6 classes, not calling super is a big runtime error. We'd need to figure out how to still give an error in those cases while still allowing this.

Once big sign that super isn't necessary in the case of factory constructors is the presence of a return statement. Along with no access to this, is might be enough.
Otherwise, is there any existing warning suppression mechanism in TypeScript?

@justinfagnani If you are returning a value, not accessing this, and not calling super, why is it defined as a class. What exactly do you mean by 'factory constructors'? I know what they are in dart, but in JavaScript/TypeScript people usually speak in terms of factories or constructors.

First, it's just valid JavaScript that can type check, so it seems like it should be supported by a superset of JavaScript. As for use cases, the custom element use case is my primary concern. HTMLElement doesn't have a callable constructor yet, so extending it requires not calling super().
As for the term "factory constructor", yes Dart explicitly has this concept, but JavaScript already supports constructors returning something other than this. I think such constructors can reasonably be called factory constructors, instead of "constructors that return something other than this".

Given that HTMLElement's constructor never actually returns, it should actually return never. I'm thinking that

It should be allowed to extend something which has a construct signature of type never.
If a construct signature of some value's type returns never, then a super call is not needed if extending from that value.
If there is a super() call, it should be an error to access this before super (which is currently the case anyway).

The examples here, specifically regarding subclasses of HTMLElement are a bit out of date.
HTMLElement is now specified to return a value. See: https://html.spec.whatwg.org/multipage/dom.html#html-element-constructors in particular step 11.

https://github.com/Microsoft/TypeScript/issues/7574 is much, much more important to the Custom Elements use cases now.

Is there any way this check could be put behind a flag?  Being able to disregard super is incredibly useful for evolutions.
In my case I want to evolve an event, so I have something like this:
class SuperEvent extends Event {
  public superHeroIdentity: string;

  constructor(event: Event) {
    super(); // really trying to get rid of this line
    (event as any).superHeroIdentity = "Megavent";
    return event;
  }
}

const boringEvent = new Event("doThing").
const superEvent = new SuperEvent(boringEvent);
console.log(superEvent); // Megavent

I know evolution's aren't a wide spread concept in the programming world just yet, but they're incredibly useful and one of the best things about javascript.  All of this is valid javascript, so it would be really nice if typescript was capable of it as well.
Also, in this case

MyElement such that (new MyElement()) instanceof MyElement is [true]


camera.chuangmi_ipc009 no picture

hi,
i have the security 360 camera (detected as camera.chuangmi_ipc009).
i can coltrol the switch but i have no image.
when i try to open the entitie_picture from browser i get error 500 internal error..
from developer:
access_token: 8536b7xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxbf123a2dee61ea
model_name: chuangmi.camera.ipc009
brand: chuangmi
frontend_stream_type: hls
model: chuangmi.camera.ipc009
lan_ip: <IP_ADDRESS>
mac_address: 04:CF:8C:06:72:28
entity_class: MiotCameraEntity
home_room: Pargit's home Balcony
miot_type: urn:miot-spec-v2:device:camera:0000A01C:chuangmi-ipc009:1
camera_control.on: true
camera_control.image_rollover: 0
camera_control.night_shot: 0
camera_control.time_watermark: true
camera_control.wdr_mode: false
glimmer_full_color-2-6: true
camera_control.recording_mode: 3
camera_control.motion_tracking: false
stream_status-3-1: 1
state_updater: cloud
sub_entities: camera_control-2.on-1, motion_event
entity_picture: /api/camera_proxy/camera.chuangmi_ipc009_7228_camera_control?token=8536b7xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxbf123a2dee61ea
friendly_name: Mi Home Security Camera 360° 1080P Camera Control
supported_features: 3
what am i missing?
thanks

Can not support.


Creating OpenAPI project comes "Error resolving dependencies" in macOS Kitura app

Context and Description
A description of the issue.
This issue is as same as #1415.
Using Kitura app to create a project that is "Starter" or "OpenAPI", it comes to fail with "Error resolving dependencies". "Skeleton" is success.
Environment Details
Information about your OS, Swift version and Xcode version if on macOS.

tools
version

macOS
Mojave 10.14.3

Xcode Version
10.1 (10B61)

Kitura app
1.1 (1)

$ swift --version
Apple Swift version 4.2.1 (swiftlang-1000.11.42 clang-1<IP_ADDRESS>)
Target: x86_64-apple-darwin18.2.0

$ xcode-select -version
xcode-select version 2354.

Steps to Reproduce

Launch the Kitura app.
Select to create a "Starter" or "Skeleton" project.
Enter the name for new project.
Click "Create" button.

Expected vs. Actual Behaviour

[ ] Expected to happen...  new project should be created.
[ ] Actually happened...  an error dialog occurs as below and no project folder is created.

Thanks.

@KBryan Do you mean to try "xcode-select --install" again?

No try the Kitura Command Line Interface installation. It should be option 2 in the installing Kitura guide.

Isn't it right that Kitura app should work without the Kitura CLI?

You would think so. Or install Kitura CLI in the background.

@uskithub If everything works after installing the cli let us know and we can look at resolving that. If not then can you please copy the contents of ypur Package.swift and Package.resolved files from the project if they exist?
Thanks

@uskithub @KBryan
The macOS app does not use the CLI in the background nor does it require it. The only link between the macOS app and the CLI is that they both target the same repository for cloning down the projects.
One thing I can suggest is ensuring that your command-line tools are actually set, installing them isn't always enough sadly.
To check if your Command line tools are set:

Open Xcode
Click on Xcode in the task bar and select preferences from the drop down (or press ⌘ + ,)
Once the UI has popped up, go to the locations tab
Ensure the Command Line Tools: field has a value, if it does not try setting it.
Rerun the macOS app project creation

Let me know if this helps!

@kilnerm I tried to install Kitura CLI by Homebrew, but it came error below.
Is this as same reason as the error of Kitura app, isn't it?
$ brew install kitura
Updating Homebrew...
==> Installing kitura from ibm-swift/kitura
Error: Your Xcode (10.1) is too outdated.
Please update to Xcode 10.2.1 (or delete it).
Xcode can be updated from the App Store.

I will install latest Xcode and try again.

@uskithub Let me know how it goes!
If you upgrade to Xcode 10.2.1 you will be at the same level as I am and I can create the projects without issues.
Also, you should not need to install the cli tools for the Kitura app to work.

@uskithub
The reason you need to update Xcode is the macOS app and the CLI generate projects built for Swift 5 as defined in the generated Package.swift file and Swift 5 support was released in Xcode 10.2
Updating your Xcode to the latest version should resolve this issue at least :)

@uskithub Did the Xcode upgrade resolve your issue?

I will mark this as closed, if further assistance is required please re-open as necessary.


chore: cleanup imports and exports in fedimint-core and fedimint-server

Can we somehow enforce this in CI? Otherwise such changes are close to pointless since we'll regress again over time.

@tvolk131 Do you want to try enforcing it with .semgrep.yaml?

Try to enforce this using clippy. For instance, enable:
https://rust-lang.github.io/rust-clippy/master/index.html#/wildcard_imports

Please hold off on merging this pr as the aleph pr introduces a ton off changes in fedimint-server and any changes may send me into rebase hell

Please hold off on merging this pr as the aleph pr introduces a ton off changes in fedimint-server and any changes may send me into rebase hell…

I just marked this PR as draft until https://github.com/fedimint/fedimint/pull/3260 is merged

@tvolk131 You might want to submit a commit without fedimint-server changes.

You might want to submit a commit without fedimint-server changes.

Good idea! I messed around a bit and wasn't able to find a great one-size-fits-all regex to only allow wildcard imports where we want it and not where we don't. For example, it's normal to have use super::*; in the test module to avoid re-importing everything that the prod code is relying on. I settled on ^use .*::\*;$ which allows for the aforementioned case since it only counts uses that start with no whitespace (which will exclude any uses in a module declared within a file). It's not perfect, but it prevents regressions on several of the fixes in this PR.

Please still hold off on merging this pr as I am currently working on a big refactor of the server and this will cause rebase conflicts.

What's the status? LGTM.

Is it ready to review and land?

Is it ready to review and land?

@joschisan wanted to hold off on submission

Please still hold off on merging this pr as I am currently working on a big refactor of the server and this will cause rebase conflicts.

@joschisan can you please link the PR we're waiting on so I know when I should send this out for review?

@joschisan wanted to hold off on submission

AFAIK it landed a week ago or more. :D


ContentRoot is not correct on OSX

Not sure where this belongs so please feel free to close and point me in the right direction.
So I have the following in Program.cs:
            Console.Title = "Ombi";
            var host = new WebHostBuilder()
                .UseKestrel()
                .UseContentRoot(Directory.GetCurrentDirectory())
                .UseIISIntegration()
                .UseStartup<Startup>()
                .Build();

            host.Run();

Now when publishing an osx runtime, when running I get an exception thrown because it cannot find the appsettings.json at /users/TidusJar/.
Now the application is not being run from inside /users/TidusJar/ so I don't understand why it's trying to find the file in that directory.
Here is the startup.cs just for completion:
 public Startup(IHostingEnvironment env)
        {
            var builder = new ConfigurationBuilder()
                .SetBasePath(env.ContentRootPath)
                .AddJsonFile("appsettings.json", false, true)
                .AddJsonFile($"appsettings.{env.EnvironmentName}.json", true)
                .AddEnvironmentVariables();
            Configuration = builder.Build();

        }

dotnet --info
.NET Command Line Tools (1.0.1)

Product Information:
 Version:            1.0.1
 Commit SHA-1 hash:  005db40cd1

Runtime Environment:
 OS Name:     Windows
 OS Version:  10.0.14393
 OS Platform: Windows
 RID:         win10-x64
 Base Path:   C:\Program Files\dotnet\sdk\1.0.1

@tidusjar Directory.GetCurrentDirectory() is determined by the location of your console. It should match the output of pwd. Are you running dotnet like this: dotnet ~/some/path/to/MyApp.dll?

I just ran the file that was outputted from the Published folder (after dotnet publish).
So it was ran from /users/TidusJar/downloads/publish
The build is on AppVeyor and it's open source if you want me to link you to it.
I just don't understand what is going on here.

Can you share a minimal repro with exact steps to cause the issue? It's hard to tell what is going on here from what you have described.

I can, i'll have to do it later tonight.

Sorry for the late reply. I cannot seem to reproduce this with a bare bones application... I still cannot figure out why it is happening for my app though

Update, after updating all the nuget packages to the latest including Microsoft.AspNetCore I can now reproduce it using a File>New project
Here is the repository:
https://github.com/tidusjar/DotNetPublishOSX

In the screenshot, your current working directory is ~ aka /Users/TidusJar. This means Directory.GetCurrentDirectory() is not pointing to the folder that contains appsettings.json
Try this.
cd ~/Desktop/publish2/
./DotNetPublishOSXTest

Interesting, that now works.
Strange that before upgrading the Microsoft.AspNetCore package it was working fine.
The issue is now that it tells me it's running on port 5000 but I get 404 errors when navigating to it, that's possibly something else.
Thanks.


Missing pytz dependency

Needs to have pytz added into the install.

Actually only now needed for testing, but why not -- kept it in.


Anerdw: Watch dingdinghotpot.com

Anerdw requests the watch of the watch_keyword dingdinghotpot\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

dingdinghotpot\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by tripleee in Charcoal HQ


Simple CDN example

It'd be great if there were a simple copy+paste CDN example in the readme. This would allow people to easily try it out in the browser, deno, etc. with a simple copy-paste code snippet. I tried this:
let webp = await import("https://cdn.jsdelivr.net/npm/@jsquash/webp@1.2.0/+esm");

and it loads, but when I try decoding:
await webp.decode(arrayBuffer)

it can't find the codec files. I saw this example in the readme:
import decode, { init as initWebpDecode } from '@jsquash/webp/decode';

initWebpDecode(WASM_MODULE); // The `WASM_MODULE` variable will need to be sourced by yourself and passed as an ArrayBuffer.
const image = await fetch('./image.webp').then(res => res.arrayBuffer()).then(decode);

But https://cdn.jsdelivr.net/npm/<EMAIL_ADDRESS>doesn't exist, and @jsquash/webp only seems to export decode and encode functions - nothing else.
I also tried esm.sh: https://esm.sh/<EMAIL_ADDRESS>but it isn't even able to load the module in the first place, for whatever reason.

Ah, looks like unpkg is able to correctly find the codec files! This works:
let webp = await import(`https://unpkg.com/@jsquash/webp@1.2.0/index.js?module`);
let imageData = await webp.decode(arrayBuffer);

Could an example like that be added to the readme? Let me know if you want me to make the pull request.

@josephrocca Thanks for the suggestion. I can look into adding an unpkg example 👍
Looks like there might be an issue with jsDelivr and wasm files. Is there a known fix for this? If not, I think it's best to stick with unpkg.
I will note that this package has been built specifically for the browser runtimes. I am unsure of Deno and Bun compatibility at this time and am in no rush to implement.

Thanks! A simple example like that in the readme would be really helpful helpful I think.
It doesn't currently work with Deno (just says "Decoding error"), but that's likely not your problem anyway, since Deno aims to be ~completely compatible with browsers (so long as e.g. DOM isn't needed), so it should eventually work as they continue to improve compatability.

@josephrocca Deno does seem to work with what I've played around with. I've added some examples in commit 60a959a.
Deno has yet to support the ImageData API (https://github.com/denoland/deno/issues/19288) so you'll need to polyfill that.
Let me know if you're still encountering issues and I can take a look 👍

Thanks, Jamie! :pray:


Make storage upload have no chunk size by default.

Fixes #546.
@tseaver @thobrla
I took a stab at the issue but am still unsure of a few things:

Does apitools actually attempt a full upload when chunksize=None? (/cc @craigcitro)
Would we be better with a boolean like use_chunked=False and then just use the chunk size on the Blob?
Is having a separate keyword unintuitive?

Also @thobrla I'm curious, RE: "We should allow the user to override the chunk size". Do we need a default chunk size for downloads? In the case that someone creates an object with a custom chunk size, should we use it in this method or still try the "all in one go" approach?

Coverage remained the same at 100.0% when pulling afc9994bdf825a9d5076445253e88f10f15a55b8 on dhermes:fix-546 into b395360d429059e041ad84f3068ffb6a6dca0be4 on GoogleCloudPlatform:master.

It hasn't been merged into the mainline yet, but I implemented a chunksize=None approach for uploads in gsutil's fork of apitools: https://github.com/GoogleCloudPlatform/gsutil/blob/master/gslib/third_party/storage_apitools/transfer.py#L773
However, because you're using httplib2, there are a number of other issues that you'll need to solve to get this to work.  https://github.com/GoogleCloudPlatform/gsutil/blob/master/gslib/gcs_json_media.py has some examples.

As for chunk size in general, the ideal thing is not to use chunks for uploads or downloads at all unless you have a specific reason to do so (for example, buffering a streaming transfer).

Rather than passing in an upload_chunk_size, wouldn't it be more sensible to have Blob.CHUNK_SIZE be None as the appropriate default, but settable for cases where the application wanted to do chunking (maybe via a subclass?).

@tseaver That's why I asked "Do we need a default chunk size for downloads?".
From @thobrla answer above it seems that a default is not needed.
I'm still unclear if passing chunksize=None to our vendored in code is sufficient to fix #546.

Are we leaving the blob's own CHUNK_SIZE around, but just using it for downloads?  Should we be making it an explicit parameter there, too?

I plan on implementing the default chunk_size=None and then just using blob.chunk_size the way the class constant was used.
I just wanted to make sure passing chunksize=None to our vendored in code is sufficient before moving too much further.

so i've finally got myself an official repo for apitools; i'm planning on finally doing a round-robin merge to get all the copies back in sync. in particular:

if you're waiting on a fix that's only in the gsutil branch, let me know, and
we can also hopefully get you out of the business of having to keep your own copy of apitools code.

@craigcitro w00t! Thanks for the news.
The main question is

Does apitools actually attempt a full upload when chunksize=None?

which @thobrla indicates is only in upstream (gsutil).

Ping @craigcitro

Does apitools actually attempt a full upload when chunksize=None?

sorry, i missed this question earlier in the thread. i believe the code you're looking for is still upstream in gsutil, but i'm working on getting the various versions of apitools unified.

@craigcitro Do you need help on the unification?

UPDATE: Chatting with @craigcitro today (March 2, 2015) it seems the gsutil upstream changes have been merged into https://github.com/google/apitools
@tseaver Do you want to vendor in the latest updates from apitools and then I'll rebase? (I could vendor in too, but presume you could do it faster since you did it the first 2 times.)

Yeah, I'll vendor it in.

@craigcitro  I've done the re-vendoring, but now lack context to get the last set of tests passing:
======================================================================
ERROR: test_upload_from_file_resumable (gcloud.storage.test_blob.Test_Blob)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/tseaver/projects/agendaless/Google/src/gcloud-python/gcloud/storage/test_blob.py", line 418, in test_upload_from_file_resumable
    blob.upload_from_file(fh, rewind=True)
  File "/home/tseaver/projects/agendaless/Google/src/gcloud-python/gcloud/storage/blob.py", line 354, in upload_from_file
    finish_callback=lambda *args: None)
  File "/home/tseaver/projects/agendaless/Google/src/gcloud-python/_gcloud_vendor/apitools/base/py/transfer.py", line 804, in StreamInChunks
    additional_headers=additional_headers)
  File "/home/tseaver/projects/agendaless/Google/src/gcloud-python/_gcloud_vendor/apitools/base/py/transfer.py", line 764, in __StreamMedia
    '%d' % self.progress)
CommunicationError: Failed to transfer all bytes in chunk, upload paused at byte 4

======================================================================
FAIL: test_download_as_string (gcloud.storage.test_blob.Test_Blob)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/tseaver/projects/agendaless/Google/src/gcloud-python/gcloud/storage/test_blob.py", line 328, in test_download_as_string
    self.assertEqual(fetched, b'abcdef')
AssertionError: 'abc' != 'abcdef'
- abc
+ abcdef

======================================================================
FAIL: test_download_to_file (gcloud.storage.test_blob.Test_Blob)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/tseaver/projects/agendaless/Google/src/gcloud-python/gcloud/storage/test_blob.py", line 272, in test_download_to_file
    self.assertEqual(fh.getvalue(), b'abcdef')
AssertionError: 'abc' != 'abcdef'
- abc
+ abcdef

======================================================================
FAIL: test_download_to_filename (gcloud.storage.test_blob.Test_Blob)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/tseaver/projects/agendaless/Google/src/gcloud-python/gcloud/storage/test_blob.py", line 307, in test_download_to_filename
    self.assertEqual(wrote, b'abcdef')
AssertionError: 'abc' != 'abcdef'
- abc
+ abcdef

----------------------------------------------------------------------

It looks as though code which deals with explicitly-chunked stuff from the server side is now broken.

is the easiest way for me to play with it just to clone your branch?

Likely so:  I don't want to make it a PR here until things pass.  Just run tox -e py27 to see it fail.

@tseaver @craigcitro I'm happy to take up the vendor-ing in process of HEAD in apitools. What is required? @tseaver What stopped you before?

i think he was hitting test failures on upload/download; i'm intending to try it, but i've been believing that for 3+ weeks. :wink:

I can babysit you if you like.

my issue is that it hasn't hit the top of my todo list -- currently heads-down on something else completely.
gsutil is currently using the version of apitools at master, so i'm reasonably confident in that code. i just need to drop the new version in and see why it's failing for veneer.

Cool

#755 will lead to de-vendoring apitools, which will then require us to get our tests compatible with the new semantics (causing the failures above).
Once that lands, we can re-visit this one.

I agree. After hacking on #754 and a late night chat with Craig, it seems that is the best way forward.

@dhermes seems like merge of #811 requires revisiting / rebasing this PR?

Yes this PR is the one that made us realize #811 was "necessary" (more like was an option).

Closing this PR and going to take the new approach of just making CHUNK_SIZE optional.


Why not an iPad release with wasm32-wasi with AOT

Hi, I'm a WASM and CXL researcher at UCSC. I'd like to write C++ natively on iPad Pro since it's already equipped with M2 and 8GB Ram the same as MacBook. I'm wondering if vscode and all extensions are compiled with wasm32-wasi with AOT, it should automatically work. What's the bottleneck of doing so.

using AOT is neither remote ssh or running in simulator.

https://wasmcon2023.sched.com/event/1PCMJ/implementing-a-wasi-host-for-visual-studio-code-dirk-baumer-microsoft?iframe=no&w=100%&sidebar=yes&bg=no Your team has already made this a thing! We should make this happen together.


Updating examples with React 16

[x] Updated react-* dependencies
[x] Client side: render -> hydrate
[ ] Update Typescript examples: waiting for react-dom update

Nice!
Any idea on when will TS release types for 16?

Types for react was just updated. I will update the example asap

For TS, let's just cast ReactDOM to any and call hydrate()
(ReactDOM as any).hydrate()

I'll fix TS


Create codeql-analysis.yml

Why:

What's being changed:

Check off the following:

[x] All of the tests are passing.
[ ] I have reviewed my changes in staging.
[x] For content changes, I have reviewed the localization checklist
[x] For content changes, I have reviewed the Content style guide for GitHub Docs.

Hi @Mellbabe 👋🏼
Thanks for taking the time to contribute to this project.  For changes of this nature, we ask that you open an issue first so we can discuss the problem you're hoping to solve before starting work on an implementation. We also ask that you follow the pull request template when opening a pull request, to help clarify your intent. Please also take a look at our contributing docs for more info.
Seeing as we already have a CodeQL workflow, I'm going to close this pull request. If there's something missing from that existing workflow that needs to be improved, please open an issue for discussion.
Thanks!


code clean up, remove unused comments

Can you also update this comment from calcTradeSrcAmount (KyberNetwork)
/// @notice Recalculates srcAmounts and stores into tradingReserves, given the new destAmount.
Should be "stores into reservesData"

will be handled in another commit


begin

Description

Screenshots (if appropriate):

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] I have used ESLint & Prettier to follow the code style of this project.
[ ] I have updated the documentation accordingly.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.

Coverage remained the same at 93.255% when pulling f1df16f81b2c9bf6cf7c56e35cf992847a59b1d7 on 3009aksingh:begin into 3f9b3c728927542d878618c05f14510566c68255 on patw0929:master.

@3009aksingh The intension of #Hacktoberfest is to impact on open source community more frequently. Please DO NOT open an invalid PR.


added tabView

Thank you for your efforts.
I couldn't push the changes because of getting branch name error. I changed the branch name from  feat/hashtagViewPageTabs to  feat/hashtag-view-page-tabs. That's why your branch deleted and PR is closed automatically. Because of that I created #76 including my small styling and translation changes.