[BUG] Tests fail on WaitForURLAsync() when run in headless mode but work without it

Hi
I have these test (that you can just try out) that fail on the following line if run with headless == true but else they just run fine.
  await Page.WaitForURLAsync("https://eventstreamingpublicwebdev.azurewebsites.net/");
where I get

waiting for navigation to "https://eventstreamingpublicwebdev.azurewebsites.net/" until "Load"

I have tried searching for a reason but just can´t see what I´m doing wrong. But bear with me since this is only day two of me trying to use Playwright.
But you should be able to try this out and see the test fail by running the code either in Visual Studio Test Explorer or with dotnet test --settings:.runsettings
using Microsoft.Playwright;
using Microsoft.Playwright.NUnit;

namespace My.PlaywrightTests
{
    public class FrontPagelogin : PageTest
    {
        [SetUp]
        public async Task Setup()
        {
            await Page.GotoAsync(url: "https://eventstreamingpublicwebdev.azurewebsites.net/");
        }

        [Test]
        public async Task This_works_when_headless_is_false()
        {
            // If I start tracing this works
            await Page.Context.Tracing.StartAsync(new()
            {
                Screenshots = false,
                Snapshots = true, //<-- This makes the test succeeed in the least time
                Sources = false
            });

            await Page.GotoAsync("https://eventstreamingpublicwebdev.azurewebsites.net/LoginSelector");
            await Page.Locator("a[role=\"button\"]:has-text(\"Innskráning áhorfanda\")").ClickAsync();

            var loginPage = new LoginPage(Page);
            await loginPage.Login("playwrightppv", "1q2w3E*");

            await Page.WaitForURLAsync("https://eventstreamingpublicwebdev.azurewebsites.net/");

            // Stop tracing and export it into a zip archive.
            await Page.Context.Tracing.StopAsync(new()
            {
                Path = "trace.zip"
            });

            await Expect(Page.Locator("#dropdownMenuUser img")).ToBeVisibleAsync();
        }

        [Test]
        public async Task Doesnt_work_when_headless_is_false()
        {
            await Page.GotoAsync("https://eventstreamingpublicwebdev.azurewebsites.net/LoginSelector");
            await Page.Locator("a[role=\"button\"]:has-text(\"Innskráning áhorfanda\")").ClickAsync();

            var loginPage = new LoginPage(Page);
            await loginPage.Login("playwrightppv", "1q2w3E*");

            // fails here!
            await Page.WaitForURLAsync("https://eventstreamingpublicwebdev.azurewebsites.net/");

            await Expect(Page.Locator("#dropdownMenuUser img")).ToBeVisibleAsync();
        }
    }

  // Here are my first abstraction classes for my pages since I want to be able to reuse the login logic.

    public class MyLoginPage : MyBasePage
    {
        public MyLoginPage(IPage page) : base(page) { }
        public async Task Login(string userName, string pasword)
        {
            await Page.Locator("input[name=\"LoginInput\\.UserNameOrEmailAddress\"]").ClickAsync();
            await Page.Locator("input[name=\"LoginInput\\.UserNameOrEmailAddress\"]").FillAsync(userName);

            await Page.Locator("input[name=\"LoginInput\\.Password\"]").ClickAsync();
            await Page.Locator("input[name=\"LoginInput\\.Password\"]").FillAsync(pasword);
            await Page.Locator("id=termsandcondition").CheckAsync();

            await Page.Locator("#loginsubmitbtn").ClickAsync();
        }
    }

    public class MyBasePage
    {
        public IPage Page;

        public MyBasePage(IPage page) => this.Page = page;
    }
}

my .runsettings file
<?xml version="1.0" encoding="utf-8"?>
<RunSettings>
	<Playwright>
		<BrowserName>chromium</BrowserName>
		<LaunchOptions>
			<Headless>true</Headless>
			<Channel>msedge</Channel>
		</LaunchOptions>
	</Playwright>
</RunSettings>

my test project file
<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <TargetFramework>net6.0</TargetFramework>
    <ImplicitUsings>enable</ImplicitUsings>
    <Nullable>enable</Nullable>
    <IsPackable>false</IsPackable>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="Microsoft.NET.Test.Sdk" Version="17.3.1" />
    <PackageReference Include="Microsoft.Playwright" Version="1.25.0" />
    <PackageReference Include="Microsoft.Playwright.NUnit" Version="1.25.0" />
    <PackageReference Include="NUnit" Version="3.13.3" />
    <PackageReference Include="NUnit3TestAdapter" Version="4.2.1" />
    <PackageReference Include="NUnit.Analyzers" Version="3.3.0" />
    <PackageReference Include="coverlet.collector" Version="3.1.2" />
  </ItemGroup>
</Project>

Context:

Playwright Version: 1.25.0 and same NUnit version
Operating System: Windows
Node.js version: v12.16.2
Browser: Chromium
Extra: Microsoft Visual Studio Enterprise 2022 (64-bit) - Preview
Version 17.4.0 Preview 2.0

I tried to reproduce it, but for me it's unfortunately passing. Could you try setting the DEBUG=pw:api env? This should give a hint what's going wrong.

Sometimes some tests run fine the first time but not after that. Can you run it again?
But yes I had tried with debug and only see that it times out. Maybe you can spot something?
C:\Dev\IBeinni\aspnet-core\test\BSR.Beinni.Playwright.Tests> dotnet test --settings:.runsettings
  Determining projects to restore...
  All projects are up-to-date for restore.
  BSR.Beinni.PlaywrightTests -> C:\Dev\IBeinni\aspnet-core\test\BSR.Beinni.Playwright.Tests\bin\Debug\net6.0\BSR.Beinni
  .PlaywrightTests.dll
Test run for C:\Dev\IBeinni\aspnet-core\test\BSR.Beinni.Playwright.Tests\bin\Debug\net6.0\BSR.Beinni.PlaywrightTests.dll (.NETCoreApp,Version=v6.0)
Microsoft (R) Test Execution Command Line Tool Version 17.3.0 (x64)
Copyright (c) Microsoft Corporation.  All rights reserved.

Starting test execution, please wait...
A total of 1 test files matched the specified pattern.
2022-09-19T20:53:41.978Z pw:api navigating to "https://eventstreamingpublicwebdev.azurewebsites.net/", waiting until "load"
2022-09-19T20:53:42.570Z pw:api   "commit" event fired
2022-09-19T20:53:42.570Z pw:api   navigated to "https://eventstreamingpublicwebdev.azurewebsites.net/LandingPage"
2022-09-19T20:53:43.310Z pw:api   "domcontentloaded" event fired
2022-09-19T20:53:43.361Z pw:api   "load" event fired
2022-09-19T20:53:43.368Z pw:api navigating to "https://eventstreamingpublicwebdev.azurewebsites.net/LoginSelector", waiting until "load"
2022-09-19T20:53:43.891Z pw:api   "commit" event fired
2022-09-19T20:53:43.891Z pw:api   navigated to "https://eventstreamingpublicwebdev.azurewebsites.net/LoginSelector"
2022-09-19T20:53:44.996Z pw:api   "load" event fired
2022-09-19T20:53:44.996Z pw:api   "domcontentloaded" event fired
2022-09-19T20:53:45.004Z pw:api waiting for selector "a[role="button"]:has-text("Innskr├íning ├íhorfanda")"
2022-09-19T20:53:45.023Z pw:api   selector resolved to visible ÔÇª
2022-09-19T20:53:45.027Z pw:api attempting click action
2022-09-19T20:53:45.027Z pw:api   waiting for element to be visible, enabled and stable
2022-09-19T20:53:45.043Z pw:api   element is visible, enabled and stable
2022-09-19T20:53:45.043Z pw:api   scrolling into view if needed
2022-09-19T20:53:45.046Z pw:api   done scrolling
2022-09-19T20:53:45.048Z pw:api   performing click action
2022-09-19T20:53:45.865Z pw:api   click action done
2022-09-19T20:53:45.865Z pw:api   waiting for scheduled navigations to finish
2022-09-19T20:53:45.865Z pw:api   "commit" event fired
2022-09-19T20:53:45.866Z pw:api   navigated to "https://streamworksidentitydev.azurewebsites.net/Account/Login?ReturnUrl=%2Fconnect%2Fauthorize%2Fcallback%3Fclient_id%3DBeinni_Web_Public%26redirect_uri%3Dhttps%253A%252F%252Feventstreamingpublicwebdev.azurewebsites.net%252Fsignin-oidc%26response_type%3Dcode%2520id_token%26scope%3Dopenid%2520profile%2520role%2520email%2520phone%2520Beinni%26response_mode%3Dform_post%26nonce%3D637992176252883502.OTdmZmU1MzQtNTZiZi00ZDZhLWJlNmUtYzFlMjM3YTA4NGQ5MzE1MjdlY2YtNGUwNi00MTliLWE1MTUtMmY2MGRmZmVmNzll%26state%3DCfDJ8Nz0aZ4MpSdEq6-Csy0Lf5XVHw1g4LRIy4pYVUJmazZoIhKB9CFiKIhAbJB7aqURO6rY8uxyILAAk-VKxHh9OAHxig7aLpRnsMIF2REeojjs_wofBWA7WMN-Uwt_h7-VGV09rD170A4ehB6B6heAtzc_rQ_EOFg2rFlUcrYhlBBUvTyonuEQDWqOAEHgoeoUOyPupjQomMW60mOMBiOAZ8a-c96IVK8JG-yrFJnaDOmGG1-dvkO-l7lx_71GZ3318QW35bVGzpBIWeyhOGkCxTV6S-z_QjpOm6Y-j5ny1ldfPfMT-579yTQ64fZ-VGT-zKpXxcRvcpFzNhq-6UG3g0c%26x-client-SKU%3DID_NETSTANDARD2_0%26x-client-ver%3D<IP_ADDRESS>"
2022-09-19T20:53:45.866Z pw:api   navigated to "https://streamworksidentitydev.azurewebsites.net/Account/Login?ReturnUrl=%2Fconnect%2Fauthorize%2Fcallback%3Fclient_id%3DBeinni_Web_Public%26redirect_uri%3Dhttps%253A%252F%252Feventstreamingpublicwebdev.azurewebsites.net%252Fsignin-oidc%26response_type%3Dcode%2520id_token%26scope%3Dopenid%2520profile%2520role%2520email%2520phone%2520Beinni%26response_mode%3Dform_post%26nonce%3D637992176252883502.OTdmZmU1MzQtNTZiZi00ZDZhLWJlNmUtYzFlMjM3YTA4NGQ5MzE1MjdlY2YtNGUwNi00MTliLWE1MTUtMmY2MGRmZmVmNzll%26state%3DCfDJ8Nz0aZ4MpSdEq6-Csy0Lf5XVHw1g4LRIy4pYVUJmazZoIhKB9CFiKIhAbJB7aqURO6rY8uxyILAAk-VKxHh9OAHxig7aLpRnsMIF2REeojjs_wofBWA7WMN-Uwt_h7-VGV09rD170A4ehB6B6heAtzc_rQ_EOFg2rFlUcrYhlBBUvTyonuEQDWqOAEHgoeoUOyPupjQomMW60mOMBiOAZ8a-c96IVK8JG-yrFJnaDOmGG1-dvkO-l7lx_71GZ3318QW35bVGzpBIWeyhOGkCxTV6S-z_QjpOm6Y-j5ny1ldfPfMT-579yTQ64fZ-VGT-zKpXxcRvcpFzNhq-6UG3g0c%26x-client-SKU%3DID_NETSTANDARD2_0%26x-client-ver%3D<IP_ADDRESS>"
2022-09-19T20:53:45.869Z pw:api   navigations have finished
2022-09-19T20:53:45.872Z pw:api waiting for selector "input[name="LoginInput\.UserNameOrEmailAddress"]"
2022-09-19T20:53:45.892Z pw:api   selector resolved to visible <input value="" type="text" data-val="true" maxlength="ÔÇª/>
2022-09-19T20:53:45.894Z pw:api attempting click action
2022-09-19T20:53:45.894Z pw:api   waiting for element to be visible, enabled and stable
2022-09-19T20:53:46.291Z pw:api   element is visible, enabled and stable
2022-09-19T20:53:46.292Z pw:api   scrolling into view if needed
2022-09-19T20:53:46.292Z pw:api   done scrolling
2022-09-19T20:53:46.296Z pw:api   performing click action
2022-09-19T20:53:46.301Z pw:api   click action done
2022-09-19T20:53:46.301Z pw:api   waiting for scheduled navigations to finish
2022-09-19T20:53:46.303Z pw:api   navigations have finished
2022-09-19T20:53:46.306Z pw:api waiting for selector "input[name="LoginInput\.UserNameOrEmailAddress"]"
2022-09-19T20:53:46.313Z pw:api   selector resolved to visible <input value="" type="text" data-val="true" maxlength="ÔÇª/>
2022-09-19T20:53:46.315Z pw:api elementHandle.fill("playwrightppv")
2022-09-19T20:53:46.315Z pw:api   waiting for element to be visible, enabled and editable
2022-09-19T20:53:46.320Z pw:api   element is visible, enabled and editable
2022-09-19T20:53:46.324Z pw:api waiting for selector "input[name="LoginInput\.Password"]"
2022-09-19T20:53:46.329Z pw:api   selector resolved to visible <input type="password" data-val="true" maxlength="128" ÔÇª/>
2022-09-19T20:53:46.331Z pw:api attempting click action
2022-09-19T20:53:46.331Z pw:api   waiting for element to be visible, enabled and stable
2022-09-19T20:53:46.361Z pw:api   element is visible, enabled and stable
2022-09-19T20:53:46.361Z pw:api   scrolling into view if needed
2022-09-19T20:53:46.361Z pw:api   done scrolling
2022-09-19T20:53:46.364Z pw:api   performing click action
2022-09-19T20:53:46.368Z pw:api   click action done
2022-09-19T20:53:46.368Z pw:api   waiting for scheduled navigations to finish
2022-09-19T20:53:46.369Z pw:api   navigations have finished
2022-09-19T20:53:46.370Z pw:api waiting for selector "input[name="LoginInput\.Password"]"
2022-09-19T20:53:46.372Z pw:api   selector resolved to visible <input type="password" data-val="true" maxlength="128" ÔÇª/>
2022-09-19T20:53:46.374Z pw:api elementHandle.fill("1q2w3E*")
2022-09-19T20:53:46.374Z pw:api   waiting for element to be visible, enabled and editable
2022-09-19T20:53:46.377Z pw:api   element is visible, enabled and editable
2022-09-19T20:53:46.382Z pw:api waiting for selector "id=termsandcondition"
2022-09-19T20:53:46.385Z pw:api   selector resolved to visible <input value="true" type="checkbox" data-val="true" id=ÔÇª/>
2022-09-19T20:53:46.388Z pw:api attempting click action
2022-09-19T20:53:46.388Z pw:api   waiting for element to be visible, enabled and stable
2022-09-19T20:53:46.409Z pw:api   element is visible, enabled and stable
2022-09-19T20:53:46.409Z pw:api   scrolling into view if needed
2022-09-19T20:53:46.410Z pw:api   done scrolling
2022-09-19T20:53:46.412Z pw:api   performing click action
2022-09-19T20:53:46.417Z pw:api   click action done
2022-09-19T20:53:46.417Z pw:api   waiting for scheduled navigations to finish
2022-09-19T20:53:46.417Z pw:api   navigations have finished
2022-09-19T20:53:46.419Z pw:api waiting for selector "#loginsubmitbtn"
2022-09-19T20:53:46.421Z pw:api   selector resolved to visible <button type="button" name="Action" value="Login" id="loÔÇª>Innskr├í</button>
2022-09-19T20:53:46.422Z pw:api attempting click action
2022-09-19T20:53:46.422Z pw:api   waiting for element to be visible, enabled and stable
2022-09-19T20:53:46.443Z pw:api   element is visible, enabled and stable
2022-09-19T20:53:46.443Z pw:api   scrolling into view if needed
2022-09-19T20:53:46.443Z pw:api   done scrolling
2022-09-19T20:53:46.446Z pw:api   performing click action
2022-09-19T20:53:46.451Z pw:api   click action done
2022-09-19T20:53:46.451Z pw:api   waiting for scheduled navigations to finish
2022-09-19T20:53:46.452Z pw:api   navigations have finished
2022-09-19T20:53:46.473Z pw:api waiting for navigation to "https://eventstreamingpublicwebdev.azurewebsites.net/" until "Load"
2022-09-19T20:53:46.986Z pw:api   "load" event fired
2022-09-19T20:53:46.986Z pw:api   "domcontentloaded" event fired
2022-09-19T20:53:47.494Z pw:api   "networkidle" event fired
  Failed Bought_Events_Page_ [35 s]
  Error Message:
   System.TimeoutException : Timeout 30000ms exceeded.
=========================== logs ===========================
waiting for navigation to "https://eventstreamingpublicwebdev.azurewebsites.net/" until "Load"
============================================================
  ----> System.TimeoutException : Timeout 30000ms exceeded.
  Stack Trace:
     at Microsoft.Playwright.Core.Waiter.WaitForPromiseAsync[T](Task`1 task, Action dispose) in /_/src/Playwright/Core/Waiter.cs:line 179
   at Microsoft.Playwright.Core.Frame.WaitForNavigationAsync(FrameWaitForNavigationOptions options) in /_/src/Playwright/Core/Frame.cs:line 226
   at BSR.Beinni.PlaywrightTests.FrontPagelogin.Bought_Events_Page_() in C:\Dev\IBeinni\aspnet-core\test\BSR.Beinni.Playwright.Tests\LoginTests\Frontpagelogin.cs:line 100
   at NUnit.Framework.Internal.TaskAwaitAdapter.GenericAdapter`1.BlockUntilCompleted()
   at NUnit.Framework.Internal.MessagePumpStrategy.NoMessagePumpStrategy.WaitForCompletion(AwaitAdapter awaiter)
   at NUnit.Framework.Internal.AsyncToSyncAdapter.Await(Func`1 invoke)
   at NUnit.Framework.Internal.Commands.TestMethodCommand.RunTestMethod(TestExecutionContext context)
   at NUnit.Framework.Internal.Commands.TestMethodCommand.Execute(TestExecutionContext context)
   at NUnit.Framework.Internal.Commands.BeforeAndAfterTestCommand.<>c__DisplayClass1_0.<Execute>b__0()
   at NUnit.Framework.Internal.Commands.DelegatingTestCommand.RunTestMethodInThreadAbortSafeZone(TestExecutionContext context, Action action)
--TimeoutException
   at Microsoft.Playwright.Helpers.TaskHelper.<>c__DisplayClass2_0.<WithTimeout>b__0() in /_/src/Playwright/Helpers/TaskHelper.cs:line 73
   at Microsoft.Playwright.Helpers.TaskHelper.WithTimeout(Task task, Func`1 timeoutAction, TimeSpan timeout, CancellationToken cancellationToken) in /_/src/Playwright/Helpers/TaskHelper.cs:line 109
   at Microsoft.Playwright.Core.Waiter.WaitForPromiseAsync[T](Task`1 task, Action dispose) in /_/src/Playwright/Core/Waiter.cs:line 171
  Standard Error Messages:
 2022-09-19T20:53:41.978Z pw:api navigating to "https://eventstreamingpublicwebdev.azurewebsites.net/", waiting until "load"
 2022-09-19T20:53:42.570Z pw:api   "commit" event fired
 2022-09-19T20:53:42.570Z pw:api   navigated to "https://eventstreamingpublicwebdev.azurewebsites.net/LandingPage"
 2022-09-19T20:53:43.310Z pw:api   "domcontentloaded" event fired
 2022-09-19T20:53:43.361Z pw:api   "load" event fired
 2022-09-19T20:53:43.368Z pw:api navigating to "https://eventstreamingpublicwebdev.azurewebsites.net/LoginSelector", waiting until "load"
 2022-09-19T20:53:43.891Z pw:api   "commit" event fired
 2022-09-19T20:53:43.891Z pw:api   navigated to "https://eventstreamingpublicwebdev.azurewebsites.net/LoginSelector"
 2022-09-19T20:53:44.996Z pw:api   "load" event fired
 2022-09-19T20:53:44.996Z pw:api   "domcontentloaded" event fired
 2022-09-19T20:53:45.004Z pw:api waiting for selector "a[role="button"]:has-text("Innskr├íning ├íhorfanda")"
 2022-09-19T20:53:45.023Z pw:api   selector resolved to visible ÔÇª
 2022-09-19T20:53:45.027Z pw:api attempting click action
 2022-09-19T20:53:45.027Z pw:api   waiting for element to be visible, enabled and stable
 2022-09-19T20:53:45.043Z pw:api   element is visible, enabled and stable
 2022-09-19T20:53:45.043Z pw:api   scrolling into view if needed
 2022-09-19T20:53:45.046Z pw:api   done scrolling
 2022-09-19T20:53:45.048Z pw:api   performing click action
 2022-09-19T20:53:45.865Z pw:api   click action done
 2022-09-19T20:53:45.865Z pw:api   waiting for scheduled navigations to finish
 2022-09-19T20:53:45.865Z pw:api   "commit" event fired
 2022-09-19T20:53:45.866Z pw:api   navigated to "https://streamworksidentitydev.azurewebsites.net/Account/Login?ReturnUrl=%2Fconnect%2Fauthorize%2Fcallback%3Fclient_id%3DBeinni_Web_Public%26redirect_uri%3Dhttps%253A%252F%252Feventstreamingpublicwebdev.azurewebsites.net%252Fsignin-oidc%26response_type%3Dcode%2520id_token%26scope%3Dopenid%2520profile%2520role%2520email%2520phone%2520Beinni%26response_mode%3Dform_post%26nonce%3D637992176252883502.OTdmZmU1MzQtNTZiZi00ZDZhLWJlNmUtYzFlMjM3YTA4NGQ5MzE1MjdlY2YtNGUwNi00MTliLWE1MTUtMmY2MGRmZmVmNzll%26state%3DCfDJ8Nz0aZ4MpSdEq6-Csy0Lf5XVHw1g4LRIy4pYVUJmazZoIhKB9CFiKIhAbJB7aqURO6rY8uxyILAAk-VKxHh9OAHxig7aLpRnsMIF2REeojjs_wofBWA7WMN-Uwt_h7-VGV09rD170A4ehB6B6heAtzc_rQ_EOFg2rFlUcrYhlBBUvTyonuEQDWqOAEHgoeoUOyPupjQomMW60mOMBiOAZ8a-c96IVK8JG-yrFJnaDOmGG1-dvkO-l7lx_71GZ3318QW35bVGzpBIWeyhOGkCxTV6S-z_QjpOm6Y-j5ny1ldfPfMT-579yTQ64fZ-VGT-zKpXxcRvcpFzNhq-6UG3g0c%26x-client-SKU%3DID_NETSTANDARD2_0%26x-client-ver%3D<IP_ADDRESS>"
 2022-09-19T20:53:45.866Z pw:api   navigated to "https://streamworksidentitydev.azurewebsites.net/Account/Login?ReturnUrl=%2Fconnect%2Fauthorize%2Fcallback%3Fclient_id%3DBeinni_Web_Public%26redirect_uri%3Dhttps%253A%252F%252Feventstreamingpublicwebdev.azurewebsites.net%252Fsignin-oidc%26response_type%3Dcode%2520id_token%26scope%3Dopenid%2520profile%2520role%2520email%2520phone%2520Beinni%26response_mode%3Dform_post%26nonce%3D637992176252883502.OTdmZmU1MzQtNTZiZi00ZDZhLWJlNmUtYzFlMjM3YTA4NGQ5MzE1MjdlY2YtNGUwNi00MTliLWE1MTUtMmY2MGRmZmVmNzll%26state%3DCfDJ8Nz0aZ4MpSdEq6-Csy0Lf5XVHw1g4LRIy4pYVUJmazZoIhKB9CFiKIhAbJB7aqURO6rY8uxyILAAk-VKxHh9OAHxig7aLpRnsMIF2REeojjs_wofBWA7WMN-Uwt_h7-VGV09rD170A4ehB6B6heAtzc_rQ_EOFg2rFlUcrYhlBBUvTyonuEQDWqOAEHgoeoUOyPupjQomMW60mOMBiOAZ8a-c96IVK8JG-yrFJnaDOmGG1-dvkO-l7lx_71GZ3318QW35bVGzpBIWeyhOGkCxTV6S-z_QjpOm6Y-j5ny1ldfPfMT-579yTQ64fZ-VGT-zKpXxcRvcpFzNhq-6UG3g0c%26x-client-SKU%3DID_NETSTANDARD2_0%26x-client-ver%3D<IP_ADDRESS>"
 2022-09-19T20:53:45.869Z pw:api   navigations have finished
 2022-09-19T20:53:45.872Z pw:api waiting for selector "input[name="LoginInput\.UserNameOrEmailAddress"]"
 2022-09-19T20:53:45.892Z pw:api   selector resolved to visible <input value="" type="text" data-val="true" maxlength="ÔÇª/>
 2022-09-19T20:53:45.894Z pw:api attempting click action
 2022-09-19T20:53:45.894Z pw:api   waiting for element to be visible, enabled and stable
 2022-09-19T20:53:46.291Z pw:api   element is visible, enabled and stable
 2022-09-19T20:53:46.292Z pw:api   scrolling into view if needed
 2022-09-19T20:53:46.292Z pw:api   done scrolling
 2022-09-19T20:53:46.296Z pw:api   performing click action
 2022-09-19T20:53:46.301Z pw:api   click action done
 2022-09-19T20:53:46.301Z pw:api   waiting for scheduled navigations to finish
 2022-09-19T20:53:46.303Z pw:api   navigations have finished
 2022-09-19T20:53:46.306Z pw:api waiting for selector "input[name="LoginInput\.UserNameOrEmailAddress"]"
 2022-09-19T20:53:46.313Z pw:api   selector resolved to visible <input value="" type="text" data-val="true" maxlength="ÔÇª/>
 2022-09-19T20:53:46.315Z pw:api elementHandle.fill("playwrightppv")
 2022-09-19T20:53:46.315Z pw:api   waiting for element to be visible, enabled and editable
 2022-09-19T20:53:46.320Z pw:api   element is visible, enabled and editable
 2022-09-19T20:53:46.324Z pw:api waiting for selector "input[name="LoginInput\.Password"]"
 2022-09-19T20:53:46.329Z pw:api   selector resolved to visible <input type="password" data-val="true" maxlength="128" ÔÇª/>
 2022-09-19T20:53:46.331Z pw:api attempting click action
 2022-09-19T20:53:46.331Z pw:api   waiting for element to be visible, enabled and stable
 2022-09-19T20:53:46.361Z pw:api   element is visible, enabled and stable
 2022-09-19T20:53:46.361Z pw:api   scrolling into view if needed
 2022-09-19T20:53:46.361Z pw:api   done scrolling
 2022-09-19T20:53:46.364Z pw:api   performing click action
 2022-09-19T20:53:46.368Z pw:api   click action done
 2022-09-19T20:53:46.368Z pw:api   waiting for scheduled navigations to finish
 2022-09-19T20:53:46.369Z pw:api   navigations have finished
 2022-09-19T20:53:46.370Z pw:api waiting for selector "input[name="LoginInput\.Password"]"
 2022-09-19T20:53:46.372Z pw:api   selector resolved to visible <input type="password" data-val="true" maxlength="128" ÔÇª/>
 2022-09-19T20:53:46.374Z pw:api elementHandle.fill("1q2w3E*")
 2022-09-19T20:53:46.374Z pw:api   waiting for element to be visible, enabled and editable
 2022-09-19T20:53:46.377Z pw:api   element is visible, enabled and editable
 2022-09-19T20:53:46.382Z pw:api waiting for selector "id=termsandcondition"
 2022-09-19T20:53:46.385Z pw:api   selector resolved to visible <input value="true" type="checkbox" data-val="true" id=ÔÇª/>
 2022-09-19T20:53:46.388Z pw:api attempting click action
 2022-09-19T20:53:46.388Z pw:api   waiting for element to be visible, enabled and stable
 2022-09-19T20:53:46.409Z pw:api   element is visible, enabled and stable
 2022-09-19T20:53:46.409Z pw:api   scrolling into view if needed
 2022-09-19T20:53:46.410Z pw:api   done scrolling
 2022-09-19T20:53:46.412Z pw:api   performing click action
 2022-09-19T20:53:46.417Z pw:api   click action done
 2022-09-19T20:53:46.417Z pw:api   waiting for scheduled navigations to finish
 2022-09-19T20:53:46.417Z pw:api   navigations have finished
 2022-09-19T20:53:46.419Z pw:api waiting for selector "#loginsubmitbtn"
 2022-09-19T20:53:46.421Z pw:api   selector resolved to visible <button type="button" name="Action" value="Login" id="loÔÇª>Innskr├í</button>
 2022-09-19T20:53:46.422Z pw:api attempting click action
 2022-09-19T20:53:46.422Z pw:api   waiting for element to be visible, enabled and stable
 2022-09-19T20:53:46.443Z pw:api   element is visible, enabled and stable
 2022-09-19T20:53:46.443Z pw:api   scrolling into view if needed
 2022-09-19T20:53:46.443Z pw:api   done scrolling
 2022-09-19T20:53:46.446Z pw:api   performing click action
 2022-09-19T20:53:46.451Z pw:api   click action done
 2022-09-19T20:53:46.451Z pw:api   waiting for scheduled navigations to finish
 2022-09-19T20:53:46.452Z pw:api   navigations have finished
 2022-09-19T20:53:46.473Z pw:api waiting for navigation to "https://eventstreamingpublicwebdev.azurewebsites.net/" until "Load"
 2022-09-19T20:53:46.986Z pw:api   "load" event fired
 2022-09-19T20:53:46.986Z pw:api   "domcontentloaded" event fired
 2022-09-19T20:53:47.494Z pw:api   "networkidle" event fired

2022-09-19T20:54:16.741Z pw:api navigating to "https://eventstreamingpublicwebdev.azurewebsites.net/", waiting until "load"
2022-09-19T20:54:17.236Z pw:api   "commit" event fired
2022-09-19T20:54:17.237Z pw:api   navigated to "https://eventstreamingpublicwebdev.azurewebsites.net/LandingPage"
2022-09-19T20:54:17.956Z pw:api   "domcontentloaded" event fired
2022-09-19T20:54:18.225Z pw:api   "load" event fired
2022-09-19T20:54:18.250Z pw:api navigating to "https://eventstreamingpublicwebdev.azurewebsites.net/LoginSelector", waiting until "load"
2022-09-19T20:54:18.390Z pw:api   "commit" event fired
2022-09-19T20:54:18.390Z pw:api   navigated to "https://eventstreamingpublicwebdev.azurewebsites.net/LoginSelector"
2022-09-19T20:54:18.841Z pw:api   "load" event fired
2022-09-19T20:54:18.842Z pw:api   "domcontentloaded" event fired
2022-09-19T20:54:18.856Z pw:api waiting for selector "a[role="button"]:has-text("Innskr├íning ├íhorfanda")"
2022-09-19T20:54:18.872Z pw:api   selector resolved to visible ÔÇª
2022-09-19T20:54:18.875Z pw:api attempting click action
2022-09-19T20:54:18.875Z pw:api   waiting for element to be visible, enabled and stable
2022-09-19T20:54:18.892Z pw:api   element is visible, enabled and stable
2022-09-19T20:54:18.892Z pw:api   scrolling into view if needed
2022-09-19T20:54:18.893Z pw:api   done scrolling
2022-09-19T20:54:18.897Z pw:api   performing click action
2022-09-19T20:54:19.614Z pw:api   click action done
2022-09-19T20:54:19.614Z pw:api   waiting for scheduled navigations to finish
2022-09-19T20:54:19.615Z pw:api   "commit" event fired
2022-09-19T20:54:19.615Z pw:api   navigated to "https://streamworksidentitydev.azurewebsites.net/Account/Login?ReturnUrl=%2Fconnect%2Fauthorize%2Fcallback%3Fclient_id%3DBeinni_Web_Public%26redirect_uri%3Dhttps%253A%252F%252Feventstreamingpublicwebdev.azurewebsites.net%252Fsignin-oidc%26response_type%3Dcode%2520id_token%26scope%3Dopenid%2520profile%2520role%2520email%2520phone%2520Beinni%26response_mode%3Dform_post%26nonce%3D637992176590468503.OTNiZWZmNDItZGFmNi00OTQzLThjNDctOTExOGJjNGUxNTc0OTgyNmJlM2ItYTk5ZC00OWQ1LTg4MDYtMWY5NzAyYmYzMTJi%26state%3DCfDJ8Nz0aZ4MpSdEq6-Csy0Lf5WQWcvPWvB_LvTZouDE8lxyKPGtkRUaQtiNWTscL9n3lf0hvpklyNK0ZuvQD5SSIsSO_pior48ll2zySWI5_9nUtZODMMhiL_CrYSXY7_hAc4y7mzXerQfmS3-QuShNww9mxkvKQVf__A_uQsSLsr4nuHaHfMy6pRioAysQxijFibqF-51X6iPktmaIMX8BHRFpeOq9P1_swkeEliQ5eNy0XdHFyO0T0dE4ICvcH1Pm8ZkHd7tYQABFoZHp6OuS3oflqzgXHqtka2wOl2plsbuK4-UaT6qhJBtUMLfem2suWdNrpCc9MvYxVxnmk7K3CVk%26x-client-SKU%3DID_NETSTANDARD2_0%26x-client-ver%3D<IP_ADDRESS>"
2022-09-19T20:54:19.615Z pw:api   navigated to "https://streamworksidentitydev.azurewebsites.net/Account/Login?ReturnUrl=%2Fconnect%2Fauthorize%2Fcallback%3Fclient_id%3DBeinni_Web_Public%26redirect_uri%3Dhttps%253A%252F%252Feventstreamingpublicwebdev.azurewebsites.net%252Fsignin-oidc%26response_type%3Dcode%2520id_token%26scope%3Dopenid%2520profile%2520role%2520email%2520phone%2520Beinni%26response_mode%3Dform_post%26nonce%3D637992176590468503.OTNiZWZmNDItZGFmNi00OTQzLThjNDctOTExOGJjNGUxNTc0OTgyNmJlM2ItYTk5ZC00OWQ1LTg4MDYtMWY5NzAyYmYzMTJi%26state%3DCfDJ8Nz0aZ4MpSdEq6-Csy0Lf5WQWcvPWvB_LvTZouDE8lxyKPGtkRUaQtiNWTscL9n3lf0hvpklyNK0ZuvQD5SSIsSO_pior48ll2zySWI5_9nUtZODMMhiL_CrYSXY7_hAc4y7mzXerQfmS3-QuShNww9mxkvKQVf__A_uQsSLsr4nuHaHfMy6pRioAysQxijFibqF-51X6iPktmaIMX8BHRFpeOq9P1_swkeEliQ5eNy0XdHFyO0T0dE4ICvcH1Pm8ZkHd7tYQABFoZHp6OuS3oflqzgXHqtka2wOl2plsbuK4-UaT6qhJBtUMLfem2suWdNrpCc9MvYxVxnmk7K3CVk%26x-client-SKU%3DID_NETSTANDARD2_0%26x-client-ver%3D<IP_ADDRESS>"
2022-09-19T20:54:19.620Z pw:api   navigations have finished
2022-09-19T20:54:19.627Z pw:api waiting for selector "input[name="LoginInput\.UserNameOrEmailAddress"]"
2022-09-19T20:54:19.653Z pw:api   selector resolved to visible <input value="" type="text" data-val="true" maxlength="ÔÇª/>
2022-09-19T20:54:19.655Z pw:api attempting click action
2022-09-19T20:54:19.655Z pw:api   waiting for element to be visible, enabled and stable
2022-09-19T20:54:20.172Z pw:api   element is visible, enabled and stable
2022-09-19T20:54:20.172Z pw:api   scrolling into view if needed
2022-09-19T20:54:20.173Z pw:api   done scrolling
2022-09-19T20:54:20.179Z pw:api   performing click action
2022-09-19T20:54:20.185Z pw:api   click action done
2022-09-19T20:54:20.185Z pw:api   waiting for scheduled navigations to finish
2022-09-19T20:54:20.185Z pw:api   navigations have finished
2022-09-19T20:54:20.191Z pw:api waiting for selector "input[name="LoginInput\.UserNameOrEmailAddress"]"
2022-09-19T20:54:20.194Z pw:api   selector resolved to visible <input value="" type="text" data-val="true" maxlength="ÔÇª/>
2022-09-19T20:54:20.197Z pw:api elementHandle.fill("playwrightppv")
2022-09-19T20:54:20.199Z pw:api   waiting for element to be visible, enabled and editable
2022-09-19T20:54:20.203Z pw:api   element is visible, enabled and editable
2022-09-19T20:54:20.212Z pw:api waiting for selector "input[name="LoginInput\.Password"]"
2022-09-19T20:54:20.215Z pw:api   selector resolved to visible <input type="password" data-val="true" maxlength="128" ÔÇª/>
2022-09-19T20:54:20.216Z pw:api attempting click action
2022-09-19T20:54:20.216Z pw:api   waiting for element to be visible, enabled and stable
2022-09-19T20:54:20.242Z pw:api   element is visible, enabled and stable
2022-09-19T20:54:20.242Z pw:api   scrolling into view if needed
2022-09-19T20:54:20.242Z pw:api   done scrolling
2022-09-19T20:54:20.247Z pw:api   performing click action
2022-09-19T20:54:20.254Z pw:api   click action done
2022-09-19T20:54:20.254Z pw:api   waiting for scheduled navigations to finish
2022-09-19T20:54:20.255Z pw:api   navigations have finished
2022-09-19T20:54:20.260Z pw:api waiting for selector "input[name="LoginInput\.Password"]"
2022-09-19T20:54:20.263Z pw:api   selector resolved to visible <input type="password" data-val="true" maxlength="128" ÔÇª/>
2022-09-19T20:54:20.266Z pw:api elementHandle.fill("1q2w3E*")
2022-09-19T20:54:20.269Z pw:api   waiting for element to be visible, enabled and editable
2022-09-19T20:54:20.277Z pw:api   element is visible, enabled and editable
2022-09-19T20:54:20.285Z pw:api waiting for selector "id=termsandcondition"
2022-09-19T20:54:20.291Z pw:api   selector resolved to visible <input value="true" type="checkbox" data-val="true" id=ÔÇª/>
2022-09-19T20:54:20.298Z pw:api attempting click action
2022-09-19T20:54:20.298Z pw:api   waiting for element to be visible, enabled and stable
2022-09-19T20:54:20.328Z pw:api   element is visible, enabled and stable
2022-09-19T20:54:20.328Z pw:api   scrolling into view if needed
2022-09-19T20:54:20.328Z pw:api   done scrolling
2022-09-19T20:54:20.333Z pw:api   performing click action
2022-09-19T20:54:20.341Z pw:api   click action done
2022-09-19T20:54:20.341Z pw:api   waiting for scheduled navigations to finish
2022-09-19T20:54:20.342Z pw:api   navigations have finished
2022-09-19T20:54:20.351Z pw:api waiting for selector "#loginsubmitbtn"
2022-09-19T20:54:20.354Z pw:api   selector resolved to visible <button type="button" name="Action" value="Login" id="loÔÇª>Innskr├í</button>
2022-09-19T20:54:20.356Z pw:api attempting click action
2022-09-19T20:54:20.356Z pw:api   waiting for element to be visible, enabled and stable
2022-09-19T20:54:20.393Z pw:api   element is visible, enabled and stable
2022-09-19T20:54:20.393Z pw:api   scrolling into view if needed
2022-09-19T20:54:20.394Z pw:api   done scrolling
2022-09-19T20:54:20.399Z pw:api   performing click action
2022-09-19T20:54:20.404Z pw:api   "domcontentloaded" event fired
2022-09-19T20:54:20.404Z pw:api   "load" event fired
2022-09-19T20:54:21.077Z pw:api   click action done
2022-09-19T20:54:21.077Z pw:api   waiting for scheduled navigations to finish
2022-09-19T20:54:21.077Z pw:api   "commit" event fired
2022-09-19T20:54:21.078Z pw:api   navigated to "https://streamworksidentitydev.azurewebsites.net/connect/authorize/callback?client_id=Beinni_Web_Public&redirect_uri=https%3A%2F%2Feventstreamingpublicwebdev.azurewebsites.net%2Fsignin-oidc&response_type=code%20id_token&scope=openid%20profile%20role%20email%20phone%20Beinni&response_mode=form_post&nonce=637992176590468503.OTNiZWZmNDItZGFmNi00OTQzLThjNDctOTExOGJjNGUxNTc0OTgyNmJlM2ItYTk5ZC00OWQ1LTg4MDYtMWY5NzAyYmYzMTJi&state=CfDJ8Nz0aZ4MpSdEq6-Csy0Lf5WQWcvPWvB_LvTZouDE8lxyKPGtkRUaQtiNWTscL9n3lf0hvpklyNK0ZuvQD5SSIsSO_pior48ll2zySWI5_9nUtZODMMhiL_CrYSXY7_hAc4y7mzXerQfmS3-QuShNww9mxkvKQVf__A_uQsSLsr4nuHaHfMy6pRioAysQxijFibqF-51X6iPktmaIMX8BHRFpeOq9P1_swkeEliQ5eNy0XdHFyO0T0dE4ICvcH1Pm8ZkHd7tYQABFoZHp6OuS3oflqzgXHqtka2wOl2plsbuK4-UaT6qhJBtUMLfem2suWdNrpCc9MvYxVxnmk7K3CVk&x-client-SKU=ID_NETSTANDARD2_0&x-client-ver=<IP_ADDRESS>"
2022-09-19T20:54:21.078Z pw:api   navigated to "https://streamworksidentitydev.azurewebsites.net/connect/authorize/callback?client_id=Beinni_Web_Public&redirect_uri=https%3A%2F%2Feventstreamingpublicwebdev.azurewebsites.net%2Fsignin-oidc&response_type=code%20id_token&scope=openid%20profile%20role%20email%20phone%20Beinni&response_mode=form_post&nonce=637992176590468503.OTNiZWZmNDItZGFmNi00OTQzLThjNDctOTExOGJjNGUxNTc0OTgyNmJlM2ItYTk5ZC00OWQ1LTg4MDYtMWY5NzAyYmYzMTJi&state=CfDJ8Nz0aZ4MpSdEq6-Csy0Lf5WQWcvPWvB_LvTZouDE8lxyKPGtkRUaQtiNWTscL9n3lf0hvpklyNK0ZuvQD5SSIsSO_pior48ll2zySWI5_9nUtZODMMhiL_CrYSXY7_hAc4y7mzXerQfmS3-QuShNww9mxkvKQVf__A_uQsSLsr4nuHaHfMy6pRioAysQxijFibqF-51X6iPktmaIMX8BHRFpeOq9P1_swkeEliQ5eNy0XdHFyO0T0dE4ICvcH1Pm8ZkHd7tYQABFoZHp6OuS3oflqzgXHqtka2wOl2plsbuK4-UaT6qhJBtUMLfem2suWdNrpCc9MvYxVxnmk7K3CVk&x-client-SKU=ID_NETSTANDARD2_0&x-client-ver=<IP_ADDRESS>"
2022-09-19T20:54:21.080Z pw:api   "load" event fired
2022-09-19T20:54:21.082Z pw:api   "domcontentloaded" event fired
2022-09-19T20:54:21.083Z pw:api   navigations have finished

Failed!  - Failed:     1, Passed:     1, Skipped:     0, Total:     2, Duration: 39 s - BSR.Beinni.PlaywrightTests.dll (net6.0)

C:\Dev\IBeinni\aspnet-core\test\BSR.Beinni.Playwright.Tests>

Any clue what this might be @mxschmitt? And this all just runs fine on your end again and again?

Unfortunately not, I'd try to debug it with tracing, to find out how the website looks like if the logs are not helping.

Closing for now since we can't act on it, feel free to re-file with a smaller repro.


fix path for async-google-apis-common in cargo.toml

examples didn't build, fixed the cargo toml files

good spot, thank you!


ARROW-13743: [CI] OSX job fails due to incompatible git and libcurl

@github-actions crossbow submit -g conda

Though this resolves the immediate build issue, it would be time for another "recipe sync" again. We should start thinking on alternative ways to have nightly conda builds, since it's pretty hard to maintain the vendored feedstock setup (not the recipes themselves).
@xhochy we could clone the arrow-cpp-feedstock then use the azure templates including the matrices defined therein, though:

I'm not sure whether we could override matrix parameters like UPLOAD_PACKAGES
How future-proof would it be, since the feedstocks keep evolving
How could we incorporate the arrow-cpp packages to similarly configured r-arrow builds

I'd also consider to just remove the conda package builds altogether, and turn the conda-forge build validation to a release task where we would try to build the RC directly in the feedstock.
cc @nealrichardson

I'd also consider to just remove the conda package builds altogether, and turn the conda-forge build validation to a release task where we would try to build the RC directly in the feedstock.

Please don't do that :( We use the conda packages in several places for testing, this would break a lot of testing of upstream packages against arrow nightlies.
Cloning the feedstock could be an option, one thing we wanted to do then would be to change some values in conda-forge.yml to upload to different channels and rerender using conda-smithy.

Please don't do that :( We use the conda packages in several places for testing, this would break a lot of testing of upstream packages against arrow nightlies.

Good to know that :)

Cloning the feedstock could be an option, one thing we wanted to do then would be to change some values in conda-forge.yml to upload to different channels and rerender using conda-smithy.

Perhaps we could create an apache artifactory repository for the nightlies?


Call as docker compose instead of docker-compose in CI

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 94.66%. Comparing base (6516ca4) to head (b506128).
Report is 9 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1108      +/-   ##
==========================================
+ Coverage   94.62%   94.66%   +0.04%
==========================================
  Files         182      190       +8
  Lines       18870    18890      +20
==========================================
+ Hits        17855    17882      +27
+ Misses       1015     1008       -7

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


incremental_compiler_test is flaky on mac-arm64

There are new test failures on [cfe] Verify that only new method invocation nodes are generated when supported.
The tests
pkg/vm/test/incremental_compiler_test RuntimeError (expected Pass)

are failing on configurations
unittest-asserts-release-mac-arm64

Log:
00:08 +14 -1: expression evaluation from source [E]

  Bad state: No element

  dart:core-patch/growable_array.dart 332:5           List.first
  pkg/vm/test/incremental_compiler_test.dart 1676:21  RemoteVm._computeMainId
  ===== asynchronous gap ===========================
  pkg/vm/test/incremental_compiler_test.dart 1648:52  RemoteVm.mainId
  ===== asynchronous gap ===========================
  pkg/vm/test/incremental_compiler_test.dart 1703:14  RemoteVm.getIsolate
  ===== asynchronous gap ===========================
  pkg/vm/test/incremental_compiler_test.dart 1197:27  main.<fn>.launchBreakAndEvaluate.<fn>

https://dart-ci.appspot.com/log/pkg-mac-release-arm64/unittest-asserts-release-mac-arm64/15/pkg/vm/test/incremental_compiler_test
/cc @aam @johnniwinther

Again today https://dart-ci.appspot.com/log/pkg-mac-release-arm64/unittest-asserts-release-mac-arm64/309/pkg/vm/test/incremental_compiler_test

And today: https://dart-ci.appspot.com/log/pkg-mac-release-arm64/unittest-asserts-release-mac-arm64/767/pkg/vm/test/incremental_compiler_test
Why does this only occur on arm64 macs though?

I marked this test as flaky manually, so it will no longer appear as switching between passing and failing.  After the next build completes, it should show up as flaky in the current results page and on the flakiness dashboard

It swapped status again on mac-arm64 today
unittest-asserts-release-mac-arm64
flaky -> RuntimeError (expected Pass)
pkg/vm/test/incremental_compiler_test

log: https://dart-ci.appspot.com/log/pkg-mac-release-arm64/unittest-asserts-release-mac-arm64/992/pkg/vm/test/incremental_compiler_test

This test is actually flaky on all platforms:
go/dart-flakiness?fb=name:eq:pkg%2Fvm%2Ftest%2Fincremental_compiler_test

00:09 +14 -1: expression evaluation from source [E]

  Bad state: No element

  dart:core-patch/growable_array.dart 339:5           List.first
  pkg/vm/test/incremental_compiler_test.dart 1673:21  RemoteVm._computeMainId
  ===== asynchronous gap ===========================
  pkg/vm/test/incremental_compiler_test.dart 1645:52  RemoteVm.mainId
  ===== asynchronous gap ===========================
  pkg/vm/test/incremental_compiler_test.dart 1700:14  RemoteVm.getIsolate
  ===== asynchronous gap ===========================
  pkg/vm/test/incremental_compiler_test.dart 1196:27  main.<fn>.launchBreakAndEvaluate.<fn>

Consider enabling the flag chain-stack-traces to receive more detailed exceptions.
For example, 'dart test --chain-stack-traces'.

https://logs.chromium.org/logs/dart/buildbucket/cr-buildbucket/8831453547242854513/+/u/test_results/new_test_failures__logs_

//cc @bkonyi the latest failure seems to indicate isolates.first is empty, did anything change in service protocol to cause this ?

@a-siva from what I can tell, this has always been happening. Chances are that the test has connected to the service before the main isolate has come up and is getting an empty isolate list from the VM response.

https://dart-review.googlesource.com/c/sdk/+/63645 should hopefully fix it

Manually marked as flaky again.


Various new features of macOS 11.0

This is another pass of adding new macOS 11.0 features to metal-rs. It lays some groundwork to add new ray tracing API, as well as adding things like dynamic libraries, function pointers, etc. Some naming changes were also made.
This is still work in progress, but I wanted to merge as I go to avoid drifting too much. There are some comments left for things yet to be done.
I also added a simple example of using shader dynamic libraries.
I expect some discussion and cleanup, so I will squash commits once we're all happy with this PR.

Please use "Resolve Conversation" on items that are addressed, so that we know when it's time to look at the code again.

Please use "Resolve Conversation" on items that are addressed, so that we know when it's time to look at the code again.

@bsekura what's the status? Is it waiting for re-review of some points, or all ready?

@bsekura what's the status? Is it waiting for re-review of some points, or all ready?

That should do it for now. Please check and merge if there are no issues. Sorry, I was unavailable for a bit and it took longer than expected.

That should do it for now. Please check and merge if there are no issues. Sorry, I was unavailable for a bit and it took longer than expected.

I'm on it.
Squash via rebase is giving me a headache because of merge with upstream.
Are you able to merge and squash on your end using github's features?

I'm on it.
Squash via rebase is giving me a headache because of merge with upstream.
Are you able to merge and squash on your end using github's features?


Get-OrganizationRelationship results in error after running both scripts

Does anyone know what I can do to see where the org relationship is incorrect?

Good morning,
Can you please send mail to<EMAIL_ADDRESS>with your source and target domains. Also, did running the setup script state the OrgRelationship was created successfully?
Thanks,
Roman

Started working out of no where.


Update default load raster params to test codecov

Codecov Report

Merging #63 (7bc13a6) into develop (b49fd97) will increase coverage by 4.05%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##           develop      #63      +/-   ##
===========================================
+ Coverage    85.01%   89.07%   +4.05%
===========================================
  Files            4        4
  Lines          594      595       +1
===========================================
+ Hits           505      530      +25
+ Misses          89       65      -24

Impacted Files
Coverage Δ

coastlines/vector.py
90.96% <100.00%> (+0.02%)
:arrow_up:

coastlines/continental.py
88.29% <0.00%> (+25.53%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Mortal needs permanent accounts on tenhou

It's been bugging me for a while and I don't think I can ignore it any longer:
Even before I started playign with mortals I've been rolling a lot of new accounts and it felt like tenhou is doing something to spice up the hands of new accounts. They statisically were more likely to be strong and finish in bizarre ways. After I started playing with mortals AND nagas, it became pretty obvious that naga's hands are normal while mortal way too often recieves the typical "newbie" hand rng.
The problem got way worse with the introduction of 4.0 where mortal seems to have learned to take advantage of that and disproportinately go damaten. It really needs to get off its "I am a newbie" high and actually get registered so that the game doesn't treat it with kid's gloves.
I know people call me crazy, but it really feels like tenhou is doing something weird with their new accounts. It's nothing as overt as other servers where you just can't lose in your first games, but all my experience tells me something is fishy with that. It's just disproportionately too often that rng is rigged towards these

Are you sure about that?🤔 I've never experienced such issue, nor have I ever thought about it, and I don't see the statistical evidence behind it. Even if it's true, how old do you think Tenhou would consider an account "old"? And what makes it "old" in the first place? Age or play counts? Does play counts on private lobby count or not? There are so many follow-up questions that I don't think it's worth delving deeper into them, but rather accept the assumption that the games are fair.

> Are you sure about that?
Obviously not, it's just something that's been bugging me really really strongly.  Naga (almost) never demonstrates the same abundance of expensive closed hands early.

Well, I don't think I could help with that...


Xcode 10 Beta 3 header issue

While trying to compile with Xcode 10 beta 3 it fails with header permission issue, I have tried several things such as clearing pods, clearing pod cache, clearing derived data etc.
This works as expected in Xcode beta 2
Expected Results
👍 Compile :)
Actual Results
open ... Realm/Realm.framework/Headers/RLMPlatform.h: Permission denied
Steps to Reproduce
Compile with latest Realm modules from Cocoapods
Version of Realm and Tooling
Realm framework version: Latest
Realm Object Server version: Latest
Xcode version: Xcode 10 beta 3
iOS/OSX version: OS X 10.14 Beta 3
Dependency manager + version: Cocoapods 1.5.3
This is related to - #5827 but specific to Xcode 10 Beta 3

It seems Xcode has an issue with the fact the file is empty. Insert a comment or something into the file, e.g. // This file is blank and Xcode compiles the project just fine.

@apoltix
Hi i am having problem when compiling the project using Xcode 10 Beta 3 with following error :
'impl/weak_realm_notifier.hpp' file not found
Also i couldnt find the Pods/Realm/include/RLMPlatform.h
inside my Realm. I am using RealmSwift latest version.
Hopefully you can guide me thanks

For the record chmod 666 Pods/Realm/include/RLMPlatform.h also does the trick for building.

@CedricGatay Your tip fixed the problem, thanks !


Yabai ignoring some config parameters like window_shadow et al.

I use macOS Monterey on a Mac Mini 2018 (so, intel), and I know yabai is still not supported for it. I still think that pointing out to the developer the current issue can be useful since I couldn't find some similar report on the github issue tracker.
My yabai version is installed via "brew install koekeishiya/formulae/yabai --HEAD".
Some config parameters are completely ignored. The ones that I have found to be broken after some pretty quick testing are window_shadow (on, off and float do not make any difference: the shadow is always present), as well as active_window_opacity and normal_window_opacity (windows are always fully opaque even then window_opacity is on and their opacity value are set to something like 0.5).
Yabai is SO great, I hope developers can restore its amazing capabilities soon.
Keep up the incredible work.

I have the same problem on Big Sur (11.2.3), yesterday it worked, now it doesn't anymore. Thought i was doing something wrong.

Okay update: solved it.
The problem for me was, that the scripting addition wasn't loaded, so that may work for you too.

You are right, the scripting addition does not load automatically, even when you add the required commands in the rc file, as suggested in the documentation. I added the sudoers file to use passwordless yabai, but that seems to not work. Maybe I have to recheck all the things.


Omit breaks in 3.9.2

TypeScript Version:
3.9.2

Search Terms:
3.9.2 Omit
Code
interface A {
  my: 'aaa';
}

interface B {
  my: 'bbb';
}

interface C extends Omit<A & B, 'my'> {
  my: string;
}

Expected behavior:
Can define my with Omited like prev version.
Actual behavior:

Property 'my' of type 'string' is not assignable to string index type 'never'.(2411)

Playground Link:
https://www.typescriptlang.org/play/?ssl=1&ssc=1&pln=12&pc=1#code/JYOwLgpgTgZghgYwgAgILIN7ILAChnIC2AngFzIDkc1FA3HgL556iSyIoBCmO+RZlAEbC6jZrlbR4SZAGFkEAB6QQAEwDOyAPKFgYADzoAZMk4AaSiQoA+HngIly6sFFABzeria4gA
Related Issues:

Effectively duplicate of #38241, related to breaking change #37195.

The issue here is that A & B is an empty intersection (i.e. a type for which you couldn't possibly construct a value) that now reduces to never. We previously didn't catch such types.
You could instead write your code as
type Base = Omit<A, 'my'> & Omit<B, 'my'>;

interface C extends Base {
  my: string;
}

That is, omit the conflicting discriminants before you intersect the types.

@ahejlsberg , but never can be omit:
interface A {
  my: never;
}

interface C extends Omit<A, 'my'> {
  my: string;
}

https://www.typescriptlang.org/play/?ssl=1&ssc=1&pln=8&pc=1#code/JYOwLgpgTgZghgYwgAgILIN7ILAChnIC2AngFzIgQBu0A3HgL556iSyIoDCyEAHpCAAmAZ2QB5QsDAAeVABpkAchKKAfJhz4iZZMLBRQAc3q4muIA

Yes, but any type that includes a property of type never is a type with no possible values, so we're not talking about something that couldn't exist in the real world. Ideally we'd reduce all such types to never (that is, instead of { my: never } we'd simply have never) but it is costly to check for and tricky to do in a lazily evaluated type system.


Support output descriptor

depends on #694 , previous attempt is #684
Currently it is independent from #695 , and it follows bitcoin core's spec.

Actually I've just realized that many Inconvenience that I'm facing right now might be fixed by using OutputDescriptor. I will  revive this PR and add RPC methods too from now on.

There is a new descriptor type sortedmulti in the bitcoin core so I'm trying to update the descriptor now.

ping @lontivero do you plan using output descriptor this in the near term? If so, can you review that?

I am going to review it during the weekend. I think Wasabi could use output descriptors soon. We could display the OD for exporting the wallet and imported in Core or export public/private keys in a better way.

This work is not a monkey porting directly from bitcoin core but a implementation from scratch, i mean, it is clearly based on the bitcoin core but not copied. Classes, methods, identifiers, code structures are different and that makes the "comparison" hard to do. Most of the changes make sense to me btw, HD instead of Bip32 and other similar are preferable to me too.
Some parts are completely different, the parser is the more obvious case. Given it is hard to grasp to me (because there are concepts that are unknown to me) i decided to insert modifications in the core tests and in this pr's test in order to see if they both behave in the same way. The bitcoin core tests pass green even if i insert empty spaces before, in between or after parenthesis, brackets. The tests in this pr fail.
There are a few design decisions that I don't understand and that could be simply the result of  coding paradigms but i would like to understand. For example, GetPubkey method in Core is overridden by each Descriptor class while in this PR is implemented with a switch statement comparing types. What is the reason @joemphilips?
I will continue reviewing and understanding the code when I find more time. This is a great work @NicolasDorier, just give me a few more days. Btw, I enjoy the functional style but i agree that the parser was coded in a way that c# does not fit well.

@joemphilips in Core the cache is there like a think that all KeyProviders should be aware of but it is obviously only for HDKeyProviders and i need to get more familiar with your design in order to be able to do it.

There are a few design decisions that I don't understand and that could be simply the result of coding paradigms but i would like to understand. For example, GetPubkey method in Core is overridden by each Descriptor class while in this PR is implemented with a switch statement comparing types. What is the reason @joemphilips?

Short answer: It is a functional way.
Long answer: 1. I want implementation of the OutputDescriptor to be "closed" inside this library. i.e. user's should not create the new type by overriding OutputDescriptor, So I did not want to use virtual or abstract methods.
2. I think it is easier to understand when the logics are grouped in this way. If we use abstract methods we might forget to override in subtypes. In this way it is easy to see that methods are implemented for every possible types.

i decided to insert modifications in the core tests and in this pr's test in order to see if they both behave in the same way. The bitcoin core tests pass green even if i insert empty spaces before, in between or after parenthesis, brackets. The tests in this pr fail.

This is good catch. When I started this work, bitcoin-core OD was very strict about parsing and it did not permit any white space. I will update the parser then.
Btw, I found out that OD does not help me for the problem I was facing right now, so there is no hurry in my side. Take your time for reviewing.

I want implementation of the OutputDescriptor to be "closed" inside this library. i.e. user's should not create the new type by overriding OutputDescriptor, So I did not want to use virtual or abstract methods.

When you want to do this, you can just declare the abstract/virtual methods internal.

When you want to do this, you can just declare the abstract/virtual methods internal.

But doesn't it make it impossible for user to use the method?

@joemphilips yes, one thing often used also is have a method "BlahBlah" public and another one "BlahBlahCore" internal/protected.
With BlahBlah which don't have to do much... That's ugly if you have too many methods that need that, but if it is a one or two, I think that;s fine.

@lontivero you plan to still review some stuff or should I start review as well?

I will not review it more.

@joemphilips I think I will merge that soon. One question: About KeyId and WitScriptId. Do you really need it in say FlatSigningRepository?
As time pass, I get more and more convinced that KeyId/ScriptId/WitScriptId are classes that should never have existed in the first place, so I am curious why you need it.

I can try using uint160/uint250 instead if you want, I've just used it because I like using different types for those cases. (It makes hard to misuse the API.)
Let me check if that works or not.

After testing a bit, I think it is possible to use uint160/uint256 for ISigningRepository but It requires substantial refactoring.
e.g. I want to use the api like pk.WitHash.ScriptPubKey.Hash.ScriptPubKey or PayToPubkeyHashTemplate.ExtractScriptPubKeyParameters() which uses KeyId or ScriptIdso I first have to add a new methods/properties to PubKey , ScriptTemplate , that will be huge change on the existing code.
I suppose it is out of the scope for this PR, if you really want to make KeyId/ScriptId obsolete, first we’d better make those types obsolete in existing code.
(which I don’t think is necessary though btw, having wrapper types like WitScriptId and ScriptId is a nice way to specify the intention.)

@joemphilips don't refactor to use uint160/uint256 instead I just want to know, why you need those Ids classes rather than just ScriptPubKey

It is done in that way in original implementation
It is a bit smaller
It is more easy to understand the intention (e.g. for TryGetPubKey(KeyId keyId, out PubKey pubkey) , if the first argument is Script, reader might get confused whether that is ScriptPubKey for the p2pk, or ScriptPubKey for the p2pkh)

Would you consider merging this? I have a plan to use it.

Released a new version.


add flag to optionally generate structured output

To use lightbeam in an automated data pipeline it would be useful to have it generate structured output noting the number of records sent and skipped by resource and status code, the run timestamp, and possibly other information. Open questions include:

what should the flag be? perhaps --results-file output.json
what should the output format be? (YAML, JSON, something else?)
besides the items noted above, what else should be included in the results? perhaps the Ed-Fi API base_url? anything else?

Tagging @jayckaiser for thoughts.

Based on our conversation today, I'm proposing that

lightbeam's structured output is enabled with a cli flag --results-file ./results.json
output format is JSON, like this:{
  "timestamp": "2023-05-15 02:04:18Z00",
  "api_url": "https://edfi3.somedistrict.org/api/",
  "source_dir": "/path/to/some/dir/",
  "resources": {
    "studentSchoolAssociations": {
      "records_processed": 100,
      "records_skipped" :10,
      "records_attempted": 90,
      "records_success": 75,
      "records_failed": 15,
      "failed_statuses": {
        "409": {
          "messages": [
            {
              "message": "Invalid StudentReference",
              "count": 6,
              "line_numbers": [3, 7, 8, 31, 64, 88]
            },
            {
              "message": "Invalid SchoolReference",
              "count": 9,
              "lines": [5, 9, 12, 13, 26, 27, 29, 30, 56]
            },
          ]
        },
        ...
      }
    },
    ...
  }
  "total_records_processed": 100,
  "total_records_skipped": 10,
  "total_records_attempted": 90,
  "total_records_success": 75,
  "total_records_failed": 15
}

Is this too verbose? i.e., do we need the total_ across all resources?

We also discussed the exit codes lightbeam should return in different circumstances, to trigger the AirFlow BashOperator task to raise an AirflowSkipException or AirflowException (per the Airflow docs). Is it correct that

if total_records_skipped == total_records_processed, lightbeam should return exit code 99? (so the Airflow task skips)
if total_records_failed>0 lightbeam should return exit code 1? (so the Airflow task fails)

One other issue has to do with reporting line numbers: lightbeam can process either a single JSONL file (source_dir/students.jsonl) or an entire directory of JSONL files (source_dir/students/*.jsonl). In the latter case, how would line numbers be determined/interpreted?
Finally, one tiny question, should line numbers be 0-based or 1-based?

Closing this issue as it was implemented in this PR.


Lottie doesn't play with imperative API when in a Modal

I have a lottie file that works great in a normal view, but when I try to add it to a Modal (https://github.com/maxs15/react-native-modalbox) it doesn't play at all. I just get a rendering of the first frame. How can I fix? I am using the imperative API.

@ay5000 Please post your code. I had a similar issue and my problem was my reference to 'this' which was lost.

export default class LottieView extends React.Component {
  componentDidMount() {
    this.animation.play();
  console.log("LOTTIE VIEW MOUNTED")
}

render() {

return (
  <View style={this.props.style}>
    <Animation
      ref={animation => { this.animation = animation; }}
      loop
      style={{
        width: '100%',
        height: '100%',
        backgroundColor:'transparent'
      }}
      source={'file.....'}
    />
  </View>
);
}

}
So in console "LOTTIE VIEW MOUNTED" does print when the parent view renders (and the modal which holds the LottieView is off screen.

Without looking at the Modal code, I would think that the modal is always loaded but hidden so basically the animation already played by the time you show the modal.
Try replacing loop with loop={true} or playing the animation right after you open the modal.
Note: I could never made loop worked, I always used a setInterval to keep the animation playing.

@sfratini thanks for the tips. Can you show an example of how you're using setInterval? I think that may just be easier.

Sure. So these are snippets of my EmptyComponent that shows when a list is empty:
constructor(props){
        super(props);
        this.state = {
            emptyProgress: new Animated.Value(0)
        };
    }

<Animation
                    style={this.getStyle(styles, ['emptyAnimation'])}  //This is a generic method that returns the merged style because I support Themes.
                    source={this.getAnimationManager().getAnimationSource(empty.animation.id)} //I keep a dictionary of animations sources so I can change it from backend
                    progress={this.state.emptyProgress}
                    />

componentDidMount(){
        this.loadData();  //Just my function that loads the info
        this.startEmptyAnimation();
    }

    startEmptyAnimation = () =>{
        this.timingAnimation();  // First we run the animation once because otherwise the animation does not start right away
        setInterval(this.timingAnimation, 2500);  //Restarts every 2.5 seconds
    }

    timingAnimation = () => {
        this.setState({emptyProgress: new Animated.Value(0)}, () => {
            Animated.timing(this.state.emptyProgress, {
                toValue: 1,
                duration: 1500,  //Duration of my animation
              }).start();
        });
    }

@ay5000 My guess is that this isn't Lottie specific. If you think there is something wrong with Lottie, you can reopen this

  componentDidMount() {
   setTimeout(() => this.animation.play(), 100);
  }

Fixed things for me. This should really work with this though but I guess the modal mounts stuff before it fades in breaking things?

Place the code in Modal body makes it works for me.
PS: I'm using native Modal

It seems the bug is caused by that play() requires the root view in the native codes. However, the root view is detached by the react native Modal component.
The workaround is to call play() one frame later than componentDidMount()
componentDidMount() {     Platform.OS === 'ios'? requestAnimationFrame(this.animation.play.bind(this.animation)) : this.animation.play();   }


Move the main loop that processes itemsToProcess to a function

Move the main loop that processes itemsToProcess (after parsing CLI args)
and construction of stages dict out to a function.
The function takes only the itemsToProcess list that is
constructed by parsing the args.item inputs as well as the base-url.
Within the function the code is essentially unchanged, and the
function returns the completed stages dictionary.
The only other change is to remove the branch "if args.output" when
constructing the savePath...args.output is required, so it will always
be set (also, the alternative 'rootdir' appears to not be defined).
This version is updated to handle the newly added pkg-skip-if settings.

Just wanted to follow up and see if you think any changes are needed here.  Thanks.

Looks good but my only question is does this change any of the current behaviors? In other words is this is a breaking change?

No, it isn't breaking.
I just moved the work that you do after building the itemsToProcess list into a function.  Your wiki instructions to call generatejson.py via cli should not need to change at all.
The improvement is that it is easier to use this as part of a larger process now, by including from generatejson import *, building a list that matches itemsToProcess and then calling the new function build_item_dict.  Previously we had done this by using subprocess to mimic what you describe in the wiki, but that just seemed like a bit of a hack.
Thanks again for making this.  It has been extremely valuable for us.

Clever. :)

Thanks for the PR. Merged.


[MINOR][SQL][DOCS] Reformat the tables in SQL migration guide

What changes were proposed in this pull request?

Reformat the tables to be located with a proper indentation under the corresponding item to be consistent.

Fix Table 2's contents to be more readable with code blocks.

Table 1
Before:

After:

Table 2
Before:

After:

How was this patch tested?
Manually built the doc.

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/testing-k8s-prb-make-spark-distribution-unified/7686/
Test PASSed.

Test build #102010 has started for PR 23723 at commit 6db7fde.

Test build #102010 has finished for PR 23723 at commit 6db7fde.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/102010/
Test PASSed.

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/testing-k8s-prb-make-spark-distribution-unified/7687/
Test PASSed.

Test build #102013 has started for PR 23723 at commit 5677857.

Merged to master.


Missing syntax test in Rakefile

Line 19 of Rakefile reads:
desc "Run syntax, lint, and spec tests."
But the Rakefile specifies no syntax tests. We should add them.

Added PR 164


Set execute permission on runnable python scripts

Description

Python scripts got a shebang some time ago, but some were missing execute permission.

Thanks - been meaning to get to that :-)


Read default regexes from configmap for tests.

@yithian @gregsheremeta
/hold

/hold cancel

If this goes before https://github.com/openshift/hive/pull/1539 @yithian will have to rebase again so
/hold

/unhold

/test e2e-pool


samples: set correct minimum firmware version of XBee3 802.15.4 and DigiMesh platforms in the relay frames samples

Only Zigbee and Cellular modules support relay frames communication at
this time.
Signed-off-by: Ruben Moral<EMAIL_ADDRESS>

Thanks for the suggestion, @tomlogic. I have changed the minimum fw version of 802.14.5 as well; the build of version 1004 we have received to test does have support for relay frames too.


Camera path is not configured correctly, please edit the 'device_path' config value. Fedora 33

Can't add new camera. camera model Lenovo 500
[filip@filip-desktop ~]$ sudo howdy add
[sudo] password for filip:
Adding face model for the user filip
Enter a label for this new model [Initial model] (max 24 characters): Lenovo
Camera path is not configured correctly, please edit the 'device_path' config value.
Exception ignored in: <function VideoCapture.__del__ at 0x7fa2e560b8b0>
Traceback (most recent call last):
  File "/usr/lib64/security/howdy/recorders/video_capture.py", line 55, in __del__
    self.internal.release()
AttributeError: 'VideoCapture' object has no attribute 'internal'

[filip@filip-desktop ~]$ sudo howdy snapshot
Camera path is not configured correctly, please edit the 'device_path' config value.
Exception ignored in: <function VideoCapture.__del__ at 0x7f795d7ba670>
Traceback (most recent call last):
  File "/usr/lib64/security/howdy/recorders/video_capture.py", line 55, in __del__
    self.internal.release()
AttributeError: 'VideoCapture' object has no attribute 'internal'

I've searched for similar issues already, and my issue has not been reported yet.
Linux distribution (if applicable): Fedora 33
Howdy version (sudo howdy version): 2.6.0

Have you configured the correct camera device as the device_path?

Have you configured the correct camera device as the device_path?

Than you ! :) I didn't know that I should add my camera to device_path


Add files via upload

Get JetBrains license for student

@murphy142 I am sorry, the domain sis.hust.edu.vn is removed from our trusted domains list because it was abused in the past. If you are the student of this school, please enroll to GitHub Student Developer Program. Then apply for JetBrains educational subscription with your GitHub account (GitHub tab at https://www.jetbrains.com/shop/eform/students).