Improve compatibility with Serilog

This PR improves support for Serilog as a logging target. The changes are in the Microsoft.Framework.Logging.Serilog adapter only.
There are a few changes rolled up here; I'm happy to split/squash/etc. as needed but thought I'd get the ball rolling and some feedback first.
The PR:

Fixes support for the ASP.NET Debug level and avoids a NotSupportedException
Uses the Serilog pipeline for message template formatting
Uses the Serilog pipeline for exception processing
Updates the Serilog package dependency to 1.5 (latest)

Of these, 1 & 4 are fairly self-explanatory - details of 2 & 3 below.
Message template formatting
ASP.NET Logging supports "Serilog-style {Message} templates" but uses its own formatting infrastructure to process these. In console/file output the difference is pretty much indistinguishable, but elsewhere this makes for a second-class Serilog experience.
Here's a "before" shot of the sample app, using the Literate Console sink which colors output via type information:

All of the messages show in blue because they're just strings; the "after" shot shows the difference, especially in the second message:

The example shows a cosmetic difference - it's nice to have a guide to what parts of a log event are going to be easily queryable later on - but other impacts are more fundamental to Serilog's usability.
For example, it's intended a Serilog user can silence an unwanted event with code like:
    .Filter.ByExcluding(le => {
        return le.MessageTemplate.Text == "Very {Noisy} Event";
    })

In effect:

the message template is Serilog's internal representation of the event type

The unmodified integration does not support this because all events use the same "{Message:l}" template.
The change made here to fix this does so by ignoring ASP.NET's built-in formatting; good compatibility with Serilog seems like a reasonable trade-off here.
(Sinks that are bandwidth-constrained will also benefit from removing the duplicated copy of each element of the message.)
Exception processing
Serilog has its own processing pipeline that allows users to serialize/interrogate exceptions for their own purposes, and many sinks have special handling for exceptions attached to log events. (You can see a trivial case again in the screenshots above.)
The unmodified integration formats the exception into the message text, and adds some helper properties to get back some of the structured exception data. This bloats the log event payload, and will also create headaches for log searches when some of an application's exceptions are logged via the standard property, and some use the ones introduced by ASP.NET.
The PR removes this and passes the exception through as-is, an approach enabled by the move away from built-in formatting discussed above.
Caveats
The change to property enrichment filters out the "{OriginalFormat}" property while stacking ForContext() calls; I don't think this will perform measurably worse than the eariler enricher-based version, but if optimization has been done here I can take it back in the custom-enricher direction
Anyone already dependent on the "Exception", "ExceptionMessage" and "ExceptionType" properties can get them back by adding the enricher below:
class AspNetStyleExceptionEnricher : ILogEventEnricher
{
    public void Enrich(ILogEvent logEvent, ILogEventPropertyFactory propertyFactory)
    {
        if (logEvent.Exception == null)
        {
            return;
        }

        logEvent.AddPropertyIfAbsent(propertyFactory.CreateProperty(
                    "Exception",
                    exception.ToString()));

        logEvent.AddPropertyIfAbsent(propertyFactory.CreateProperty(
                    "ExceptionType",
                    exception.GetType().FullName));

        logEvent.AddPropertyIfAbsent(propertyFactory.CreateProperty(
                    "ExceptionMessage",
                    exception.Message));
    }
}

Hi @nblumhardt, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla2.dotnetfoundation.org.

TTYL, DNFBOT;

Travis build seems to have failed in dnu pack but the error isn't related to anything I can see in the PR?
CLA signed an hour or so ago :)

@nblumhardt, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.
Thanks, DNFBOT;

@nblumhardt Ideally, this package wouldn't live in this repository. We did it to bootstrap the effort and validate our design. We want 3rd parties to own their logging components and extensions for the ILogger system.

Hey @davidfowl - that would be great; let me chat with the other Serilog project folks about the best place to bring it over.
I'd be happy to PR lifting it out, since I have this shiny new CLA burning a hole in my pocket..? :-)

Yep!

@nblumhardt if you can make a new home for the Serilog adapter we'd be happy to link to it from the Logging readme (or, of course, send a PR for that :smile: ).

Nearly there! An initial version of the package is on NuGet. Instructions and so forth are in the README at https://github.com/serilog/serilog-framework-logging
Couple of notes:
The most significant change is to the signature of UseSerilog() - it now accepts a Serilog.ILogger rather than a LoggerConfiguration. This is to allow framework and non-framework code to use the same logging pipeline.
If the ILogger is not passed, Serilog's default static Log will be used, so the simplest configuration now looks like:
// Set up Serilog
Log.Logger = new LoggerConfiguration().CreateLogger();

// Configure `m.f.Logging`
loggerFactory.UseSerilog();

Other than that, usage is the same, and output is pretty similar to what's in the PR branch.
One rough edge I'd love to avoid is the need to re-specify levels on both the Serilog and framework loggers. I am considering having:
loggerFactory.UseSerilog();

"Inherit" the Serilog level and apply it to the framework logger. I'm sure there are other options.
One last thing - is this pattern considered reasonable in ASP.NET code today?
Using string.Format() directly:
if (_logger.IsEnabled(LogLevel.Verbose))
{
    _logger.LogVerbose(string.Format("Copying file {0} to the response body", fileContext.SubPath));
}

instead of delegating to the logger:
if (_logger.IsEnabled(LogLevel.Verbose))
{
    _logger.LogVerbose("Copying file {0} to the response body", fileContext.SubPath);
}

means that event type and property information (e.g. SubPath) isn't available through the logging pipeline.

@nblumhardt should be called AddSerilog(). Use is for middleware, it's add here because you're adding a provider to the list of logger providers.

Ah, sorry - the mistake is in my comment. AddSerilog() is the method name :+1:

We've been moving more code to delegate to not call string.Format explicitly. That's leftover from before we had those methods.

Closing this PR, will open another for the sample removal and the wiki entry. Thanks @davidfowl and @Eilon for the input!

@nblumhardt open up the repo for bugs.

Done - # 1 is all yours: https://github.com/serilog/serilog-framework-logging/issues

Hey guys
Is it possible to set up serilog for azure function project?

Hi, it looks like you are   posting on a closed issue/PR/commit!
We're very likely to lose track of your bug/feedback/question unless you:

Open a new issue
Explain very clearly what you need help with
If you think you have found a bug, include detailed repro steps so that we can investigate the problem.


Problem with custom resource cookbook after upgrade to Chef Infra Client 16.2.44

Description
I am using managed_directory cookbook from Supermarket ( https://supermarket.chef.io/cookbooks/managed_directory ). It was working in Chef Infra 16.1. After upgrade to 16.2.44 I can not use depends cookbook_name in metadata.rb and then use its custom resource in recipe since I got:
[2020-06-18T09:50:06+02:00] FATAL: NoMethodError: undefined method managed_directory' for cookbook: cookbook_name, recipe: recipe_name :Chef::Recipe`
I tried adding include_recipe 'managed_directory' in the recipe in which I am trying to use the managed_directory resource, but to no avail.
Chef Version
16.2.44
Platform Version
CentOS 7
Replication Case
I believe that you just need to try and use custom resource cookbook and try to use its resource in a recipe.
Client Output
/var/chef/cache/cookbooks/cookbook_name/recipes/recipe_name.rb:

 84>> managed_directory '/directory' do
 85:    action :clean
 86:    clean_directories true
 87:    clean_links true
 88:    clean_files true
 89:  end

System Info:
------------
chef_version=16.2.44
platform=cloudlinux
platform_version=7.8
ruby=ruby 2.7.1p83 (2020-03-31 revision a0c7c23c9c) [x86_64-linux]
program_name=/usr/bin/chef-client
executable=/opt/chef/bin/chef-client

Running handlers:
[2020-06-18T09:50:06+02:00] ERROR: Running exception handlers
Running handlers complete
[2020-06-18T09:50:06+02:00] ERROR: Exception handlers complete
Chef Infra Client failed. 0 resources updated in 34 seconds
[2020-06-18T09:50:06+02:00] FATAL: Stacktrace dumped to /var/chef/cache/chef-stacktrace.out
[2020-06-18T09:50:06+02:00] FATAL: Please provide the contents of the stacktrace.out file if you file a bug report
[2020-06-18T09:50:06+02:00] DEBUG: NoMethodError: undefined method `managed_directory' for cookbook: cookbook_name, recipe: recipe_name :Chef::Recipe
/var/chef/cache/cookbooks/cookbook_name/recipes/recipe_name.rb:84:in `from_file'
/opt/chef/embedded/lib/ruby/gems/2.7.0/gems/chef-16.2.44/lib/chef/mixin/from_file.rb:34:in `instance_eval'
/opt/chef/embedded/lib/ruby/gems/2.7.0/gems/chef-16.2.44/lib/chef/mixin/from_file.rb:34:in `from_file'
/opt/chef/embedded/lib/ruby/gems/2.7.0/gems/chef-16.2.44/lib/chef/cookbook_version.rb:230:in `load_ruby_recipe'
/opt/chef/embedded/lib/ruby/gems/2.7.0/gems/chef-16.2.44/lib/chef/cookbook_version.rb:200:in `load_recipe'
/opt/chef/embedded/lib/ruby/gems/2.7.0/gems/chef-16.2.44/lib/chef/run_context.rb:393:in `load_recipe'
/opt/chef/embedded/lib/ruby/gems/2.7.0/gems/chef-16.2.44/lib/chef/run_context.rb:349:in `block in include_recipe'
/opt/chef/embedded/lib/ruby/gems/2.7.0/gems/chef-16.2.44/lib/chef/run_context.rb:348:in `each'
/opt/chef/embedded/lib/ruby/gems/2.7.0/gems/chef-16.2.44/lib/chef/run_context.rb:348:in `include_recipe'
/opt/chef/embedded/lib/ruby/gems/2.7.0/gems/chef-16.2.44/lib/chef/dsl/include_recipe.rb:26:in `include_recipe'
/var/chef/cache/cookbooks/cookbook_name/recipes/default.rb:43:in `from_file'
/opt/chef/embedded/lib/ruby/gems/2.7.0/gems/chef-16.2.44/lib/chef/mixin/from_file.rb:34:in `instance_eval'
/opt/chef/embedded/lib/ruby/gems/2.7.0/gems/chef-16.2.44/lib/chef/mixin/from_file.rb:34:in `from_file'
/opt/chef/embedded/lib/ruby/gems/2.7.0/gems/chef-16.2.44/lib/chef/cookbook_version.rb:230:in `load_ruby_recipe'
/opt/chef/embedded/lib/ruby/gems/2.7.0/gems/chef-16.2.44/lib/chef/cookbook_version.rb:200:in `load_recipe'
/opt/chef/embedded/lib/ruby/gems/2.7.0/gems/chef-16.2.44/lib/chef/run_context.rb:393:in `load_recipe'
/opt/chef/embedded/lib/ruby/gems/2.7.0/gems/chef-16.2.44/lib/chef/run_context/cookbook_compiler.rb:174:in `block in compile_recipes'
/opt/chef/embedded/lib/ruby/gems/2.7.0/gems/chef-16.2.44/lib/chef/run_context/cookbook_compiler.rb:171:in `each'
/opt/chef/embedded/lib/ruby/gems/2.7.0/gems/chef-16.2.44/lib/chef/run_context/cookbook_compiler.rb:171:in `compile_recipes'
/opt/chef/embedded/lib/ruby/gems/2.7.0/gems/chef-16.2.44/lib/chef/run_context/cookbook_compiler.rb:79:in `compile'
/opt/chef/embedded/lib/ruby/gems/2.7.0/gems/chef-16.2.44/lib/chef/run_context.rb:223:in `load'
/opt/chef/embedded/lib/ruby/gems/2.7.0/gems/chef-16.2.44/lib/chef/policy_builder/expand_node_object.rb:103:in `setup_run_context'
/opt/chef/embedded/lib/ruby/2.7.0/forwardable.rb:235:in `setup_run_context'
/opt/chef/embedded/lib/ruby/gems/2.7.0/gems/chef-16.2.44/lib/chef/client.rb:498:in `setup_run_context'
/opt/chef/embedded/lib/ruby/gems/2.7.0/gems/chef-16.2.44/lib/chef/client.rb:284:in `run'
/opt/chef/embedded/lib/ruby/gems/2.7.0/gems/chef-16.2.44/lib/chef/application.rb:292:in `run_with_graceful_exit_option'
/opt/chef/embedded/lib/ruby/gems/2.7.0/gems/chef-16.2.44/lib/chef/application.rb:268:in `block in run_chef_client'
/opt/chef/embedded/lib/ruby/gems/2.7.0/gems/chef-16.2.44/lib/chef/local_mode.rb:42:in `with_server_connectivity'
/opt/chef/embedded/lib/ruby/gems/2.7.0/gems/chef-16.2.44/lib/chef/application.rb:251:in `run_chef_client'
/opt/chef/embedded/lib/ruby/gems/2.7.0/gems/chef-16.2.44/lib/chef/application/base.rb:335:in `run_application'
/opt/chef/embedded/lib/ruby/gems/2.7.0/gems/chef-16.2.44/lib/chef/application.rb:68:in `run'
/opt/chef/embedded/lib/ruby/gems/2.7.0/gems/chef-bin-16.2.44/bin/chef-client:25:in `<top (required)>'
/usr/bin/chef-client:162:in `load'
/usr/bin/chef-client:162:in `<main>'
[2020-06-18T09:50:06+02:00] FATAL: NoMethodError: undefined method `managed_directory' for cookbook: cookbook_namel, recipe: recipe_name :Chef::Recipe

That's documented as a breaking change in the 16.2 release notes:
https://discourse.chef.io/t/chef-infra-client-16-2-released/17284
The change is here:
https://github.com/chef/chef/pull/9890
The issue with Chef 16.0 which prompted the change is linked in the ticket:
https://github.com/chef/chef/issues/9885
The reason why fixing #9885 was necessary this way was that it clearly is getting used and affects people AND the fact that anyone who hits that bug is going to need to talk to me, specifically, as the one person in the world to help them fix it -- which is unacceptable since I don't scale.  The alternative change in #9890 gets us to a world where the behavior is simple and the break is easily understandable, and where a cookstyle rule can be written to identify and fix the issue:
https://github.com/chef/cookstyle/blob/master/lib/rubocop/cop/chef/deprecation/resource_uses_only_resource_name.rb
We could not go 11 months without being able to cookstyle a rule to fix #9885, and forever have that as a blocker to people upgrading to 16 where cookstyle could never get them over the hurdle.

@lamont-granquist thanks for reply. I am trying to wrap my head around this. In other words, can I fix it by calling custom resource from other cookbook in some other way, or do I need to modify the cookbook with custom resource?


Update scan.ts

Otherwise this breaks
$brush.pipe(
    scan(
      (acc, curr) => acc.set(curr.dimension, curr.brush),
      new Map<D, Interval<number>>()
    )
  );

Thanks for opening the PR.
Having a another look at the typings for scan and reduce is on my list of things to do. There are a number of open issues that related to the scan typings: #3150 and #3879. Any changes to the scan typings should take those into account.
The change in this PR appears to be the same as the change suggested in #2897 - which was not merged. See the conversation in that PR for the reasons. I'm not saying that those reasons still apply - and I've not re-read the conversation recently - but it does provide some context.
IMO, now that the testing infrastructure supports dtslint, I don't think we should change the typings until we have dtslint-based tests that document/describe the current behaviour.
Also any changes to the scan typings will likely need to be made to the reduce typings, too.

Thanks for getting back to me so quickly. I'm going to close this PR then.
I just started using rxjs yesterday and tripped over this issue. I'll just set the types manually for now.

Well, hopefully, I've not discouraged you from contributing, as that wasn't my intention.
Anyway, I'll bump the priority of my writing some dtslint tests for scan and reduce, so that any changes we make to the typings need not be so scary.

Oh no, I'm not discouraged not at all. I know how open source development goes and I'm impressed how quickly you responded. Thanks for taking my request seriously!


Wrong url Github link in Azure Active Directory v2.0 authentication libraries

Link to article:
https://docs.microsoft.com/en-us/azure/active-directory/develop/reference-v2-libraries#microsoft-supported-client-libraries
Problem:
The link that is supposed to redirect the user to the MSAL.js github page, is instead redirecting the user to the MSAL angularJs page (https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/dev/lib/msal-angularjs/README.md)

Fixed.
#please-close


Public room - Concierge welcome message displayed several times for same account

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Go https://staging.new.expensify.com/
and login
Join public room by clicking https://staging.new.expensify.com/r/2660055103772983
Leave the room
Join the room again

Expected Result:
One Welcome message should be displayed for same account. It should be displayed for latest joining I guess.
Actual Result:
I see Concierge welcome message for each joining.
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[ ] Windows / Chrome
[ ] MacOS / Desktop

Version Number: <IP_ADDRESS>
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://user-images.githubusercontent.com/93399543/233865634-bef79c75-ce26-4d0a-acd0-159e852e5aed.mp4
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
View all open jobs on GitHub

Triggered auto assignment to @NicMendonca (Bug), see https://stackoverflow.com/c/expensify/questions/14418 for more details.

Bug0 Triage Checklist (Main S/O)

[ ] This "bug" occurs on a supported platform (ensure Platforms in OP are ✅)
[ ] This bug is not a duplicate report (check E/App issues and #expensify-bugs)

If it is, comment with a link to the original report, close the issue and add any novel details to the original issue instead

[ ] This bug is reproducible using the reproduction steps in the OP. S/O

If the reproduction steps are clear and you're unable to reproduce the bug, check with the reporter and QA first, then close the issue.
If the reproduction steps aren't clear and you determine the correct steps, please update the OP.

[ ] This issue is filled out as thoroughly and clearly as possible

Pay special attention to the title, results, platforms where the bug occurs, and if the bug happens on staging/production.

[ ] I have reviewed and subscribed to the linked Slack conversation to ensure Slack/Github stay in sync

I don't think it's a bug to be shown "welcome to the public room" when you've left/ re-joined. It's Concierge's call to action that were successfully added to the room. In OldDot when you're added/ removed / added back to a policy you are notified so I think its as expected.


Add code samples: use class expression to implements construct signature

Another simple way is to use class expressions:
interface ClockConstructor {
  new (hour: number, minute: number);
}

interface ClockInterface {
  tick();
}

const Clock: ClockConstructor = class Clock implements ClockInterface {
  constructor(h: number, m: number) {}
  tick() {
      console.log("beep beep");
  }
}

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


light source is not show

Hey, i use that code :
int result = LightAPI.get().setLightLevel(light.location.getWorld().getName(), light.type, light.location.getBlockX(), light.location.getBlockY(), light.location.getBlockZ(), light.level, EditPolicy.FORCE_IMMEDIATE, SendPolicy.IMMEDIATE, null);

		switch (result) {
		  case ResultCode.SUCCESS:
			  Main.getLog().log(Level.INFO, "Success " + result);
		    break;
		  case ResultCode.MOVED_TO_DEFERRED:
			  Main.getLog().log(Level.INFO, "Light moved " + result);
		    break;
		  default:
		    Main.getLog().log(Level.WARNING, "Something is wrong. Result code: " + result);
		    break;
		}

to create a light source but that problem is that it tell me "Success 0" but that light don't show and i have the last version of the plugin.

I call it in a function in an other class who manage every light and after I call this function in a onCommand.

Sorry, but I can't reproduce this problem. As a solution, I can suggest using other policies and make sure that there are no changes with blocks around the light source.

You know what i will post my plugin on github with the jar do you can see everything.

https://github.com/entonoire/LightManager/
by the way i'm on spigot 1.16.5

You incorrectly used arguments:
You used
(worldName, lightType, getBlockX(), getBlockY(), getBlockZ(), lightLevel)
And you need to use
(worldName, getBlockX(), getBlockY(), getBlockZ(), lightLevel, lightType)

No, I was looking at the old code
https://github.com/entonoire/LightManager/blob/old/src/fr/vallfeur/lme/Light.java#L49

Issue closed: LightAPI is no longer being maintained. Use LightBlock instead


Test-bot failed with "stable version should not decrease"

I have a fomula like this:
  if MacOS.version <= :el_capitan
    url "https://github.com/MaskRay/ccls.git",
        :tag => "0.20180812",
        :revision => "06aa25233567ae16a58a6f5237aacfd9e02aa29d"
  else
    url "https://github.com/MaskRay/ccls.git",
        :tag => "0.20180913",
        :revision => "56c6ec43dfd87ed2e44418b8d172307d87327a64"
  end

And then build each version with independent image:
matrix:
  include:
    - env: OSX=10.11
      compiler: clang
      osx_image: xcode8
    - env: OSX=10.12
      compiler: clang
      osx_image: xcode9.2

So far, everything is going well, all build jobs passed:

But after increasing the reversion from 0.20180913 to 0.20180924 for osx 10.12:
  if MacOS.version <= :el_capitan
    url "https://github.com/MaskRay/ccls.git",
        :tag => "0.20180812",
        :revision => "06aa25233567ae16a58a6f5237aacfd9e02aa29d"
  else
    url "https://github.com/MaskRay/ccls.git",
-       :tag => "0.20180913",
+       :tag => "0.20180924",
-       :revision => "56c6ec43dfd87ed2e44418b8d172307d87327a64"
+       :revision => "41fcc0272c8c93fcbe52f24ef587e633a9dcc7e1"
  end

I've got failure from job(OSX=10.11):
$ export OSX=10.11
...
$ if [ "$OSX" == "10.12" ]; then brew test-bot --skip-setup; else brew test-bot; fi
...
==> brew audit twlz0ne/ccls/ccls --online
...
Error: 1 problem in 1 formula detected
twlz0ne/ccls/ccls:
  * stable version should not decrease (from 0.20180913 to 0.20180812)
==> FAILED

I didn't change the reversion for osx 10.11, why prompting these? Seems the reversions are missed up.
And at the same time, the job(OSX=10.12) passed.

We don't support different versions per-OS in test-bot. We'll review a PR to fix this either here or in Homebrew/brew.


Problem with firebase messaging plugin

Create a new flutter project from Mac
Add the following plugins in pubspec.yaml

 sqflite: ^2.0.0+2
 shared_preferences: ^2.0.3
 path_provider: ^2.0.1
 font_awesome_flutter: ^8.11.0
 connectivity: ^3.0.2
 share: ^2.0.1
 http: ^0.13.0
 firebase_core: ^1.0.2
 firebase_dynamic_links: ^0.8.0

Run flutter pub run

Open Podfile and change version to 10.0
in terminal, go to iOS folder and type pod install
We can see the successful installation of pod
Now, add firebase_messaging: ^9.1.0
run flutter pub run and cd ios then pod install again, the compilation will fail now.

firebase_core: Using Firebase SDK version '7.3.0' defined in 'firebase_core'
firebase_dynamic_links: Using Firebase SDK version '7.3.0' defined in 'firebase_core'
firebase_messaging: Using Firebase SDK version '7.3.0' defined in 'firebase_core'
[!] CocoaPods could not find compatible versions for pod "firebase_core":
In Podfile:
firebase_core (from .symlinks/plugins/firebase_core/ios)
Specs satisfying the firebase_core (from .symlinks/plugins/firebase_core/ios) dependency were found, but they required a higher minimum deployment target.

@maheshkumar2150
firebase is a 3rd party plugin, please open an issue in the dedicated github
or provide your flutter doctor -v, your flutter run -v
and a minimal reproducible code sample without 3rd party plugins

flutter doctor -v
[✓] Flutter (Channel stable, 2.0.3, on macOS 11.2.3 20D91 darwin-x64, locale en-GB)
• Flutter version 2.0.3 at /Users/mahesh/DevLibrary/flutter_sdk/flutter
• Framework revision 4d7946a68d (2 weeks ago), 2021-03-18 17:24:33 -0700
• Engine revision 3459eb2436
• Dart version 2.12.2
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
• Android SDK at /Users/mahesh/DevLibrary/android_sdk
• Platform android-30, build-tools 30.0.3
• Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
• All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS
• Xcode at /Applications/Xcode.app/Contents/Developer
• Xcode 12.4, Build version 12D4e
• CocoaPods version 1.10.1
[✓] Chrome - develop for the web
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[✓] Android Studio (version 4.1)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
🔨 https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
[✓] VS Code (version 1.55.0)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.21.0
[✓] Connected device (1 available)
• Chrome (web) • chrome • web-javascript • Google Chrome 89.0.4389.114
• No issues found!

[ +107 ms] executing: [/Users/mahesh/DevLibrary/flutter_sdk/flutter/] git -c log.showSignature=false log -n 1 --pretty=format:%H
[  +61 ms] Exit code 0 from: git -c log.showSignature=false log -n 1 --pretty=format:%H
[   +2 ms] 4d7946a68d26794349189cf21b3f68cc6fe61dcb
[        ] executing: [/Users/mahesh/DevLibrary/flutter_sdk/flutter/] git tag --points-at 4d7946a68d26794349189cf21b3f68cc6fe61dcb
[  +32 ms] Exit code 0 from: git tag --points-at 4d7946a68d26794349189cf21b3f68cc6fe61dcb
[        ] 2.0.3
[  +56 ms] executing: [/Users/mahesh/DevLibrary/flutter_sdk/flutter/] git rev-parse --abbrev-ref --symbolic @{u}
[  +18 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[        ] origin/stable
[        ] executing: [/Users/mahesh/DevLibrary/flutter_sdk/flutter/] git ls-remote --get-url origin
[  +17 ms] Exit code 0 from: git ls-remote --get-url origin
[        ] https://github.com/flutter/flutter.git
[  +66 ms] executing: [/Users/mahesh/DevLibrary/flutter_sdk/flutter/] git rev-parse --abbrev-ref HEAD
[  +19 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[        ] stable
[   +8 ms] executing: sw_vers -productName
[  +19 ms] Exit code 0 from: sw_vers -productName
[        ] macOS
[        ] executing: sw_vers -productVersion
[  +17 ms] Exit code 0 from: sw_vers -productVersion
[        ] 11.2.3
[        ] executing: sw_vers -buildVersion
[  +17 ms] Exit code 0 from: sw_vers -buildVersion
[        ] 20D91
[   +8 ms] executing: sysctl hw.optional.arm64
[   +7 ms] Exit code 1 from: sysctl hw.optional.arm64
[        ] sysctl: unknown oid 'hw.optional.arm64'
[  +92 ms] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[   +2 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[  +60 ms] executing: /Users/mahesh/DevLibrary/android_sdk/platform-tools/adb devices -l
[   +9 ms] executing: /usr/bin/xcode-select --print-path
[   +8 ms] Exit code 0 from: /usr/bin/xcode-select --print-path
[        ] /Applications/Xcode.app/Contents/Developer
[   +6 ms] executing: sysctl hw.optional.arm64
[   +4 ms] Exit code 1 from: sysctl hw.optional.arm64
[        ] sysctl: unknown oid 'hw.optional.arm64'
[        ] executing: xcrun xcodebuild -version
[ +240 ms] Exit code 0 from: xcrun xcodebuild -version
[        ] Xcode 12.4
Build version 12D4e
[   +3 ms] executing: xcrun xcdevice list --timeout 2
[   +4 ms] xcrun simctl list --json devices
[        ] executing: xcrun simctl list --json devices
[  +66 ms] List of devices attached
[ +139 ms] {
"devices" : {
"com.apple.CoreSimulator.SimRuntime.tvOS-14-3" : [
{
"dataPath" : "/Users/mahesh/Library/Developer/CoreSimulator/Devices/996D6E42-CE35-4ED7-85BA-5E751D2A03F9/data",
"logPath" : "/Users/mahesh/Library/Logs/CoreSimulator/996D6E42-CE35-4ED7-85BA-5E751D2A03F9",
"udid" : "996D6E42-CE35-4ED7-85BA-5E751D2A03F9",
"isAvailable" : true,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-TV-1080p",
"state" : "Shutdown",
"name" : "Apple TV"
},
{
"dataPath" : "/Users/mahesh/Library/Developer/CoreSimulator/Devices/2F4586AA-57EE-4AFE-ADED-16A218E807EB/data",
"logPath" : "/Users/mahesh/Library/Logs/CoreSimulator/2F4586AA-57EE-4AFE-ADED-16A218E807EB",
"udid" : "2F4586AA-57EE-4AFE-ADED-16A218E807EB",
"isAvailable" : true,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-TV-4K-4K",
"state" : "Shutdown",
"name" : "Apple TV 4K"
},
{
"dataPath" : "/Users/mahesh/Library/Developer/CoreSimulator/Devices/3A547177-F215-4BE8-8ECB-D4027C1596AE/data",
"logPath" : "/Users/mahesh/Library/Logs/CoreSimulator/3A547177-F215-4BE8-8ECB-D4027C1596AE",
"udid" : "3A547177-F215-4BE8-8ECB-D4027C1596AE",
"isAvailable" : true,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-TV-4K-1080p",
"state" : "Shutdown",
"name" : "Apple TV 4K (at 1080p)"
}
],
"com.apple.CoreSimulator.SimRuntime.watchOS-7-2" : [
{
"dataPath" : "/Users/mahesh/Library/Developer/CoreSimulator/Devices/9BAB6894-BE7F-493B-A3DE-C0AB4987CD89/data",
"logPath" : "/Users/mahesh/Library/Logs/CoreSimulator/9BAB6894-BE7F-493B-A3DE-C0AB4987CD89",
"udid" : "9BAB6894-BE7F-493B-A3DE-C0AB4987CD89",
"isAvailable" : true,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-Watch-Series-5-40mm",
"state" : "Shutdown",
"name" : "Apple Watch Series 5 - 40mm"
},
{
"dataPath" : "/Users/mahesh/Library/Developer/CoreSimulator/Devices/119E9465-F360-4BE3-A8AA-43CDC2816735/data",
"logPath" : "/Users/mahesh/Library/Logs/CoreSimulator/119E9465-F360-4BE3-A8AA-43CDC2816735",
"udid" : "119E9465-F360-4BE3-A8AA-43CDC2816735",
"isAvailable" : true,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-Watch-Series-5-44mm",
"state" : "Shutdown",
"name" : "Apple Watch Series 5 - 44mm"
},
{
"dataPath" : "/Users/mahesh/Library/Developer/CoreSimulator/Devices/211E2966-4699-47EE-93EB-EC8D0A8C3F65/data",
"logPath" : "/Users/mahesh/Library/Logs/CoreSimulator/211E2966-4699-47EE-93EB-EC8D0A8C3F65",
"udid" : "211E2966-4699-47EE-93EB-EC8D0A8C3F65",
"isAvailable" : true,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-Watch-Series-6-40mm",
"state" : "Shutdown",
"name" : "Apple Watch Series 6 - 40mm"
},
{
"dataPath" : "/Users/mahesh/Library/Developer/CoreSimulator/Devices/63C5DEB6-EE15-47B6-8AF6-6A6AD5991EEF/data",
"logPath" : "/Users/mahesh/Library/Logs/CoreSimulator/63C5DEB6-EE15-47B6-8AF6-6A6AD5991EEF",
"udid" : "63C5DEB6-EE15-47B6-8AF6-6A6AD5991EEF",
"isAvailable" : true,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.Apple-Watch-Series-6-44mm",
"state" : "Shutdown",
"name" : "Apple Watch Series 6 - 44mm"
}
],
"com.apple.CoreSimulator.SimRuntime.iOS-14-4" : [
{
"dataPath" : "/Users/mahesh/Library/Developer/CoreSimulator/Devices/AC96118A-7F68-4D8C-B2A6-7F2218BB17DD/data",
"logPath" : "/Users/mahesh/Library/Logs/CoreSimulator/AC96118A-7F68-4D8C-B2A6-7F2218BB17DD",
"udid" : "AC96118A-7F68-4D8C-B2A6-7F2218BB17DD",
"isAvailable" : true,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-8",
"state" : "Shutdown",
"name" : "iPhone 8"
},
{
"dataPath" : "/Users/mahesh/Library/Developer/CoreSimulator/Devices/4721A373-3F76-4C4C-AFCF-5C5545856905/data",
"logPath" : "/Users/mahesh/Library/Logs/CoreSimulator/4721A373-3F76-4C4C-AFCF-5C5545856905",
"udid" : "4721A373-3F76-4C4C-AFCF-5C5545856905",
"isAvailable" : true,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-8-Plus",
"state" : "Shutdown",
"name" : "iPhone 8 Plus"
},
{
"dataPath" : "/Users/mahesh/Library/Developer/CoreSimulator/Devices/E11EE158-2C0A-4B69-ADCC-C0C863D5F4A0/data",
"logPath" : "/Users/mahesh/Library/Logs/CoreSimulator/E11EE158-2C0A-4B69-ADCC-C0C863D5F4A0",
"udid" : "E11EE158-2C0A-4B69-ADCC-C0C863D5F4A0",
"isAvailable" : true,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-11",
"state" : "Shutdown",
"name" : "iPhone 11"
},
{
"dataPath" : "/Users/mahesh/Library/Developer/CoreSimulator/Devices/CFB4DCCE-0D4B-43F5-A944-A08FBB7CE606/data",
"logPath" : "/Users/mahesh/Library/Logs/CoreSimulator/CFB4DCCE-0D4B-43F5-A944-A08FBB7CE606",
"udid" : "CFB4DCCE-0D4B-43F5-A944-A08FBB7CE606",
"isAvailable" : true,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-11-Pro",
"state" : "Shutdown",
"name" : "iPhone 11 Pro"
},
{
"dataPath" : "/Users/mahesh/Library/Developer/CoreSimulator/Devices/B083B122-F9C0-4B66-A596-E818125E78EE/data",
"logPath" : "/Users/mahesh/Library/Logs/CoreSimulator/B083B122-F9C0-4B66-A596-E818125E78EE",
"udid" : "B083B122-F9C0-4B66-A596-E818125E78EE",
"isAvailable" : true,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-11-Pro-Max",
"state" : "Shutdown",
"name" : "iPhone 11 Pro Max"
},
{
"dataPath" : "/Users/mahesh/Library/Developer/CoreSimulator/Devices/3C82DF1B-8B66-4A17-810F-CECF05148F17/data",
"logPath" : "/Users/mahesh/Library/Logs/CoreSimulator/3C82DF1B-8B66-4A17-810F-CECF05148F17",
"udid" : "3C82DF1B-8B66-4A17-810F-CECF05148F17",
"isAvailable" : true,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-SE--2nd-generation-",
"state" : "Shutdown",
"name" : "iPhone SE (2nd generation)"
},
{
"dataPath" : "/Users/mahesh/Library/Developer/CoreSimulator/Devices/785A74EB-A4D5-4E90-A7BF-6A3510905A83/data",
"logPath" : "/Users/mahesh/Library/Logs/CoreSimulator/785A74EB-A4D5-4E90-A7BF-6A3510905A83",
"udid" : "785A74EB-A4D5-4E90-A7BF-6A3510905A83",
"isAvailable" : true,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-12-mini",
"state" : "Shutdown",
"name" : "iPhone 12 mini"
},
{
"dataPath" : "/Users/mahesh/Library/Developer/CoreSimulator/Devices/0138A1CC-22D8-4A83-9AFB-2975687063C6/data",
"logPath" : "/Users/mahesh/Library/Logs/CoreSimulator/0138A1CC-22D8-4A83-9AFB-2975687063C6",
"udid" : "0138A1CC-22D8-4A83-9AFB-2975687063C6",
"isAvailable" : true,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-12",
"state" : "Shutdown",
"name" : "iPhone 12"
},
{
"dataPath" : "/Users/mahesh/Library/Developer/CoreSimulator/Devices/39909246-F780-414F-BC2F-BA93146B2F53/data",
"logPath" : "/Users/mahesh/Library/Logs/CoreSimulator/39909246-F780-414F-BC2F-BA93146B2F53",
"udid" : "39909246-F780-414F-BC2F-BA93146B2F53",
"isAvailable" : true,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-12-Pro",
"state" : "Shutdown",
"name" : "iPhone 12 Pro"
},
{
"dataPath" : "/Users/mahesh/Library/Developer/CoreSimulator/Devices/4BF95EED-5F24-4425-A766-9908661A182B/data",
"logPath" : "/Users/mahesh/Library/Logs/CoreSimulator/4BF95EED-5F24-4425-A766-9908661A182B",
"udid" : "4BF95EED-5F24-4425-A766-9908661A182B",
"isAvailable" : true,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPhone-12-Pro-Max",
"state" : "Shutdown",
"name" : "iPhone 12 Pro Max"
},
{
"dataPath" : "/Users/mahesh/Library/Developer/CoreSimulator/Devices/7E59B903-F592-4960-A4C0-3456726C867C/data",
"logPath" : "/Users/mahesh/Library/Logs/CoreSimulator/7E59B903-F592-4960-A4C0-3456726C867C",
"udid" : "7E59B903-F592-4960-A4C0-3456726C867C",
"isAvailable" : true,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPod-touch--7th-generation-",
"state" : "Shutdown",
"name" : "iPod touch (7th generation)"
},
{
"dataPath" : "/Users/mahesh/Library/Developer/CoreSimulator/Devices/353E755B-B604-4A31-972F-AFCF5E03486C/data",
"logPath" : "/Users/mahesh/Library/Logs/CoreSimulator/353E755B-B604-4A31-972F-AFCF5E03486C",
"udid" : "353E755B-B604-4A31-972F-AFCF5E03486C",
"isAvailable" : true,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPad-Pro--9-7-inch-",
"state" : "Shutdown",
"name" : "iPad Pro (9.7-inch)"
},
{
"dataPath" : "/Users/mahesh/Library/Developer/CoreSimulator/Devices/98694C5E-4B21-4672-BDF2-4F3834E8004B/data",
"logPath" : "/Users/mahesh/Library/Logs/CoreSimulator/98694C5E-4B21-4672-BDF2-4F3834E8004B",
"udid" : "98694C5E-4B21-4672-BDF2-4F3834E8004B",
"isAvailable" : true,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPad-Pro--11-inch---2nd-generation-",
"state" : "Shutdown",
"name" : "iPad Pro (11-inch) (2nd generation)"
},
{
"dataPath" : "/Users/mahesh/Library/Developer/CoreSimulator/Devices/9C6DE855-7245-4CC6-B9AE-6C60573EE147/data",
"logPath" : "/Users/mahesh/Library/Logs/CoreSimulator/9C6DE855-7245-4CC6-B9AE-6C60573EE147",
"udid" : "9C6DE855-7245-4CC6-B9AE-6C60573EE147",
"isAvailable" : true,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPad-Pro--12-9-inch---4th-generation-",
"state" : "Shutdown",
"name" : "iPad Pro (12.9-inch) (4th generation)"
},
{
"dataPath" : "/Users/mahesh/Library/Developer/CoreSimulator/Devices/39D0761E-8AC3-494A-8429-8F25B118CFC7/data",
"logPath" : "/Users/mahesh/Library/Logs/CoreSimulator/39D0761E-8AC3-494A-8429-8F25B118CFC7",
"udid" : "39D0761E-8AC3-494A-8429-8F25B118CFC7",
"isAvailable" : true,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPad--8th-generation-",
"state" : "Shutdown",
"name" : "iPad (8th generation)"
},
{
"dataPath" : "/Users/mahesh/Library/Developer/CoreSimulator/Devices/42E20446-BCC1-47F6-AC72-5C9438C70D21/data",
"logPath" : "/Users/mahesh/Library/Logs/CoreSimulator/42E20446-BCC1-47F6-AC72-5C9438C70D21",
"udid" : "42E20446-BCC1-47F6-AC72-5C9438C70D21",
"isAvailable" : true,
"deviceTypeIdentifier" : "com.apple.CoreSimulator.SimDeviceType.iPad-Air--4th-generation-",
"state" : "Shutdown",
"name" : "iPad Air (4th generation)"
}
]
}
}
[+2954 ms] [
{
"simulator" : true,
"operatingSystemVersion" : "14.4 (18D46)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone13,4",
"identifier" : "4BF95EED-5F24-4425-A766-9908661A182B",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-12-pro-max-1",
"modelName" : "iPhone 12 Pro Max",
"name" : "iPhone 12 Pro Max"
},
{
"simulator" : true,
"operatingSystemVersion" : "14.3 (18K559)",
"available" : true,
"platform" : "com.apple.platform.appletvsimulator",
"modelCode" : "AppleTV6,2",
"identifier" : "2F4586AA-57EE-4AFE-ADED-16A218E807EB",
"architecture" : "x86_64",
"modelUTI" : "com.apple.apple-tv-4k",
"modelName" : "Apple TV 4K",
"name" : "Apple TV 4K"
},
{
"simulator" : true,
"operatingSystemVersion" : "14.4 (18D46)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPad11,7",
"identifier" : "39D0761E-8AC3-494A-8429-8F25B118CFC7",
"architecture" : "x86_64",
"modelUTI" : "com.apple.ipad-8-wwan-1",
"modelName" : "iPad (8th generation)",
"name" : "iPad (8th generation)"
},
{
"simulator" : true,
"operatingSystemVersion" : "14.4 (18D46)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPad8,9",
"identifier" : "98694C5E-4B21-4672-BDF2-4F3834E8004B",
"architecture" : "x86_64",
"modelUTI" : "com.apple.ipad-pro-11-2nd-1",
"modelName" : "iPad Pro (11-inch) (2nd generation)",
"name" : "iPad Pro (11-inch) (2nd generation)"
},
{
"simulator" : true,
"operatingSystemVersion" : "14.4 (18D46)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone12,3",
"identifier" : "CFB4DCCE-0D4B-43F5-A944-A08FBB7CE606",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-11-pro-1",
"modelName" : "iPhone 11 Pro",
"name" : "iPhone 11 Pro"
},
{
"simulator" : true,
"operatingSystemVersion" : "7.2 (18S561)",
"available" : true,
"platform" : "com.apple.platform.watchsimulator",
"modelCode" : "Watch5,4",
"identifier" : "119E9465-F360-4BE3-A8AA-43CDC2816735",
"architecture" : "x86_64",
"modelUTI" : "com.apple.watch-series5-1",
"modelName" : "Apple Watch Series 5 - 44mm",
"name" : "Apple Watch Series 5 - 44mm"
},
{
"simulator" : true,
"operatingSystemVersion" : "14.3 (18K559)",
"available" : true,
"platform" : "com.apple.platform.appletvsimulator",
"modelCode" : "AppleTV6,2",
"identifier" : "3A547177-F215-4BE8-8ECB-D4027C1596AE",
"architecture" : "x86_64",
"modelUTI" : "com.apple.apple-tv-4k",
"modelName" : "Apple TV 4K (at 1080p)",
"name" : "Apple TV 4K (at 1080p)"
},
{
"simulator" : true,
"operatingSystemVersion" : "14.3 (18K559)",
"available" : true,
"platform" : "com.apple.platform.appletvsimulator",
"modelCode" : "AppleTV5,3",
"identifier" : "996D6E42-CE35-4ED7-85BA-5E751D2A03F9",
"architecture" : "x86_64",
"modelUTI" : "com.apple.apple-tv-4",
"modelName" : "Apple TV",
"name" : "Apple TV"
},
{
"simulator" : true,
"operatingSystemVersion" : "7.2 (18S561)",
"available" : true,
"platform" : "com.apple.platform.watchsimulator",
"modelCode" : "Watch5,3",
"identifier" : "9BAB6894-BE7F-493B-A3DE-C0AB4987CD89",
"architecture" : "x86_64",
"modelUTI" : "com.apple.watch-series5-1",
"modelName" : "Apple Watch Series 5 - 40mm",
"name" : "Apple Watch Series 5 - 40mm"
},
{
"simulator" : true,
"operatingSystemVersion" : "14.4 (18D46)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone10,5",
"identifier" : "4721A373-3F76-4C4C-AFCF-5C5545856905",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-8-plus-2",
"modelName" : "iPhone 8 Plus",
"name" : "iPhone 8 Plus"
},
{
"simulator" : true,
"operatingSystemVersion" : "14.4 (18D46)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone10,4",
"identifier" : "AC96118A-7F68-4D8C-B2A6-7F2218BB17DD",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-8-2",
"modelName" : "iPhone 8",
"name" : "iPhone 8"
},
{
"simulator" : true,
"operatingSystemVersion" : "7.2 (18S561)",
"available" : true,
"platform" : "com.apple.platform.watchsimulator",
"modelCode" : "Watch6,1",
"identifier" : "211E2966-4699-47EE-93EB-EC8D0A8C3F65",
"architecture" : "x86_64",
"modelUTI" : "com.apple.watch-series6-1",
"modelName" : "Apple Watch Series 6 - 40mm",
"name" : "Apple Watch Series 6 - 40mm"
},
{
"simulator" : true,
"operatingSystemVersion" : "14.4 (18D46)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone12,1",
"identifier" : "E11EE158-2C0A-4B69-ADCC-C0C863D5F4A0",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-11-1",
"modelName" : "iPhone 11",
"name" : "iPhone 11"
},
{
"simulator" : true,
"operatingSystemVersion" : "14.4 (18D46)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone12,8",
"identifier" : "3C82DF1B-8B66-4A17-810F-CECF05148F17",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-se-1",
"modelName" : "iPhone SE (2nd generation)",
"name" : "iPhone SE (2nd generation)"
},
{
"simulator" : true,
"operatingSystemVersion" : "7.2 (18S561)",
"available" : true,
"platform" : "com.apple.platform.watchsimulator",
"modelCode" : "Watch6,2",
"identifier" : "63C5DEB6-EE15-47B6-8AF6-6A6AD5991EEF",
"architecture" : "x86_64",
"modelUTI" : "com.apple.watch-series6-1",
"modelName" : "Apple Watch Series 6 - 44mm",
"name" : "Apple Watch Series 6 - 44mm"
},
{
"simulator" : true,
"operatingSystemVersion" : "14.4 (18D46)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone12,5",
"identifier" : "B083B122-F9C0-4B66-A596-E818125E78EE",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-11-pro-max-1",
"modelName" : "iPhone 11 Pro Max",
"name" : "iPhone 11 Pro Max"
},
{
"simulator" : true,
"operatingSystemVersion" : "14.4 (18D46)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPad13,2",
"identifier" : "42E20446-BCC1-47F6-AC72-5C9438C70D21",
"architecture" : "x86_64",
"modelUTI" : "com.apple.ipad-air4-1",
"modelName" : "iPad Air (4th generation)",
"name" : "iPad Air (4th generation)"
},
{
"simulator" : true,
"operatingSystemVersion" : "14.4 (18D46)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone13,2",
"identifier" : "0138A1CC-22D8-4A83-9AFB-2975687063C6",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-12-1",
"modelName" : "iPhone 12",
"name" : "iPhone 12"
},
{
"simulator" : true,
"operatingSystemVersion" : "14.4 (18D46)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPad6,4",
"identifier" : "353E755B-B604-4A31-972F-AFCF5E03486C",
"architecture" : "x86_64",
"modelUTI" : "com.apple.ipad-pro-9point7-a1674-b9b7ba",
"modelName" : "iPad Pro (9.7-inch)",
"name" : "iPad Pro (9.7-inch)"
},
{
"simulator" : true,
"operatingSystemVersion" : "14.4 (18D46)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPod9,1",
"identifier" : "7E59B903-F592-4960-A4C0-3456726C867C",
"architecture" : "x86_64",
"modelUTI" : "com.apple.ipod-touch-7-2",
"modelName" : "iPod touch (7th generation)",
"name" : "iPod touch (7th generation)"
},
{
"simulator" : true,
"operatingSystemVersion" : "14.4 (18D46)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPad8,12",
"identifier" : "9C6DE855-7245-4CC6-B9AE-6C60573EE147",
"architecture" : "x86_64",
"modelUTI" : "com.apple.ipad-pro-12point9-4th-1",
"modelName" : "iPad Pro (12.9-inch) (4th generation)",
"name" : "iPad Pro (12.9-inch) (4th generation)"
},
{
"simulator" : true,
"operatingSystemVersion" : "14.4 (18D46)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone13,1",
"identifier" : "785A74EB-A4D5-4E90-A7BF-6A3510905A83",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-12-mini-1",
"modelName" : "iPhone 12 mini",
"name" : "iPhone 12 mini"
},
{
"simulator" : true,
"operatingSystemVersion" : "14.4 (18D46)",
"available" : true,
"platform" : "com.apple.platform.iphonesimulator",
"modelCode" : "iPhone13,3",
"identifier" : "39909246-F780-414F-BC2F-BA93146B2F53",
"architecture" : "x86_64",
"modelUTI" : "com.apple.iphone-12-pro-1",
"modelName" : "iPhone 12 Pro",
"name" : "iPhone 12 Pro"
}
]
[   +5 ms] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[   +1 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[  +98 ms] Skipping pub get: version match.
[  +22 ms] Found plugin admob_flutter at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/admob_flutter-1.0.1/
[  +19 ms] Found plugin connectivity at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/connectivity-3.0.3/
[   +6 ms] Found plugin connectivity_for_web at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/connectivity_for_web-0.4.0/
[   +3 ms] Found plugin connectivity_macos at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/connectivity_macos-0.2.0/
[  +13 ms] Found plugin firebase_core at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_core-1.0.2/
[   +4 ms] Found plugin firebase_core_web at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_core_web-1.0.2/
[   +2 ms] Found plugin firebase_dynamic_links at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_dynamic_links-0.8.0/
[   +3 ms] Found plugin firebase_messaging at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_messaging-9.1.0/
[   +5 ms] Found plugin firebase_messaging_web at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_messaging_web-1.0.3/
[  +17 ms] Found plugin path_provider at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/path_provider-2.0.1/
[   +2 ms] Found plugin path_provider_linux at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/path_provider_linux-2.0.0/
[   +2 ms] Found plugin path_provider_macos at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/path_provider_macos-2.0.0/
[   +4 ms] Found plugin path_provider_windows at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/path_provider_windows-2.0.0/
[   +9 ms] Found plugin share at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/share-2.0.1/
[   +3 ms] Found plugin shared_preferences at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/shared_preferences-2.0.5/
[   +2 ms] Found plugin shared_preferences_linux at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/shared_preferences_linux-2.0.0/
[   +1 ms] Found plugin shared_preferences_macos at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/shared_preferences_macos-2.0.0/
[   +4 ms] Found plugin shared_preferences_web at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/shared_preferences_web-2.0.0/
[   +1 ms] Found plugin shared_preferences_windows at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/shared_preferences_windows-2.0.0/
[   +3 ms] Found plugin sqflite at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/sqflite-2.0.0+3/
[ +128 ms] Found plugin admob_flutter at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/admob_flutter-1.0.1/
[   +7 ms] Found plugin connectivity at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/connectivity-3.0.3/
[   +1 ms] Found plugin connectivity_for_web at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/connectivity_for_web-0.4.0/
[   +1 ms] Found plugin connectivity_macos at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/connectivity_macos-0.2.0/
[   +7 ms] Found plugin firebase_core at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_core-1.0.2/
[   +2 ms] Found plugin firebase_core_web at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_core_web-1.0.2/
[   +2 ms] Found plugin firebase_dynamic_links at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_dynamic_links-0.8.0/
[   +1 ms] Found plugin firebase_messaging at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_messaging-9.1.0/
[   +2 ms] Found plugin firebase_messaging_web at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_messaging_web-1.0.3/
[  +11 ms] Found plugin path_provider at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/path_provider-2.0.1/
[   +1 ms] Found plugin path_provider_linux at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/path_provider_linux-2.0.0/
[   +1 ms] Found plugin path_provider_macos at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/path_provider_macos-2.0.0/
[   +1 ms] Found plugin path_provider_windows at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/path_provider_windows-2.0.0/
[   +4 ms] Found plugin share at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/share-2.0.1/
[   +1 ms] Found plugin shared_preferences at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/shared_preferences-2.0.5/
[   +1 ms] Found plugin shared_preferences_linux at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/shared_preferences_linux-2.0.0/
[   +1 ms] Found plugin shared_preferences_macos at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/shared_preferences_macos-2.0.0/
[   +2 ms] Found plugin shared_preferences_web at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/shared_preferences_web-2.0.0/
[   +1 ms] Found plugin shared_preferences_windows at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/shared_preferences_windows-2.0.0/
[   +1 ms] Found plugin sqflite at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/sqflite-2.0.0+3/
[  +25 ms] Generating /Users/mahesh/development/flutter/ttt/android/app/src/main/java/io/flutter/plugins/GeneratedPluginRegistrant.java
[ +221 ms] Launching lib/main.dart on Chrome in debug mode...
[ +187 ms] Updating assets
[ +136 ms] Waiting for connection from debug service on Chrome...
[   +6 ms] Found plugin admob_flutter at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/admob_flutter-1.0.1/
[   +6 ms] Found plugin connectivity at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/connectivity-3.0.3/
[   +1 ms] Found plugin connectivity_for_web at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/connectivity_for_web-0.4.0/
[        ] Found plugin connectivity_macos at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/connectivity_macos-0.2.0/
[   +5 ms] Found plugin firebase_core at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_core-1.0.2/
[   +1 ms] Found plugin firebase_core_web at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_core_web-1.0.2/
[   +1 ms] Found plugin firebase_dynamic_links at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_dynamic_links-0.8.0/
[   +1 ms] Found plugin firebase_messaging at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_messaging-9.1.0/
[   +2 ms] Found plugin firebase_messaging_web at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_messaging_web-1.0.3/
[  +10 ms] Found plugin path_provider at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/path_provider-2.0.1/
[   +1 ms] Found plugin path_provider_linux at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/path_provider_linux-2.0.0/
[        ] Found plugin path_provider_macos at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/path_provider_macos-2.0.0/
[   +2 ms] Found plugin path_provider_windows at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/path_provider_windows-2.0.0/
[   +3 ms] Found plugin share at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/share-2.0.1/
[   +1 ms] Found plugin shared_preferences at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/shared_preferences-2.0.5/
[   +1 ms] Found plugin shared_preferences_linux at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/shared_preferences_linux-2.0.0/
[   +1 ms] Found plugin shared_preferences_macos at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/shared_preferences_macos-2.0.0/
[   +3 ms] Found plugin shared_preferences_web at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/shared_preferences_web-2.0.0/
[   +1 ms] Found plugin shared_preferences_windows at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/shared_preferences_windows-2.0.0/
[   +1 ms] Found plugin sqflite at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/sqflite-2.0.0+3/
[  +22 ms] Found plugin admob_flutter at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/admob_flutter-1.0.1/
[   +4 ms] Found plugin connectivity at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/connectivity-3.0.3/
[   +2 ms] Found plugin connectivity_for_web at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/connectivity_for_web-0.4.0/
[   +1 ms] Found plugin connectivity_macos at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/connectivity_macos-0.2.0/
[   +3 ms] Found plugin firebase_core at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_core-1.0.2/
[   +1 ms] Found plugin firebase_core_web at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_core_web-1.0.2/
[        ] Found plugin firebase_dynamic_links at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_dynamic_links-0.8.0/
[        ] Found plugin firebase_messaging at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_messaging-9.1.0/
[   +1 ms] Found plugin firebase_messaging_web at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/firebase_messaging_web-1.0.3/
[   +6 ms] Found plugin path_provider at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/path_provider-2.0.1/
[   +1 ms] Found plugin path_provider_linux at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/path_provider_linux-2.0.0/
[        ] Found plugin path_provider_macos at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/path_provider_macos-2.0.0/
[   +1 ms] Found plugin path_provider_windows at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/path_provider_windows-2.0.0/
[   +3 ms] Found plugin share at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/share-2.0.1/
[   +1 ms] Found plugin shared_preferences at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/shared_preferences-2.0.5/
[        ] Found plugin shared_preferences_linux at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/shared_preferences_linux-2.0.0/
[        ] Found plugin shared_preferences_macos at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/shared_preferences_macos-2.0.0/
[   +1 ms] Found plugin shared_preferences_web at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/shared_preferences_web-2.0.0/
[   +1 ms] Found plugin shared_preferences_windows at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/shared_preferences_windows-2.0.0/
[   +2 ms] Found plugin sqflite at /Users/mahesh/DevLibrary/flutter_sdk/flutter/.pub-cache/hosted/pub.dartlang.org/sqflite-2.0.0+3/
[ +108 ms] <- reset
[  +16 ms] /Users/mahesh/DevLibrary/flutter_sdk/flutter/bin/cache/dart-sdk/bin/dart --disable-dart-dev /Users/mahesh/DevLibrary/flutter_sdk/flutter/bin/cache/artifacts/engine/darwin-x64/frontend_server.dart.snapshot --sdk-root /Users/mahesh/DevLibrary/flutter_sdk/flutter/bin/cache/flutter_web_sdk/ --incremental --target=dartdevc --debugger-module-names --experimental-emit-debug-metadata -DFLUTTER_WEB_AUTO_DETECT=true --output-dill /var/folders/5s/5bzzk2fs6jdd7kpyns96xlvw0000gn/T/flutter_tools.wsUduH/flutter_tool.0QNFAO/app.dill --libraries-spec file:///Users/mahesh/DevLibrary/flutter_sdk/flutter/bin/cache/flutter_web_sdk/libraries.json --packages /Users/mahesh/development/flutter/ttt/.dart_tool/package_config.json -Ddart.vm.profile=false -Ddart.vm.product=false --enable-asserts --track-widget-creation --filesystem-root /var/folders/5s/5bzzk2fs6jdd7kpyns96xlvw0000gn/T/flutter_tools.wsUduH/flutter_tools.M04xs4 --filesystem-scheme org-dartlang-app --initialize-from-dill build/c7922d95bf4a2462b75c84a97c312edb.cache.dill.track.dill --platform file:///Users/mahesh/DevLibrary/flutter_sdk/flutter/bin/cache/flutter_web_sdk/kernel/flutter_ddc_sdk.dill --no-sound-null-safety
[  +25 ms] <- compile org-dartlang-app:/web_entrypoint.dart
[+24793 ms] Waiting for connection from debug service on Chrome... (completed in 25.0s)
[   +1 ms] Synced 29.5MB.
[        ] <- accept
[        ] Caching compiled dill
[ +129 ms] Using Google Chrome 89.0.4389.114
[ +915 ms] [CHROME]:
[   +1 ms] [CHROME]:DevTools listening on ws://<IP_ADDRESS>:49450/devtools/browser/605763cd-fb40-484c-933f-63a6862656f6
[+1129 ms] DwdsInjector: Received request for entrypoint at http://localhost:49446/main_module.bootstrap.js
[  +12 ms] MetadataProvider: Loading debug metadata...
[  +17 ms] MetadataProvider: Loaded debug metadata
[  +13 ms] DwdsInjector: Injected debugging metadata for entrypoint at http://localhost:49446/main_module.bootstrap.js
[+3617 ms] DevHandler: Debug service listening on ws://<IP_ADDRESS>:49468/ooxPB9uJe2o=/ws
[  +16 ms] Debug service listening on ws://<IP_ADDRESS>:49468/ooxPB9uJe2o=/ws
[        ] Running with unsound null safety
[        ] For more information see https://dart.dev/null-safety/unsound-null-safety
[   +3 ms] 🔥  To hot restart changes while running, press "r" or "R".
[        ] For a more detailed help message, press "h". To quit, press "q".

As explained above, issues with third-party plugins need to be reported to their developers.

Flutterfire and cocoapods are not responding.
Same is working without any problem in windows.
I tried to completely uninstall and reinstall everything in macos.
I am facing the same problem.
Development is stopped. What should i do now?

@maheshkumar2150
if you need assistance with your code please follow the link I want help writing my application in the new issue menu
or ask on discord, reddit and slack
if you think it's a bug with firebase , please open an issue in the dedicated github


Video stops playing after sometime

After the video plays for less than a minute the screen goes black and it stops basically

I'm facing same issue . It occurs for every video
Mostly every video starts playing but after a minute or less it goes black or it's just stops for a long while


MSAL.js does not work with IE11.

Even Updated version is not supported.
https://cloud.githubusercontent.com/assets/13203188/25239637/d1872fb4-25f0-11e7-9748-6fc91586d871.png

@sunrawat  Please don't remove our template while creating an issue. This helps us get more details about the issue so that we can support you better.

I am using loginRedirect and latest version of msal by installing
npm install msal for my angular 6 project.

@sunrawat  Are you using msal-angular library or msal.js library?

related: #414
seems like #414 isnt labeled with bug, so i thought I'd reference it here to help things move along.

As mentioned above this is related to #414. Closing this as duplicate.


this is literally a convoluted JSON.parse/JSON.stringify

doesnt even handle dates smh

This is literally a convoluted rationale for filing an issue. This is open source and free. I made it for myself and shared. You don't like it? I don't care.  Why waste your time (and mine) with useless griping? And please, learn how to use punctuation.


wip

Please read contributing guidelines and remove this line.

#5294  👈
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @fcarreiro and the rest of your teammates on  Graphite

Benchmark results
Metrics with a significant change:

note_trial_decrypting_time_in_ms (64): 110 (+94%)

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Values are compared against data from master at commit 6e218d41 and shown if the difference exceeds 1%.
L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
8 txs
32 txs
64 txs

l1_rollup_calldata_size_in_bytes
5,668
18,820
36,356

l1_rollup_calldata_gas
66,400
239,116
469,016

l1_rollup_execution_gas
647,498
929,474
1,305,196

l2_block_processing_time_in_ms
1,289 (-1%)
4,828 (-4%)
9,225 (+2%)

note_successful_decrypting_time_in_ms
192 (-2%)
532 (-5%)
974 (-5%)

note_trial_decrypting_time_in_ms
97.7 (-6%)
49.1 (-35%)
:warning: 110 (+94%)

l2_block_building_time_in_ms
18,217 (-1%)
68,852 (-1%)
136,321 (-1%)

l2_block_rollup_simulation_time_in_ms
8,193 (-1%)
29,067 (+1%)
56,946

l2_block_public_tx_process_time_in_ms
9,999 (-1%)
39,725 (-2%)
79,274 (-2%)

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric
5 blocks
10 blocks

node_history_sync_time_in_ms
14,240
28,080 (+4%)

note_history_successful_decrypting_time_in_ms
1,258 (+3%)
2,430 (-1%)

note_history_trial_decrypting_time_in_ms
104 (+55%)
161 (-7%)

node_database_size_in_bytes
19,066,960
35,860,560 (+1%)

pxe_database_size_in_bytes
29,859
59,414

Circuits stats
Stats on running time and I/O sizes collected for every circuit run across all benchmarks.

Circuit
circuit_simulation_time_in_ms
circuit_input_size_in_bytes
circuit_output_size_in_bytes

private-kernel-init
282
44,366
28,244

private-kernel-ordering
217
52,868
14,326

base-parity
1,889 (+3%)
128
311

base-rollup
723
165,787
925

root-parity
1,515 (-7%)
1,244
311

root-rollup
63.4
4,487
789

private-kernel-inner
646 (-1%)
73,771
28,244

public-kernel-app-logic
445 (-2%)
35,260
28,215

public-kernel-tail
173 (-1%)
40,926
28,215

merge-rollup
8.35 (-1%)
2,696
925

Tree insertion stats
The duration to insert a fixed batch of leaves into each tree type.

Metric
1 leaves
16 leaves
64 leaves
128 leaves
512 leaves
1024 leaves
2048 leaves
4096 leaves
32 leaves

batch_insert_into_append_only_tree_16_depth_ms
10.1 (+1%)
16.1
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_count
16.8
31.6
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_ms
0.585
0.495
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_32_depth_ms
N/A
N/A
46.2
72.1 (-1%)
231
446
872
1,731
N/A

batch_insert_into_append_only_tree_32_depth_hash_count
N/A
N/A
96.0
159
543
1,055
2,079
4,127
N/A

batch_insert_into_append_only_tree_32_depth_hash_ms
N/A
N/A
0.473
0.445 (-1%)
0.420
0.417
0.413
0.415
N/A

batch_insert_into_indexed_tree_20_depth_ms
N/A
N/A
54.2 (-1%)
107
336 (-2%)
668 (+1%)
1,310 (-2%)
2,616 (-1%)
N/A

batch_insert_into_indexed_tree_20_depth_hash_count
N/A
N/A
104
207
691
1,363
2,707
5,395
N/A

batch_insert_into_indexed_tree_20_depth_hash_ms
N/A
N/A
0.481 (-1%)
0.481
0.456 (-1%)
0.460 (+1%)
0.454 (-1%)
0.453 (-1%)
N/A

batch_insert_into_indexed_tree_40_depth_ms
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
61.5

batch_insert_into_indexed_tree_40_depth_hash_count
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
109

batch_insert_into_indexed_tree_40_depth_hash_ms
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
0.538

Miscellaneous
Transaction sizes based on how many contract classes are registered in the tx.

Metric
0 registered classes

tx_size_in_bytes
22,012

Transaction processing duration by data writes.

Metric
0 new note hashes
1 new note hashes

tx_pxe_processing_time_ms
3,205 (-4%)
1,758

Metric
0 public data writes
1 public data writes

tx_sequencer_processing_time_ms
12.2 (+8%)
1,242 (-1%)


Update yaspeller to latest version

We are using way too old yaspeller version, which caused issue #378

Cool finding. Now it has some whitespace issue tho, it is suggesting to fix almost every word with " word" (ie. added leading space)... another config issue?
Typos: 1
1. In (suggest:  In)

It seems to pass in CI (says "Passed" in th log), but it seems to care which files are edited. So if I edit a readme to get yaspeller triggered, it still explodes.
yaspeller................................................................Failed
- hook id: yaspeller
- exit code: 1

/home/tumi/.cache/pre-commit/repoz9kpkrkq/node_env-system/lib/node_modules/yaspeller/node_modules/minimatch/dist/cjs/ast.js:86
    #fillNegs() {
             ^

SyntaxError: Unexpected token '('
    at wrapSafe (internal/modules/cjs/loader.js:915:16)
    at Module._compile (internal/modules/cjs/loader.js:963:27)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
    at Module.load (internal/modules/cjs/loader.js:863:32)
    at Function.Module._load (internal/modules/cjs/loader.js:708:14)
    at Module.require (internal/modules/cjs/loader.js:887:19)
    at require (internal/modules/cjs/helpers.js:74:18)
    at Object.<anonymous> (/home/tumi/.cache/pre-commit/repoz9kpkrkq/node_env-system/lib/node_modules/yaspeller/node_modules/minimatch/dist/cjs/index.js:9:18)
    at Module._compile (internal/modules/cjs/loader.js:999:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)

Does it do same for you, if you edit readme.md and then try commit it, or is it just on my system?

``

It seems to pass in CI (says "Passed" in th log), but it seems to care which files are edited. So if I edit a readme to get yaspeller triggered, it still explodes.
yaspeller................................................................Failed
- hook id: yaspeller
- exit code: 1

/home/tumi/.cache/pre-commit/repoz9kpkrkq/node_env-system/lib/node_modules/yaspeller/node_modules/minimatch/dist/cjs/ast.js:86
    #fillNegs() {
             ^

SyntaxError: Unexpected token '('
    at wrapSafe (internal/modules/cjs/loader.js:915:16)
    at Module._compile (internal/modules/cjs/loader.js:963:27)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)
    at Module.load (internal/modules/cjs/loader.js:863:32)
    at Function.Module._load (internal/modules/cjs/loader.js:708:14)
    at Module.require (internal/modules/cjs/loader.js:887:19)
    at require (internal/modules/cjs/helpers.js:74:18)
    at Object.<anonymous> (/home/tumi/.cache/pre-commit/repoz9kpkrkq/node_env-system/lib/node_modules/yaspeller/node_modules/minimatch/dist/cjs/index.js:9:18)
    at Module._compile (internal/modules/cjs/loader.js:999:30)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1027:10)

Does it do same for you, if you edit readme.md and then try commit it, or is it just on my system?

I made a trial in this PR: I added a line in README, but the test still passed. It passed for me locally as well.
Did you do something more special in your edit?

/assign @lentzi90


Fix url links

Type of issue
Outdated article
Feedback
We updated our nodejs samples to a new set of directories and the links need to be updated.
Page URL
https://learn.microsoft.com/en-us/microsoftteams/platform/bots/how-to/teams conversational ai/teams-conversation-ai-overview#code-samples
Content source URL
https://github.com/MicrosoftDocs/msteams-docs/blob/main/msteams-platform/bots/how-to/Teams conversational AI/teams-conversation-ai-overview.md
Author
@michaelmaillot
Document Id
56a54b92-6f7c-0fcc-6689-d84794bb25bc

Hello @corinagum - Thanks for raising the feedback.
We will look into it and let you know the updates.


Incorrect Route::resource generation

As you can see in the following screenshot, there is one route name of a resource generated differently from the rest:

The PATCH members/{members} route has a name of "dashboard2." - which is the "as" index of the route group the resource call is in.
I tried to create a PR myself, but couldn't understand the process of generating the routes.

I guess that the problem was solved as I took another look through the files and routes.
The PUT and PATCH routes do the same and therefore just one needs to have a name...

Except the thing, that the empty PATCH route name shouldn't be "prefixed" maybe?

Nope. :)

I can't extract, what you want to tell me :P Could you elaborate a bit?


Change to VolumeSnapshot CRD v1beta1

This PR changes VolumeSnapshot CRD version from v1alpha1 to v1beta1.

/assign @mistyhacks @jimangel

/cc @jingxu97 @msau42

@xing-yang could you please ref the code PR here so that we can track the status of it? Thanks!

This is delayed to 1.17.  PR is here:
https://github.com/kubernetes/kubernetes/pull/80058

@sftim we should not have merged this PR, as the feature is delayed to 1.16

Oops! Let me PR something to revert that.

🤦


Check signed-off-by via TravisCI

Signed-off-by: Augustina Ragwitz<EMAIL_ADDRESS>

Closes Issue #20


feat: Support configuring local IP address for N9 interface

Until now, eupf only allowed configuring the local IP address for the N3 interface, which actually ended up being used for both N3 and N9 (GTP-U forwarding towards other uplink UPFs).
However, that limitation poses so problems under some production scenarios. Some users require running an UPF to forward GTPv1U traffic from network A to network B and viceversa, where those 2 networks are not reachable to each other, only through the UPF host.
This happens for instance when cellular operators don't control/own the entirety of their networks, e.g. a network which runs their NAT under a satellite link with private addresses (eg VPN) which end up at a single host.
As a result, the UPF requires managing at least 2 separate local IP addresses for GTP-U traffic: One (usually private) IP address towards the RAN, and one (usually public, or another private network) IP address towards the Corei. As a result, when a PFCP client (an SMF, or osmo-hnbgw, or osmo-s1gw to mention some other examples) tries to setup a session to forward GTPU traffic from network A (RAN) to network B (Core), will result in eUPF forwarding the GTP-U packet to the Core but using the RAN configured IP as the GTPU packet local IP address.
Hence, either local routing will be wrong, or the Core will drop the received packet, or won't know how to route traffic back to it.
This patch allows eupf to be used co-located with 3G osmo-hnbgw [1] and 4G osmo-s1gw [2] under the mentioned network setups, both supporting PFCP to manage a UPF to forward data plane also in GTP1U protocol.
[1] https://osmocom.org/projects/osmohnbgw
[2] https://gitea.osmocom.org/erlang/osmo-s1gw
Related: https://github.com/edgecomllc/eupf/issues/577

@edgecomllc any feedback here? Something I should look at or fix?

Hi @pespin
It's a awesome contribution!
BTW, is the underlined part below necessary?
cmd/core/pfcp_session_handlers.go
+					log.Info().Msgf("PESPIN: Using N9 local IP address %v", localN9Ip)
                                                         ~~~~~~~~

Also, what did you use for the 5G Core C-Plane to verify the ULCL operation?
Is it free5GC? Or is it any commercial 5G Core?
Please let me know if you don't mind.
Thanks.

Hi @pespin,
Sorry for the delay. I have two common point on this PR:

I would rather make N9 address optional and set N9 address equal to N3 address by default.
Because of the first point, it's not necessary to add N9 address in every deployment config.

What do you think? Does it make sense?
-- BR, Alex

@pirog-spb I have this in my TODO list, will have a look soon whenever I find some time.

@pirog-spb I have this in my TODO list, will have a look soon whenever I find some time.

If you don't mind, I'd do it myself

@pirog-spb maybe in that case you could submit a PR with my patch + your changes on top making the N9 IP address optional and merge them without squashing? I'd be happy with that approach.

@pirog-spb also if you want let me know when you submit the PR, I can give it a test in our gtplab setup to confirm it's working fine.

@pespin Please check #585

Abandoning in favour of https://github.com/edgecomllc/eupf/pull/585


Publish app (nice to have)

It would be great if the app was published to some package managers.
mac: homebrew
windoze: chocolatey
linux: not sure if there one single place

Homebrew-Cask has this already:
https://github.com/caskroom/homebrew-cask/blob/master/Casks/graphql-ide.rb
$ brew cask install graphql-ide
==> Downloading https://github.com/redound/graphql-ide/releases/download/v1.1.0/GraphQL.IDE.app.zip
######################################################################## 100,0%
==> Verifying checksum for Cask graphql-ide
==> Moving App 'GraphQL IDE.app' to '/Applications/GraphQL IDE.app'
🍺  graphql-ide was successfully installed!

As long as that's up-to-date with releases, it should be added to the README


Update pt-BR.coffee

Coverage remained the same at 61.885% when pulling 41bcec7ef3193123ccd1fc03a2b20a8af55ea3cb on traducaoenlix:patch-1 into 9d02af732817686c28b80e65bd40d013df1e9800 on codecombat:master.

Thanks!


Use #[derive] for Copy/Clone in s! and friends

Description
Extracted from #3261 as a pre-requisite change.
Allows use of #[cfg] to skip items in an s! block without creating invalid, orphaned impl blocks.
Checklist

[ ] Relevant tests in libc-test/semver have been updated
[ ] No placeholder or unstable values like *LAST or *MAX are included (see #3131)
[x] Tested locally (cd libc-test && cargo test --target mytarget);
especially relevant for platforms that may not be checked in CI

How does this change impact the MSRV?  (I tried building with the currently declared 1.13.0 but that is completely broken, it can't even resolve the Cargo.toml since some versions of the cc crate have a feature named after a dependency)

For 0.2 we test down to 1.19 - do the derives work on 1.19? If so then we can backport with no problem, I was just assuming they wouldn't since we don't have this already, but could be wrong there.
There is no problem for main since that only goes down to 1.63.

Deriving Copy and Clone was present in Rust 1.0, my theory for why they're manually implemented in s! is to ensure that the generated code for Clone is a memcpy even in debug builds (the unoptimized implementation of Clone  is a recursive call into Clone for each field, even if those fields are all Copy).  As discussed in the other MR, if that is a genuine problem for developers they can chose to compile libc with optimizations even if they're compiling the rest of their crate(s) in debug mode.
I'm pretty sure this change can be ported to the 0.2 branch with the above caveat if you wished.


修coverage的套件設定

Coverage increased (+23.5%) to 70.875% when pulling a40ff0bd373664c54df97b3c79003d189c2e6293 on 修coverage into 8f0d323f5fb7fe59fd06a015a1045f951a567920 on master.


popup on first time visit

popup on first time visit

@03amir  Please attach a screenshot with your  PR  .

@03amir   Gr8 work  , I have merged your PR


Link to version 7 in readme is broken

Hi Matt,
I just spent a good hour trying to work out why my code wasn't working properly before working out that it was a breaking change at the iodine side from the latest version. That'll teach me not to explicitly include version numbers in my CDN links...
In any case, the link to version 7 in your readme delivers a 404 so would be worth updating that:

Thanks. Fixed it :)


corona top10 rank

There's a little trouble with top10 rank:
 -corona usa
 USA: World Rank: #2 | Cases: 300,028 (+22,867) (+8.3%) | Deaths: 8,137 (2.7%) (+733) (+9.9%) | Recovered: 14,464 (4.8%) | Active: 277,427 (271,111 Mild) (6,316 Serious) (97.7%/2.3%) | Cases/1M: 906 | Deaths/1M: 25 | Updated: 5.7m ago
 -corona --top10
 #1: Total: (1,169,323/62,730), #2: USA (300,028/8,137), #3: Spain (124,736/11,744), #4: Italy (124,632/15,362), #5: Germany (92,150/1,330), #6: France (82,165/6,507), #7: China (81,639/3,326), #8: Iran (55,743/3,452), #9: UK (41,903/4,313), #10: Turkey (20,921/425) | Updated: 5.8m ago

Yeah, they added a World row as well as Total which threw off the rankings, fixed in latest commit.


build order issue of add_deps

xmake 2.3.3
xmake.lua:
target('aaa')
    on_build(function(target)
        print('build aaa')
    end)

target('bbb')
    add_deps('aaa')

    on_build(function(target)
        print('build bbb')
    end)

target('ccc')
    add_deps('bbb')
    set_kind('static')
    add_files('aaa.c')

I expect that the output order should be:
build aaa
build bbb
compiling.release aaa.c

The actual output is:
build aaa
compiling.release aaa.c
build bbb

The sample project file is attached.
thanks.
test.zip

Please call set_policy("build.across_targets_in_parallel", false) to disable across_targets_in_parallel policy for the given target.
target('ccc')
    add_deps('bbb')
    set_kind('static')
    add_files('aaa.c')
    set_policy("build.across_targets_in_parallel", false)

ok, thanks for the solution.


Switch expectError to expectPass where applicable to keep tests consistent with each other

Closes: #1988
What is the purpose of the change
Most of our table driven tests check errors by using expectPass, but there are a few tests lingering around that seem to use expectError. Since we are starting to introduce testing standards for our codebase, a small but important test cleanup would be to align all of our tests to use the same convention to remove the inconsistency. This PR makes this change where applicable.
Brief Changelog

Switch expectError to expectPass in balancer tests

Testing and Verifying
This change is a trivial rework / code cleanup without any test coverage.
Documentation and Release Note

Does this pull request introduce a new feature or user-facing behavior changes? (no)
Is a relevant changelog entry added to the Unreleased section in CHANGELOG.md? (no)
How is the feature or change documented? (not documented)

yeah, also not sure this is worth doing right now / here


Adding Rex-Ray support to DC/OS

Taking over from #220.

We need to move the DVDCLI tarball to downloads.dcos.io. /cc @lingmann

Need to move the download to downloads.dcos.io, but once that happens this can ship

Working on the downloads move now...

FWIW jie and gilbert both mentioned today that dvdcli 0.2 was probably not
compatible with the mesos docker volume isolator.
On Wed, Jul 20, 2016 at 12:48 PM, Cody Maloney<EMAIL_ADDRESS>wrote:

Merged #347 https://github.com/dcos/dcos/pull/347.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dcos/dcos/pull/347#event-729257836, or mute the
thread
https://github.com/notifications/unsubscribe-auth/ACPVLAt_6f9mJqKqjp6aU6zOkJJ15Nq8ks5qXlFtgaJpZM4JNBpJ
.

Can you add a blocker JIRA for that?

done
On Wed, Jul 20, 2016 at 12:54 PM, Cody Maloney<EMAIL_ADDRESS>wrote:

Can you add a blocker JIRA for that?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dcos/dcos/pull/347#issuecomment-234010966, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACPVLIAHrpKc98f_af4-rb--qSWRZSxuks5qXlLhgaJpZM4JNBpJ
.


Add streaming match generation

This PR proposes "streaming match generation" for GrandCypher. It depends on the changes in this corresponding PR https://github.com/aplbrain/grandiso-networkx/pull/39.
This change is designed to improve the performance of large openCypher queries. It employs a streaming match generation strategy to iteratively process each result.
For example, with this code snippet:
import time

import networkx as nx

from grandcypher import GrandCypher

host = nx.DiGraph()

start = time.time()
size = 1000000
for x in range(size):
    host.add_node(x, name=x)
    host.add_edge(x, x + 1)

print(f"Built graph in {time.time() - start}s")

qry = """
MATCH (A) -[]-> (B) -[]-> (C) -[]-> (D)
RETURN A.name, B.name, C.name, D.name
LIMIT 1
"""

start = time.time()
res = GrandCypher(host).run(qry)
print(f"Query took {time.time() - start}s")
print(res)

The current code base takes:
Built graph in 3.705066442489624s
Query took 86.24252390861511s
{'A.name': [0], 'B.name': [1], 'C.name': [2], 'D.name': [3]}

With this PR, it takes:
Built graph in 2.572826623916626s
Query took 0.003414630889892578s
{'A.name': [0], 'B.name': [1], 'C.name': [2], 'D.name': [3]}

While this query on the surface seems ridiculous, it's not too different than:
SELECT * from table LIMIT 1

For situations where you may just want to sample a few rows.
Here are a couple additional examples:
qry = """
MATCH (A{name: 0}) -[]-> (B) -[]-> (C) -[]-> (D)
RETURN A.name, B.name, C.name, D.name
LIMIT 1
"""

Current:
Built graph in 2.583895444869995s
Query took 0.6473803520202637s
{'A.name': [0], 'B.name': [1], 'C.name': [2], 'D.name': [3]}

With this PR:
Built graph in 3.0622048377990723s
Query took 0.003484010696411133s
{'A.name': [0], 'B.name': [1], 'C.name': [2], 'D.name': [3]}

qry = """
MATCH (A) -[]-> (B{name: 1}) -[]-> (C) -[]-> (D)
RETURN A.name, B.name, C.name, D.name
LIMIT 1
"""

Current:
Built graph in 2.8512825965881348s
Query took 25.05796718597412s
{'A.name': [0], 'B.name': [1], 'C.name': [2], 'D.name': [3]}

With this PR:
Built graph in 2.822657346725464s
Query took 0.0033731460571289062s
{'A.name': [0], 'B.name': [1], 'C.name': [2], 'D.name': [3]}

qry = """
MATCH (A) -[]-> (B) -[]-> (C) -[]-> (D)
WHERE D.name = 100
RETURN A.name, B.name, C.name, D.name
LIMIT 1
"""

Current:
Built graph in 3.100694179534912s
Query took 85.86176109313965s
{'A.name': [97], 'B.name': [98], 'C.name': [99], 'D.name': [100]}

With this PR:
Built graph in 2.6066715717315674s
Query took 0.013916015625s
{'A.name': [97], 'B.name': [98], 'C.name': [99], 'D.name': [100]}

This change also adds an optional default limit that can be applied to all queries. It's worth noting that this only improves performance when a query has results. For queries without results, it still goes through the whole graph looking for results. I thought about adding a maximum iterations parameter but didn't include that with this PR.

Wow these are some pretty compelling performance numbers!! 😍

That's correct, this change works with the current version of grandiso. But as you said, it wouldn't benefit from the short circuiting logic without the changes from grandiso.

Ok I've thought about it a lot and I think the "right" answer is to NOT bump the version dep on grandiso in this library, since it's a nonbreaking and backwards compatible change and I'd rather avoid the possibility of adding incompatibilities into existing projects; but I will merge this presently and anyone who installs from now on should get the latest of both, and enjoy the huge performance bump from your work!!
Thank you again! Excited to play around with this some more :)

Sounds like a good approach to me!


Dds 1175 use presigned urls for upload

Before submitting this PR

Description: Add a summary of the changes in this PR and the related issue.
Jira task / GitHub issue: Link to the github issue or add the Jira task ID here.
How to test: Add information on how someone could manually test this functionality. As detailed as possible.
Type of change: Check the relevant boxes in the section below
Add docstrings and comments to code, even if you personally think it's obvious.

What type of change(s) does the PR contain?

[ ] New feature

[ ] Breaking: Please describe the reason for the break and how we can fix it.
[ ] Non-breaking

[ ] Bug fix

[ ] Breaking: Please describe the reason for the break and how we can fix it.
[ ] Non-breaking

[ ] Security Alert fix
[ ] Documentation
[ ] Tests (only)
[ ] Workflow

Checklist

Sprintlog

[ ] Added
[ ] Not needed (E.g. PR contains only tests)

Rebase / Update / Merge from base branch (the branch from which the current is forked)

[ ] Done
[ ] Not needed

Blocking PRs

[ ] Merged
[ ] No blocking PRs

PR to master branch

[ ] Yes: Read the release instructions

[ ] I have followed steps 1-7.

[ ] No

Actions / Scans

Black: Python code formatter. Does not execute. Only tests.
Run black . locally to execute formatting.

[ ] Passed

Pylint: Python code linter. Does not execute. Only tests.
Fix code producing warnings. Code must get 10/10.

[ ] Warnings fixed
[ ] Passed

Prettier: General code formatter. Our use case: MD and yaml mainly.
Run npx prettier --write . locally to execute formatting.

[ ] Passed

Yamllint: Linting of yaml files.

[ ] Passed

Tests: Pytest to verify that functionality works as expected.

[ ] New tests added
[ ] No new tests
[ ] Passed

TestPyPi: Build CLI and publish to TestPyPi in order to verify before release.

[ ] Passed

CodeQL: Scan for security vulnerabilities, bugs, errors

[ ] New alerts: Go through them and either fix, dismiss och ignore. Add reasoning in items below.
[ ] Alerts fixed: What?
[ ] Alerts ignored / dismissed: Why?
[ ] Passed

Trivy: Security scanner

[ ] New alerts: Go through them and either fix, dismiss och ignore. Add reasoning in items below.
[ ] Alerts fixed: What?
[ ] Alerts ignored / dismissed: Why?
[ ] Passed

Snyk: Security scanner

[ ] New alerts: Go through them and either fix, dismiss och ignore. Add reasoning in items below.
[ ] Alerts fixed: What?
[ ] Alerts ignored / dismissed: Why?
[ ] Passed

Closing. Will not have time to fix.


[entropy_src/rtl] Corner cases in handling delays

This commit handles a number of corner cases that can occur due to the
non-zero processing time of the SHA engine. Though all of these were
identified as by long delays in verifying the cs_aes_halt_req/ack
handshake, the following issues could all come up due to rapid
poorly-timed programming sequences.
The general issues are that:

The SHA engine is unresponsive to disable events while processing, and
The bypass FIFO can stall for a number of reasons (BOOT mode
finished, mismatch between HT window size and seed size, etc).

The following corner-case delay scenarios are handled in this commit.
Missed Disable Pulses
The main_sm does not see disable pulses while the SHA block is
processing. (NOTE: For the purposes of this discussion AES-halt
handshakes are considered part of the SHA process time).  This
is by design as the SHA engine needs to complete it's sequence once
started. This can cause the module to remain in Continuous mode after
enabled rather than go back to Startup mode as required.
The correction here is to monitor for disable events that occur during
SHA processing and hold the main_sm disabled until processing has
completed. This forces the SM to return to Idle before proceeding.
If such stalls occur in the main_sm the rest of the core stalls as
well thanks to backpressure on the FIFOs
Lingering SHA Outputs
If SHA processing were instantaneous, a disable event would clear the
esfinal FIFO, and this FIFO would remain clear after re-enablement.
However if a disable event occurs during SHA processing, this ongoing
seed conditioning will continue, a possibly end up in the output FIFO.
For consistency and verifiability, these core now monitors for these
"stale" seeds, snd flushes them at the input of the esfinal FIFO.
Configuration Change During SHA processing
The core can toggle between bypass and non-bypass mode while disabled.
Since the core does not respond to disable pulses immediately, the
SHA3 block may also have inputs stalled waiting to be added to a
following seed.
Verification assumes that any 64-bits gathered in conditioning mode
will be instantly loaded into the conditioner, and will become part
of any following seed.  However if the conditioner stalls for processing
and the core is reconfigured the seed could be re-rerouted to the
bypass FIFO.
This mostly presents a big challenge for verification, However
maintaining consistency in this data-flow modele will help prevent
potential security issues.  This scenario merits a few changes:

The Pre-conditioning FIFO is now reserved for only conditioning data.
This lets the verification environment know that once any 64-bit word
has been submitted to the SHA3 engine, that word can considered already
absorbed regardless of delays.  Bypass data is now picked up directly at
the PostHT FIFO

Because many registers control the selection of bypass mode, the
signal es_bypass_mode is now a register which is only latched at
enable time.  This prevents misrouting of RNG data dues to transients
in configuration

Non-Blocking Bypass FIFO
The Bypass FIFO can block the rest of the pipeline when in bypass mode
for its own unique reasons.  If the bypass health-test window is larger
than a seed (or just a non-integer multiple of a seed), the Bypass FIFO
can become full before a full HT window.  Since bypass mode only
generates one seed per enable, these FIFO can also become full once
this single seed in generated.  For these reasons the Bypass FIFO is
left non-blocking.

Note this commit is currently derived from #14644.   Please only look at the second commit when reviewing this PR.


LibSass 3.2 support

Is this library compatible with LibSass 3.2?

@willemdewit the libsass-net currently supports libsass 3.2-beta5 , the next nuget version release should support 3.2 at least or 3.2.2

@willemdewit Please update your version of LibSassnet & libsassnet.web, they now support libsass 3.2.2


[ASCII-1434] Migrate metadata endpoints to providers

What does this PR do?
Previous work:

https://github.com/DataDog/datadog-agent/pull/24045
https://github.com/DataDog/datadog-agent/pull/24872
https://github.com/DataDog/datadog-agent/pull/25234

Continuation of the componentization work, this PR registers /metadata/x routes with EndpointProviders from the respective components.
We need  https://github.com/DataDog/datadog-agent/pull/25234 merged before we can merge this as it untangles a circular import with the comp/logs/agent and others being required in the api interface, some of those changes were cherrypicked to have a green build but were not fully implemented in this PR.
The main changes can be found in f70a417 and tests added in 38738a0

Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

there are e2e tests for most of these routes

/merge


Created sorting algorithm

Purpose
Sort the lpa's by donors surname for the dashboard page so that it is organised and easier to search
Fixes UML-675
Approach
I run a for on the list of lpa's and extract the donors surname to a new array. This array of surnames is then sorted alphabetically. Finally, I run a for loop on each of the surnames in the now ordered surname array. Within this for loop, we loop through each lpa in the list until we find an lpa that matches the current surname from the surname array. When found, we add that lpa to a new array, remove it from the lpa array and continue to the next ordered surname to find its match.
Checklist

[ ] I have performed a self-review of my own code
[ ] I have added relevant logging with appropriate levels to my code
[ ] I have updated documentation (Confluence/GitHub wiki/tech debt doc) where relevant
[ ] I have added tests to prove my work
[ ] The product team have tested these changes

Coverage decreased (-0.4%) to 80.156% when pulling 3eb5834e3bf1a5f5f2f89154733e5c09e214a13c on UML-675-Alphabetical-lpas into c869fddc803517cc3c123b701e556f217378d913 on master.


refactor: wallet create/restore loading screen

Description

new screen that handles both wallet creation and restoring
It handles all the recovery, so we don't need to switch screens, no waiting or black screens

Linked Issues/Tasks
closes #2213
Type of change
Refactoring
Tests
No test
QA Notes

test wallet creation
test wallet restore
test wallet restore + LN backup restore failed

There is a regression in that if I abort the restore by closing the app and then open it again now it never finishes. Have to wipe wallet from recovery and then try again.
https://github.com/user-attachments/assets/609e89dd-e7ae-405a-a069-db9f25014598

There is a regression in that if I abort the restore by closing the app and then open it again now it never finishes. Have to wipe wallet from recovery and then try again.

Fixed in the latest commint


Fatal Error in call peaks when starting with tag aligns

Hello,
I am running into an error in call_peaks when I run the following command:
srun -p part1 --mem=1G --pty /bin/bash

bds_scr job_1 /home/username/job_1.log -s slurm /path/to/atac_dnase_pipelines/atac.bds -q part1 -nth 4 -species mm10 -se -enable_idr -title job_1 -tag1 /path/to/peaks/sample_1/align/rep1/sample_1.trim.nodup.tagAlign.gz -tag2 /path/to/peaks/sample_2/align/rep1/sample_2.trim.nodup.tagAlign.gz -tag3 /path/to/peaks/sample_3/align/rep1/sample_3.trim.nodup.tagAlign.gz -out_dir /path/to/peaks/job_1_IDR

I would greatly appreciate any help in debugging this issue. The log file is attached.
job_1.log
Thank you.
-Easwaran

Can you increase memory for MACS2 (by adding -mem_macs2 20G to the command line) and try again?
some references:
https://github.com/JuliaLang/julia/issues/14807
https://stackoverflow.com/questions/27825280/change-the-rlimit-nproc-in-linux


The Convolution layout Issue

Can libxsmm support the NCHW and KCRS layout for convolution?

There are various routines to copy whatever format into or out of LIBXSMM-DNN's internal formats (NCHWc, KCRSck). Routines exist for all supported type-favors (as well as modded versions to omit certain transposes).

Do you have something specifically in mind with this question, e.g., sample code?

I improved getting started with LIBXSMM-DNN and added a README. Though, we just recently transitioned this code base from LIBXSMM into a separate/this repository.
Thank you for your question, and feel free to raise any issue you might run into!


Add full support for negative numbers

Fix #103
Add some tests for negative time

Thank you!

No problem 😄!