[iOS] enable versionning in xcode project

Motivation
Current Xcode project does not include settings to enable auto-incrementing build numbers using agvtool as described here. Tools like Fastlane, for example, rely on this for commands like increment_build_number. Having these settings enabled by default ensures that people will have one less thing to worry about setting up CI for RN based projects.

By analyzing the blame information on this pull request, we identified @jhen0409 and @tonyxiao to be potential reviewers.

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla - and if you have received this in error or have any questions, please drop us a line at<EMAIL_ADDRESS>Thanks!

@callmephilip updated the pull request - view changes

@callmephilip updated the pull request - view changes

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks!

@facebook-github-bot shipit

Thanks for importing. If you are an FB employee go to Phabricator to review internal test results.

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 thumbmunkeys.com has exceeded the max emails per hour (60/60 (100%)) allowed.  Message will be reattempted later
------- This is a copy of the message, including all the headers. ------
Received: from filter01.reliabledns.org ([<IP_ADDRESS>]:53695)
by en02-ams.stablehost.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256)
(Exim 4.87)
(envelope-from<EMAIL_ADDRESS>id 1biJRa-003JeC-RM
for<EMAIL_ADDRESS>Fri, 09 Sep 2016 10:54:04 +0000
Received: from github-smtp2-ext3.iad.github.net ([<IP_ADDRESS>] helo=github-smtp2b-ext-cp1-prd.iad.github.net)
by filter01.reliabledns.org with esmtps (TLSv1.2:DHE-RSA-AES256-SHA:256)
(Exim 4.85)
(envelope-from<EMAIL_ADDRESS>id 1biJRX-00058n-I0
for<EMAIL_ADDRESS>Fri, 09 Sep 2016 03:54:02 -0700
Date: Fri, 09 Sep 2016 03:53:58 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com;
s=pf2014; t=1473418438;
bh=PQnUMYiwEsGgR0TBB9DOwS7bN4wuirMsco4csrdS37s=;
h=From:Reply-To:To:In-Reply-To:References:Subject:List-ID:
List-Archive:List-Post:List-Unsubscribe:From;
b=jGKe42vWwW2DB5R41hq9bl36cLgzinZq9oHMyBo0sS60h9GGYIhS/le716WhY9wCA
35eDMcvaNljIY4cBCIVugh7LhPO4imjWqltZMZUDK6mQ9yLmY/cNUB31ftihytJmaR
Vp6x9+4vnii229xLWOEn55JkxX6hbdQUg+WBwioQ=
From: Facebook Community Bot<EMAIL_ADDRESS>Reply-To: facebook/react-native<EMAIL_ADDRESS>To: facebook/react-native<EMAIL_ADDRESS>Message-ID<EMAIL_ADDRESS>In-Reply-To<EMAIL_ADDRESS>References<EMAIL_ADDRESS>Subject: Re: [facebook/react-native] [iOS] enable versionning in xcode project
(#9511)
Mime-Version: 1.0
Content-Type: multipart/alternative;
boundary="--==_mimepart_57d294c65cf60_2ddc3fc09ed112a0329689";
charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: facebook-github-bot-4
X-GitHub-Recipient: bunnyboy1
List-ID: facebook/react-native <react-native.facebook.github.com>
List-Archive: https://github.com/facebook/react-native
List-Post<EMAIL_ADDRESS>List-Unsubscribe<EMAIL_ADDRESS>https://github.com/notifications/unsubscribe/ARoNg6biC03cmo_YWbeAW2YDXzyoKAlRks5qoTrGgaJpZM4JpaeB
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address<EMAIL_ADDRESS>Received-SPF: pass (filter01.reliabledns.org: domain of github.com designates <IP_ADDRESS> as permitted sender) client-ip=<IP_ADDRESS><EMAIL_ADDRESS>helo=github-smtp2b-ext-cp1-prd.iad.github.net;
X-SPF-Result: filter01.reliabledns.org: domain of github.com designates <IP_ADDRESS> as permitted sender
Authentication-Results: filter01.reliabledns.org; dmarc=pass header.from=github.com
X-Filter-ID: s0sct1PQhAABKnZB5plbIamwIYzgudGL4tMY9zS3pea7KY6rzXjgC+rgKYUjsj8D0JuF70A4EJMc
Wn6O/bsgoWSYW6KbZfj8apx6ohl75uX35Caz8bqM3i8tzwcg+lnkZzoX7PhhDs80mBQKIGWwu/ZE
jF4Pov/vsc2Cwocc9pJwJVSL6KLw+g28lkb31HyS94pE1Cssu3RLQ0/o4r6NbA8zp1yYIFRkRN8y
Bn+CxV3c2rxRLzIn+w+J3NDyjtIKbiDqpvcqvGr62J6i5S97spz3A1ed2ITkOuMtrwds5D4lTQ4T
s4pbWtZ3YR/lXG1VJq/4FZbX1lzD9O+fyiIjB8wTNR/tjjZvmBdM/4lPZO2sASVdHfbtk3LlI8pB
wr4jGeKz8vlEl/GSEiCnxc6Ard0BaVp3jhK5GOBJIv+LCtDC+P7wO5Dn5esh4VR+ptzHN0JkcMmQ
sV7j9toT40ga/GYzx2Zgyhf3OXiddZgacWc1/+H6OHgtV1bmxcq0CB3pmrFpDzdgJQc/rZDiOC7K
RpZxGk3X7U/CrpemaTYEqjR6fyHrrsngmi97syQy+4L3p7+eg7tptOUU98CNo4IBbK0jiD6XqsJZ
tjQxlyCdsezJow6Hi0pxrFS5O4yOAY8o6W0BvTIC60F9LNR/0kDSJQ==
X-Report-Abuse-To<EMAIL_ADDRESS>Authentication-Results: reliabledns.org; spf=pass<EMAIL_ADDRESS>Authentication-Results: reliabledns.org; dkim=pass header.i=github.com
X-SpamExperts-Class: ham
X-SpamExperts-Evidence: Combined (0.27)
X-Recommended-Action: accept
X-Spam-Status: No, score=3.5
X-Spam-Score: 35
X-Spam-Bar: +++
X-Ham-Report: Spam detection software, running on the system "en02-ams.stablehost.com",
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:  Thanks for importing. If you are an FB employee go to Phabricator
to review internal test results. -- You are receiving this because you are
subscribed to this thread. Reply to this email directly or view it on GitHub:
https://github.com/facebook/react-native/pull/9511#issuecomment-245881928
[...]
Content analysis details:   (3.5 points, 5.0 required)
pts rule name              description

2.4 RCVD_IN_SORBS_SPAM     RBL: SORBS: sender is a spam source
[<IP_ADDRESS> listed in dnsbl.sorbs.net]
-0.0 RCVD_IN_DNSWL_NONE     RBL: Sender listed at http://www.dnswl.org/, no
trust
[<IP_ADDRESS> listed in list.dnswl.org]
1.5 SPF_SOFTFAIL           SPF: sender does not match SPF record (softfail)
-1.9 BAYES_00               BODY: Bayes spam probability is 0 to 1%
[score: 0.0000]
1.6 HTML_IMAGE_ONLY_24     BODY: HTML: images with 2000-2400 bytes of words
0.0 HTML_MESSAGE           BODY: HTML included in message
-0.1 DKIM_VALID             Message has at least one valid DKIM or DK signature
-0.1 DKIM_VALID_AU          Message has a valid DKIM or DK signature from author's
domain
0.1 DKIM_SIGNED            Message has a DKIM or DK signature, not necessarily valid
X-Spam-Flag: NO
----==_mimepart_57d294c65cf60_2ddc3fc09ed112a0329689
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: 7bit
Thanks for importing. If you are an FB employee go to Phabricator to review internal test results.
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/facebook/react-native/pull/9511#issuecomment-245881928
----==_mimepart_57d294c65cf60_2ddc3fc09ed112a0329689
Content-Type: text/html;
charset=UTF-8
Content-Transfer-Encoding: 7bit
Thanks for importing. If you are an FB employee go to Phabricator to review internal test results.
—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_57d294c65cf60_2ddc3fc09ed112a0329689--

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 thumbmunkeys.com has exceeded the max emails per hour (61/60 (101%)) allowed.  Message will be reattempted later
------- This is a copy of the message, including all the headers. ------
Received: from filter03.reliabledns.org ([<IP_ADDRESS>]:42546)
by en02-ams.stablehost.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256)
(Exim 4.87)
(envelope-from<EMAIL_ADDRESS>id 1biJRy-003JnI-Qr
for<EMAIL_ADDRESS>Fri, 09 Sep 2016 10:54:28 +0000
Received: from o8.sgmail.github.com ([<IP_ADDRESS>])
by filter03.reliabledns.org with esmtps (TLSv1.2:DHE-RSA-AES128-SHA:128)
(Exim 4.85)
(envelope-from<EMAIL_ADDRESS>id 1biJRx-00008j-0I
for<EMAIL_ADDRESS>Fri, 09 Sep 2016 03:54:26 -0700
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=github.com;
h=from:reply-to:to:in-reply-to:references:subject:mime-version:content-type:content-transfer-encoding:list-id:list-archive:list-post:list-unsubscribe;
s=s20150108; bh=ONS5S9wQUGGi6ojg98pwVe2mYM4=; b=ho5LiqTiaX+AtnK3
3t7iTH9feoGaagix4gfJ5qr7s/o+dftnA8GquNZtLO9hvacR4SGClvclqex48lAZ
KaGiNHtvVpeqmfSQl74ivpsigeD9VJVGZk15LnYWzucmPpgRCUJTV3CBOp+jU1hU
Qz9bVf/pbB9JA5mT67J/PMwICXs=
Received: by filter0460p1mdw1.sendgrid.net with SMTP id filter0460p1mdw1.17019.57D294A92D
2016-09-09 10:53:29.261629817 +0000 UTC
Received: from github-smtp2b-ext-cp1-prd.iad.github.net (github-smtp2b-ext-cp1-prd.iad.github.net [<IP_ADDRESS>])
by ismtpd0001p1iad1.sendgrid.net (SG) with ESMTP id VjpSui0jQ8m58nPcPJS-Rg
for<EMAIL_ADDRESS>Fri, 09 Sep 2016 10:53:29.180 +0000 (UTC)
Date: Fri, 09 Sep 2016 03:53:29 -0700
From: Pieter De Baets<EMAIL_ADDRESS>Reply-To: facebook/react-native<EMAIL_ADDRESS>To: facebook/react-native<EMAIL_ADDRESS>Message-ID<EMAIL_ADDRESS>In-Reply-To<EMAIL_ADDRESS>References<EMAIL_ADDRESS>Subject: Re: [facebook/react-native] [iOS] enable versionning in xcode project
(#9511)
Mime-Version: 1.0
Content-Type: multipart/alternative;
boundary="--==_mimepart_57d294a92471_526a3ff7d18092c03307eb";
charset=UTF-8
Content-Transfer-Encoding: 7bit
Precedence: list
X-GitHub-Sender: javache
X-GitHub-Recipient: bunnyboy1
List-ID: facebook/react-native <react-native.facebook.github.com>
List-Archive: https://github.com/facebook/react-native
List-Post<EMAIL_ADDRESS>List-Unsubscribe<EMAIL_ADDRESS>https://github.com/notifications/unsubscribe/ARoNg1871D5wPohvu6KwbEn2LYJikeLoks5qoTqpgaJpZM4JpaeB
X-Auto-Response-Suppress: All
X-GitHub-Recipient-Address<EMAIL_ADDRESS>X-SG-EID: wxILpmbMy+DMOe8s3uTnYJqhMhAtpIHhpRnO60rP0k8PT99jJZJxEuCt1OM2Zkay/m/alYk5CTUgud
WEQycE+E0zlBlBsohyMlpR5H8t4MZRQzriNTIfRAZ8RlSi3jDbEKB50O4Vm9Kpq6aVVLzTL07eg1EB
rgeYnxYGrUt5RQhHULQpXe8vXVQlNUZcnjEdtAXfucpZs+qAC1fK0cLxaUht+qtsT3mj1fa275Se2/
M=
Received-SPF: pass (filter03.reliabledns.org: domain of sgmail.github.com designates <IP_ADDRESS> as permitted sender) client-ip=<IP_ADDRESS><EMAIL_ADDRESS>helo=o8.sgmail.github.com;
X-SPF-Result: filter03.reliabledns.org: domain of sgmail.github.com designates <IP_ADDRESS> as permitted sender
X-Sender-Warning: sgmail.github.com has no MX records
Authentication-Results: filter03.reliabledns.org; dmarc=pass header.from=github.com
X-Filter-ID: s0sct1PQhAABKnZB5plbIT1RbOwy06L9REYyr9AwRQTwqQ7CW4gxUeeyoz1oed5P/SEnTgrA37IX
TZjA4tFfC9o7/kuvJ3wuZWRdcwKwe1+/dW/xGlBq3/UmIKUCpDxGneIVwSf+lCa+FY3nagRj3wdr
IZ+D/FAg6XyPDmfkLA7rcxAODBZO2BOkcGk4nUtaWBCJFgBso8Q3X4tROJ1gHlarIGSMLt5vX9V9
rVXE/wBcR6vcRlDk/cSBa4A2VcTnkxlSZxHxTWgJwgGAdAfYx0QbUSmybXI9Q2wJvH91K4x1/xY7
b1I8OIpxoI7mFpwMSmEIS4GON+6FOG36iMWh1HrC+mnu8HU6+1MultOxIl093SsS4aMXJmiJ2G0e
b5ahm8p6HlShAEYnwZBavOYADGb0g2n0QCK0NUarjxzvKHXDqcigOvSxdRnthmhn8Zn6nJvJDVm7
fp8WWz+diuw4AEUWb7Au9+OsDspaYXORD9DExXy0aVT1HuhJQmP8nOV/gcSXPi64HW9TLHbE1xGc
sIqosGRVic0wJZbsnU20WkB8LSJSyBhtnWbngGtasJkXBf0jdZtXXwRMZ/pKak7GRV+Sy3brvYFg
uJ068d7ZjkeRv8Gjvtc3eeZ2pvOmIPvav2ToL5w5nDAUe12FhqWGsTEvuGslKTrRIXcXpFg5ivY=
X-Report-Abuse-To<EMAIL_ADDRESS>Authentication-Results: reliabledns.org; spf=pass<EMAIL_ADDRESS>Authentication-Results: reliabledns.org; dkim=pass header.i=github.com
X-SpamExperts-Class: ham
X-SpamExperts-Evidence: Combined (0.07)
X-Recommended-Action: accept
X-Spam-Status: No, score=1.0
X-Spam-Score: 10
X-Spam-Bar: +
X-Ham-Report: Spam detection software, running on the system "en02-ams.stablehost.com",
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:  @facebook-github-bot shipit -- You are receiving this because
you are subscribed to this thread. Reply to this email directly or view it
on GitHub: https://github.com/facebook/react-native/pull/9511#issuecomment-245881844
[...]
Content analysis details:   (1.0 points, 5.0 required)
pts rule name              description

-0.0 RCVD_IN_DNSWL_NONE     RBL: Sender listed at http://www.dnswl.org/, no
trust
[<IP_ADDRESS> listed in list.dnswl.org]
1.5 SPF_SOFTFAIL           SPF: sender does not match SPF record (softfail)
-1.9 BAYES_00               BODY: Bayes spam probability is 0 to 1%
[score: 0.0000]
0.0 HTML_MESSAGE           BODY: HTML included in message
1.5 HTML_IMAGE_ONLY_20     BODY: HTML: images with 1600-2000 bytes of words
-0.1 DKIM_VALID             Message has at least one valid DKIM or DK signature
-0.1 DKIM_VALID_AU          Message has a valid DKIM or DK signature from author's
domain
0.1 DKIM_SIGNED            Message has a DKIM or DK signature, not necessarily valid
X-Spam-Flag: NO
----==_mimepart_57d294a92471_526a3ff7d18092c03307eb
Content-Type: text/plain;
charset=UTF-8
Content-Transfer-Encoding: 7bit
@facebook-github-bot shipit
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/facebook/react-native/pull/9511#issuecomment-245881844
----==_mimepart_57d294a92471_526a3ff7d18092c03307eb
Content-Type: text/html;
charset=UTF-8
Content-Transfer-Encoding: 7bit
@facebook-github-bot shipit
—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_57d294a92471_526a3ff7d18092c03307eb--


No enabled audio or video stream

Have you read the FAQ and checked for duplicate open issues?
Yes
What version of Shaka Player are you using?
3.0.5
Can you reproduce the issue with our latest release version?
Yes
Can you reproduce the issue with the latest code from master?
Not possible to check
Are you using the demo app or your own custom app?
Custom app
If custom app, can you reproduce the issue using our demo app?
No, everything works correctly on https://shaka-player-demo.appspot.com/demo/#build=uncompiled
What browser and OS are you using?
Chrome and Windows
For embedded devices (smart TVs, etc.), what model and firmware version are you using?
Chromecast NC2-6A5
What are the manifest and license server URIs?
Sent to<EMAIL_ADDRESS>What did you do?
Tried to play live stream
What did you expect to happen?
Stream plays without issues
What actually happened?
The stream does not load.
I can see that there's request for the Manifest being made, but there's no request for license or chunks.
The only thing that distinguishes this situation from the case when stream plays normally is information in the console:
[cast.player.core.MediaSourceManager] no enabled audio or video stream

Thank you for your answer! I will provide more detailed info in another email.

To elaborate further on the issue:
After accessing the URL.
You'll see the json representing the data for the stream. You can ignore the DRM property as we set up this stream to NOT protected. You can check it in Shaka Player Demo ( I sent direct url via email).
We're using CAF but I downloaded cast_receiver_framework.js and changed it to use ShakaPlayer 3.0.5, but also tested this issue with the cast_receiver_framework.js which can be found here:
www.gstatic.com/cast/sdk/libs/caf_receiver/v3/cast_receiver_framework.js"
Issue is occurring for both versions (2.5 and 3.0.5).
The issue occurs only for Chromecast receiver app. I can play the stream without any problem with the Shaka Player Demo test site.
If you're not located in the EU, we have to ask you for your IP so that we can whitelist your access to the stream.
If you need any additional info, please contact me.

Some more background on the streams.
The streams are coming from VSPP streaming platform and are token protected. For that reason the request Url was provided to get a new manifest url with a valid token. In production situations we target DASH+Widevine; but for testing a clear DASH stream can be used.

As the error message "[cast.player.core.MediaSourceManager] no enabled audio or video stream" does not come from Shaka Player, I believe you should ask for support from the Cast Application Framework.  https://developers.google.com/cast/support
Sorry!


Update license year

What it solves
Outdated license year
How this PR fixes it
The MIT license year has been updated to 2022.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 32.49%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
3160

Relevant Lines:
8679

💛  - Coveralls


Spring-vault hmac verify support is missing

Vault supports hmac verification as below but spring-vault doesn't provide a way to do it.
Request
curl --location --request POST 'https://<IP_ADDRESS>:8200/v1/transit/verify/default-mac/sha2-256' \
--header 'X-Vault-Token: s.NvdLGh4ohtgcXEShSCYfB73n' \
--header 'X-Vault-Request: true' \
--header 'Content-Type: application/json' \
--data-raw '{
    "input": "QW1vbCBHYWlrd2FkIHFhOCBDcnlwdG8tYXBpIDIuMTIgZGF0YWJhc2UgOQ==",
    "hmac" : "vault:v1:VZMQieAS6eodoGvW9KybcMe1Er5EzyHwvp0XivUOYr8="
}'

Response
{
    "request_id": "e0049996-0be7-6991-081f-045639742384",
    "lease_id": "",
    "renewable": false,
    "lease_duration": 0,
    "data": {
        "valid": true
    },
    "wrap_info": null,
    "warnings": null,
    "auth": null
}

Support is there in VaultTransitTemplate but it suffers from same issue as algorithm is passed in body instead of url path of transit api.


Rate limit middleware

Goals:

[ ] Ensure endpoints groups (the middleware can be global or works in a route)

[x] In route
[ ] Global (we don't need it right now)

[x] get rate limit
[x] LUA script
[x] response header or error
[ ] Check if possible using EVALSHA command to remember LUA script
[x] Configuration parameters to enable/disable all or one endpoint group rate limits
[x] Travis (Dockerfile and tests)

To consider:

We must use a new Redis db for this purpose

Initially, we have had doubts about remaining value https://github.com/brandur/redis-cell/issues/12 of the redis-cell, but, after some research, @Tonino have created a PR https://github.com/brandur/redis-cell/pull/13 solving the problem.


feat(ios): set AllowBackNavigationGestures dynamically from JavaScript

Currently there is no way to set AllowBackNavigationGestures in Javascript except set this preference in config.xml
For those need to set this preference dynamically in cordova project, this might be useful

Please merge this ASAP! This is a needed feature!

@jcesarmobile Could you take a look with this PR? Just a simple feature request.It just help a lot for having more native app feeling.Thanks a lot.

its been ages, why isn't its merged, or any other plans to make Webview for configurable with more options
@samuelbeaulieu @Cow258 @jcesarmobile


Fix typo on readme

The npm install command is corrupted.
There is a & but it should be a @.
Thanks
MrNossiom

Hey @mrmckeb is there a chance to merge this soon as it's one of many duplicate PRs that we've already received for this issue:

#10317 (open)
#10081
#10093
#9925

Hope you are all staying safe & healthy! Cheers

Adding one more duplicate PR to this list: https://github.com/facebook/create-react-app/pull/10671 🤓

Maybe we could close some duplicate issues...

Duplicate of #10317


bug: ion-footer overlap another. Same for ion-tab-bar

Bug Report
Ionic version:

[x] 4.3.0
Steps to reproduce:
Open next page in route. Back to the previous page in route. If you have ion-footer on previous and current pages you will have this bug. If the previous page with ion-footer and current page without - all correct, animation working fine.
I created a simple app with 4 pages (but this bug between two pages). Same layout and logic on each of these pages.
Simple page. Header (First page without ion-back-button). Content. Footer
Related code:

HTML
<ion-header>
  <ion-toolbar>
    <ion-buttons slot="start">
      <ion-back-button></ion-back-button>
    </ion-buttons>
    <ion-title>
      HEADER 2
    </ion-title>
  </ion-toolbar>
</ion-header>

<ion-content>
  CONTENT 2
</ion-content>

<ion-footer>
  <ion-button
    (click)="openTest3()">
    <ion-label>OPEN 3</ion-label>
  </ion-button>
</ion-footer>

TS
import { Component } from '@angular/core';
import { Router } from '@angular/router';

@Component({
  templateUrl: './test.component.html',
  styleUrls: ['./test.component.scss'],
})
export class Test2Component {

  constructor(private router: Router) {
  }

  openTest3() {
    this.router.navigateByUrl(`index/test3`);
  }

}

ROUTES
export const testRoutes: Routes = [
  {
    path: 'test',
    component: TestComponent,
  },
  {
    path: 'test2',
    component: Test2Component,
  },
  {
    path: 'test3',
    component: Test3Component,
  },
  {
    path: 'test4',
    component: Test4Component,
  }
];

https://gyazo.com/5241574a02561afb0709b8d2cc173621
Same issue with ion-tab-bar.

With ion-toolbar
<ion-footer>
  <ion-toolbar>
    FOOTER
  </ion-toolbar>
</ion-footer>

https://gyazo.com/62eea20eec353c2e231225ca64ef2e4a

Thanks for the issue. Is this still an issue with the latest version of Ionic Framework? If so, please provide a repo with the code required to reproduce this issue.


ft: propogate redis password from config

This commit takes the optional Redis password defined in the config and
propagates the config to localCache and Utapi.

PR has been updated. Reviewers, please be cautious.

@ironman-machine
SCALITY_UTAPI_BRANCH=ft/S3C-697-redis-passsword
try

Hello @rahulreddy
"SCALITY_UTAPI_BRANCH=ft/S3C-697-redis-passsword": Success
"try": Success: Try build successfully launched on 'http://ci.ironmann.io/gh/scality/Integration/14214' with the following env. args:
{
    "SCALITY_UTAPI_BRANCH": "ft/S3C-697-redis-passsword",
    "SCALITY_INTEGRATION_BRANCH": "ultron/rel/6.4",
    "REPO_NAME": "S3",
    "DEFAULT_BRANCH": "rel/6.4",
    "SCALITY_S3_BRANCH": "ft/S3C-698-redis-passsword"
}

:sunny: :+1: circleCI test succeeded!


Target path from the command line

Is it possible with redub to specify a target path on the command line?
Use case: redub build --target-path="/usr/bin/app-name"
So one can have a deterministic target-path – even if the project recipe changes.
Classic DUB feature request: https://github.com/dlang/dub/issues/902

Isn't that feature request actually dub build --root=

Implemented --targetPath and --targetName flags, while keeping it optimized for using cache on same build types :)

You absolutely rock :metal:


feat(components): create new LabwareStackRender component

Overview
According to new modal designs for labware/adapter/module stacks on desktop and ODD, we need to render an isometric view of each element of the stack, maintaining the topography of each stacked element. The isometric views are constructed by transforming and aligning the labware SVG (top face) along with two new rects (front and left side). All three are scaled, skewed, and rotated at 30˚ angles or its derivatives (reference).
The "bottom" labware definition is an optional prop, so we have an affordance for rendering an isometric view of a single labware from the same component. The user can choose to highlight both or none of the labware in the stack, resulting in a fill of blue30.
In addition, adapters are handled in the following way:

If the adapter is used as the top definition and there is no bottom definition, we render the non-transformed LabwareAdapter svg
if the adapter is used as the bottom definition, we render the isometric transform of the well-less adapter face. NOTE In this PR, the adapter's height is maintained, but we may also consider setting the height for a bottom adapter as a constant, rendering a standard-height rectangular prism with well-less face.

Closes PLAT-374, PLAT-377, PLAT-394, PLAT-375
Test Plan and Hands on Testing
Difficult to test immediately without new clickable stack on deck map.
Changelog

create new isometric view LabwareStackRender component with precedent set from LabwareRender component
modify props for LabwareOutline, Well, and StaticLabware to accommodate optional fill color (for optional blue highlight in LabwareStackRender)

Review requests
Please check code logic and smoke test instances of LabwareRender on App and PD. I can make changes to the render once the stack modal is ready.
Risk assessment
Low-Medium. LabwareStackRender is not yet implemented anywhere, but peripheral components touched by this PR are used extensively across our applications, but the changes are minimal

Could we add something in storybook for this?


deps: update dependencies

This addresses known issues in cloudflare/circl and go-git.

Will fix vet issue separately.


Guide Improvement: Game.GetPlayer() returns Error: Function 'GetPlayer' not found or is not a global - because game needs to be run as admin.

I was about to post an issue about not being able to run Game.GetPlayer(), but I set the game to run as admin because of a hunch, which now allows me to run that command. So this issue is now instead just a suggestion to add that information in the script tutorial/releases 😃

Is this with 1.4.2?

Yes, and 1.0.5

Admin isn't required and shouldn't be. You have something strange with your setup.

I saw in the release notes that a fix relating to autoexec.lua not running when starting the game from the launcher, seems likely that my problem what related to that rather than running as admin.


Can I turn on the camera without using the GPU?

I want to use the terminal to store the depth map remotely, but sdk seems to have to use the desktop environment to open the depth camera. Is there any solution?

You could maybe try to setup an x-server-dummy like this:
https://techoverflow.net/2019/02/23/how-to-run-x-server-using-xserver-xorg-video-dummy-driver-on-ubuntu/

@ruis1996 thank you for the feedback, may I ask, the machine that you want to remote in (the one connect to the device), are talking about linux or windows?

if it is linux, you can try what @RoseFlunder  suggested, and please take a look this issue #562
if it is windows, you should be able to do that without problem

@rabbitdaxi  @RoseFlunder
Thank you for your reply.
My sys is Ubuntu18.04.3-mate.
I will try the methods you provided, I will return feedback later, thank you.

@rabbitdaxi  @RoseFlunder
I tried @rabbitdaxi ‘s method, but it can't work in my system. Is there any other way to solve it?

@ruis1996 , can you also try "export DISPLAY=:1" not sure whether it is helping, but it seems helps me if I do using a putty remote to a linux machine through SSH

@rabbitdaxi
Your method works me when I have a monitor connected to the remote PC to which I connect via SSH.
When I disconnect the monitor and restart the remote pc and connect via SSH again, exporting a DISPLAY environment variable is not sufficent because the X-Server isn't running and no graphics driver is loaded as far as I can see it.
I am searching for a solution to use the sdk (sensor & body tracking) on a headless (no monitor connected) ubuntu machine.
For the moment connecting via SSH and starting the application would be sufficent.
In the future the app should run as a systemd service that will be started automatically as a service when the machine starts.

Can someone from Microsoft please give an update on this issue?
There are various bits of information scattered over a few issues, but there is no official or simple confirmed working solution for using a kinect from a headless linux environment, and myself and others have tried workarounds suggested but with no success. This use case is very common for research purposes.


Closing the Application Doesn't Remove it from Alt+Tab List

Even after clicking the "X" with the application minimizing to the system tray, it still shows up in the Alt+Tab list.
I would expect the application to not show up in the Alt+Tab list when the window isn't visible.

I believe you're right. I don't think the app should show on 'Alt+Tab' I'll look into that!

Hi, this has now been resolved in the lastest version: https://github.com/jamesbrindle/YTMusicUploader/releases.
Thank you reporting this BTW - Much appreciated.


merge package template from arlac77/npm-package-template

Updated standard to latest version

Codecov Report

Merging #131 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #131   +/-   ##
=======================================
  Coverage   91.41%   91.41%
=======================================
  Files          18       18
  Lines         163      163
=======================================
  Hits          149      149
  Misses         14       14

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 804417e...ab384e4. Read the comment docs.

Coverage remained the same at 91.411% when pulling ab384e4ea43c127690c52f95a829876af4c88c3c on template-sync-1 into 804417eb7087e2e466298efa2fe2127418489a8c on master.


Styling does not work

I have tried to update colorlist in global config, but it does not work.
Check stackblitz: https://stackblitz.com/edit/minimal-confirm-box-s13g4b

Same here, doesn't matter what colours I set in app.module, they do not change.
I had to add CSS to my global styles, eg:
.ed-btn-customone {
  background-color: #2d922d; // slightly darker main color green, to override costlypopup CUSTOMONE
}

Sorry for waiting so long, fixed it in 3.1.4 release https://github.com/costlydeveloper/ngx-awesome-popup/releases/tag/3.1.4
https://stackblitz.com/edit/minimal-confirm-box-o6ubr5?file=package.json


Bugfixes and small enhancements

Bugfixes for issues #7 #9 #10
Various other fixes and small enhancements

For some reason, this branch is giving me this error when I try and use the extension:
[2021-11-04 06:18:36.758] [ERROR] [Adapter]: Failed to load tests - Test discovery failed: Browser Error - An error was thrown in afterAll
Uncaught Error: Module build failed (from ./node_modules/sass-loader/dist/cjs.js):
Error: Node Sass does not yet support your current environment: Windows 64-bit with Unsupported runtime (89)
For more information on which environments are supported please see:
https://github.com/sass/node-sass/releases/tag/v4.14.1
    at module.exports (J:\work\some-project\mobile-app\source\app\node_modules\node-sass\lib\binding.js:13:13)
    at Object.<anonymous> (J:\work\some-project\mobile-app\source\app\node_modules\node-sass\lib\index.js:14:35)
    at Module._compile (internal/modules/cjs/loader.js:1125:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1155:10)
    at Module.load (internal/modules/cjs/loader.js:982:32)
    at Module._load (internal/modules/cjs/loader.js:823:14)
    at Function.f._load (electron/js2c/asar_bundle.js:5:12913)
    at Module.require (internal/modules/cjs/loader.js:1006:19)
    at require (internal/modules/cjs/helpers.js:88:18)
    at getDefaultSassImplementation (J:\work\some-project\mobile-app\source\app\node_modules\sass-loader\dist\utils.js:42:10)
    at getSassImplementation (J:\work\some-project\mobile-app\source\app\node_modules\sass-loader\dist\utils.js:50:30)
    at Object.loader (J:\work\some-project\mobile-app\source\app\node_modules\sass-loader\dist\index.js:34:59)
Error: Module build failed (from ./node_modules/sass-loader/dist/cjs.js):
Error: Node Sass does not yet support your current environment: Windows 64-bit with Unsupported runtime (89)
For more information on which environments are supported please see:
https://github.com/sass/node-sass/releases/tag/v4.14.1
    at module.exports (J:\work\some-project\mobile-app\source\app\node_modules\node-sass\lib\binding.js:13:13)
    at Object.<anonymous> (J:\work\some-project\mobile-app\source\app\node_modules\node-sass\lib\index.js:14:35)
    at Module._compile (internal/modules/cjs/loader.js:1125:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1155:10)
    at Module.load (internal/modules/cjs/loader.js:982:32)
    at Module._load (internal/modules/cjs/loader.js:823:14)
    at Function.f._load (electron/js2c/asar_bundle.js:5:12913)
    at Module.require (internal/modules/cjs/loader.js:1006:19)
    at require (internal/modules/cjs/helpers.js:88:18)
    at getDefaultSassImplementation (J:\work\some-project\mobile-app\source\app\node_modules\sass-loader\dist\utils.js:42:10)
    at getSassImplementation (J:\work\some-project\mobile-app\source\app\node_modules\sass-loader\dist\utils.js:50:30)
    at Object.loader (J:\work\some-project\mobile-app\source\app\node_modules\sass-loader\dist\index.js:34:59)
    at Object.OEKy (http://localhost:9977/base/test/karma-bundle.js?809142f8c3201b9437491c04337786f3a369e211:57768:7)
    at __webpack_require__ (http://localhost:9977/base/test/karma-bundle.js?809142f8c3201b9437491c04337786f3a369e211:20:30)
    at Object.t+Ps (http://localhost:9977/base/test/karma-bundle.js?809142f8c3201b9437491c04337786f3a369e211:135384:27)
    at __webpack_require__ (http://localhost:9977/base/test/karma-bundle.js?809142f8c3201b9437491c04337786f3a369e211:20:30)
    at Module.main (http://localhost:9977/base/test/karma-bundle.js?809142f8c3201b9437491c04337786f3a369e211:124748:76)
    at __webpack_require__ (http://localhost:9977/base/test/karma-bundle.js?809142f8c3201b9437491c04337786f3a369e211:20:30)
    at Module.c3R7 (http://localhost:9977/base/test/karma-bundle.js?809142f8c3201b9437491c04337786f3a369e211:104765:67)
    at __webpack_require__ (http://localhost:9977/base/test/karma-bundle.js?809142f8c3201b9437491c04337786f3a369e211:20:30)
    at Module.i0VB (http://localhost:9977/base/test/karma-bundle.js?809142f8c3201b9437491c04337786f3a369e211:119379:68)
    at __webpack_require__ (http://localhost:9977/base/test/karma-bundle.js?809142f8c3201b9437491c04337786f3a369e211:20:30)
    at webpackContext (http://localhost:9977/base/test/karma-bundle.js?809142f8c3201b9437491c04337786f3a369e211:82209:9)
    at Array.map (<anonymous>)
    at requireAllInContext (http://localhost:9977/base/test/karma-bundle.js?809142f8c3201b9437491c04337786f3a369e211:47484:32)
    at Array.forEach (<anonymous>)
    at runTests (http://localhost:9977/base/test/karma-bundle.js?809142f8c3201b9437491c04337786f3a369e211:47480:12)
    at Module.<anonymous> (http://localhost:9977/base/test/karma-bundle.js?809142f8c3201b9437491c04337786f3a369e211:47469:1)
    at Module.Ivzx (http://localhost:9977/base/test/karma-bundle.js?809142f8c3201b9437491c04337786f3a369e211:47487:30)
    at __webpack_require__ (http://localhost:9977/base/test/karma-bundle.js?809142f8c3201b9437491c04337786f3a369e211:20:30)
    at http://localhost:9977/base/test/karma-bundle.js?809142f8c3201b9437491c04337786f3a369e211:84:18
    at http://localhost:9977/base/test/karma-bundle.js?809142f8c3201b9437491c04337786f3a369e211:87:10
[2021-11-04 06:18:36.761] [INFO] [Adapter]: Finished loading tests in 24.32 secs (Failed)

I can run npm run test manually without issue, and there's no global node-sass implementation installed. It's only when karma is being invoked by the extension here that it seems to fail 🤔
I'll troubleshoot a bit more soon!

If I pass in the full path to the local karma install, this works. E.g., adding this to the project's settings.json:
  "karmaTestExplorer.karmaProcessCommand": "j:/work/some-project/mobile-app/source/app/node_modules/.bin/karma.cmd",

Things also work if  the command in the launchers to be node instead of process.execPath (which is code.exe):

I think what's going on here is that the node version code.exe pretends to be is different to the node version I have on path. The node-sass is a compiled output, and isn't able to run with the different version of node on Windows.
If I instead adjust this to use the node on path, then it works as expected because it's the runtime node-sass was compiled for.

@peitschie Thanks for troubleshooting that. It should now use the node executable from PATH, only falling back to code.exe when that's not found. Can you verify again with your project setup? Thanks.

That worked perfectly on all the codebases I tried it with 🎉
Thanks so much for this 😺

@peitschie Great, I've published it to the marketplace. Feel free report any future issues you run into. Thanks.


[Bug] invalid jsonpath when key has ":" in its name

Expected Behavior
jsonpath should resolve correctly
Actual Behavior
Using the response of a previous request to set an environment variable errors out when the json property has a : in its name
Reproduction Steps
Use this json (response from another request):
{
  "hydra:member": [
    {
      "@id': "/entities/xxxx",
      ...
    },
    { ... },
    { ... }
  ],
  "hydra:totalItems": 3
}

use $['hydra:member'][0]['@id'] as the jsonpath expression, live preview shows:
Invalid JSONPath query: $['hydra:member'][0]['@id']
Is there an existing issue for this?

[X] I have searched the issue tracker for this problem.

Additional Information
This solution worked great before and was broken with recent updates
Insomnia Version
2021.6.0-1
What operating system are you using?
Other Linux
Operating System Version
Linux 5.10.70-1-MANJARO #1 SMP PREEMPT Thu Sep 30 15:29:01 UTC 2021 x86_64 GNU/Linux
Installation method
AUR package
Last Known Working Insomnia version
2021.5.3

Hi! Thanks for reporting.    I dug into this and there's some good news:
TLDR, use ` to escape the @
$['hydra:member'][0]['`@id']

I created https://mockbin.org/bin/cdc1f76d-b720-4a91-abbc-f0410f2f4222/view for the sake of testing this.  It returns:
{
  "hydra:member": [
    {
      "@id": "0123-4567-8888",
      "type": "Avenger"
    },
    {
      "@id": "0123-4567-8910"
    }
  ],
  "@test": true
}

It's not anything to do with :, it's actually the @ that's the troublemaker.
This query works just fine:
$['hydra:member'][0]

But when you introduce the @ is when the problem starts.  The issue is that @ is a reserved character in jsonpath and different libraries handle it a little differently based on some vagueness in the spec.  Recently in a PR we updated to jsonpath-plus because the prior npm, jsonpath, was blocking a major project and (apparently, by the issues on jsonpath repo) no workarounds to the problems we hit existed.
Despite having test coverage for this (in insomnia-plugin-response), this specific case wasn't one of them.  The part that's unfortunate is that both jsonpath and jsonpath-plus are "JSONPath Spec Compliant" :tm:, and yet, clearly, as you have seen, they have subtly different behaviors in places.
I can confirm this is a regression, but I'm going to raise this to the rest of the team to know more about changes in the future.  I doubt we're going to be switching back to jsonpath for one thing because (as far as we know) we can't, but for another that jsonpath-plus has double the weekly downloads (almost a million) and is more regularly maintained, and seems just healthier overall.
Here's an example of it working with the latest release:

Separate of this specific syntax issue, I'd like to ask whether jq syntax would have been preferable to you in this case.  We're building a case all the time, it seems, for doing that (see https://github.com/Kong/insomnia/issues/777) and I wanted to know if that would have been just as good a solution to your problem in this instance.

Great ! Thanks for your reply, the escape solution with ['`@id'] perfectly answers the problem :).
The integration of jq may be top to allow more manipulations.


Must set rbenv version before bundle

Closing in lieu of https://github.com/gds-operations/vcloud-launcher/pull/125


Build Tag Activated Drivers/Executors

This patch enables the specific activation of storage drivers/executors via build tags. The tags libstorage_storage_driver and libstorage_storage_executor, if absent, will result in all drivers/executors being activated. This is the previous, default behavior. However, if the tags libstorage_storage_driver and libstorage_storage_executor are present along with libstorage_storage_driver_NAME and libstorage_storage_executor_NAME, where NAME is the name of a driver, ex. ebs, then only that driver and executor are considered for compilation.

 There are comments on each nil import! Ugh.

Current coverage is 30.89% (diff: 100%)

No coverage report found for master at 099d442.

Powered by Codecov. Last update 099d442...0bc6b8c


The metric I got is different from that reported in the paper

First thanks for providing the code. I tried to test the algorithm by running the inference (python senet_infer.py) on the validation dataset. The metrics I obtained is avg_sig=3.785319, avg_bak=3.273069, avg_ovl=3.141790 while the number reported in the paper is: avg_sig=3.86, avg_bak=3.33, avg_ovl=3.22. I'm wondering whether I missed something. I didn't change any code and use exactly the same evaluation code mentioned in the paper. FYI, when I tested on the noisy data (no enhancement is applied), the numbers I got is the same as that in paper. Any idea?

Hi.
Thanks for your interest, and sorry to hear about your issue. I am pretty busy at the moment and I no longer have access to a GPU machine. How urgently do you need an answer?
In case that helps in the meantime, I believe I have somewhere the audio files that were generated (and scored) for the paper results. Let me know.

Thanks for your replying @francoisgermain ! It will be very helpful if you can point me to the already generated enhanced audios for validation dataset. When you get time later, I appreciate if you can run the inference code and recompute the metrics for the generated audio. For your information, the number I got is computed on 1080Ti GPU and none of your code is changed.

Hi,
I have also met this problem when running the inference code using pre-trained weights provided in the repo and generated the enhanced utterances.
The evaluation tool we are using is from here,
and the scores we've got are:
| PESQ | CSIG | CBAK | COVL | SSNR
Deep Feature Loss (paper)            |     -     |  3.86  |  3.33   |   3.22  | -
Deep Feature Loss (code)             |  2.58   |  3.80  |  2.72   |  3.19   | 0.60
It seems that the main differences are CBAK and SSNR.
I will be very grateful if you can give me any support for this. Thank you!


"Top of Round" alert does not fire if "Repeating" is true

Creating a "Top of Round" alert using these settings will result in the alert not firing:
Trigger after rounds = 1
Repeat frequency = 1

Thanks for the report! This should be fixed in the next version, which I hope to release today.


Augment website with talk notes and output

Background and problem
In my opinion, the IPFS Thing website is great for:

Official/polished communication and branding.  It brings a sense of "legitimacy" to the event.
Good balance between collaboration and review/control with the GitHub PR flow for organizing tracks and talks.  It's self-service for someone to propose a track/talk but there also gates in place to help make sure it "fits".

I don't think the site is great for quick edits for capturing things like discussion notes or links to other resources (slides, videos, etc.).  If there is friction of needing to get PRs merged to get this stuff in, it's going to prevent participants from doing it.  I want to remove as much friction as possible.
As a result, I'd propose we have another place that allows quicker self-service note/output capturing per talk.  We can always add a pointer to these per-talk "pages".
Requirements

"easy" editing to capture notes, URLs, outputs from a talk
self-service to adjust as new talks are added.  One shouldn't need to rely on anyone else to spin this up.

Possible solutions
Notion
Pros:

Collaborative editing
Simple to use
Can have structured data

Cons:

Proprietary SaaS platform
Instance "owned" by one company (e.g., PL EngRes, Number0)
If don't have an account already, it's another proprietary thing that someone eventually has to pay for.

IPFS Discourse
Pros:

Not branded toward a single company
Open Source product
It's where we ask the community to discuss anyway thus naturally gives higher visibility to the community
Much of the community already has accounts for it, and if they don't it's self-service to get one.

Cons:

Not going to get a quick table export of all the sessions with some structured data (e.g., links to slides, videos).  The biggest value I see in structured data is for catching the cases where we're missing things like slides, videos.
Doesn't have collaborative editing for notetaking during a session.  It won't be transparent what others have typed/captured until they submit.  This can lead to duplication or cause folks to assume that someone else is taking care of it.
To make it easily navigatable, I think we'll need to create one post per talk.  I don't know if there's a way to do a bulk import of posts from a CSV file.

GitHub
Similar to IPFS Discourse.
Additional Pros:

Everyone has an account.
Surely possible to easily precreate a bunch of issues or "talk files" that PRs get created against

Additional Cons:

If PRs are involved, there are extra steps for getting content merged.

Recommendation
Lean into IPFS Discourse.  To pull this off, I would:

Create an IPFS Thing category
Create a post for each track (example where this had already been done)
For each .toml track in https://github.com/ipfs-shipyard/ipfs-thing-2022/tree/main/events, set the "website" to the discuss.ipfs.io post.
Communicate expectations of track leads and participants to use Discourse for capturing track links and outputs.

We unfortunately don't get collaborative editing, but it's self-service for anyone to make posts and replies through the event as things evolve.

Discourse can enable “wiki” editing. It’s not real time collaborative but it can be made to edit by anyone.
And thanks for channeling exactly what I was thinking ;)
I still need to change the link for my track.

PR to add IPFS Discourse "website" links for each track: https://github.com/ipfs-shipyard/ipfs-thing-2022/pull/118

yeah, this website is not meant to capture notes or outputs -- let's definitely do that elsewhere
thanks for generating discourse pages and PRing in -- It's great to have a good default
i think various people will find different platforms more or less effective for them. I don't think forcing one thing is viable or optimal. track leads (or even the session speaker/facilitator/lead) should have a default, but ultimately decide what's best for them.

@BigLep is #118 enough to close this out or do we need more done to close this out?

Yeah, I think we're good to close this out.  Doing so now...


transformexpression with origin

@JiahuiJiang

and my build failed :-P lol can we just merge yours and cut a release?

@JiahuiJiang @mccheah can you make sure to update pr to upstream? Also I wouldn't merge this without tests but you were quicker than me


Wrong escaping of HTML tags in long texts (in integration settings)

Tags are not escaped anymore:
Example below tag BR!

@LucasBrazi06 : Tu sais d'ou ca peux venir?

Just merged a PR that fixed it ;-)

We also have a problem with the text of the confirmation dialogs!

We also have a problem with the text of the confirmation dialogs!

In the i18n we could put an Array of strings, 1 per line and detect in the dialog the multiline text and add the right HTML tags in that case (.)
What do you think?

We also have a problem with the text of the confirmation dialogs!

In the i18n we could put an Array of strings, 1 per line and detect in the dialog the multiline text and add the right HTML tags in that case (
.) What do you think?

Let me check ... I was using the HTML Tag escaping in the billing as well (when asking to confirm the billing activation). This was working fine at that time. I need to understand why!

We also have a problem with the text of the confirmation dialogs!

In the i18n we could put an Array of strings, 1 per line and detect in the dialog the multiline text and add the right HTML tags in that case (
.) What do you think?

Let me check ... I was using the HTML Tag escaping in the billing as well (when asking to confirm the billing activation). This was working fine at that time. I need to understand why!

The root cause of the new behavior is a security fix from Siwar to prevent xss injection attacks!

We also have a problem with the text of the confirmation dialogs!

In the i18n we could put an Array of strings, 1 per line and detect in the dialog the multiline text and add the right HTML tags in that case (
.) What do you think?

Let me check ... I was using the HTML Tag escaping in the billing as well (when asking to confirm the billing activation). This was working fine at that time. I need to understand why!

The root cause of the new behavior is a security fix from Siwar to prevent xss injection attacks!

@LucasBrazi06 : We have the same security issue with the EULA text. I would therefore suggest reverting the fix from Siwar (for now).
What do you think?
Here is the previous behavior!

@LucasBrazi06 : We have the same security issue with the EULA text. I would therefore suggest reverting the fix from Siwar (for now).
What do you think?

I agree as the source of the HTML is not provided from the end-user but by the application itself.
We can think of the multi line in the i18n mid-term to remove the HTML tags in it which is not nice.


Need to clarify all dimension values of "Status" about Total Update Deployment Machine Runs

Hi PG,
I believe that this document needs to clarify all dimension values of "Status" about Total Update Deployment Machine Runs.
The alert setting view can show only "Status" that Log Analytics has collected. So customers who didn't run any deployment of update management or didn't encounter the failure of update management can't filter alerts by using "Status". Because they can't know what "Status" will appear.

Best regards.

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

ID: b26e8f87-1ec9-0fdd-b4f9-7ad29ae2f2f5
Version Independent ID: 46227d12-5abd-2966-ad3e-48a8c3d6560c
Content: How to create alerts for Azure Automation Update Management
Content Source: articles/automation/update-management/configure-alerts.md
Service: automation
Sub-service: update-management
GitHub Login: @SGSneha
Microsoft Alias: sudhirsneha

@kongou-ae Thanks for the feedback! We are currently investigating and will update you shortly.

@kongou-ae  - Thanks for bringing this to our attention.
I'm going to assign this to the document author so they can update the document accordingly.

For those looking for the possible values, a successful update will go through the following states:

NotStarted
InProgress
Succeeded

For the moment I have no information about other states.


Laravel 5.2 Shift

This pull request includes the changes for upgrading to Laravel 5.2.
Before merging, you should:

Checkout the laravel-5.2-shift branch
Review all pull request comments for additional changes
Run composer update
Thoroughly test your application

Commit any additional changes to the laravel-5.2-shift branch. If there were changes you feel could have been automated, please leave a comment on this pull request to help improve Laravel Shift.

slice, chunk, and reverse methods now preserve keys on the collection in Laravel 5.2. You should review your usage of these methods.
I found potential uses of these methods in:

app/Console/Commands/MakeSitemap.php
app/Console/Commands/ImportTags.php
app/Console/Commands/OaiPmhDownloadImages.php
app/Console/Commands/MigrateTags.php
app/Http/Controllers/AuthorityController.php
app/Http/Controllers/ItemController.php

Laravel 5.2 adds Middleware Groups for convenience. Since this may require changes to your routes and controllers, I did not upgrade app/Http/Kernel.php. You should review Middleware Groups in more detail. When ready, merge your app/Http/Kernel.php with the 5.2 version and update your routes/controllers manually.

Laravel 5.2 changed the value of $redirectTo from /home to / in app/Http/Controllers/Auth/AuthController.php. I did not make this change since you may have customized it for your app. However, you may wish to change this if you are not using Auth or if you want to follow the latest Laravel conventions.

Laravel 5.2 modified the default Middleware. Since your middleware differs from the Laravel 5.1 default, you will need to compare the following middleware against the 5.2 versions and merge any changes.

app/Http/Middleware/Authenticate.php

Laravel 5.2 condenses the default User model dramatically. Since your app/User.php differs from the Laravel 5.1 default, you will need to compare yours against the 5.2 version and merge any changes.

Laravel 5.2 updated the database session driver. If you are using the database driver, you need to add the user_id (nullable integer), ip_address (nullable string), and user_agent (text) columns to your session database table.

Laravel 5.2 now prefers using get() on the request object instead of the Input facade. Since I found potential references to the Input facade, I did not remove the alias in app/config.php.
If you would like to upgrade to using the request object, review the potential references of the Input facade in:

app/Console/Commands/OaiPmhHarvest.php
app/Item.php
app/Http/routes.php
app/Http/Controllers/CatalogController.php
app/Http/Controllers/FileuploaderController.php
app/Http/Controllers/ClanokController.php
app/Http/Controllers/AuthorController.php
app/Http/Controllers/CollectionController.php
app/Http/Controllers/SketchbookController.php
app/Http/Controllers/KolekciaController.php
app/Http/Controllers/SlideController.php
app/Http/Controllers/ArticleController.php
app/Http/Controllers/AuthorityController.php
app/Http/Controllers/UserController.php
app/Http/Controllers/AuthController.php
app/Http/Controllers/SpiceHarvesterController.php
app/Http/Controllers/ItemController.php
app/Helpers/general.php
resources/views/items/form.blade.php
resources/views/users/form.blade.php
resources/views/harvests/index.blade.php
resources/views/harvests/form.blade.php
resources/views/kolekcie.blade.php
resources/views/katalog.blade.php
resources/views/slides/form.blade.php
resources/views/sketchbooks/form.blade.php
resources/views/articles/form.blade.php
resources/views/collections/form.blade.php
resources/views/authorities/form.blade.php
resources/views/autori.blade.php

I could not upgrade the following configuration files since they differed from the 5.1 defaults. You need to compare these configuration files against the default Laravel 5.2 configuration files and merge any changes:

config/cache.php
config/database.php
config/services.php

Laravel 5.2 updated the public/.htaccess to handle the Authorization header. Since your public/.htaccess file differed from the Laravel default, you need to review the Laravel 5.2 version and merge any changes.


linked dependency causes tests to fail

Describe the bug
Thanks so much for creating such wonderful tooling :)
I believe I have found a bug and hope I can describe it well enough here:

a library project that has @mui/base as a dependency and exports files using it
a test project that uses the library and has tests executed via vitest
hook the library into the test project via a file: resolution and the tests pass ✅
hook the library into the test project via a link: resolution and the tests fail with this error message ❌:

yarn run v1.22.19
$ vitest run

 RUN  v0.34.3 /Users/aokeeffe/Developer/vitest-link-reproduction/test-projects/vite-project

stderr | src/Test.test.jsx > renders a button
Warning: Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://reactjs.org/link/invalid-hook-call for tips about how to debug and fix this problem.
Warning: Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://reactjs.org/link/invalid-hook-call for tips about how to debug and fix this problem.
Error: Uncaught [TypeError: Cannot read properties of null (reading 'useRef')]
    at reportException (/Users/aokeeffe/Developer/vitest-link-reproduction/test-projects/vite-project/node_modules/jsdom/lib/jsdom/living/helpers/runtime-script-errors.js:66:24)
    at innerInvokeEventListeners (/Users/aokeeffe/Developer/vitest-link-reproduction/test-projects/vite-project/node_modules/jsdom/lib/jsdom/living/events/EventTarget-impl.js:353:9)
    at invokeEventListeners (/Users/aokeeffe/Developer/vitest-link-reproduction/test-projects/vite-project/node_modules/jsdom/lib/jsdom/living/events/EventTarget-impl.js:286:3)
    at HTMLUnknownElementImpl._dispatch (/Users/aokeeffe/Developer/vitest-link-reproduction/test-projects/vite-project/node_modules/jsdom/lib/jsdom/living/events/EventTarget-impl.js:233:9)
    at HTMLUnknownElementImpl.dispatchEvent (/Users/aokeeffe/Developer/vitest-link-reproduction/test-projects/vite-project/node_modules/jsdom/lib/jsdom/living/events/EventTarget-impl.js:104:17)
    at HTMLUnknownElement.dispatchEvent (/Users/aokeeffe/Developer/vitest-link-reproduction/test-projects/vite-project/node_modules/jsdom/lib/jsdom/living/generated/EventTarget.js:241:34)
    at Object.invokeGuardedCallbackDev (/Users/aokeeffe/Developer/vitest-link-reproduction/test-projects/vite-project/node_modules/react-dom/cjs/react-dom.development.js:4213:16)
    at invokeGuardedCallback (/Users/aokeeffe/Developer/vitest-link-reproduction/test-projects/vite-project/node_modules/react-dom/cjs/react-dom.development.js:4277:31)
    at beginWork$1 (/Users/aokeeffe/Developer/vitest-link-reproduction/test-projects/vite-project/node_modules/react-dom/cjs/react-dom.development.js:27451:7)
    at performUnitOfWork (/Users/aokeeffe/Developer/vitest-link-reproduction/test-projects/vite-project/node_modules/react-dom/cjs/react-dom.development.js:26560:12) TypeError: Cannot read properties of null (reading 'useRef')
    at Object.useRef (/Users/aokeeffe/Developer/vitest-link-reproduction/node_modules/react/cjs/react.development.js:1630:21)
    at Button (/Users/aokeeffe/Developer/vitest-link-reproduction/node_modules/@mui/base/node/Button/Button.js:54:27)
    at renderWithHooks (/Users/aokeeffe/Developer/vitest-link-reproduction/test-projects/vite-project/node_modules/react-dom/cjs/react-dom.development.js:16305:18)
    at updateForwardRef (/Users/aokeeffe/Developer/vitest-link-reproduction/test-projects/vite-project/node_modules/react-dom/cjs/react-dom.development.js:19226:20)
    at beginWork (/Users/aokeeffe/Developer/vitest-link-reproduction/test-projects/vite-project/node_modules/react-dom/cjs/react-dom.development.js:21636:16)
    at HTMLUnknownElement.callCallback (/Users/aokeeffe/Developer/vitest-link-reproduction/test-projects/vite-project/node_modules/react-dom/cjs/react-dom.development.js:4164:14)
    at HTMLUnknownElement.callTheUserObjectsOperation (/Users/aokeeffe/Developer/vitest-link-reproduction/test-projects/vite-project/node_modules/jsdom/lib/jsdom/living/generated/EventListener.js:26:30)
    at innerInvokeEventListeners (/Users/aokeeffe/Developer/vitest-link-reproduction/test-projects/vite-project/node_modules/jsdom/lib/jsdom/living/events/EventTarget-impl.js:350:25)
    at invokeEventListeners (/Users/aokeeffe/Developer/vitest-link-reproduction/test-projects/vite-project/node_modules/jsdom/lib/jsdom/living/events/EventTarget-impl.js:286:3)
    at HTMLUnknownElementImpl._dispatch (/Users/aokeeffe/Developer/vitest-link-reproduction/test-projects/vite-project/node_modules/jsdom/lib/jsdom/living/events/EventTarget-impl.js:233:9)
Warning: Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://reactjs.org/link/invalid-hook-call for tips about how to debug and fix this problem.
Warning: Invalid hook call. Hooks can only be called inside of the body of a function component. This could happen for one of the following reasons:
1. You might have mismatching versions of React and the renderer (such as React DOM)
2. You might be breaking the Rules of Hooks
3. You might have more than one copy of React in the same app
See https://reactjs.org/link/invalid-hook-call for tips about how to debug and fix this problem.
Error: Uncaught [TypeError: Cannot read properties of null (reading 'useRef')]
    at reportException (/Users/aokeeffe/Developer/vitest-link-reproduction/test-projects/vite-project/node_modules/jsdom/lib/jsdom/living/helpers/runtime-script-errors.js:66:24)
    at innerInvokeEventListeners (/Users/aokeeffe/Developer/vitest-link-reproduction/test-projects/vite-project/node_modules/jsdom/lib/jsdom/living/events/EventTarget-impl.js:353:9)
    at invokeEventListeners (/Users/aokeeffe/Developer/vitest-link-reproduction/test-projects/vite-project/node_modules/jsdom/lib/jsdom/living/events/EventTarget-impl.js:286:3)
    at HTMLUnknownElementImpl._dispatch (/Users/aokeeffe/Developer/vitest-link-reproduction/test-projects/vite-project/node_modules/jsdom/lib/jsdom/living/events/EventTarget-impl.js:233:9)
    at HTMLUnknownElementImpl.dispatchEvent (/Users/aokeeffe/Developer/vitest-link-reproduction/test-projects/vite-project/node_modules/jsdom/lib/jsdom/living/events/EventTarget-impl.js:104:17)
    at HTMLUnknownElement.dispatchEvent (/Users/aokeeffe/Developer/vitest-link-reproduction/test-projects/vite-project/node_modules/jsdom/lib/jsdom/living/generated/EventTarget.js:241:34)
    at Object.invokeGuardedCallbackDev (/Users/aokeeffe/Developer/vitest-link-reproduction/test-projects/vite-project/node_modules/react-dom/cjs/react-dom.development.js:4213:16)
    at invokeGuardedCallback (/Users/aokeeffe/Developer/vitest-link-reproduction/test-projects/vite-project/node_modules/react-dom/cjs/react-dom.development.js:4277:31)
    at beginWork$1 (/Users/aokeeffe/Developer/vitest-link-reproduction/test-projects/vite-project/node_modules/react-dom/cjs/react-dom.development.js:27451:7)
    at performUnitOfWork (/Users/aokeeffe/Developer/vitest-link-reproduction/test-projects/vite-project/node_modules/react-dom/cjs/react-dom.development.js:26560:12) TypeError: Cannot read properties of null (reading 'useRef')
    at Object.useRef (/Users/aokeeffe/Developer/vitest-link-reproduction/node_modules/react/cjs/react.development.js:1630:21)
    at Button (/Users/aokeeffe/Developer/vitest-link-reproduction/node_modules/@mui/base/node/Button/Button.js:54:27)
    at renderWithHooks (/Users/aokeeffe/Developer/vitest-link-reproduction/test-projects/vite-project/node_modules/react-dom/cjs/react-dom.development.js:16305:18)
    at updateForwardRef (/Users/aokeeffe/Developer/vitest-link-reproduction/test-projects/vite-project/node_modules/react-dom/cjs/react-dom.development.js:19226:20)
    at beginWork (/Users/aokeeffe/Developer/vitest-link-reproduction/test-projects/vite-project/node_modules/react-dom/cjs/react-dom.development.js:21636:16)
    at HTMLUnknownElement.callCallback (/Users/aokeeffe/Developer/vitest-link-reproduction/test-projects/vite-project/node_modules/react-dom/cjs/react-dom.development.js:4164:14)
    at HTMLUnknownElement.callTheUserObjectsOperation (/Users/aokeeffe/Developer/vitest-link-reproduction/test-projects/vite-project/node_modules/jsdom/lib/jsdom/living/generated/EventListener.js:26:30)
    at innerInvokeEventListeners (/Users/aokeeffe/Developer/vitest-link-reproduction/test-projects/vite-project/node_modules/jsdom/lib/jsdom/living/events/EventTarget-impl.js:350:25)
    at invokeEventListeners (/Users/aokeeffe/Developer/vitest-link-reproduction/test-projects/vite-project/node_modules/jsdom/lib/jsdom/living/events/EventTarget-impl.js:286:3)
    at HTMLUnknownElementImpl._dispatch (/Users/aokeeffe/Developer/vitest-link-reproduction/test-projects/vite-project/node_modules/jsdom/lib/jsdom/living/events/EventTarget-impl.js:233:9)
The above error occurred in the <ForwardRef(Button)> component:

    at Button (/Users/aokeeffe/Developer/vitest-link-reproduction/node_modules/@mui/base/node/Button/Button.js:47:7)
    at p (/Users/aokeeffe/Developer/vitest-link-reproduction/test-projects/workaround-package/dist/vitest-link-reproduction.js:7:24)

Consider adding an error boundary to your tree to customize error handling behavior.
Visit https://reactjs.org/link/error-boundaries to learn more about error boundaries.

 ❯ src/Test.test.jsx (1)
   × renders a button

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Failed Tests 1 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯

 FAIL  src/Test.test.jsx > renders a button
TypeError: Cannot read properties of null (reading 'useRef')
 ❯ Object.useRef ../../node_modules/react/cjs/react.development.js:1630:21
 ❯ Button ../../node_modules/@mui/base/node/Button/Button.js:54:27
 ❯ renderWithHooks node_modules/react-dom/cjs/react-dom.development.js:16305:18
 ❯ updateForwardRef node_modules/react-dom/cjs/react-dom.development.js:19226:20
 ❯ beginWork node_modules/react-dom/cjs/react-dom.development.js:21636:16
 ❯ beginWork$1 node_modules/react-dom/cjs/react-dom.development.js:27426:14
 ❯ performUnitOfWork node_modules/react-dom/cjs/react-dom.development.js:26560:12
 ❯ workLoopSync node_modules/react-dom/cjs/react-dom.development.js:26466:5
 ❯ renderRootSync node_modules/react-dom/cjs/react-dom.development.js:26434:7
 ❯ recoverFromConcurrentError node_modules/react-dom/cjs/react-dom.development.js:25850:20

⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/1]⎯

 Test Files  1 failed (1)
      Tests  1 failed (1)
   Start at  11:02:28
   Duration  1.28s (transform 26ms, setup 0ms, collect 437ms, tests 16ms, environment 635ms, prepare 74ms)

error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

From my understanding there should be no difference between these two scenarios and the tests should pass. Please let me know if I can provide more info to make it clearer :)
Reproduction
https://github.com/ArloL/vitest-link-reproduction
System Info
System:
  OS: macOS 13.5.1
  CPU: (10) arm64 Apple M1 Pro
  Memory: 364.38 MB / 16.00 GB
  Shell: 5.9 - /bin/zsh
Binaries:
  Node: 20.5.1 - /opt/homebrew/bin/node
  Yarn: 1.22.19 - /opt/homebrew/bin/yarn
  npm: 9.8.0 - /opt/homebrew/bin/npm
Browsers:
  Safari: 16.6
npmPackages:
  @vitejs/plugin-react: ^4.0.0 => 4.0.4
  vite: ^4.1.4 => 4.4.9

Used Package Manager
yarn
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

I've run into this same error when using Jest and linking local NPM packages which have react as dependency. The linked packages were bringing their own copy of React into the runtime. In Jest the solution was to configure moduleNameMapper to resolve react to a single location every time. Maybe Vite's resolve could be configured to do the same? This is something that should be done by user, not in Vitest itself.
This issue may have some examples https://github.com/facebook/react/issues/13991.

Maybe resolve.dedupe can help?
https://vitejs.dev/config/shared-options.html#resolve-dedupe

Thanks for the suggesstions ☺ I just tried adding the resolve.dedupe setting - hopefully I got it right:
https://github.com/ArloL/vitest-link-reproduction/commit/63e2573ed8654443fdb04b5c7dad6d17aad0b955
Sadly it did not make the tests pass. Did I maybe add it in the wrong section?

Any luck here?  I'm seeing a similar issue, and adding resolve.dedupe didn't change anything for me either.

I got a little further: the second react comes from the root library. Apparently it starts searching the directory tree upward from where the actual JS file is (test-projects/workaround-package/dist/index.js) - not where it "is" via the symlink (test-projects/vite-project/node_modules/vitest-link-reproduction/dist/index.js). That search never comes across the react we want (test-projects/vite-project/node_modules/react) and then it finds what it needs in the root (node_modules/react). And that is how it ends up being there twice. Now how to solve that … no idea … something like --preserve-symlinks sounds like it does what I want, or am I missing something?

something like --preserve-symlinks sounds like it does what I want, or am I missing something?

There is resolve.preserveSymlinks option: https://vitejs.dev/config/shared-options.html#resolve-preservesymlinks

Thanks for the suggesition. I think I tried it before and it did not work. To be safe I just added it to my reproduction: https://github.com/ArloL/vitest-link-reproduction/commit/8e3f1229a52f62c21da6533d767de04a6104090e
Sadly the link build still fails: https://github.com/ArloL/vitest-link-reproduction/actions/runs/6526130338/job/17719549269

Maybe this will help, I'm working with a linked custom package that reuses the same dependency and solved it with resolve.mainFields and forcing to use use esmodules first. This seems to fix it for me
  resolve: {
    dedupe: ['mobx'], //mobx is in custom linked package and main package
    mainFields: ['module', 'main'], //this is needed to work
  },

I tried adding it: https://github.com/ArloL/vitest-link-reproduction/commit/8de886b449ca58b5e0175376d540f009b8527014 but sadly it still fails: https://github.com/ArloL/vitest-link-reproduction/actions/runs/6804415276

It looks like adding @mui/base to resolve.dedupe and removing preserveSymlinks fixes it.
https://stackblitz.com/edit/github-uvwz3x?file=test-projects%2Fvite-project%2Fvite.config.js
Currently @mui/base is coming from (root)/node_modules/@mui/base and thus it ends up pulling react from (root)/node_modules/react while test-projects/vite-project/src/Test.test.jsx is using react from (root)/test-projects/vite-project/node_modules/react. After deduping, @mui/base will come from (root)/test-projects/vite-project/node_modules/@mui/base and thus it can see the same react as vite-project tests.
While debugging and studying the internal of Vite resolve.dedupe, I found that DEBUG=vite:resolve-details might come in handy to see where @mui/base is coming from during Vitest.
Running DEBUG=vite:resolve-details yarn run test
❯ DEBUG=vite:resolve-details yarn run test
yarn run v1.22.19
$ vitest
  vite:resolve-details [package entry] vite -> /home/projects/github-uvwz3x/test-projects/vite-project/node_modules/vite/dist/node/index.js +0ms
  vite:resolve-details [package entry] @vitejs/plugin-react -><EMAIL_ADDRESS>+14ms
  vite:resolve-details [package entry] vitest -> /home/projects/github-uvwz3x/test-projects/vite-project/node_modules/vitest/dist/index.js +166ms

 DEV  v1.1.0 /home/projects/github-uvwz3x/test-projects/vite-project

  vite:resolve-details [@fs] <EMAIL_ADDRESS>-> /home/projects/github-uvwz3x/test-projects/vite-project/node_modules/vite/dist/client/env.mjs +2s
  vite:resolve-details [@fs] <EMAIL_ADDRESS>-> /home/projects/github-uvwz3x/test-projects/vite-project/node_modules/vite/dist/client/env.mjs +1ms
  vite:resolve-details [fs] /home/projects/github-uvwz3x/test-projects/vite-project/src/Test.test.jsx -> /home/projects/github-uvwz3x/test-projects/vite-project/src/Test.test.jsx +709ms
  vite:resolve-details [fs] /home/projects/github-uvwz3x/test-projects/vite-project/src/Test.test.jsx -> /home/projects/github-uvwz3x/test-projects/vite-project/src/Test.test.jsx +0ms
  vite:resolve-details [package entry] @testing-library/react -><EMAIL_ADDRESS>+21ms
  vite:resolve-details [package entry] vitest-link-reproduction -> /home/projects/github-uvwz3x/test-projects/workaround-package/dist/vitest-link-reproduction.js +1ms
  vite:resolve-details [node/deep-import] ./jsx-dev-runtime -> /home/projects/github-uvwz3x/test-projects/vite-project/node_modules/react/jsx-dev-runtime.js +1ms
  vite:resolve-details [package entry] vitest -> /home/projects/github-uvwz3x/test-projects/vite-project/node_modules/vitest/dist/index.js +0ms
  vite:resolve-details [fs] /home/projects/github-uvwz3x/test-projects/workaround-package/dist/vitest-link-reproduction.js -> /home/projects/github-uvwz3x/test-projects/workaround-package/dist/vitest-link-reproduction.js +158ms
  vite:resolve-details [fs] /home/projects/github-uvwz3x/test-projects/workaround-package/dist/vitest-link-reproduction.js -> /home/projects/github-uvwz3x/test-projects/workaround-package/dist/vitest-link-reproduction.js +0ms
  vite:resolve-details [package entry] @mui/base -><EMAIL_ADDRESS>+2ms
  vite:resolve-details [package entry] react -> /home/projects/github-uvwz3x/test-projects/vite-project/node_modules/react/index.js +0ms

 ✓ src/Test.test.jsx (1)
   ✓ renders a button

 Test Files  1 passed (1)
      Tests  1 passed (1)
   Start at  17:22:09
   Duration  2.54s (transform

Thanks, @hi-ogawa. What you describe makes perfect sense and I can confirm that it fixes my issue.
I am not sure if my assumptions are reasonable but I would have expected that preserveSymlinks should have worked just the same.

I am not sure if my assumptions are reasonable but I would expect that preserveSymlinks works just the same.

Good point. I'm testing with preserveSymlinks further and I think what's happening is that, with this option, vitest-link-production is resolved as node_modules/vitest-link-reproduction/dist/vitest-link-reproduction.js, but then Vitest's node_modules externalization kicks in, so Node runtime will eventually import this vitest-link-reproduction.js, which then maybe ends up following symlink again.
To prevent "externalizing" it, I think there is test.server.deps.linline otpion, so doing this seems to work:
https://stackblitz.com/edit/github-uvwz3x-6kmuvy?file=test-projects%2Fvite-project%2Fvite.config.js
import { defineConfig } from 'vite';
import react from '@vitejs/plugin-react';

// https://vitejs.dev/config/
export default defineConfig({
  plugins: [react()],
  resolve: {
    dedupe: ['react', 'react-dom', 'react/jsx-runtime'],
    preserveSymlinks: true,
  },
  test: {
    environment: 'jsdom',
    server: {
      deps: {
        inline: [/vitest-link-reproduction/],
      },
    },
  },
});

And this what I see when running DEBUG=vite:resolve-details yarn run test run:
  vite:resolve-details [url] /node_modules/vitest-link-reproduction/dist/vitest-link-reproduction.js -> /home/projects/github-uvwz3x/test-projects/vite-project/node_modules/vitest-link-reproduction/dist/vitest-link-reproduction.js +164ms
  vite:resolve-details [url] /node_modules/vitest-link-reproduction/dist/vitest-link-reproduction.js -> /home/projects/github-uvwz3x/test-projects/vite-project/node_modules/vitest-link-reproduction/dist/vitest-link-reproduction.js +1ms
  vite:resolve-details [package entry] @mui/base -><EMAIL_ADDRESS>+1ms
  vite:resolve-details [package entry] react -> /home/projects/github-uvwz3x/test-projects/vite-project/node_modules/react/index.js +1ms

Sadly that setup fails for me: https://github.com/ArloL/vitest-link-reproduction/pull/80


Feature - Support hexa (#RRGGBBAA, and #RGBA) conversions

Right now there is no support for hex with alpha (something missing in the main dependency of this plugin). I am working to resolve at Qix-/color-string#33. If it won't be resolved there, I will work to add a solve within this plugin.

archiving this repo


COPOD model acting strangely compared to other models

Hi, I was attempting to add the COPOD model to the compare_all_models.py file in the examples folder and it had a strange result.
I ran a similar script with fewer models and they perform normally, while COPOD does not. I have attached an image of the output and can upload my notebook as well, if needed.
I apologize if ignorance on my part is causing this to happen, but I cannot seem to find the problem.

Hi Sean, can you upload your notebook and I can take a look at it? Thanks.

import numpy as np
from scipy import stats
import matplotlib.pyplot as plt
%matplotlib inline
import matplotlib.font_manager

from pyod.models.abod import ABOD
from pyod.models.knn import KNN
from pyod.models.copod import COPOD

<frozen importlib._bootstrap>:219: RuntimeWarning: numpy.ufunc size changed, may indicate binary incompatibility. Expected 192 from C header, got 216 from PyObject
<frozen importlib._bootstrap>:219: RuntimeWarning: numpy.ufunc size changed, may indicate binary incompatibility. Expected 192 from C header, got 216 from PyObject
<frozen importlib._bootstrap>:219: RuntimeWarning: numpy.ufunc size changed, may indicate binary incompatibility. Expected 192 from C header, got 216 from PyObject

from pyod.utils.data import generate_data, get_outliers_inliers

#generate random data with two features
X_train, Y_train = generate_data(n_train=200,train_only=True, n_features=2)

# by default the outlier fraction is 0.1 in generate data function
outlier_fraction = 0.1

# store outliers and inliers in different numpy arrays
x_outliers, x_inliers = get_outliers_inliers(X_train,Y_train)

n_inliers = len(x_inliers)
n_outliers = len(x_outliers)

#separate the two features and use it to plot the data
F1 = X_train[:,[0]].reshape(-1,1)
F2 = X_train[:,[1]].reshape(-1,1)
F3 = x_outliers[:, [0]].reshape(-1,1)
F4 = x_outliers[:, [1]].reshape(-1,1)

# create a meshgrid
xx , yy = np.meshgrid(np.linspace(-10, 10, 200), np.linspace(-10, 10, 200))

# scatter plot
plt.scatter(F1,F2)
#plt.scatter(F3, F4, c='r')
plt.xlabel('F1')
plt.ylabel('F2')

Text(0, 0.5, 'F2')

classifiers = {
     'Angle-based Outlier Detector (ABOD)'   : ABOD(contamination=outlier_fraction),
     'K Nearest Neighbors (KNN)' :  KNN(contamination=outlier_fraction),
     'Copula-Based' : COPOD(contamination=outlier_fraction)
}

#set the figure size
plt.figure(figsize=(10, 10))

for i, (clf_name,clf) in enumerate(classifiers.items()) :
    # fit the dataset to the model
    clf.fit(X_train)

    # predict raw anomaly score
    scores_pred = clf.decision_function(X_train)*-1

    # prediction of a datapoint category outlier or inlier
    y_pred = clf.predict(X_train)

    # no of errors in prediction
    n_errors = (y_pred != Y_train).sum()
    print('No of Errors : ',clf_name, n_errors)

    # rest of the code is to create the visualization

    # threshold value to consider a datapoint inlier or outlier
    threshold = stats.scoreatpercentile(scores_pred, 100*outlier_fraction)

    # decision function calculates the raw anomaly score for every point
    Z = clf.decision_function(np.c_[xx.ravel(), yy.ravel()]) * -1
    Z = Z.reshape(xx.shape)

    subplot = plt.subplot(1, 3, i + 1)

    # fill blue colormap from minimum anomaly score to threshold value
    subplot.contourf(xx, yy, Z, levels = np.linspace(Z.min(), threshold, 10),cmap=plt.cm.Blues_r)

    # draw red contour line where anomaly score is equal to threshold
    a = subplot.contour(xx, yy, Z, levels=[threshold],linewidths=2, colors='red')

    # fill orange contour lines where range of anomaly score is from threshold to maximum anomaly score
    subplot.contourf(xx, yy, Z, levels=[threshold, Z.max()],colors='orange')

    # scatter plot of inliers with white dots
    b = subplot.scatter(X_train[:-n_outliers, 0], X_train[:-n_outliers, 1], c='white',s=20, edgecolor='k')
    # scatter plot of outliers with black dots
    c = subplot.scatter(X_train[-n_outliers:, 0], X_train[-n_outliers:, 1], c='black',s=20, edgecolor='k')
    subplot.axis('tight')

    subplot.legend(
        [a.collections[0], b, c],
        ['learned decision function', 'true inliers', 'true outliers'],
        prop=matplotlib.font_manager.FontProperties(size=10),
        loc='lower right')

    subplot.set_title(clf_name)
    subplot.set_xlim((-10, 10))
    subplot.set_ylim((-10, 10))
plt.savefig('fig.png')
plt.show()

No of Errors :  Angle-based Outlier Detector (ABOD) 7
No of Errors :  K Nearest Neighbors (KNN) 0
No of Errors :  Copula-Based 2

import numpy as np
from scipy import stats
import matplotlib.pyplot as plt
%matplotlib inline
import matplotlib.font_manager

from pyod.models.abod import ABOD
from pyod.models.knn import KNN
from pyod.models.copod import COPOD

from pyod.utils.data import generate_data, get_outliers_inliers

#generate random data with two features
X_train, Y_train = generate_data(n_train=200,train_only=True, n_features=2)

# by default the outlier fraction is 0.1 in generate data function
outlier_fraction = 0.1

# store outliers and inliers in different numpy arrays
x_outliers, x_inliers = get_outliers_inliers(X_train,Y_train)

n_inliers = len(x_inliers)
n_outliers = len(x_outliers)

#separate the two features and use it to plot the data
F1 = X_train[:,[0]].reshape(-1,1)
F2 = X_train[:,[1]].reshape(-1,1)
F3 = x_outliers[:, [0]].reshape(-1,1)
F4 = x_outliers[:, [1]].reshape(-1,1)

# create a meshgrid
xx , yy = np.meshgrid(np.linspace(-10, 10, 200), np.linspace(-10, 10, 200))

# scatter plot
plt.scatter(F1,F2)
#plt.scatter(F3, F4, c='r')
plt.xlabel('F1')
plt.ylabel('F2')

classifiers = {
     'Angle-based Outlier Detector (ABOD)'   : ABOD(contamination=outlier_fraction),
     'K Nearest Neighbors (KNN)' :  KNN(contamination=outlier_fraction),
     'Copula-Based' : COPOD(contamination=outlier_fraction)
}

#set the figure size
plt.figure(figsize=(10, 10))

for i, (clf_name,clf) in enumerate(classifiers.items()) :
    # fit the dataset to the model
    clf.fit(X_train)

    # predict raw anomaly score
    scores_pred = clf.decision_function(X_train)*-1

    # prediction of a datapoint category outlier or inlier
    y_pred = clf.predict(X_train)

    # no of errors in prediction
    n_errors = (y_pred != Y_train).sum()
    print('No of Errors : ',clf_name, n_errors)

    # rest of the code is to create the visualization

    # threshold value to consider a datapoint inlier or outlier
    threshold = stats.scoreatpercentile(scores_pred, 100*outlier_fraction)

    # decision function calculates the raw anomaly score for every point
    Z = clf.decision_function(np.c_[xx.ravel(), yy.ravel()]) * -1
    Z = Z.reshape(xx.shape)

    subplot = plt.subplot(1, 3, i + 1)

    # fill blue colormap from minimum anomaly score to threshold value
    subplot.contourf(xx, yy, Z, levels = np.linspace(Z.min(), threshold, 10),cmap=plt.cm.Blues_r)

    # draw red contour line where anomaly score is equal to threshold
    a = subplot.contour(xx, yy, Z, levels=[threshold],linewidths=2, colors='red')

    # fill orange contour lines where range of anomaly score is from threshold to maximum anomaly score
    subplot.contourf(xx, yy, Z, levels=[threshold, Z.max()],colors='orange')

    # scatter plot of inliers with white dots
    b = subplot.scatter(X_train[:-n_outliers, 0], X_train[:-n_outliers, 1], c='white',s=20, edgecolor='k')
    # scatter plot of outliers with black dots
    c = subplot.scatter(X_train[-n_outliers:, 0], X_train[-n_outliers:, 1], c='black',s=20, edgecolor='k')
    subplot.axis('tight')

    subplot.legend(
        [a.collections[0], b, c],
        ['learned decision function', 'true inliers', 'true outliers'],
        prop=matplotlib.font_manager.FontProperties(size=10),
        loc='lower right')

    subplot.set_title(clf_name)
    subplot.set_xlim((-10, 10))
    subplot.set_ylim((-10, 10))
plt.savefig('fig.png')
plt.show()

No of Errors :  Angle-based Outlier Detector (ABOD) 7
No of Errors :  K Nearest Neighbors (KNN) 0
No of Errors :  Copula-Based 2

I think this is expected due to the decision boundary of copod is not exactly "continuous". The number of errors look reasonable. Note this visualization is for illustrative purpose only. Some algorithms, such as abod and copod, that do not have smooth and continuous decision boundary will look strange...

Ok, thank you!


Missing Accessibility Report button with @ladle/react v3.1.0 and up

Describe the bug
For some reason I lost the accessibility report and button when upgrading ladle, I tried different versions and the last one that works for me is 3.0.0
Reproduction
I was able to reproduce with Stackblitz.
Just change the dependency to:
    "@ladle/react": "3.0.0",

to see the accessibility report button.
Environment

OS: MacOS Ventura 13.6
Browser: Firefox 118 Chrome 118
(I wasn't aware both browsers are now in matching version numbers 😅)

It's just disabled by default now. You can easily enable it again: https://ladle.dev/docs/a11y
axe-core is a pretty big dependency so we don't want to bundle it with Ladle unless it's actively used.

Thanks! I suggest to include changes in defaults in the release notes next time.


Overlong function signature

    pub unsafe fn reborrow_mut(&mut self) -> Handle<NodeRef<marker::Mut, K, V, NodeType>, HandleType> {

Another example:
    pub fn merge(mut self) -> Handle<NodeRef<marker::Mut<'a>, K, V, marker::Internal>, marker::Edge> {

How is this possible?

Since this is tagged easy, how might one go about fixing it (and https://github.com/rust-lang-nursery/rustfmt/issues/1048)?

I would start here: https://github.com/rust-lang-nursery/rustfmt/blob/master/src/items.rs#L1221 and insert a bunch of printlns (or use a debugger) to figure out the path the code is taking and the widths being passed down to the helper functions, at some point it should be clear that a helper is being asked to format into a width that is one larger than it ought to be. Whilst not being a lot of fun, this is usually quite easy to figure out. Exactly how to fix it depends on what the problem looks like. It might be as simple as adding a constant 1 to something.

Tried to reproduce it by writing a test with your first example. To make it accept the function I adapted the signature a bit. The output looks good:
pub unsafe fn reborrow_mut(&mut AAAAAAAAA: Test)                            -> Handle<NodeRef<marker::Mut, K, V, NodeType>, HandleType> { }
Am I missing something?

whoops sorry made a mistake

@juicejitsu Great! @nrc can you help @juicejitsu land this fix? Looks like they've got a patch ready to go.

@juicejitsu I had the same idea like you but there are at least two corner cases which have to be considered. Please have a look at #1089. Maybe you want to finish that PR? Sadly I have nearly no spare time right now...

@dawirstejeck Sure! Taking a look

This can be closed now, right?


Passing additional options to task command

My task definition uses FARGATE as a launch type, which I believe requires the awsvpc networking mode. That means in order to run my task, I need to be able to pass additional options to the run-task command, eg:
--network-configuration "awsvpcConfiguration={assignPublicIp=ENABLED,subnets=[subnet-aaa],securityGroups=[sg-bbb]}"
Would you accept a pull request for this, and if so, would you want additional options to run-task simply appended to the ufo run task command like the cluster option is?

OK cool, yeah I couldn't use ufo to create the Fargate services either for the same reason. You can add these options to your task definition template to test:
"requiresCompatibilities": ["FARGATE"], "networkMode": "awsvpc", "executionRoleArn": "<%= @execution_role_arn %>",
I think I should have some time this weekend to play around with it.

@lostinpatterns Added fargate support with #31.  Ending up introducing a new conceptual file called .ufo/params.yml.  The file .ufo/params.yml allows you to adjust the parameters that get sent to the aws-sdk run_task method.  This allows support for Fargate and any other thing that the aws-sdk might add in the future. More info here: Ufo Params Docs
Also provided a ufo upgrade3_3_to_3_4 command that creates the starter .ufo/params.yml. Run and follow instructions if you're already on version 3.3:
ufo upgrade3_3_to_3_4

It's pretty awesome to be able to run an one off task and only pay for that task with fargate.
Closing this out.

Sorry for the really slow turnaround - got pulled on to something else so had to step away from the project I was working on that was using ufo. I just upgraded ufo in that project, set up my params file, and ran a one-off task for it on Fargate. Worked great, thank you!


[SMALLFIX] Removed explicit type arguments in AllocatorContractTest

Removed some explicit type parameters in the AllocatorContractTest class.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/9932/
Test PASSed.

LGTM. Thanks.


add progress reporting for restic backups & restores

xref #20 #21
Describe the problem/challenge you have
During long-running restic backups/restores, there is no visibility into what (if anything) is happening, making it hard to know if the backup/restore is making progress or hung, how long the operation might take, etc.
Describe the solution you'd like
We should capture progress during restic operations and make it user-visible somewhere (could be in a status field on the PVB/PVR, or in an Event, or somewhere else - TBD).
restic backup provides progress reporting to stdout. @jmontleon did a POC of capturing this periodically and writing it to the PVB's status (see this comment).
restic restore does not yet have such progress reporting; however, the restic ls SNAPSHOT_ID command will give a listing of all files in a backup, and we could potentially use that along with periodic listing of files in the directory being restored to provide something useful to the user.
This definitely needs some experimentation and design work, but IMHO we need to do this before declaring restic GA, as it's just too hard to know what's going on right now.
@prydonius if you're looking for something to do next week, some R&D here would definitely be useful!

restic backup provides progress reporting to stdout. @jmontleon did a POC of capturing this periodically and writing it to the PVB's status (see this comment).

FYI took me a while to figure out that the JSON output for restic backup requires 0.9.5, our current images shit 0.9.4, so we'll need to update that.

Closed by #1821 and #1854


Build Incompatibility with Python 3.12

Describe the bug
Python 3.12 has removed the 'imp' module:
https://github.com/python/cpython/issues/98040
This is blocking my ability to build BSK using the venv.
To reproduce
Build basic setup provided in Docs for MacOS:
https://hanspeterschaub.info/basilisk/Install/installOnMacOS.html

$ xcode-select --install

$ brew install swig

$ brew install cmake

$ brew link cmake

DOWNLOAD LATEST Python version, Python 3.12

$ python3 -m venv .venv

(.venv) $ pip3 install wheel

(.venv) $ pip3 install -v "conan==1.61.0"

$ python3 conanfile.py

error:

According to Python 3.12 docs, 'imp' module has been replaced.
https://github.com/python/cpython/issues/98040
Expected behavior
Fully build sim
Resolved this locally by removing Python 3.12.0 and downloading Python 3.11.6 (Note: operating with only 1 python version at all times)
Desktop (please complete the following information):

OS: [Macos]
Version [Ventura 13.5]
Python version [3.12.0]

Additional context
Add any other context about the problem or potential solution paths here.
This was resolved locally by using Python 3.11.6

Have you tried updating to the latest conan?
https://github.com/conan-io/conan/pull/14841
https://docs.conan.io/1/changelog.html#nov-2023

I used conan v1.XX as that was labeled as necessary in the build instructions; I'll refactor that and get python 3.12 stood up
It seems the issue I am running into was covered in the bug fix you provided, thanks!


What's the best way to write unit tests for Web API controllers that use Saule?

I'm working on a backend Web API for an Ember app to consume. I'm wondering what the best way is to test my API endpoints before I hand them over to my front end teammates. Thanks!

We have some tests in Saule's test suite that fire a request at the server and check the response. Maybe those can be of help to you?
If you don't care so much about the exact JSON that's returned, you can just unit test your controller as you always would, and check the resulting object rather than JSON response.

Thanks for the feedback. I'm hoping to unit test (in .NET) my controller methods and validate the output JSON format. Is that possible?

@bxh It depends on what you call a unit test. The tests I linked should work for you, but they're not typically referred to as 'unit test', since they call into the API from the outside, seeing only what your Ember app would see. If that's what you want, then that's what I recommend.

I'm closing this issue. Feel free to re-open if your question was not answered.


Add method to format message to LogRecord.

Add method to format message to LogRecord.

Change rolled back.


Add instructions to readme on how to add new schemes

It would be helpful for future researchers who want to use our extension to know how they can create their own schemes. I imagine like a list with a few bullet points fairly abstract. Just which files they would need to work on. This could be a subsection of the scheme section after scheme 7.

I've started working on this. It's still incomplete and messy, but it's a good start. I'll continue developing it when I can, but for now it isn't a priority.

@ekuller, is it clear to you per the readme how one could add new schemes? Is there anything that would need to be added?

In general, this looks good to me. @ekuller will take a brief look and make additions or changes. Then, we can close this issue.

@ekuller, take a look, and then we can close this issue.


Added cmake file to be able to compile PHP-CPP under Windows

Should help issues: #337, #314, #57

good job


Shipping is shown as "free" on cart

For details & screenshot please see https://jira.hybris.com/browse/SPA-1423
Priority: Medium
Environment Details
recipe : b2c_acc_oms
using spartacus storefront
platform commerce-suite-1811.0.26891
Expected Results
Estimated shipping should be 9.99$
Observed Results
Notice how the 9.99$ is included in the subtotal but shown as "Free" in estimated shipping.
Steps to Reproduce

Log in as an user
Place an order while selecting "Standard delivery" for 9.99$
Submit the order

We don't have any way of estimating shipping yet, so cart should show TBD until we update this.

PR #1714

I smoke tested and the third requirement does not behave as expected:

if user changes shipping destination, the shipping should go back to TBD, the shipping method is cleared, and the user has to choose a shipping method again.

The shipping method isn't cleared when I change the shipping address.  Suggestion to make to make the logic simpler: each time we select an address, we could clear the shipping method.  Does this make sense?
Also, I think this requirement:

in checkout: the subtotal should show TBD until the user chooses a shipping destination, then the amount should change.

Small thing, but I think the second requirement was about selecting the shipping method, and not the shipping destination (I guess this was the intent):

in checkout: the subtotal should show TBD until the user chooses a shipping destination, then the amount should change.

Requirements above cleared up.  They are updated in Xymmer's comment.  A followup spike is created to investigate the third requirement.
The second requirement is also cleared up.

Just wait for a green e2e build before merge.

Tested on dev22.
It's now TBD until the user chooses the shipping method.

Shipping amount is changed when user changes shipping method.

Only thing that doesn't work and that's already pointed out with ticket GH-1743 is when we change the shipping address. Looks like it's reflected in the order summary but not in the shipping methods options.


Test the faiss-example, why the answer rocketqa gived is the whole paragraph, not the short answer!

I tested the faiss-example, why the answer rocketqa gived was the whole paragraph, not the short answer. Is there something need to set? Compare with the following picture, it seems to be no part of extracting the short answer.

Sorry to mislead you, this picture shows the whole process of QA system: Retrieval, Rerank and Extract. RocketQA now released the first 2 steps, retriever and reranker, so the examples only return the whole paragraph.  We will release the answer extractor model soon.


2021 m1 macbooks with notch support

Any ideas for how to support notched displays?
The process widget is unusable because it gets totally obscured by the notch on my new m1 macbook
Having the process and other data widgets anchored to the center notch and expanding out leftward and rightward could be a clean look

Indeed! For now the only solution preventing this issue is to set simple-bar position to bottom screen. I'll look into a proper way for handling this but I like what you are suggesting. :)

@yorhodes can you show the current simple-bar on new macbook with notch look like?
i am very curious 😂

is there any progress on this topic? Im going crazy without the bar.

@yorhodes can you show the current simple-bar on new macbook with notch look like?
i am very curious 😂

I indeed need to get this done, I'll keep you updated :)

Second this. Or is there a quick patch we can manually apply so as to make the process section align immediately after the space section? Thanks.

Second this. Or is there a quick patch we can manually apply so as to make the process section align immediately after the space section? Thanks.

Agreed, a process section aligned left would be fine for me. The right side is full of crypto tickers anyway.

I added this option in settings:

Let me know if this is better now. :)

I added this option in settings:
Let me know if this is better now. :)
Edit: You'll need to restart Übersicht as I merged both widgets into one (data + spaces = index).

Works great, thanks!!
One minor issue, looks like the rectangles are taller now and the top pixel or two is getting cut off.

I'm closing this issue as the main topic has been resolved, feel free to open a new one if anything else is needed.