Skew Challenge not accepting answer on Safari.

Challenge use-the-css-transform-property-skewx has an issue.
User Agent is: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/602.4.8 (KHTML, like Gecko) Version/10.0.3 Safari/602.4.8.
Please describe how to reproduce this issue, and include links to screenshots if possible.

When changed from transform: skew(24deg); to transform: skewX(24deg);. This passes. Revising your code will correct the issue.

This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a temporary error. The following address(es) deferred:
<EMAIL_ADDRESS>Domain funtasticlabs.com has exceeded the max emails per hour (107/100 (107%)) allowed.  Message will be reattempted later
------- This is a copy of the message, including all the headers. ------
Received: from mailin-01.elitehosts.com ([<IP_ADDRESS>]:60195 helo=offsite.elitehosts.com)
by neo.internetwebserver.net with esmtp (Exim 4.87)
(envelope-from<EMAIL_ADDRESS>id 1dnx32-0003Rj-2m
for<EMAIL_ADDRESS>Fri, 01 Sep 2017 21:16:32 -0400
Received: from o10.sgmail.github.com ([<IP_ADDRESS>]:4492)
by offsite.elitehosts.com with esmtp (Exim 4.69)
(envelope-from<EMAIL_ADDRESS>id 1dnx2s-0001rw-J5
for<EMAIL_ADDRESS>Fri, 01 Sep 2017 21:16:22 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com;
h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe;
s=s20150108; bh=FxKOV0HKLq0dt7BdPcMZhtVZPRs=; b=XhOtn5f1LP7++anH
NlRLtB6D4SLYiRUr75pa7a6h2AvwpESdnbhSrNh7zAamR2NQH/dX/aBPugq1ri7r
t5UtksQG0n/pMvyUUQntcK2/kfwjweCeeuadm37PSUyuENlW1wIjjLbTGwW4MJib
QaZl9rCyqKScFlZjAs3r7NYRV/U=
Received: by filter0668p1mdw1.sendgrid.net with SMTP id filter0668p1mdw1-7793-59AA0664-21
2017-09-02 01:16:20.751689406 +0000 UTC
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [<IP_ADDRESS>])
by ismtpd0040p1mdw1.sendgrid.net (SG) with ESMTP id XoMXXDHpTdi-MJ0N4DKrFw
for<EMAIL_ADDRESS>Sat, 02 Sep 2017 01:16:20.712 +0000 (UTC)
Date: Sat, 02 Sep 2017 01:16:21 +0000 (UTC)
From: Quincy Larson<EMAIL_ADDRESS>Reply-To: freeCodeCamp/freeCodeCamp<EMAIL_ADDRESS>To: freeCodeCamp/freeCodeCamp<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Message-ID<EMAIL_ADDRESS>In-Reply-To<EMAIL_ADDRESS>References<EMAIL_ADDRESS>Subject: Re: [freeCodeCamp/freeCodeCamp] Skew Challenge not accepting answer
on Safari. (#13097)
Mime-Version: 1.0
Content-Type: multipart/alternative;
boundary="--==_mimepart_59aa0662e442a_bfe3f947717fc3c18947a";
charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: QuincyLarson
X-GitHub-Recipient: manzilo
X-GitHub-Reason: subscribed
List-ID: freeCodeCamp/freeCodeCamp <freeCodeCamp.freeCodeCamp.github.com>
List-Archive: https://github.com/freeCodeCamp/freeCodeCamp
List-Post<EMAIL_ADDRESS>List-Unsubscribe<EMAIL_ADDRESS>https://github.com/notifications/unsubscribe/AL1KCoNYR2GTR80uxTtdgDc-z160x-IWks5seKxigaJpZM4L14rn
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address<EMAIL_ADDRESS>X-SG-EID: 83UmH9Yz2HjU1qKK7JE10vR6ZA73mzRCr3l9ny8S/eH7V0xOclBD/Mdtqpxi/WqtcvHbYO9Cwrbmci
NdowHg1nHZYu4P7B98h0CQv8I6MO0kUOlDrmQkUucZruzPHvdBirirwFWD3E7TW2NY2qhHKZ809vTV
yrtWPfA8Lyd7BkhU41eJpYG6TmEIuDT6mGwjuoC8TeKwDtHad4DOkbrePx6TDWCK1pZ5vMo8oUYId4
Y=
X-MAILIN-01-MailScanner-Information: Please contact the ISP for more information
X-MAILIN-01-MailScanner-ID: 1dnx2s-0001rw-J5
X-MAILIN-01-MailScanner: Found to be clean
X-MAILIN-01-MailScanner-SpamCheck: not spam, SpamAssassin (not cached,
score=-1.666, required 10, AWL 0.12, BAYES_00 -1.90,
HTML_IMAGE_ONLY_24 1.62, HTML_MESSAGE 0.00, KHOP_THREADED -1.50,
SPF_PASS -0.00, T_RP_MATCHES_RCVD -0.01, URIBL_BLOCKED 0.00)
X-MailScanner-From<EMAIL_ADDRESS>X-Spam-Status: No
----==_mimepart_59aa0662e442a_bfe3f947717fc3c18947a
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: 7bit
Closed #13097.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/freeCodeCamp/freeCodeCamp/issues/13097#event-1232190154
----==_mimepart_59aa0662e442a_bfe3f947717fc3c18947a
Content-Type: text/html;
charset=UTF-8
Content-Transfer-Encoding: 7bit
Closed #13097.
—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or mute the thread.

{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/freeCodeCamp/freeCodeCamp","title":"freeCodeCamp/freeCodeCamp","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/freeCodeCamp/freeCodeCamp"}},"updates":{"snippets":[{"icon":"DESCRIPTION","message":"Closed #13097."}],"action":{"name":"View Issue","url":"https://github.com/freeCodeCamp/freeCodeCamp/issues/13097#event-1232190154"}}}
----==_mimepart_59aa0662e442a_bfe3f947717fc3c18947a--

This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a temporary error. The following address(es) deferred:
<EMAIL_ADDRESS>Domain oss-india.net has exceeded the max emails per hour (107/100 (107%)) allowed.  Message will be reattempted later
------- This is a copy of the message, including all the headers. ------
Received: from mail-oi0-f54.google.com ([<IP_ADDRESS>]:34301)
by server14.hostingraja.in with esmtps (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128)
(Exim 4.89)
(envelope-from<EMAIL_ADDRESS>id 1dnx3j-003lZV-QS
for<EMAIL_ADDRESS>Sat, 02 Sep 2017 06:47:32 +0530
Received: by mail-oi0-f54.google.com with SMTP id w10so13895179oie.1
for<EMAIL_ADDRESS>Fri, 01 Sep 2017 18:16:55 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:delivered-to:dkim-signature:dkim-signature:date
:from:reply-to:to:cc:message-id:in-reply-to:references:subject
:mime-version:content-transfer-encoding:precedence:list-id
:list-archive:list-post:list-unsubscribe;
bh=cUT+y3q+jDLvYaW6cdI4JY7Ppngq2mbIhy1wCUcMutI=;
b=J+NmMyouOxXPT6kJnScs9TnU3Wi+IpOKtctCwupUq5Ue47bzf16M8QoF0JgyNVWp/D
sa6kCSNlsxuz7pzW9YMW0kDY8yfa8mekderleF32BOsL+g0ho0kVIHXfMMe7H7c5JE0T
l+2lXvVAuYmY0i/td9Dfwlp2I4cNNtJxdxWSTYQAsALCmNy4oJk/EUKHJzgqvSisDx5y
0KXgYcYhIVdBPf+OA2thv5Www9SE1T3X1NAYtZAeqQxXV+elAxv5IIAZVXU2niNQbNWK
tCdCf8BCTkcs8FBVJKUErs0j5gJhmgWZQn0Yh2f00UZW0fg3ULU0+G4ovck7/AyVgide
JwrQ==
X-Gm-Message-State: AHPjjUh9XMWAdM/YddkLENbn5oYKDPrJ52Iumg/VuRBekpoYqcxpAOki
LtUJNC/Y9ASht2Gfu9KJuzFdBUHASm8hw30PQGi6OQ==
X-Received: by <IP_ADDRESS> with SMTP id m65mr4694896oig.25.1504314993433;
Fri, 01 Sep 2017 18:16:33 -0700 (PDT)
X-Forwarded-To<EMAIL_ADDRESS>X-Forwarded-For<EMAIL_ADDRESS><EMAIL_ADDRESS>Delivered-To<EMAIL_ADDRESS>Received: by <IP_ADDRESS> with SMTP id q13csp1352768ofe;
Fri, 1 Sep 2017 18:16:32 -0700 (PDT)
X-Google-Smtp-Source: ADKCNb4fVTvLmFblXBFRdiY3eYf8VdViu76hNpGKFYFfWgHmEr0U0cf0gOYVmPyfjJrELagwQJGv
X-Received: by <IP_ADDRESS> with SMTP id b65mr1198486itg.172.1504314992644;
Fri, 01 Sep 2017 18:16:32 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1504314992; cv=none;
d=google.com; s=arc-20160816;
b=HYCiiJgk8Nzlee3aE0qcrR7/aoKR6TMIkoSYhrS+oW7ZpKX2pWlwMuOBb22gcUa4vh
ODs7brVg904K4bTke4ZyiP4/Z+S7Hgo/Kh+Ey+4eMEY4tQxeqAowXGqC1kd010A2p0+e
2IZ3Jq3De7Yru1NvP5/NDU4pR21LsdS0vIa7X4UmRmsb8vlSRyuAb755V1PZfyWCA3th
RPF8F+w3j4B+EZtINuHuBbyQ1AxDIrFbQ+U8c+N+WtgVUN9ei9gaIaoFq+bqU56bivjs
Tgr/l/7uRex8v79yaC4TnekZkfbZkTw4g1sZZlqeB819LdozPt0XeJrzu7MWR7BvAvw2
m7gg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816;
h=list-unsubscribe:list-post:list-archive:list-id:precedence
:content-transfer-encoding:mime-version:subject:references
:in-reply-to:message-id:cc:to:reply-to:from:date:dkim-signature
:dkim-signature:arc-authentication-results;
bh=cUT+y3q+jDLvYaW6cdI4JY7Ppngq2mbIhy1wCUcMutI=;
b=coz5WUQK3Wse9HPtXcy0ecOTRnKcba11P8r3YktbZc6KG4Wm6ASYmmhbvc5zUJQoe4
q3LPJHrj/8763tEWfgqcW4sD4+iuRnCdfmEMwfREqsfanXXjs+Ue12aaifiLWjWuPowm
WbpTTkp8GtBG3Mo6XhHnBxXw53R3a6vWBHprX5gjzlmMLYdEZKGDLiAv/0Iypw7iBYwD
pdsT8ITgEDkzFr5P9CZtnAFYkH2omZBHXue0NkHXoPkEQiHkTIqOdPb5NlfkOsbAdEKR
bEJEj9ZFKLl2F7ET8p8vqP78+FYPhrsnwYFrRByKZ1GBkw4qbnigvJYaV4MS6ZQY5I7v
c1Jg==
ARC-Authentication-Results: i=1; mx.google.com;
dkim=pass<EMAIL_ADDRESS>header.s=s20150108 header.b=tcwxps3S;
dkim=pass<EMAIL_ADDRESS>header.s=smtpapi header.b=E2IzPmFr;
spf=pass (google.com: domain of<EMAIL_ADDRESS>designates <IP_ADDRESS> as permitted sender<EMAIL_ADDRESS>dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=github.com
Received: from o6.sgmail.github.com (o6.sgmail.github.com. [<IP_ADDRESS>])
by mx.google.com with ESMTPS id j15si1244726itf.169.2<IP_ADDRESS>.16.32
for<EMAIL_ADDRESS>(version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Fri, 01 Sep 2017 18:16:32 -0700 (PDT)
Received-SPF: pass (google.com: domain of<EMAIL_ADDRESS>designates <IP_ADDRESS> as permitted sender) client-ip=<IP_ADDRESS>;
Authentication-Results: mx.google.com;
dkim=pass<EMAIL_ADDRESS>header.s=s20150108 header.b=tcwxps3S;
dkim=pass<EMAIL_ADDRESS>header.s=smtpapi header.b=E2IzPmFr;
spf=pass (google.com: domain of<EMAIL_ADDRESS>designates <IP_ADDRESS> as permitted sender<EMAIL_ADDRESS>dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=github.com
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com;
h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe;
s=s20150108; bh=rUio7zcRsBihha8n/GdOMKg5KPk=; b=tcwxps3SBBV7B3Y6
1fFj3Z94spKmRw7YhHOMpn7LRdSql1OI9NqhWs2PBWWCf7VwyVph/U1EPTb8Up6q
2oagGHz5979N0m3UljN1M1xtL4QcOuyptMZtLz2sCe7tXphLVtuyfQhhX3Y9fzep
fCarh6QkvLQXPj+2m5RaXZi74HY=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=sendgrid.info;
h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe:x-feedback-id;
s=smtpapi; bh=rUio7zcRsBihha8n/GdOMKg5KPk=; b=E2IzPmFrtt+9F0CEvM
2oCqE5jllqXb2eCQXDwI5UmDaC+MFk8xR6JFRvC+dbL9gkMg89CD5ikyoxwCa+G5
BlZ8qAhwKghre4ibQbVgRtYO9BjP3qj2R5EmB/T7Tutuedl2M+OFGLMHCmlaNI+2
rDLrzxNtujp0ZBvuKW1P2Cp84=
Received: by filter0504p1mdw1.sendgrid.net with SMTP id filter0504p1mdw1-17586-59AA0670-26
2017-09-02 01:16:32.272332875 +0000 UTC
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [<IP_ADDRESS>])
by ismtpd0038p1mdw1.sendgrid.net (SG) with ESMTP id kcDI-PIeS0SV8mc93cqSXw
for<EMAIL_ADDRESS>Sat, 02 Sep 2017 01:16:32.208 +0000 (UTC)
Date: Sat, 02 Sep 2017 01:16:32 +0000 (UTC)
From: Quincy Larson<EMAIL_ADDRESS>Reply-To: freeCodeCamp/freeCodeCamp<EMAIL_ADDRESS>To: freeCodeCamp/freeCodeCamp<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Message-ID<EMAIL_ADDRESS>In-Reply-To<EMAIL_ADDRESS>References<EMAIL_ADDRESS>Subject: Re: [freeCodeCamp/freeCodeCamp] Skew Challenge not accepting answer
on Safari. (#13097)
Mime-Version: 1.0
Content-Type: multipart/alternative;
boundary="--==_mimepart_59aa066e84fe2_bfe3f947717fc3c2116da";
charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: QuincyLarson
X-GitHub-Recipient: pawan-mehta
X-GitHub-Reason: subscribed
List-ID: freeCodeCamp/freeCodeCamp <freeCodeCamp.freeCodeCamp.github.com>
List-Archive: https://github.com/freeCodeCamp/freeCodeCamp
List-Post<EMAIL_ADDRESS>List-Unsubscribe<EMAIL_ADDRESS>https://github.com/notifications/unsubscribe/AM9SCB1aDQD5QUwEJZHqc3DxjEleXCfnks5seKxugaJpZM4L14rn
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address<EMAIL_ADDRESS>X-SG-EID: OpfRgdkK9YQWPKIAgM5UQUoN56mCdWNmGtfFv0Mnvk0phLeQIk3EA2/Nq0dBAZhPNNF0QWUWYwPJdJ
zOUAyHW2fCjZ69YtfiiBAwkvRHbO2cUvvO4TzahSn3kuTq+YsKenATsn4RxGpv28/uCbEeoXdnolq7
JDo/6rm6D8FUT/rQv3FAMwwjZfLO4SRRuRN7Q4a1mr96WpNUGybfK0yucXKUfp/F+gPapVdUYReTaJ
M=
X-Feedback-ID: 848413:6xvVEJqleZlAW7/vhv7PzD/cv5tamo2SWZDKyvugGvg=:6xvVEJqleZlAW7/vhv7PzD/cv5tamo2SWZDKyvugGvg=:SG
X-Spam-Status: No, score=1.2
X-Spam-Score: 12
X-Spam-Bar: +
X-Ham-Report: Spam detection software, running on the system "server14.hostingraja.in",
has NOT identified this incoming email as spam.  The original
message has been attached to this so you can view it or label
similar future email.  If you have any questions, see
root@localhost for details.
Content preview:  Closed #13097. -- You are receiving this because you are subscribed
to this thread. Reply to this email directly or view it on GitHub: https://github.com/freeCodeCamp/freeCodeCamp/issues/13097#event-1232190154
[...]
Content analysis details:   (1.2 points, 5.0 required)
pts rule name              description

0.0 URIBL_BLOCKED          ADMINISTRATOR NOTICE: The query to URIBL was blocked.
See
http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
for more information.
[URIs: sendgrid.info]
-0.0 RCVD_IN_MSPIKE_H3      RBL: Good reputation (+3)
[<IP_ADDRESS> listed in wl.mailspike.net]
0.0 HEADER_FROM_DIFFERENT_DOMAINS From and EnvelopeFrom 2nd level mail
domains are different
0.0 T_SPF_HELO_TEMPERROR   SPF: test of HELO record failed (temperror)
-0.0 SPF_PASS               SPF: sender matches SPF record
0.0 HTML_MESSAGE           BODY: HTML included in message
1.3 HTML_IMAGE_ONLY_24     BODY: HTML: images with 2000-2400 bytes of words
-0.1 DKIM_VALID_AU          Message has a valid DKIM or DK signature from author's
domain
-0.1 DKIM_VALID             Message has at least one valid DKIM or DK signature
0.1 DKIM_SIGNED            Message has a DKIM or DK signature, not necessarily valid
-0.0 RCVD_IN_MSPIKE_WL      Mailspike good senders
X-Spam-Flag: NO
----==_mimepart_59aa066e84fe2_bfe3f947717fc3c2116da
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: 7bit
Closed #13097.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/freeCodeCamp/freeCodeCamp/issues/13097#event-1232190154
----==_mimepart_59aa066e84fe2_bfe3f947717fc3c2116da
Content-Type: text/html;
charset=UTF-8
Content-Transfer-Encoding: 7bit
Closed #13097.
—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or mute the thread.

----==_mimepart_59aa066e84fe2_bfe3f947717fc3c2116da--

This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a temporary error. The following address(es) deferred:
<EMAIL_ADDRESS>Domain funtasticlabs.com has exceeded the max emails per hour (119/100 (119%)) allowed.  Message will be reattempted later
------- This is a copy of the message, including all the headers. ------
------ The body of the message is 44325 characters long; only the first
------ 5000 or so are included here.
Received: from mailin-01.elitehosts.com ([<IP_ADDRESS>]:60353 helo=offsite.elitehosts.com)
by neo.internetwebserver.net with esmtp (Exim 4.87)
(envelope-from<EMAIL_ADDRESS>id 1dnx7E-0004eY-0g
for<EMAIL_ADDRESS>Fri, 01 Sep 2017 21:20:52 -0400
Received: from o10.sgmail.github.com ([<IP_ADDRESS>]:35550)
by offsite.elitehosts.com with esmtp (Exim 4.69)
(envelope-from<EMAIL_ADDRESS>id 1dnx6g-00023k-5V
for<EMAIL_ADDRESS>Fri, 01 Sep 2017 21:20:19 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com;
h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe;
s=s20150108; bh=swSRR1I0OXdVvPqACIzq+YXwW6c=; b=wbA4R3lSDi3Mgyv4
SBhNQIyQ14f/D19wJHq1+PV3kmg500OUkiGfA5fTEiW+CHu9t2NrCQTfbSJgyLNi
5YmdUdBTOWjgobk/7GiSOQZANUlDb4MfnrBw5xQ4el9aKnUoeDxJixw7U324eGQJ
bt5GzV9vCDbYVS6lVtQ8vlvYpTo=
Received: by filter0621p1mdw1.sendgrid.net with SMTP id filter0621p1mdw1-31103-59AA0751-21
2017-09-02 01:20:17.43679923 +0000 UTC
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [<IP_ADDRESS>])
by ismtpd0036p1mdw1.sendgrid.net (SG) with ESMTP id fJVOpYJyR0q9vb_RMlQ6Eg
for<EMAIL_ADDRESS>Sat, 02 Sep 2017 01:20:17.315 +0000 (UTC)
Date: Sat, 02 Sep 2017 01:20:17 +0000 (UTC)
From: Pawan Mehta<EMAIL_ADDRESS>Reply-To: freeCodeCamp/freeCodeCamp<EMAIL_ADDRESS>To: freeCodeCamp/freeCodeCamp<EMAIL_ADDRESS>Cc: Manzil<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Message-ID<EMAIL_ADDRESS>In-Reply-To<EMAIL_ADDRESS>References<EMAIL_ADDRESS>Subject: Re: [freeCodeCamp/freeCodeCamp] Skew Challenge not accepting answer
on Safari. (#13097)
Mime-Version: 1.0
Content-Type: multipart/alternative;
boundary="--==_mimepart_59aa07505ffd4_5403fa003af5c3421061d";
charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: pawan-mehta
X-GitHub-Recipient: manzilo
X-GitHub-Reason: comment
List-ID: freeCodeCamp/freeCodeCamp <freeCodeCamp.freeCodeCamp.github.com>
List-Archive: https://github.com/freeCodeCamp/freeCodeCamp
List-Post<EMAIL_ADDRESS>List-Unsubscribe<EMAIL_ADDRESS>https://github.com/notifications/unsubscribe/AL1KClwRFo_uEzDtbN8ozhXsXpSrZ0-iks5seK1QgaJpZM4L14rn
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address<EMAIL_ADDRESS>X-SG-EID: 83UmH9Yz2HjU1qKK7JE10vR6ZA73mzRCr3l9ny8S/eFtW1espvzU+bq5qHUmHtSxLAqsy/niES7ODx
N4t8sgmZO0kXoIbkLV/rM9jTGKplHYeTxSGyZuO2r42h0bjjRPWv2ZQrSGhIGIRzvUWWAw58LcOvkS
oTKZ6fZqODtm5334GgpaNracIbSlmPPMJot1NrW4+FmnPaVyTMSjS6fn7rNvqM2Xqgp7ZFmJrzhYtR
0=
X-MAILIN-01-MailScanner-Information: Please contact the ISP for more information
X-MAILIN-01-MailScanner-ID: 1dnx6g-00023k-5V
X-MAILIN-01-MailScanner: Found to be clean
X-MAILIN-01-MailScanner-SpamCheck: not spam, SpamAssassin (not cached,
score=-2.473, required 10, autolearn=not spam, AWL 0.94,
BAYES_00 -1.90, HTML_MESSAGE 0.00, KHOP_THREADED -1.50,
SPF_PASS -0.00, T_RP_MATCHES_RCVD -0.01, URIBL_BLOCKED 0.00)
X-MailScanner-From<EMAIL_ADDRESS>X-Spam-Status: No
----==_mimepart_59aa07505ffd4_5403fa003af5c3421061d
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: 7bit
This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a temporary error. The following address(es) deferred:
<EMAIL_ADDRESS>Domain oss-india.net has exceeded the max emails per hour (107/100 (107%)) allowed.  Message will be reattempted later
------- This is a copy of the message, including all the headers. ------
Received: from mail-oi0-f54.google.com ([<IP_ADDRESS>]:34301)
by server14.hostingraja.in with esmtps (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128)
(Exim 4.89)
(envelope-from<EMAIL_ADDRESS>id 1dnx3j-003lZV-QS
for<EMAIL_ADDRESS>Sat, 02 Sep 2017 06:47:32 +0530
Received: by mail-oi0-f54.google.com with SMTP id w10so13895179oie.1
for<EMAIL_ADDRESS>Fri, 01 Sep 2017 18:16:55 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:delivered-to:dkim-signature:dkim-signature:date
:from:reply-to:to:cc:message-id:in-reply-to:references:subject
:mime-version:content-transfer-encoding:precedence:list-id
:list-archive:list-post:list-unsubscribe;
bh=cUT+y3q+jDLvYaW6cdI4JY7Ppngq2mbIhy1wCUcMutI=;
b=J+NmMyouOxXPT6kJnScs9TnU3Wi+IpOKtctCwupUq5Ue47bzf16M8QoF0JgyNVWp/D
sa6kCSNlsxuz7pzW9YMW0kDY8yfa8mekderleF32BOsL+g0ho0kVIHXfMMe7H7c5JE0T
l+2lXvVAuYmY0i/td9Dfwlp2I4cNNtJxdxWSTYQAsALCmNy4oJk/EUKHJzgqvSisDx5y
0KXgYcYhIVdBPf+OA2thv5Www9SE1T3X1NAYtZAeqQxXV+elAxv5IIAZVXU2niNQbNWK
tCdCf8BCTkcs8FBVJKUErs0j5gJhmgWZQn0Yh2f00UZW0fg3ULU0+G4ovck7/AyVgide
JwrQ==
X-Gm-Message-State: AHPjjUh9XMWAdM/YddkLENbn5oYKDPrJ52Iumg/VuRBekpoYqcxpAOki
LtUJNC/Y9ASht2Gfu9KJuzFdBUHASm8hw30PQGi6OQ==
X-Received: by <IP_ADDRESS> with SMTP id m65mr4694896oig.25.1504314993433;
Fri, 01 Sep 2017 18:16:33 -0700 (PDT)
X-Forwarded-To<EMAIL_ADDRESS>X-Forwarded-For<EMAIL_ADDRESS><EMAIL_ADDRESS>Delivered-To<EMAIL_ADDRESS>Received: by <IP_ADDRESS> with SMTP id q13csp1352768ofe;
Fri, 1 Sep 2017 18:16:32 -0700 (PDT)
X-Google-Smtp-Source: ADKCNb4fVTvLmFblXBFRdiY3eYf8VdViu76hNpGKFYFfWgHmEr0U0cf0gOYVmPyfjJrELagwQJGv
X-Received: by <IP_ADDRESS> with SMTP id b65mr1198486itg.172.1504314992644;
Fri, 01 Sep 2017 18:16:32 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1504314992; cv=none;
d=google.com; s=arc-20160816;
b=HYCiiJgk8Nzlee3aE0qcrR7/aoKR6TMIkoSYhrS+oW7ZpKX2pWlwMuOBb22gcUa4vh
ODs7brVg904K4bTke4ZyiP4/Z+S7Hgo/Kh+Ey+4eMEY4tQxeqAowXGqC1kd010A2p0+e
2IZ3Jq3De7Yru1NvP5/NDU4pR21LsdS0vIa7X4UmRmsb8vlSRyuAb755V1PZfyWCA3th
RPF8F+w3j4B+EZtINuHuBbyQ1AxDIrFbQ+U8c+N+WtgVUN9ei9gaIaoFq+bqU56bivjs
Tgr/l/7uRex8v79yaC4TnekZkfbZkTw4g1sZZlqeB819LdozPt0XeJrzu7MWR7BvAvw2
m7gg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816;
h=list-unsubscribe:list-post:list-archive:list-id:precedence
:content-transfer-encoding:mime-version:subject:references
:in-reply-to:message-id:cc:to:reply-to:from:date:dkim-signature
:dkim-signature:arc-authentication-results;
bh=cUT+y3q+jDLvYaW6cdI4JY7Ppngq2mbIhy1wCUcMutI=;
b=coz5WUQK3Wse9HPtXcy0ecOTRnKcba11P8r3YktbZc6KG4Wm6ASYmmhbvc5zUJQoe4
q3LPJHrj/8763tEWfgqcW4sD4+iuRnCdfmEMwfREqsfanXXjs+Ue12aaifiLWjWuPowm
WbpTTkp8GtBG3Mo6XhHnBxXw53R3a6vWBHprX5gjzlmMLYdEZKGDLiAv/0Iypw7iBYwD
pdsT8ITgEDkzFr5P9CZtnAFYkH2omZBHXue0NkHXoPkEQiHkTIqOdPb5NlfkOsbAdEKR
bEJEj9ZFKLl2F7ET8p8vqP78+FYPhrsnwYFrRByKZ1GBkw4qbnigvJYaV4MS6ZQY5I7v
c1Jg==
ARC-Authentication-Results: i=1; mx.google.com;
dkim=pass<EMAIL_ADDRESS>header.s=s20150108 header.b=tcwxps3S;
dkim=pass<EMAIL_ADDRESS>header.s=smtpapi header.b=E2IzPmFr;
spf=pass (google.com: domain of<EMAIL_ADDRESS>designates <IP_ADDRESS> as permitted sender<EMAIL_ADDRESS>dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=github.com
Received: from o6.sgmail.github.com (o6.sgmail.github.com. [<IP_ADDRESS>])
by mx.google.com with ESMTPS id j15si1244726itf.169.2<IP_ADDRESS>.16.32
for<EMAIL_ADDRESS>(version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Fri, 01 Sep 2017 18:16:32 -0700 (PDT)
Received-SPF: pass (google.com: domain of<EMAIL_ADDRESS>designates <IP_ADDRESS> as permitted sender) client-ip=<IP_ADDRESS>;
Authentication-Results: mx.google.com;
dkim=pass<EMAIL_ADDRESS>header.s=s20150108 header.b=tcwxps3S;
dkim=pass<EMAIL_ADDRESS>h

This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a temporary error. The following address(es) deferred:
<EMAIL_ADDRESS>Domain oss-india.net has exceeded the max emails per hour (123/100 (123%)) allowed.  Message will be reattempted later
------- This is a copy of the message, including all the headers. ------
------ The body of the message is 24814 characters long; only the first
------ 5000 or so are included here.
Received: from mail-oi0-f54.google.com ([<IP_ADDRESS>]:33505)
by server14.hostingraja.in with esmtps (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128)
(Exim 4.89)
(envelope-from<EMAIL_ADDRESS>id 1dnx6Y-003v6Q-KD
for<EMAIL_ADDRESS>Sat, 02 Sep 2017 06:50:31 +0530
Received: by mail-oi0-f54.google.com with SMTP id r203so13992941oih.0
for<EMAIL_ADDRESS>Fri, 01 Sep 2017 18:19:50 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:delivered-to:date:dkim-signature:from:reply-to
:to:cc:message-id:in-reply-to:references:subject:mime-version
:content-transfer-encoding:precedence:list-id:list-archive:list-post
:list-unsubscribe;
bh=eBEaALIOWhD+QDt6sHVYZEdkO4rjtXeeGE9rAkYXljw=;
b=KSe+QUTzCeKBS+G0s81ENDLQC7wNveikdYIg4ivaXEEzVNbL0Ws1GHnc5A527Hdk9h
LyABEH6Z/sHl62I47uMcbpfiMlXP8+kxTjpYWOkVKFEpyaG/OM0M8p/s9aH7JCElKccO
KG/I0JfBBUdUpLbMUc74qjLAMR7Yq7o0P9slZuiPkE8skGgPD6wH9w8w1GWLGl4ECPck
eVByI2rKKjX7yGPnNFO4OCXVmBkwnYauIoMZK/AgARrQ/hbu4mMK1cBy6AP25XOqzlBY
ncpzxFoQ8G018cP2noFUNNMp2bIjDU6RExBF/UHLNoSAWy4weCMaTa/7bYWiIM/NDbeT
h8/g==
X-Gm-Message-State: AHPjjUjIQMVS+zYeYxEBe3PbyIN+mkZ3B4fzXbyF/pOBs8lM2YTAut5c
oc0EfFS0flpGm4Xhr6YCjy3o6wAIFIVjNu4zb1iuuw==
X-Received: by <IP_ADDRESS> with SMTP id v17mr3398836oia.127.1504315168351;
Fri, 01 Sep 2017 18:19:28 -0700 (PDT)
X-Forwarded-To<EMAIL_ADDRESS>X-Forwarded-For<EMAIL_ADDRESS><EMAIL_ADDRESS>Delivered-To<EMAIL_ADDRESS>Received: by <IP_ADDRESS> with SMTP id q13csp1354423ofe;
Fri, 1 Sep 2017 18:19:27 -0700 (PDT)
X-Google-Smtp-Source: ADKCNb4MySwebloMzpncKzw/+KZkCNhpckj6fmNoRV8bKT75RStlcLdd1hiLwOy3OXigaXW38fhl
X-Received: by <IP_ADDRESS> with SMTP id o190mr4916112qke.105.1504315167109;
Fri, 01 Sep 2017 18:19:27 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; t=1504315167; cv=none;
d=google.com; s=arc-20160816;
b=CPhf0Gdr4acizX51BoFUMagHUP9WdYGwxz5WeCmGLB9MjznRw7qnO3oy18MDSIx9Pn
78Gi4R6It7PpR9Ov86CpywOCWMGR2Uea6D49ydD5baec5E+Ac1Bwweru+auh1fw3gAXD
/+NW0J84YOCNL+BLHtxIVwux71Uo7E2323X1pKPJX15PyKaMCuKsD1HKA+9vojCzPgZH
96CIRzyH7qRnBElbIfhriWrm9t3p9PcLf4/e2qgfwvv5etSYQY+5NEEqt1oFFuzDG34a
XrKmgZe/S+TXeYVPItzIE54ZpIPMIokhiZ+cBpEjzB+ObRr82fjO7u7oivmio4qepmv1
wPIA==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816;
h=list-unsubscribe:list-post:list-archive:list-id:precedence
:content-transfer-encoding:mime-version:subject:references
:in-reply-to:message-id:cc:to:reply-to:from:dkim-signature:date
:arc-authentication-results;
bh=eBEaALIOWhD+QDt6sHVYZEdkO4rjtXeeGE9rAkYXljw=;
b=fVqCQ/gpwQj7I27vL6e9c4bndMVX3eUlwQafwRw+U9OEBnJ/Rys8XmSEq6zWKNfq8G
QHZeE5zja2Ytb3IaF2XLRrwhppqEw0F6npP5mknRXchP/LKfcB4RlNC09EFY+VlX0DTJ
FB4VkyHByzouIC4Oc0O7wVtu0nR9/oOLGmSy9DlTEO8lsq0Glf/O16vbNLkDxtLG/zTn
HKsIU0zDcvU43S0JdGMHKHERFj3sIZxYEoif6hRAov9LqLPeDi4mSHV/G+SRZu6j6m93
dAFRz3FizZOy6rKDuywWZtGL6Xk5Id2H5eSV7TtswYxa088l5xiOFaOMvaUFgIHHkzFD
HnQw==
ARC-Authentication-Results: i=1; mx.google.com;
dkim=pass (test mode<EMAIL_ADDRESS>header.s=pf2014 header.b=soxKuL+b;
spf=pass (google.com: domain of<EMAIL_ADDRESS>designates <IP_ADDRESS> as permitted sender<EMAIL_ADDRESS>dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=github.com
Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2-ext2.iad.github.net. [<IP_ADDRESS>])
by mx.google.com with ESMTPS id p21si1430573qta.220.2<IP_ADDRESS>.19.26
for<EMAIL_ADDRESS>(version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Fri, 01 Sep 2017 18:19:27 -0700 (PDT)
Received-SPF: pass (google.com: domain of<EMAIL_ADDRESS>designates <IP_ADDRESS> as permitted sender) client-ip=<IP_ADDRESS>;
Authentication-Results: mx.google.com;
dkim=pass (test mode<EMAIL_ADDRESS>header.s=pf2014 header.b=soxKuL+b;
spf=pass (google.com: domain of<EMAIL_ADDRESS>designates <IP_ADDRESS> as permitted sender<EMAIL_ADDRESS>dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=github.com
Date: Fri, 01 Sep 2017 18:19:07 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com;
s=pf2014; t=1504315166;
bh=eBEaALIOWhD+QDt6sHVYZEdkO4rjtXeeGE9rAkYXljw=;
h=From:Reply-To:To:Cc:In-Reply-To:References:Subject:List-ID:
List-Archive:List-Post:List-Unsubscribe:From;
b=soxKuL+bMmteXcFGkWf/cPujB1R5cDMfukQM5THi5vLrnvdlqrDF9uEUXF24EP9Hy
HjP3+Skbj9f5mONcxH0U2WHVcDXt5QnmAM1x3eC/TypAOWw9/Pc50xdyLx/u384XIh
+Y4o4EA4yMhXrB1KXvSOtXkST5OFwW4q+xktWi+o=
From: Manzil<EMAIL_ADDRESS>Reply-To: freeCodeCamp/freeCodeCamp<EMAIL_ADDRESS>To: freeCodeCamp/freeCodeCamp<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Message-ID<EMAIL_ADDRESS>In-Reply-To<EMAIL_ADDRESS>References<EMAIL_ADDRESS>Subject: Re: [freeCodeCamp/freeCodeCamp] Skew Challenge not accepting answer
on Safari. (#13097)
Mime-Version: 1.0
Content-Type: multipart/alternative;
boundary="--==_mimepart_59aa070b2cbc7_179613fe4d2787c3c17302c";
charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: manzilo
X-GitHub-Recipient: pawan-mehta
X-GitHub-Reason: subscribed
List-ID: freeCodeCamp/freeCodeCamp <freeCodeCamp.freeCodeCamp.github.com>
List-Archive: https://github.com/freeCodeCamp/freeCodeCamp
List-Post<EMAIL_ADDRESS>List-Unsubscribe<EMAIL_ADDRESS>https://github.com/notifications/unsubscribe/AM9SCKyBNKoGxgRudQTYQrIy-3aX3_7Qks5seK0LgaJpZM4L14rn
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address<EMAIL_ADDRESS>X-Spam-Status: No, score=0.2
X-Spam-Score: 2
X-Spam-Bar: /
X-Ham-Report: Spam detection software, running on the system "server14.hostingraja.in",
has NOT identified this incoming email as spam.  The original
message has been attached to this so you can view it or label
similar future email.  If you have any questions, see
root@localhost for details.
Content preview:  This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its recipients.
This is a temporary error. The following address(es) deferred: [...]
Content analysis details:   (0.2 points, 5.0 required)
pts rule name              description

0.0 URIBL_BLOCKED          ADMINISTRATOR NOTICE: The query to URIBL was blocked.
See
http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block
for more information.
[URIs: githubusercontent.com]
0.0 HEADER_FROM_DIFFERENT_DOMAINS From and EnvelopeFrom 2nd level mail
domains are different
0.0 T_SPF_TEMPERROR        SPF: test of record failed (temperror)
0.0 HTML_MESSAGE           BODY: HTML included in message
-0.1 DKIM_VALID_AU          Message has a valid DKIM or DK signature from author's
domain
-0.1 DKIM_VALID             Message has at least one valid DKIM or DK signature
0.1 DKIM_SIGNED            Message has a DKIM or DK signature, not necessarily valid
0.2 KAM_LOTSOFHASH         Emails with lots of hash-like gibberish
X-Spam-Flag: NO
----==_mimepart_59aa070b2cbc7_179613fe4d2787c3c17302c
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: 7bit
This message was created automatically by mail delivery software.
A message that you sent could not be delivered to one or more of its
recipients. This is a temporary error. The following address(es) deferred:
<EMAIL_ADDRESS>Domain funtasticlabs.com has exceeded the max emails per hour (107/100 (107%)) allowed.  Message will be reattempted later
------- This is a copy of the message, including all the headers. ------
Received: from mailin-01.elitehosts.com ([<IP_ADDRESS>]:60195 helo=offsite.elitehosts.com)
by neo.internetwebserver.net with esmtp (Exim 4.87)
(envelope-from<EMAIL_ADDRESS>id 1dnx32-0003Rj-2m
for<EMAIL_ADDRESS>Fri, 01 Sep 2017 21:16:32 -0400
Received: from o10.sgmail.github.com ([<IP_ADDRESS>]:4492)
by offsite.elitehosts.com with esmtp (Exim 4.69)
(envelope-from<EMAIL_ADDRESS>id 1dnx2s-0001rw-J5
for<EMAIL_ADDRESS>Fri, 01 Sep 2017 21:16:22 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=github.com;
h=from:reply-to:to:cc:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe;
s=s20150108; bh=FxKOV0HKLq0dt7BdPcMZhtVZPRs=; b=XhOtn5f1LP7++anH
NlRLtB6D4SLYiRUr75pa7a6h2AvwpESdnbhSrNh7zAamR2NQH/dX/aBPugq1ri7r
t5UtksQG0n/pMvyUUQntcK2/kfwjweCeeuadm37PSUyuENlW1wIjjLbTGwW4MJib
QaZl9rCyqKScFlZjAs3r7NYRV/U=
Received: by filter0668p1mdw1.sendgrid.net with SMTP id filter0668p1mdw1-7793-59AA0664-21
2017-09-02 01:16:20.751689406 +0000 UTC
Received: from github-smtp2a-ext-cp1-prd.iad.github.net (github-smtp2a-ext-cp1-prd.iad.github.net [<IP_ADDRESS>])
by ismtpd0040p1mdw1.sendgrid.net (SG) with ESMTP id XoMXXDHpTdi-MJ0N4DKrFw
for<EMAIL_ADDRESS>Sat, 02 Sep 2017 01:16:20.712 +0000 (UTC)
Date: Sat, 02 Sep 2017 01:16:21 +0000 (UTC)
From: Quincy Larson<EMAIL_ADDRESS>Reply-To: freeCodeCamp/freeCodeCamp<EMAIL_ADDRESS>To: freeCodeCamp/freeCodeCamp<EMAIL_ADDRESS>Cc: Subscribed<EMAIL_ADDRESS>Message-ID<EMAIL_ADDRESS>In-Reply-To<EMAIL_ADDRESS>References<EMAIL_ADDRESS>Subject: Re: [freeCodeCamp/freeCodeCamp] Skew Challenge not accepting answer
on Safari. (#13097)
Mime-Version: 1.0
Content-Type: multipart/alternative;
boundary="--==_mimepart_59aa0662e442a_bfe3f947717fc3c18947a";
charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: QuincyLarson
X-GitHub-Recipient: manzilo
X-GitHub-Reason: subscribed
List-ID: freeCodeCamp/freeCodeCamp <freeCodeCamp.freeCodeCamp.github.com>
List-Archive: https://github.com/freeCodeCamp/freeCodeCamp
List-Post<EMAIL_ADDRESS>List-Unsubscribe<EMAIL_ADDRESS>https://github.com/notifications/unsubscribe/AL1KCoNYR2GTR80uxTtdgDc-z160x-IWks5seKxigaJpZM4L14rn
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address<EMAIL_ADDRESS>X-SG-EID: 83UmH9Yz2HjU1qKK7JE10vR6ZA73mzRCr3l9ny8S/eH7V0xOclBD/Mdtqpxi/WqtcvHbYO9Cwrbmci
NdowHg1nHZYu4P7B98h0CQv8I6MO0kUOlDrmQkUucZruzPHvdBirirwFWD3E7TW2NY2qhHKZ809vTV
yrtWPfA8Lyd7BkhU41eJpYG6TmEIuDT6mGwjuoC8TeKwDtHad4DOkbrePx6TDWCK1pZ5vMo8oUYId4
Y=
X-MAILIN-01-MailScanner-Information: Please contact the ISP for more information
X-MAILIN-01-MailScanner-ID: 1dnx2s-0001rw-J5
X-MAILIN-01-MailScanner: Found to be clean
X-MAILIN-01-MailScanner-SpamCheck: not spam, SpamAssassin (not cached,
score=-1.666, required 10, AWL 0.12, BAYES_00 -1.90,
HTML_IMAGE_ONLY_24 1.62, HTML_MESSAGE 0.00, KHOP_THREADED -1.50,
SPF_PASS -0.00, T_RP_MATCHES_RCVD -0.01, URIBL_BLOCKED 0.00)
X-MailScanner-From<EMAIL_ADDRESS>X-Spam-Status: No
----==_mimepart_59aa0662e442a_bfe3f947717fc3c18947a
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: 7bit
Closed #13097.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/freeCodeCamp/freeCodeCamp/issues/13097#event-1232190154
----==_mimepart_59aa0662e442a_bfe3f947717fc3c18947a
Content-Type: text/html;
charset=UTF-8
Content-Transfer-Encoding: 7bit
Closed #13097.
—You are receiving this b


added team contract

Assignee Tasks

[ ] added unit tests (or none needed)
[ ] written relevant docs (or none needed)
[ ] referenced any relevant issues (or none exist)

Guidelines
Please add a description of this Pull Request's motivation, scope, outstanding issues or potential alternatives, reasoning behind the current solution, and any other relevant information for posterity.

Your PR Notes Here

will be merged with: https://github.com/red-dove/grace-shopper/pull/8


Reimplement get_stmts_for_gene()

This reimplements get_stmts_for_gene() using non-deprecated code from the principal database client (the old implementation no longer works).

The failing tests don't seem to be related to this PR


Increase disk resolver timeout

At 500ms, the device resolver timeout is too aggressive for some cloud deployments.

which iaas requires a larger timeout value?
Sent from my iPhone

On May 18, 2016, at 9:03 PM, Krishnan Ramanathan<EMAIL_ADDRESS>wrote:
At 500ms, the device resolver timeout is too aggressive for some cloud deployments.
You can view, comment on, or merge this pull request online at:
https://github.com/cloudfoundry/bosh-agent/pull/79
Commit Summary
Increase disk resolver timeout
File Changes
M platform/provider.go (2)
Patch Links:
https://github.com/cloudfoundry/bosh-agent/pull/79.patch
https://github.com/cloudfoundry/bosh-agent/pull/79.diff
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub

I guess this issue is about Bracket Computing. Possibly it can be moved in agent settings and built together with stemcell for this IaaS.

Sorry for the delay. Per allomov's suggestion will move it to agents settings. Will send out a new pull request with the changes.

@cppforlife I posted some comments in pull request #80 but you are probably not watching that anymore. In any case, can you let me know the next steps? We need atleast one of the pull requests to be accepted for cloud foundry to work on Bracket. If you need any additional information, let me know.

@krishnanrs we have a story: https://www.pivotaltracker.com/story/show/121262327 that's almost at the top of the backlog to pull this PR.

@cppforlife since I do not know your release cycle, when would this change be available in a release branch to be picked up by CF vendors?

@krishnanrs this change was included in 3262 stemcells available on bosh.io


Flask implementation - Pyctuator messes with app logging conf

Hi,
I'm trying to install Pyctuator on our existing app on Flask/uWSGI.
Everything works fine except that pyctuator is modifying the logging configuration of the application, and some things don't work as expected after Pyctuator is set up.
Our app is created the following way (redacted to the relevant part only) :
def create_app():

    """ Flask application factory """

    # create and configure the app
    app = Flask(__name__, instance_path=instance_path, instance_relative_config=True)
    app.config.from_json('config.json')

    # Allow CORS from angers.cnp.fr
    CORS(app)

    # Add proxyfix middleware to handle redirects correctly
    # x_port = 0 to work around Kong sending incorrect X-Forwarded-Port header
    app.wsgi_app = ProxyFix(app.wsgi_app, x_host=1, x_port=0)

    # configure the DB
    # pool_recycle must be set below 3600 to avoid the session to be killed by the firewall
    engine = create_engine(app.config["DATABASE_URI"], convert_unicode=True, pool_pre_ping=True, pool_recycle=3500)

   # Enable pyctuator
    pyctuator = Pyctuator(
        app,
        "Plateforme IA",
        pyctuator_endpoint_url=app.config["ROOT_API_PATH"]+'/actuator',
        app_url=None,
        registration_url=None
    )

    pyctuator.set_build_info(
        name="Plateforme IA",
        version=app.config["VERSION"],
        time=dateutil.parser.parse(app.config["BUILD_DATE"]),
    )

    pyctuator.register_health_provider(DbHealthProvider(engine))

    sentinel = Sentinel(app.config["CACHE_REDIS_SENTINELS"], socket_timeout=1.0)
    master = sentinel.master_for(app.config["CACHE_REDIS_SENTINEL_MASTER"], socket_timeout=1.0)
    pyctuator.register_health_provider(RedisHealthProvider(master))

    return app

application = create_app()

Before setting up Pyctuator, any runtime exception will be logged in uwsgi_error.log and I can use the root logger anywhere in an endpoint code and it gets logged in uwsgi_error.log, such as :

import logging
logging.critical("Test")

After setting up Pyctuator, nothing is logged in uwsgi_error.log at all.

This is not acceptable for us.
Any idea why we have this behaviour ?
FYI if I comment the line 92 in pyctuator.py, the problem goes away :
      root_logger.addHandler(self.pyctuator_impl.logfile.log_messages)

Thanks

Hi,
we're happy you're using Pyctuator, and appreciate your effort to write the issue in details...
Of course this is not by-design, and should be fixed!!
:)
We'll update regarding a fix asap

Thank you.
I figured out to make a very simple program to reproduce the issue.

Install flask and pyctuator in a venv

Create app.py as such :

import logging
from flask import Flask
from pyctuator.pyctuator import Pyctuator

app = Flask(__name__)

@app.route('/')
def _():
    logging.critical("This should be logged")
    return 'OK'

#pyctuator = Pyctuator( app, "test", pyctuator_endpoint_url='/actuator', app_url=None, registration_url=None)

In the directory execute flask run

go to http://localhost:5000/, you should see a page with "OK" and a message should be logged on the stderr of the flask comand

Now if you uncomment the pyctuator line and try again, you should see that the message is no longer logged on stderr

👍
I was able to reproduce!!

Looking at your reproducer app:
while the critical log entires aren't shown in console, I can see them via the Pycatuator logfile API (/actuator/logfile in your case).
The reason is that the python logging system wasn't initialized before Pyctuator started.
In this case Pyctuator's logging-handler (the one that's responsible for intercepting log messages and making them available via the API) is the only handler that is installed...
As you can see in https://docs.python.org/3/library/logging.html#logging.basicConfig:

The functions debug(), info(), warning(), error() and critical() will call basicConfig() automatically if no handlers are defined for the root logger.

To fix this, you should initialize the logging system before starting Pyctuator by calling any of:

logging.info("some message")
logging.basicConfig(level=logging.INFO)
(we've used the latter in flask_example_app)

Regardless, I will change Pyctuator so it will initialize the logging system if not yet initialized which will solve this issue.

@jpays, please confirm this fix in v0.13
🙂

Ok, this makes perfect sense.
I upgraded to v0.13 and I confirm that the behaviour is fixed in the reproducer app, and also in my real application.
Thanks for your actions :)


Syntax highlighting, bracket matching etc doesn't respect nested comments

Dafny /* and */ comments nest, but the syntax highlighting, bracket matching, etc don't recognize this.  For instance,
  function foo(i: nat): nat {
    /* comment
    /* nested comment
    */ }
    */
  }

VSCode syntax highlighting doesn't properly color the } on line 4 as a comment.  Furthermore, if I put the cursor on the {, VSCode highlights the } on line 4 as the matching brace, while Dafny actually considers the } on line 6 to be the matching brace.  (And, if I use the Vim extension keybind % to jump to the matching brace, it also jumps to the wrong brace.)
This leads to counterintuitive parse errors: suppose you accidentally omitted the final }, Dafny will complain about needing a }, but VSCode will tell you everything is matched.  Or, if you accidentally have /* inside a comment, Dafny will consider the rest of the file commented out, while in VSCode everything looks fine.

It's time for an upgrade ! I just pushed a PR to fix that pesky problem.

😌


Allow auto termination of spans

Goal
Implements auto-termination of spans. This is achieved by checking whether a span has AutoTerminationMode.ON_BACKGROUND just before the session payload is constructed, and terminating it and its descendants if this is true.
Testing
Added integration tests.

@bidetofevil I added some extra test cases to the integration test & made some slight tweaks to the implementation, so putting this out for review again.


python311Packages.metar: 1.10.0 -> 1.11.0

Diff: https://github.com/python-metar/python-metar/compare/refs/tags/v1.10.0...v1.11.0
Changelog: https://github.com/python-metar/python-metar/blob/v1.11.0/CHANGELOG.md
Description of changes

Things done

Built on platform(s)

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

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

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

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

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

[ ] Fits CONTRIBUTING.md.

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

9 packages built:

home-assistant-component-tests.nws
python310Packages.metar
python310Packages.metar.dist
python310Packages.pynws
python310Packages.pynws.dist
python311Packages.metar
python311Packages.metar.dist
python311Packages.pynws
python311Packages.pynws.dist


Potential challenges around outdated node.js modules

[ ] check RegExp DoS issue in minimatch
[ ] check injection in limit/offset of sequelize
[ ] check lingo and node-uuid for known issues
[ ] update/replace all remaining modules where no challenge could be created from

npm WARN deprecated<EMAIL_ADDRESS>security/injection issue with limit/offset fixed in 3.17.0
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated<EMAIL_ADDRESS>Use uuid module instead
npm WARN deprecated<EMAIL_ADDRESS>This project is abandoned
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

A recent security report from GitLab shows 74 vulnerabilities (many of them duplicates or from devDependencies, though) in the Juice Shop. Some of them are already exploited in challenges (e.g. both JWT Tiers, XSS Tier 4). Might be worth a look for this ticket...
artifacts.zip

So unzipper v0.8.12 (https://www.npmjs.com/package/unzipper) is vulnerable to arbitrary file write vulnerability and can be used for this challenge. Flow and implementation problems are like following :

Help and suggestion are needed for the problems shown.

@CaptainFreak the vulnerability in unzipper was fixed on Apr 16th 2018 within 24 hours of the initial report (see https://github.com/ZJONSSON/node-unzipper/commit/2220ddd5b58f6252069a4f99f9475441ad0b50cd).   Feel free to explicitly include the vulnerable version for this challenge but you have to include the specific version without tilde or caret prefix and ideally note that this vulnerability has been fixed.
Here is a vulnerable zip file and you find the corresponding test here

Yes, this challenge is already completed and merged. Thanks.

Thanks @ZJONSSON, we have already pinned the version accordingly! Also thanks for actually fixing it so quickly! 👍

Awesome!   This is a really interesting project, thanks for including!!


Feature/dx12 compute

All dx11 tests now, are now run as dx12 tests on render-test. Both render and compute dx12 tests pass.

Fix problems binding in D3D12Renderer
Fix problem handling texture arrays and cubmaps on D3D12
Generate dx12 tests from dx11 tests
Control tests run from the command line (to not run D3D12 tests use the option -api all,-dx12)

API switching is only being used for Dx12 currently (because it's not a simple simple relationship from a test to Api usage)
The -api option (for slang-test), has a simple language to determine what is run. All options are run in order and are comma separated. So
-api all,-d3d12
Means all except d3d12. Alternatively
-api d3d11,ogl
Would just be fore dx11 and ogl. (As previously stated, though on dx12 switching is actually enabled in terms of test switching).

Once you've finished getting AppVeyor to ignore the d3d12 tests (or run on WARP, or whatever works for now), go ahead and add me as a requested reviewer and I'll give this a quick look.

One last note on the k prefix thing: I'm all over the map on what would be the best convention for enum tags, and so that is maybe the one place where we have the most competing ideas in the code. I'm definitely open to opinions on what we should do there, especially when it comes to having both enum class and non-class enums.

One last note on the k prefix thing: I'm all over the map on what would be the best convention for enum tags, and so that is maybe the one place where we have the most competing ideas in the code
Probably not. On another project I'm working with they are coming up with standards for k prefixing and e prefixing. I'm not really mad about this - it seems a little too hungarian notation for my liking. I don't think in practice - it's rarely important to know if something is an enum or type just by looking at it. I would expect it to be pretty clear in the majority of cases.
In the past on other projects it's been upper snake for enums. That can occasionally hit macro problems. It's not that problematic I don't think, but it's not no problem.
Anyhoo - I'm not super wedded to any of them. If it were up to just me I'd probably go either upper snake, or upper camel. Prefixing is fine too - but if we do that, it might be best to take the most common style (or project we most want to align with).


Gradle plug-in: only verify artifacts used in main application

We currently use the Gradle dependencyCheck plug-in for an Android project. The problem is that the checker flags libraries with CVE's that are only used by unit test plug-ins, they don't end up in the actual application.
It would be nice if we could configure the dependency check plug-in so that it only verifies the artifacts that actually end up in the application.

I still think there is value in having the option to analyse all. I will try and add a feature to make it optional for the plugin.

A configuration option has been added to skip dependency groups that begin with test. This will be available in the next release.

Thanks allot! :smile:


The middleware can not update the value of the storeId variable

https://github.com/ecomclub/express-app-boilerplate/blob/11425b06af8804444ac752f66d3333d9e1abfc32/app/bin/web.js#L30
@leomp12 The middleware updates the value of the storeId just inside the function. When next () calls the next function the storeId variable remains undefined outside the middleware scope.

My fault, we may use req.storeId instead.
I'll update it, thanks.

https://github.com/ecomclub/express-app-boilerplate/commit/a3bebaa30602093e6cc95f120ce9bd57906d16b8


Run full smoke test suite nightly Mon-Fri

This will run all smoke tests, Monday to Friday, at 1:30 UTC.
Adding this so we have recurring nightly feedback against latest develop for the entirety of the smoke tests.

Closing for now


Is there a way to render image sprites?

Hey all. First, thanks for all the hard work to make a great library. I actually am building a pretty large graph, and tried a bunch of different graphing libraries, and none were as fast as smooth as sigma. Super cool stuff!
My question, could anyone share a pointer on how I would go about rendering image sprites? For example, I know I can use getNodeImageProgram() to render an image for my node backgrounds. However, I have a very large graph (5k+ nodes), each with a distinct background image. So what I'd like to do is compile all these images in a large sprite file (or two, or three), and use offsets to reference the sub-portion of the image I want (thereby saving thousands of network requests). My problem is I'm not sure how to do that in webgl land.
I was actually able to follow a tutorial on how to render multiple images at different offsets using webgl (https://webglfundamentals.org/webgl/lessons/webgl-2d-drawimage.html), but I got stumped when trying to integrate it into the Sigma node program framework. I suspect it's not a huge change from the current node image program, but I'm not much of a webgl expert!
Thanks in advance for any help.

Actually, the current node image program deals with images with its own sprite (it's named a "texture atlas" in WebGL but it's basically the same thing).
I guess you could rewrite the image program where you give it directly a sprite, and each node would carry it's image coordinates. It would actually be easier to write than the current program, since it has to handle each image load, and the update of the texture atlas.

Hey! Thanks for the response : )
I was actually able to get the sprite rendering working (a few months ago, I forgot I still had this question open). It worked basically as you said -- for the most part I just ripped out a lot of the extra image loading logic, and iirc tracked the image coords a little differently. But overall a success! Thanks


fix: Status of the newest drop - Change

Thank you for your contribution to the KodaDot - One Stop Shop for Polkadot NFTs.
👇 __ Let's make a quick check before the contribution.
PR Type

[x] Bugfix

Context

[x] Closes #9290

Did your issue had any of the "$" label on it?

[x] My DOT address: Payout

Copilot Summary
copilot:summary
copilot:poem

😍 Perfect, I’ve sent the payout
💵 $20 @ 6.78 USD/DOT ~ 2.95 $DOT
🧗 16SjUbGKSdjCdWTy3NNT3JxbRVGGqD4mwkHpc6BD9U2Rp29Z
🔗 0x5deb5b5880cf7f9a4c314ffef09e6d088f596c40f417d8fee62911181f16394e
🪅 Let’s grab another issue and get rewarded!
🪄 github.com/kodadot/nft-gallery/issues


Adding support for named components to the test framework

This PR adds support for creating multiple instances of components in the test framework by giving them different names. This can be used to split apart the Apps object and create individual echo backends, an example of which is in this PR. This will also be used to create multiple pilot_agent instances.
Next up is hooking up the configuration pathway, which is not yet implemented.
I also refactored dependency processing a bit and make it a bit simpler and more straightforward so I could plug in the named dependency support.

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: nmittler, smawson
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

pkg/OWNERS [nmittler]
tests/integration2/OWNERS [nmittler]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Update the Contributor fetch request

Updated the contributor fetch request to fetch all the data.
FIXES #193.
@notsoocool Please merge ASAP.

@notsoocool Please merge the PR once you review it.


Problem with Temp Dir?

I installed on a fresh ubuntu 16.04 server image, with all default configs. The website loads up looking great on port 8089 but I always see 0 bytes recorded in the UI, and running without -d I see an error writing to the temporary directory.
I am new to docker, so I am not sure how to get a shell and check the folder. I tried docker ls and docker attach but that didn't seem to do what I want. :-\
app_1             | 2016-08-20 17:58:40,968: [INFO]: Starting new HTTP connection (1): recorder
webagg_1          | /usr/local/lib/python3.5/site-packages/urllib3/connectionpool.py:838: InsecureRequestWarning: Unverified HTTPS request
is being made. Adding certificate verification is strongly advised. See: https://urllib3.readthedocs.io/en/latest/security.html
webagg_1          |   InsecureRequestWarning)
webagg_1          | [pid: 15|app: 0|req: 13/59] <IP_ADDRESS> () {32 vars in 1298 bytes} [Sat Aug 20 17:58:40 2016] POST /live/resource/postr
eq?param.user=temp-PLZBE3I7&param.coll=temp&param.rec=recording-session-5&closest=now&url=https%3A%2F%2Fpixel.facebook.com%2Fsi%2Fkappa%2F
async%2F%3FKa%3DAbEy68WjXipDa1w2%26Kt%3D1471715920850%26Ko%3Da%26__a%3D1%26__be%3D-1%26__dyn%3D7xeXxaER2HwNJ0ZwRAKGzEyay6-C11xG3Kq2i5U4e1o
x27QdwPwDyUG4XzEa8uwh9Vobo88lwIwHwJwpUO6Egx61YCBxZ3E%26__pc%3DPHASED%253ADEFAULT%26__req%3D7%26__rev%3D2518278%26__user%3D0%26asyncSignal%
3D1607%26lsd%3DAVr0diR9 => generated 2711 bytes in 31 msecs (HTTP/1.1 200) 6 headers in 489 bytes (13 switches on core 399)
app_1             | 2016-08-20 17:58:41,008: [DEBUG]: "POST /record/live/resource/postreq?param.user=temp-PLZBE3I7&param.coll=temp&param.r
ec=recording-session-5&closest=now&url=https%3A%2F%2Fpixel.facebook.com%2Fsi%2Fkappa%2Fasync%2F%3FKa%3DAbEy68WjXipDa1w2%26Kt%3D14717159208
50%26Ko%3Da%26__a%3D1%26__be%3D-1%26__dyn%3D7xeXxaER2HwNJ0ZwRAKGzEyay6-C11xG3Kq2i5U4e1ox27QdwPwDyUG4XzEa8uwh9Vobo88lwIwHwJwpUO6Egx61YCBxZ3
E%26__pc%3DPHASED%253ADEFAULT%26__req%3D7%26__rev%3D2518278%26__user%3D0%26asyncSignal%3D1607%26lsd%3DAVr0diR9 HTTP/1.1" 200 None
recorder_1        | Traceback (most recent call last):
recorder_1        |   File "/webrecore/recorder/recorderapp.py", line 48, in _write_loop
recorder_1        |     self._write_one()
recorder_1        |   File "/webrecore/recorder/recorderapp.py", line 65, in _write_one
recorder_1        |     self.writer.write_req_resp(req, resp, params)
recorder_1        |   File "/webrecore/recorder/warcwriter.py", line 112, in write_req_resp
recorder_1        |     self._do_write_req_resp(req, resp, params)
recorder_1        |   File "/webrecore/recorder/warcwriter.py", line 427, in _do_write_req_resp
recorder_1        |     return self._write_to_file(params, write_callback)
recorder_1        |   File "/webrecore/recorder/warcwriter.py", line 453, in _write_to_file
recorder_1        |     out = self._open_file(filename, params)
recorder_1        |   File "/webrecore/recorder/warcwriter.py", line 371, in _open_file
recorder_1        |     fh = open(filename, 'a+b')
recorder_1        | FileNotFoundError: [Errno 2] No such file or directory: '/data/warcs/temp-PLZBE3I7/rec-20160820175841016175-4097da1c0d
50-ZXGJZEJH.warc.gz'

I think this was a permissions issue with ./data dir, where the Docker container did not have access to write to the data dir. I think I improved this recently by not running Docker as root but as a new user and mapping it to the user with uid 1000. This isn't guaranteed to work in all cases, but should at least make this less likely. If this happens again, the ./data/warcs dir can be set to be world writable. Let me know if this happens again on a new deployment


FW-4394 Reduce duplicate queries in dictionary entry views

Description of Changes
These changes add a context object to the dictionary views which is then passed to the dictionary entry serializer. This context object contains alphabet, ignored character, base character, character variant, and ignorable character information. This information can be collected once and reused during the fetching of each dictionary entry instead of re-querying the database each time.
If testing locally, please try the dictionary list view and detail views and compare the number of queries before and after the changes. The number should at least stay the same or decrease significantly. The changes are more noticeable on a site with a larger number of characters, character variants, ignored characters, and dictionary entries. The number of queries can be seen by using the toolbar in debug mode.
Checklist

[x] README / documentation has been updated if needed
[x] PR title / commit messages contain Jira ticket number if applicable
[x] Tests have been updated / created if applicable
[x] Admin Panel has been updated if models have been added or modified
[x] Migrations have been updated and committed if applicable

Reviewers Should Do The Following:

[x] Review the code changes here
[x] Pull the branch and test locally

Additional Notes
N/A

This definitely reduces the db queries I'm seeing locally (dictionary list went from 105 down to 42) :)


drop CMath class

Large entrance task. The goal is to stop using CMath in the shogun codebase and use the C++ standard library instead, e.g. std::log rather than CMath::log or std::sort rather than CMath::qsort.
Once a method is not used anymore, it should be dropped from the CMath class entirely.
PRs should be sent method by method pls.
Good entrance task if you want to work on modernizing shogun

Hello,
I tried doing this and updated DynArray.h but when I sent PR, it didn't pass the first test and I'm not getting what went wrong. Can you help?

@karlnapf I am ready with a PR to get rid of CMath::log but the gpl submodule needs to be updated as well..... should i make a PR against shogun-gpl ? (Its causing build to break on Travis)

Yes, exactly


Logo contribution

@batarian71 I pushed another commit to move the logo directory and to acknowledge your contribution.
Thank you very much!


Update about-me.mdx

Bunnyshell created the Environment emilia / qademosp-patch-1:master / PR-2 for PR #2:


Add Telegram Badge To The Readme That Links To The Bot

Hi @nezorflame,
thank you so much for your awesome Telegram bot. What do you think of adding a badge to the Readme that links to your bot (e.g. t.me/9gag)?

Hi. Bot is not ready yet, but as soon as it gets finished, the link will appear in the README.


fix: Ensure that resource limits that exactly equal capacity are allowed

Fixes #198
Description
Change the definition of ExceededBy to allow exact resource matches (this can happen if a Provisioner has
spec.resources.limits.cpu set to a value identical to a node's CPU count (or a multiple of a node's CPU count))
How was this change tested?
I wasn't able to find an existing test suite that handled node provisioning (I did find a pod provisioning suite but couldn't write a test that would fail before this change and would work after this change). i.e. this change is as yet untested
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

AIUI, this can happen even without:

spec.resources.limits.cpu set to a value identical to a node's CPU count (or a multiple of a node's CPU count))

For example: eligible nodes come in sizes of 12, 20, 32 or 40 CPUs, and the limit is set to 112 CPU. That should be able to be reached exactly even though the limit isn't a multiple of any eligible node's CPU count.

@willthames Do you mind adding a unit test alongside your change to catch this in the future?

Otherwise, LGTM! 🚀

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
12 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.1%) to 78.468%

Files with Coverage Reduction
New Missed Lines
%

pkg/controllers/deprovisioning/controller.go
3
76.54%

pkg/controllers/deprovisioning/events/events.go
9
80.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.1%

Covered Lines:
6228

Relevant Lines:
7937

💛  - Coveralls


Config Refactor Part 2 - Change Opt Param Names & Set File Expiry

Summary of the Pull Request
What is this about?
This is the final step of #2773. In this PR, we change the names of the optional config params. This will cause a breaking change for the CLI.
We have also added an expiry the local config value cache. Now, if a file is older than 24hrs, we delete and reset.
PR Checklist

[ ] Applies to work item: #2773
[ ] CLA signed. If not, go over here and sign the CLI.
[ ] Tests added/passed
[ ] Requires documentation to be updated
[ ] I've discussed this with core contributors already. If not checked, I'm ready to accept this work might be rejected in favor of a different grand plan. Issue number where discussion took place: #xxx

Info on Pull Request
What does this include?
Validation Steps Performed
How does someone test & validate?

Codecov Report

Merging #2835 (47681a7) into main (0c58a59) will increase coverage by 4.10%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #2835      +/-   ##
==========================================
+ Coverage   29.93%   34.03%   +4.10%
==========================================
  Files         324      163     -161
  Lines       38994    19503   -19491
==========================================
- Hits        11671     6638    -5033
+ Misses      27323    12865   -14458

Impacted Files
Coverage Δ

src/agent/onefuzz/src/machine_id.rs
11.53% <0.00%> (-8.98%)
:arrow_down:

src/agent/coverage-legacy/src/test.rs
92.85% <0.00%> (-7.15%)
:arrow_down:

src/agent/onefuzz/src/sanitizer.rs
68.65% <0.00%> (-2.97%)
:arrow_down:

src/agent/onefuzz-agent/src/worker/tests.rs
99.10% <0.00%> (-0.11%)
:arrow_down:

src/agent/onefuzz/src/asan.rs
0.00% <0.00%> (ø)

src/agent/coverage/src/record.rs
0.00% <0.00%> (ø)

src/agent/onefuzz-agent/src/setup.rs
0.00% <0.00%> (ø)

src/agent/onefuzz-agent/src/reboot.rs
0.00% <0.00%> (ø)

src/agent/onefuzz/src/input_tester.rs
0.00% <0.00%> (ø)

src/agent/coverage-legacy/src/cache.rs
0.00% <0.00%> (ø)

... and 175 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Fix issues in README and Swagger

This PR fixes #2, #3, and #4.
@ptitzler @vabarbosa Could you help review this PR when you have time?

Looks like you skipped #3

Thank you, @bdwyer2! Just submit a commit to fix it.


Support for ES6 Promises

In this pull request all user-facing APIs that take callbacks now also return promises. This change is backwards compatible.
Some tests had to be changed, as previously there were expectations that callbacks were called immediately in the same event loop cycle. This is no longer true as callbacks are scheduled with promises, but shouldn't break any user code, which should have been written with an expectation that callbacks are asynchronous in the first place.
Additional tests were added to verify that all promises resolve successfully.
This fork is also published as https://www.npmjs.com/package/noble-promise in the meantime, as I see that main repository had no merging activity for some time. I still hope that this PR will be merged eventually.
@sandeepmistry could you please have a look at this PR? Thanks a lot for the library and I look forward to your feedback.

so what would it take to get this merged?

as a review, I'd like to see the actual 4.x upgrade done in a separate PR rather than hidden in this PR.

happy to apply any changes to merge this as required by current maintainers, which I guess are @sandeepmistry and @jacobrosenthal

ok, I see there are a few conflicts. Happy to fix those if there is any indication that is the only thing blocking this from being merge. Otherwise, would love to know what else might be needed

@maxdesiatov : the Node 4.x changes are here https://github.com/noble/noble/pull/691, so when the time for rebase comes you'll need to remove your node 4.x changes.

no problem, can do that as soon as #691 is merged

@maxdesiatov : When the goahead is given, then it'd also need some examples.

Touches a lot of code sadly (mostly because of whitespace) And sad we also have to touch our tests so much. Are people still doing callback AND promise apis? That would let all the existing tests pass to start with and give much more confidence.

I think the nice part about doing both promises and callbacks is that folks can start using promises immediately and then we could deprecate the callbacks for 3.x

Please forward change to downstream fork:
#923


Consideration of child resources missing in documentation for DeployIfNotExists effect

When describing the DeployIfNotExists properties in our docs, it's stated for the Name property that when the condition values for if.field.type and then.details.type match, then Name becomes required and must be [field('name')]. This is not entirely correct, since for sub resources like subnets this will result in an error during policy evaluation. For sub resources the comparison must be [field('fullName')]

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

ID: d52df521-f6fb-6b7c-11de-7eef01d60ecd
Version Independent ID: 947c0c04-1e48-7e6f-40a3-9517294740c8
Content: Understand how effects work - Azure Policy
Content Source: articles/governance/policy/concepts/effects.md
Service: azure-policy
GitHub Login: @DCtheGeek
Microsoft Alias: dacoulte

#assign:DCtheGeek

@fawohlsc Thanks for the feedback.  I'll validate with the engineer and get back to you.
@MicrosoftDocs/azure-cxp-triage Please label 'doc-enhancement' and #in-progress.

@fawohlsc The team has confirmed this, so I've updated the doc.  When that PR merges, this issue will automatically be closed. Thanks again for the feedback and pointing this out!

@DCtheGeek this was blazing fast - many thanks! 🥇


Using go module instead of dep

 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.:x: koushki sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

@radu-matei can you review please?

@radu-matei  Would you be able to review this?


Lock the version of PyBluez

There have been a number of bugs reported related to Tilt support, where it appeared to break for a subset of users. Best that I can tell, the root cause is recent changes to the PyBluez library (and to the bluez subsystem it sits atop).
To (hopefully) prevent this in the future, it would be good to lock the version so that upgrades only happen when we want them to.
This is a reminder to get this done in the next bug fix release.

Mine indeed is dead. Do I need to downgrade?
\\ Greg

From: John<EMAIL_ADDRESS>Sent: Monday, February 17, 2020 23:24
To: thorrak/fermentrack
Cc: Subscribed
Subject: [thorrak/fermentrack] Lock the version of PyBluez (#428)
There have been a number of bugs reported related to Tilt support, where it appeared to break for a subset of users. Best that I can tell, the root cause is recent changes to the PyBluez library (and to the bluez subsystem it sits atop).
To (hopefully) prevent this in the future, it would be good to lock the version so that upgrades only happen when we want them to.
This is a reminder to get this done in the next bug fix release.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/thorrak/fermentrack/issues/428?email_source=notifications&email_token=AGEO6Z4NL34WJK2WVCF66CTRDNPGZA5CNFSM4KW4ZNH2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4IOGGHMA, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGEO6ZZA3TKHYRZWLIGDQJTRDNPGZANCNFSM4KW4ZNHQ.


[Feature] comment multiple lines

I'm new to vim. Thanks for the useful plugin.
I found this method to comment multiple specific lines.
:1,4s/^/#
But it needs to press shift multiple times.
Is there a way to comment like this?:
:1,4gcc

:1,4gcc

gcc is a keybinding not a ex-command so this won't work. You need to add before norm before gcc. So the final command will look like this :1,4norm gcc


Typescript Refactor

Codecov Report

Merging #32 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff          @@
##           master    #32   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files           1      1
  Lines          78     85    +7
  Branches        0     37   +37
=====================================
+ Hits           78     85    +7

Impacted Files
Coverage Δ

src/index.ts
100% <100%> (ø)

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 cc98224...c2e609c. Read the comment docs.


hangs with very long lines

What steps will reproduce the problem?
1. open a file that have some very long line
2. move up and/orw down through the file with the arrow keys and other methods
(such as jump to the beginning, end or file or to a substring that matches a
search)
3. move up and or down with the arrow keys through some part of the files where
there are very long lines

What is the expected output?

Nothing special should happen. Navigating could be awkward because of the fact
that the whole line doesn't even fit within the terminal, but it should never
become slow in responding to keyword or mouse interaction

What do you see instead?

vim hanged, started consuming 100% cpu and stopped responding.

This is extremely critical as it may imply data loss.

What version of the product are you using? On what operating system?

Ubuntu 14.04

Please provide any additional information below.

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 22 Oct 2014 at 8:18

I just build 7.4.889 and vim works MUCH faster/better with very long lines
(E.g. 90,000 characters)
YEA!

Okay, closing then.


Injection of ObjectMapper in ChannelBindingServiceConfiguration causes eager initialization

One of the observable effects is that the resulting ObjectMapper is not properly configured for HATEOAS.

How to reproduce: https://github.com/spring-cloud/spring-cloud-stream/pull/496#issuecomment-213470417


JAVA-2149: add ability to configure NettyStream channel type in async driver

Thanks @jamel we used this PR as the basis for the improvement 👍

Cool! Thanks a lot!


Unable to resolve module ./styles/style.sass

Help us reproduce - tell us about your environment

Windows 10, Android *

Steps to reproduce

react-native run-android

Expected result

The native version working well.

Actual result

[Screenshot, logs]
I have structured the an  existing web application like your git project, and is working. I have run react-native upgrade to generate ios and andoid folder, and create the native folder in src, if i run react-native run-android i get  Unable to resolve module ./styles/style.sass. The require('./styles/style.sass') is in folder web/index.js. Any sugeston for this, i have mising someting in the configuration?

From what I understand:

You're working on a separate project and you've tried to reproduce some of the concepts from this repo (i.e. you're not using the code as is from this repo)
You're trying to run on Android
When running react-native run-android in your project, you get an error about a sass file

Without knowing anything about your project, it sounds like you're requiring a sass file from your one of your native files.
Please let me know if I've understood correctly - as that isn't an issue with this project. Feel free to contact me separately and I'll offer my consulting rates.


Debugging does not work in Node 6.5 with inspector protocol

While verifying #25556:
Follow the steps to reproduce as in #25556, then hit F5 and observe that debugger terminates and 'hello' is not printed in debug console.
Neither putting breakpoint works.

Works for me. No errors in the console? Can you run with "trace": true and post the log?

Can you maybe try with 6.8 or 6.10 as well, because if that fails, then it's a real issue.

And is this on Windows? If so, that's probably an old known issue with Node crashing in debug mode.

OS: Windows 10
Node 6.8 worked fine.
Here is an output from debug console:
Verbose logs are written to:
C:\Users\t-mikapo\AppData\Local\Temp\vscode-node-debug2.txt
node --inspect=27672 --debug-brk test.js
Debugger listening on port 27672.
Warning: This is an experimental feature and could change at any time.

vscode-node-debug2.txt log:
OS: win32 ia32
Adapter node: v7.4.0 ia32
vscode-chrome-debug-core: 3.15.4
12:11:43, 6.6.2017
node-debug2: 1.13.1
From client: initialize({"clientID":"vscode","adapterID":"node2","pathFormat":"path","linesStartAt1":true,"columnsStartAt1":true,"supportsVariableType":true,"supportsVariablePaging":true,"supportsRunInTerminalRequest":true})
To client: {"seq":0,"type":"response","request_seq":1,"command":"initialize","success":true,"body":{"exceptionBreakpointFilters":[{"label":"All Exceptions","filter":"all","default":false},{"label":"Uncaught Exceptions","filter":"uncaught","default":true}],"supportsConfigurationDoneRequest":true,"supportsSetVariable":true,"supportsConditionalBreakpoints":true,"supportsCompletionsRequest":true,"supportsHitConditionalBreakpoints":true,"supportsRestartFrame":true,"supportsExceptionInfoRequest":true}}
From client: launch({"type":"node2","request":"launch","name":"Launch Program","program":"c:\\Users\\t-mikapo\\Documents\\Projects\\multiline-object-properties/test.js","protocol":"inspector","trace":true,"cwd":"c:\\Users\\t-mikapo\\Documents\\Projects\\multiline-object-properties"})
To client: {"seq":0,"type":"event","event":"output","body":{"category":"telemetry","output":"debugStarted","data":{"request":"launch","args":["type","request","name","program","protocol","trace","cwd","sourceMapPathOverrides","showAsyncStacks","sourceMaps"]}}}
Launch: program 'c:\Users\t-mikapo\Documents\Projects\multiline-object-properties\test.js' seems to be the generated file
node --inspect=42982 --debug-brk test.js
Discovering targets via http://<IP_ADDRESS>:42982/json
To client: {"seq":0,"type":"event","event":"output","body":{"category":"stderr","output":"Debugger listening on port 42982.\r\nWarning: This is an experimental feature and could change at any time.\r\n"}}
HTTP GET failed: Error: read ECONNRESET
Target exited
Killing process with id: 13688
Terminated: Target exited
To client: {"seq":0,"type":"event","event":"output","body":{"category":"telemetry","output":"debugStopped","data":{"reason":"Target exited"}}}
To client: {"seq":0,"type":"event","event":"terminated"}
Target closed
Terminated: Target closed
From client: disconnect({"restart":false})
Terminated: Got disconnect request
To client: {"seq":0,"type":"response","request_seq":3,"command":"disconnect","success":true}
Discovering targets via http://<IP_ADDRESS>:42982/json

Ok, if it's Windows then 6.5 just isn't really supported.


pull request for e2e test at 01/15/2017 06:56:14

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Update Installation Instructions for VS Code .NET MAUI Extension

Updated the instructions for installing the .NET MAUI Extension for VS Code including all dependencies, workloads, and target platforms.
Added clarification for setting up android as a target platform on all operating systems.

@BethMassi @maddymontaquila - Could you please review and give feedback on this PR? Thank you!

@jonpryor - Could you please review as well? Thank you!