[feature] Front end design system

User Story
As a front-end developer, I want to implement a comprehensive design system and default layout for our React application so that the app has a consistent, modern, and user-friendly interface across all pages.
Acceptance Criteria

Front-End Implementation Steps

Step 1: Research and select a design system/framework that aligns with our app’s needs (consider Material-UI, Ant Design, or custom with Tailwind CSS).
Step 2: Set up the chosen design system in the React application.
Step 3: Develop a default layout component that includes a responsive navbar mounted to the left side.
Step 4: Ensure that the layout is responsive and adapts to different screen sizes.
Step 5: Implement a basic color scheme and typography that aligns with our brand guidelines.
Step 6: Create a set of reusable UI components (buttons, inputs, cards, etc.) based on the design system.
Step 7: Ensure accessibility standards are met in the design (color contrast, keyboard navigation, ARIA attributes).
Step 8: Review and finalize the design in a Pull Request (PR) before implementation, welcoming team input and ideas.

Back-End Implementation Steps

(Not applicable for this user story as it primarily focuses on front-end development.)

Is this feature request related to a problem?
Currently, our React application lacks any design implementation.
Proposed Solution
Implement a design system that provides a consistent set of design principles and reusable components. This system will guide the development of UI elements, ensuring cohesion and a better user experience.
Alternative Solutions

Consider different design frameworks and compare their adaptability to our app's needs.
Explore the possibility of building a custom design system if existing systems do not align with our specific requirements.

Additional Context
For inspiration and visual direction, the following design concepts can be referenced:

Finance Dashboard UI Concept
Analytics Dashboard
Admin Dashboard Analytics UX
Health App Concept

The final design must be responsive and open to team input, with a focus on usability and modern aesthetics.

Proposed Color Scheme
Light Mode

Background (Primary): #FFFFFF (White)
Text (Primary): #282828 (Dark Gray)
Background (Secondary): #F3F4F6 (Gray-100)
Text (Secondary): #282828 (Dark Gray)
Button Hover Text (Inactive): #276EF1 (Blue)
Button Hover Border (Inactive): #276EF1 (Blue)

Dark Mode

Background (Primary): #282828 (Dark Gray)
Text (Primary): #F5E8C7 (Off White)
Background (Secondary): #454545 (Darker Gray)
Text (Secondary): #F5E8C7 (Off White)
Button Hover Text (Inactive): #F5E8C7 (Off White)
Button Hover Border (Inactive): #F5E8C7 (Off White)

Common

Primary Inverse Background: #C7D5F5 (Light Blue)
Primary Inverse Text: #276EF1 (Blue)
Primary Inverse Border: #276EF1 (Blue)
Dark Mode Primary Inverse Text: #282828 (Dark Gray)
Dark Mode Primary Inverse Border: #282828 (Dark Gray)

Done we will use a combination of custom components based upon the above colors as well as some Shoelace web components


pycryptodome or pycryptodomex?

iMac-TMP:mykeepassc180 joe$ virtualenv -ppython3 v
Running virtualenv with interpreter /usr/local/bin/python3
Using base prefix '/usr/local/Cellar/python/3.6.5/Frameworks/Python.framework/Versions/3.6'
New python executable in /Users/joe/Developer/mykeepassc180/v/bin/python3.6
Also creating executable in /Users/joe/Developer/mykeepassc180/v/bin/python
Installing setuptools, pip, wheel...done.
iMac-TMP:mykeepassc180 joe$ . v/bin/activate
(v) iMac-TMP:mykeepassc180 joe$ pip3 install keepassc
Collecting keepassc
Collecting kppy (from keepassc)
Collecting PyCryptodome (from keepassc)
  Using cached https://files.pythonhosted.org/packages/9c/83/8f8a9e94d3cc495dd49082ac79e366b368cd10c8d25734fbcea59de93e5a/pycryptodome-3.6.1-cp36-cp36m-macosx_10_6_intel.whl
Installing collected packages: PyCryptodome, kppy, keepassc
Successfully installed PyCryptodome-3.6.1 keepassc-1.8.0 kppy-1.5.1
(v) iMac-TMP:mykeepassc180 joe$ ./v/bin/keepassc --help
Traceback (most recent call last):
  File "./v/bin/keepassc", line 13, in <module>
    from kppy.database import KPDBv1
  File "/Users/joe/Developer/mykeepassc180/v/lib/python3.6/site-packages/kppy/database.py", line 11, in <module>
    from Cryptodome import Random
ModuleNotFoundError: No module named 'Cryptodome'
(v) iMac-TMP:mykeepassc180 joe$ pip3 install pycryptodomex
Collecting pycryptodomex
  Using cached https://files.pythonhosted.org/packages/11/8d/05bcf8e039e989c0dd4a645a66e5fcda873718b2ff8350c7d77c3b1f2a20/pycryptodomex-3.6.1-cp36-cp36m-macosx_10_6_intel.whl
Installing collected packages: pycryptodomex
Successfully installed pycryptodomex-3.6.1
(v) iMac-TMP:mykeepassc180 joe$ ./v/bin/keepassc --help
usage: keepassc [-h] [--asroot] [-d DATABASE] [-k KEYFILE] [-c]
                [-as ADDRESS_SERVER] [-ps PORT_SERVER] [-pa PORT_AGENT] [-a]
                [-dc] [-s] [-e ENTRY] [-l]

optional arguments:
  -h, --help            show this help message and exit
  --asroot              parse option to execute keepassc as root user
  -d DATABASE, --database DATABASE
                        Path to database file.
  -k KEYFILE, --keyfile KEYFILE
                        Path to keyfile.
  -c, --curses          Use curses interface while using a remote connection.
  -as ADDRESS_SERVER, --address_server ADDRESS_SERVER
                        Server address (not required if using agent)
  -ps PORT_SERVER, --port_server PORT_SERVER
                        Server port (not required if using agent)
  -pa PORT_AGENT, --port_agent PORT_AGENT
                        Agent port
  -a, --agent           Use agent for remote connection
  -dc, --direct_conn    Connect directly to server
  -s, --ssl             Use SSL/TLS
  -e ENTRY, --entry ENTRY
                        Print entry with parsed title You will see a password
                        prompt; leave it blank if you only want to use a key-
                        file Just type a part of the entry title lower-case,
                        it's case-insensitive and will search for matching
                        string parts WARNING: Your passwords will be displayed
                        directly on your command line!
  -l, --log_level       Set logging level for network use. Default is ERROR
                        but for analyzing network flow INFO could be useful.
                        Set it with keepassc [...] -l [...] to INFO
(v) iMac-TMP:mykeepassc180 joe$

It seems there was a problem in testing PyCryptodome. I experienced similar issues today while it worked during testing the change. Will look into that.

@ilovezfs I uploaded keepassc 1.8.1 and kppy 1.5.2, could you please confirm that it works now?

@raymontag yes, it works! See https://github.com/Homebrew/homebrew-core/pull/27931 which is now ✅

Perfect, thanks for reporting!


Document Potential for Notification Failure Shortly After System Startup

This took me awhile to track down, but the upshot is that a test message I added to a service, to confirm Bugsnag integration worked, resulted in "connection refused" to notify.bugsnag.com when run, and only when run, in its normal deployment configuration within a container/pod. The test message wouldn't show up in the Bugsnag dashboard for the service, and that service doesn't tend to throw Bugsnag errors normally.
Logging in to the container and running the same executable directly resulted in the test message getting through.
That indicated a timing issue, and adding a 2nd test message, sent 5 minutes after the first, confirmed that connectivity was established soon after service startup, just not soon enough for that 1st test message to get through.
Unlike many components that are initialized at startup and, as a result, initiate outgoing TCP connections, Bugsnag does not block nor retry (on a background thread) when such connections fail (due to non-fatal conditions).
That's probably appropriate for Bugsnag's client API, as callers would likely not want any unnecessary delays, nor (potentially) memory wasted on reports piling up until a TCP situation resolved itself (which might be never, i.e. a "permanent" condition, in some cases).
By contrast, a (for example) gRPC outgoing connection will either block or be established in the background, repeatedly trying to Dial() out, until it succeeds; it must, or else crucial functionality will be missing when called upon.
In that sense, Bugsnag-trace uploads are a bit more like UDP than TCP packets: no guarantee of delivery, and for sound reasons.
When an OS boots up, normal users aren't typically allowed to login until the entire system is up and running, at least to a reasonable degree. Container technologies, however, might want to start their primary service as soon as possible, even if full system services (like the TCP stack) are still starting up in parallel.
So a service might be able to Listen on a port (which is a fairly low-level operation, in the sense of having few dependencies), while it might not be able to connect out to the Internet (because complicated routing/firewall rules are still being set up) for another few seconds, possibly minutes.
Bugsnag's documentation should make this clear, so others who encounter this problem can quickly understand what's going on.
Searching for "Bugsnag connection refused", "Bugsnag reports missing", or similar, should quickly find a page (or even this Issue) explaining this timing situation. (I.e. this might be explained already, but I didn't find it searching in that fashion.)

Hey @jcburley, thanks for the report. I'd like to get a little more information on the environment in which you're running bugsnag-go to try and reproduce this issue. Running a simple binary and triggering a notification immediately after initialization of Bugsnag does not exhibit this behaviour, so I assume this may be something to do with a larger application, or the way it's run in a container?
 Is the service being run in a Docker container? Is there any reason that container depends on another container for network connectivity? e.g. are network calls routed through a VPN network container or similar?
You can add block processing of your application until a report is sent using the synchronous configuration option:
bugsnag.Notify(err, bugsnag.Configuration{Synchronous: true})

It'd be interesting to know whether use of this option fixes your early call to notify Bugsnag or not? It may not necessairly be the right way to deal with the issue in production, but would be good to narrow down whether there's some kind of timing problem a bit more.
Can you please share how you're configuring Bugsnag within your application and sending off that first notification that's seeing the connection refused response?

Hey @jcburley, thanks for the report. I'd like to get a little more information on the environment in which you're running bugsnag-go to try and reproduce this issue. Running a simple binary and triggering a notification immediately after initialization of Bugsnag does not exhibit this behaviour, so I assume this may be something to do with a larger application, or the way it's run in a container?

It's a non-trivial application (a microservice with plenty of libraries included) run in a container upon startup, i.e. it's the entrypoint.

No.

Is the service being run in a Docker container?

Yes.

Is there any reason that container depends on another container for network connectivity? e.g. are network calls routed through a VPN network container or similar?

I don't think so, but I'm not 100% sure.

You can add block processing of your application until a report is sent using the synchronous configuration option:
bugsnag.Notify(err, bugsnag.Configuration{Synchronous: true})

Hm, might be worth a try to just test this out! Though, I'm not sure we'd want that config to persist beyond the test (which is okay, the test was just to confirm Bugsnag connectivity, and was removed once that was confirmed via the 2nd, delayed, test message).

It'd be interesting to know whether use of this option fixes your early call to notify Bugsnag or not? It may not necessairly be the right way to deal with the issue in production, but would be good to narrow down whether there's some kind of timing problem a bit more.

That does sound like it'd be worth trying out, if I can find the time when I return to work next week (am on vacation).

Can you please share how you're configuring Bugsnag within your application and sending off that first notification that's seeing the connection refused response?

Will look into this when I return and have source-code access.
Thanks for responding so quickly!

Sounds good – let us know what you find from your tests. Agreed, I don't think leaving the synchronous blocking notification in long-term is good beyond just a test, but it if that fails for any reason then there may be something network related causing the issue as this should just work. Enjoy your vacation!

Hi @jcburley, Just a quick follow up to see if you have a chance to try out the suggestions? It would be good to see what your Bugsnag configuration and first notification look like if you have the source code access now, to try and progress this further.

Sorry, not yet, but will try to make time to do it soon!
On March 30, 2022 4:38:16 AM EDT, johnkiely1 @.***> wrote:

Hi @jcburley, Just a quick follow up to see if you have a chance to try out the suggestions? It would be good to see what your Bugsnag configuration and first notification look like if you have the source code access now, to try and progress this further.
--
Reply to this email directly or view it on GitHub:
https://github.com/bugsnag/bugsnag-go/issues/186#issuecomment-1082788901
You are receiving this because you were mentioned.
Message ID: @.***>
James Craig Burley, Software Architect

Hi @jcburley - it's been a little while since we heard from you on this so I'm going to close the issue for now. If you're able to share any more details let us know and we'd be happy to continue investigating 👍


New Package: devtunnels manifest submission

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.4 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/113390&drop=dogfoodAlpha

Hello @setaskin,
One or more of the installer URLs doesn't appear valid.
This may happen for sites with policies prohibiting distribution or use by third parties.
This may happen for URLs pointing to domains that do not align with the publisher domain or package domain. If you could provide supporting evidence from the publisher that the URLs for the installer are correct, that would help us to validate and approve this PR.
Template: msftbot/validationError/urls/domain

Hi @stephengillie, this is our first initial package submission. Installer url is the official microsoft url. What should I do to fix this? _

@wingetbot waivers Add Validation-Executable-Error Validation-Domain


NotEnoughStaketoWithdraw erorr on btcli st undelegate --all

steps to reproduce:
Setup 2 wallets with balances (btcli w create, btcli w faucet)
Create a subnet with wallet 1
btcli root register - become delegate (from wallet 1)
btcli st delegate - delegate 1000 from wallet 2
Wait until the next epoch - staked balance gets up to 1099...
btcli at undelegate --all - undelegate full amount fails

Fixed in dynamic branch of bittensor

See: https://github.com/opentensor/subtensor/pull/462 for fix on testnet

Closed at Stale


Authentication without Username/Password

Hello
Maybe I don't know, how I should make this.
I want to use https://api.thetvdb.com/swagger#!/Authentication/post_login and this requires instead of Username/Password the API-Key.
How can I pass the API-Key with Authentication?
Thanks...

According to that documentation, you need to send a request to the /login route with your API key, Username and Password which returns a JWT token for you. After that you can add that token as Bearer Authorization header to all your subsequent requests.
Hope that helps.


ci(websocket): publish websocket docker image to dockerhub

SUMMARY
Allow apache/superset-websocket image to dockerhub with the same tag as main image
TESTING INSTRUCTIONS
Github Actions
ADDITIONAL INFORMATION

[x] Has associated issue: #21373
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

FYI @benjaminrene it seems your PR is stuck (CI never ran), I suppose maybe because you're a first-time contributor (?).
So to unblock things I've integrated your changes into my related #21954 hoping it will get quicker review (CI passed, so the build is successful but the publish was skipped).

@benjaminrene is this PR still relevant? Asking since I noticed on the issue thread that another PR is mentioned as a fix (thanks for that). Looks like this'll need a rebase if it's still of interest, in which case it should kick-start CI and (hopefully) get us closer to merging this.

Looks like this needs a rebase, but also pinging @mistercrunch to see how it aligns with current efforts in docker-land.

Not relevant anymore AFAICT. Please review https://superset.apache.org/docs/installation/docker and reopen as an issue/PR if there's anything missing.


Fixed sort_constructors_first

Refer #149
Fixed:

sort_constructors_first

@M-A-D-A-R-A Please explain your changes done in this PR along with how it fixes the rule sort_constructors_first.

@M-A-D-A-R-A Please explain your changes done in this PR along with how it fixes the rule (sort_constructors_first). Also I don't see this rule being enabled or removed from https://github.com/CircuitVerse/mobile-app/blob/master/analysis_options.yaml#L9

I refered to this.
So for eg :-
Before it was
class CollaboratorAttributes {
    CollaboratorAttributes({
    this.name,
  });

String name;

and Now
class CollaboratorAttributes {
  String name;
  CollaboratorAttributes({
    this.name,
  });

Im new to this so i dont know i did the right thing or not.

@M-A-D-A-R-A Please explain your changes done in this PR along with how it fixes the rule (sort_constructors_first). Also I don't see this rule being enabled or removed from https://github.com/CircuitVerse/mobile-app/blob/master/analysis_options.yaml#L9

I refered to this.
So for eg :- Before it was
class CollaboratorAttributes {
    CollaboratorAttributes({
    this.name,
  });

String name;

and Now
class CollaboratorAttributes {
  String name;
  CollaboratorAttributes({
    this.name,
  });

Im new to this so i dont know i did the right thing or not.
and yeah it was mentioned in those 26 issue so i started working on this without asking I didn't knew it was disabled.

Remove the rule from analysis_options.yaml.
This https://dart-lang.github.io/linter/lints/sort_constructors_first.html says GOOD as constructor being ordered at first and BAD if constructor is not in first. Your change does exactly the opposite.

@M-A-D-A-R-A Please explain your changes done in this PR along with how it fixes the rule (sort_constructors_first). Also I don't see this rule being enabled or removed from https://github.com/CircuitVerse/mobile-app/blob/master/analysis_options.yaml#L9

I refered to this.
So for eg :- Before it was
class CollaboratorAttributes {
    CollaboratorAttributes({
    this.name,
  });

String name;

and Now
class CollaboratorAttributes {
  String name;
  CollaboratorAttributes({
    this.name,
  });

Im new to this so i dont know i did the right thing or not.
and yeah it was mentioned in those 26 issue so i started working on this without asking I didn't knew it was disabled.

Remove the rule from analysis_options.yaml.
This https://dart-lang.github.io/linter/lints/sort_constructors_first.html says GOOD as constructor being ordered at first and BAD if constructor is not in first. Your change does exactly the opposite.

So should i close this PR ?

@M-A-D-A-R-A Please explain your changes done in this PR along with how it fixes the rule (sort_constructors_first). Also I don't see this rule being enabled or removed from https://github.com/CircuitVerse/mobile-app/blob/master/analysis_options.yaml#L9

I refered to this.
So for eg :- Before it was
class CollaboratorAttributes {
    CollaboratorAttributes({
    this.name,
  });

String name;

and Now
class CollaboratorAttributes {
  String name;
  CollaboratorAttributes({
    this.name,
  });

Im new to this so i dont know i did the right thing or not.
and yeah it was mentioned in those 26 issue so i started working on this without asking I didn't knew it was disabled.

Remove the rule from analysis_options.yaml.
This https://dart-lang.github.io/linter/lints/sort_constructors_first.html says GOOD as constructor being ordered at first and BAD if constructor is not in first. Your change does exactly the opposite.

So should i close this PR ?

If you can fix this rule, then you can make further changes to resolve the issues in this PR otherwise you can close it.

@M-A-D-A-R-A Please explain your changes done in this PR along with how it fixes the rule (sort_constructors_first). Also I don't see this rule being enabled or removed from https://github.com/CircuitVerse/mobile-app/blob/master/analysis_options.yaml#L9

I refered to this.
So for eg :- Before it was
class CollaboratorAttributes {
    CollaboratorAttributes({
    this.name,
  });

String name;

and Now
class CollaboratorAttributes {
  String name;
  CollaboratorAttributes({
    this.name,
  });

Im new to this so i dont know i did the right thing or not.
and yeah it was mentioned in those 26 issue so i started working on this without asking I didn't knew it was disabled.

Remove the rule from analysis_options.yaml.
This https://dart-lang.github.io/linter/lints/sort_constructors_first.html says GOOD as constructor being ordered at first and BAD if constructor is not in first. Your change does exactly the opposite.

So should i close this PR ?

If you can fix this rule, then you can make further changes to resolve the issues in this PR otherwise you can close it.

So like you said it was already in good state I think i shoul close this PR.

@M-A-D-A-R-A Please explain your changes done in this PR along with how it fixes the rule (sort_constructors_first). Also I don't see this rule being enabled or removed from https://github.com/CircuitVerse/mobile-app/blob/master/analysis_options.yaml#L9

I refered to this.
So for eg :- Before it was
class CollaboratorAttributes {
    CollaboratorAttributes({
    this.name,
  });

String name;

and Now
class CollaboratorAttributes {
  String name;
  CollaboratorAttributes({
    this.name,
  });

Im new to this so i dont know i did the right thing or not.
and yeah it was mentioned in those 26 issue so i started working on this without asking I didn't knew it was disabled.

Remove the rule from analysis_options.yaml.
This https://dart-lang.github.io/linter/lints/sort_constructors_first.html says GOOD as constructor being ordered at first and BAD if constructor is not in first. Your change does exactly the opposite.

So should i close this PR ?

If you can fix this rule, then you can make further changes to resolve the issues in this PR otherwise you can close it.

So like you said it was already in good state I think i shoul close this PR.

Please note that the rule is still disabled, our aim is to enable the rule and make the changes if we are not following them so that Flutter Analyzer doesn't throw errors/warnings.

@M-A-D-A-R-A Please explain your changes done in this PR along with how it fixes the rule (sort_constructors_first). Also I don't see this rule being enabled or removed from https://github.com/CircuitVerse/mobile-app/blob/master/analysis_options.yaml#L9

I refered to this.
So for eg :- Before it was
class CollaboratorAttributes {
    CollaboratorAttributes({
    this.name,
  });

String name;

and Now
class CollaboratorAttributes {
  String name;
  CollaboratorAttributes({
    this.name,
  });

Im new to this so i dont know i did the right thing or not.
and yeah it was mentioned in those 26 issue so i started working on this without asking I didn't knew it was disabled.

Remove the rule from analysis_options.yaml.
This https://dart-lang.github.io/linter/lints/sort_constructors_first.html says GOOD as constructor being ordered at first and BAD if constructor is not in first. Your change does exactly the opposite.

So should i close this PR ?

If you can fix this rule, then you can make further changes to resolve the issues in this PR otherwise you can close it.

So like you said it was already in good state I think i shoul close this PR.

Please note that the rule is still disabled, our aim is to enable the rule and make the changes if we are not following them so that Flutter Analyzer doesn't throw errors/warnings.

So should i Enable this this rule?

@M-A-D-A-R-A Please explain your changes done in this PR along with how it fixes the rule (sort_constructors_first). Also I don't see this rule being enabled or removed from https://github.com/CircuitVerse/mobile-app/blob/master/analysis_options.yaml#L9

I refered to this.
So for eg :- Before it was
class CollaboratorAttributes {
    CollaboratorAttributes({
    this.name,
  });

String name;

and Now
class CollaboratorAttributes {
  String name;
  CollaboratorAttributes({
    this.name,
  });

Im new to this so i dont know i did the right thing or not.
and yeah it was mentioned in those 26 issue so i started working on this without asking I didn't knew it was disabled.

Remove the rule from analysis_options.yaml.
This https://dart-lang.github.io/linter/lints/sort_constructors_first.html says GOOD as constructor being ordered at first and BAD if constructor is not in first. Your change does exactly the opposite.

So should i close this PR ?

If you can fix this rule, then you can make further changes to resolve the issues in this PR otherwise you can close it.

So like you said it was already in good state I think i shoul close this PR.

Please note that the rule is still disabled, our aim is to enable the rule and make the changes if we are not following them so that Flutter Analyzer doesn't throw errors/warnings.

So should i Enable this this rule, and then work on this ?

Yep


Adding support to Babylon.JS for morph targets

Fixes a compiler error in serializers (capitalization of a memeber)
Adds support to morph targets to have tangent data

Thanks a lot!


Assembly name is compiling to lower-case in netcoreapp2.1 project.

When I run dotnet build to compile my netcoreapp2.1 project, the System.Reflection.Assembly.FullName is lowercase.
typeof(TestObject).AssemblyQualifiedName returns
Test.TestObject, test, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null
typeof(TestObject).Assembly.FullName returns
test, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null
To Reproduce
Steps to reproduce the behavior:

Create new mvc project using dotnet new mvc
Build project using dotnet build
Write assembly name to console using Console.WriteLine(typeof(TestObject).Assembly.FullName.

Expected behavior
The expected values should be
typeof(TestObject).AssemblyQualifiedName returns
Test.TestObject, Test, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null
typeof(TestObject).Assembly.FullName returns
Test, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null
Additional context
.NET Core SDK (reflecting any global.json):
 Version:   2.1.402
 Commit:    3599f217f4

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

Host (useful for support):
  Version: 2.1.4
  Commit:  85255dde3e

.NET Core SDKs installed:
  1.1.10 [C:\Program Files\dotnet\sdk]
  2.1.201 [C:\Program Files\dotnet\sdk]
  2.1.202 [C:\Program Files\dotnet\sdk]
  2.1.300-preview2-008533 [C:\Program Files\dotnet\sdk]
  2.1.300 [C:\Program Files\dotnet\sdk]
  2.1.302 [C:\Program Files\dotnet\sdk]
  2.1.402 [C:\Program Files\dotnet\sdk]

.NET Core runtimes installed:
  Microsoft.AspNetCore.All 2.1.0-preview2-final [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.1.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.1.1 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.1.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.All 2.1.4 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.All]
  Microsoft.AspNetCore.App 2.1.0-preview2-final [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.1.0 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.1.1 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.1.2 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.AspNetCore.App 2.1.4 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 1.0.12 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 1.1.9 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.0.7 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.0.9 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.1.0-preview2-26406-04 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.1.0 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.1.1 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.1.2 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
  Microsoft.NETCore.App 2.1.4 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]

Also, I tried setting the <AssemblyName> is the .csproj file and it then works as expected.

What is the name of your .csproj file? The default value of AssemblyName is the file name of your project.

Hmm, we did but in that case the csproj was the wrong casing which mucked with the generated assembly name.
For reference here's the issue that was slightly similar, but different 😞 : https://github.com/Microsoft/msbuild/issues/3665

Thanks for contacting us. We're closing this issue as there was no community involvement here for quite a while now. If you're still facing this issue, feel free to reopen it.


Add lookup method to all contexts

Pull Request Type

[ ] Bug fix
[x] New feature
[ ] Refactoring
[ ] Documentation update
[ ] Chore

Description
Add lookup(_:) to all context types to support an ability to find an already cached atom value.

Closing as it might be misused


Want some guidence before contributiing

Hey, @jt-nti I explored this repo and find it interesting and want to contribute to this. I am DevOps and a full-stack web3 developer. Can u please suggest to me some First-time contributions?
Thank You !

Thank you so much for the quick prompt. I raised Pr  #95  (starting from the documentation part).


Support for Android Q Dark Theme

https://developer.android.com/preview/features/darktheme

This was fixed in v3.0.0


feat: update golang-github-spf13-viper to 1.12.0

Go configuration with fangs
Issue: https://github.com/deepin-community/sig-deepin-sysdev-team/issues/552
Log: update repo

/lgtm
/approve


As an administrator, I would like to see a report of all of the accepted pieces with the information associated with them so I would be able to reference back to this easily.

As an administrator, I would like to see a report of all of the accepted pieces with the information associated with them so I would be able to reference back to this easily.

Bigger picture, artist name, dimensions

Report should have  name, group names, title, media type, size, email, and the answers to the questions. I think that is everything.


use bindgen to regenerate bindings at build-time

This keeps compatibility with no_std by using constants from core or by using C types from the libc crate instead of std.

Sure. I'm trying to reproduce the issues I had yesterday right now.

Looking at how bindgen generates typedef for size_t I assume it might be possible that usize in Rust is not equivalent to size_t on some platforms
As otherwise all other integers used by xxhash are fixed size.
So can you point me to sys/types.h used by fedora's toolchain?

Lol surprisingly it doesn't even work as it is on ubunt and macos in github CI...

The only difference can be that size_t is a 32-bit number on 32-bit systems, but a 64-bit number on 64-bit systems. So bindings that are generated on x86_64 and use u64 instead of usize for size_t are not compatible with 32-bit libraries, but if they use usize, it should do the correct thing.

I manually checked my bindings, they use size_t
I know remember why I stopped using bindgen
It incorrectly generated definitions of state.
See what is generated on my machine
#[repr(C)]
#[derive(Debug, Copy, Clone)]
pub struct XXH3_state_s {
    _unused: [u8; 0],
}

Real definition:
pub const XXH3_INTERNALBUFFER_SIZE: libc::c_int = 256;
pub const XXH3_SECRET_DEFAULT_SIZE: libc::c_int = 192;
#[repr(C)]
#[repr(align(64))]
#[derive(Debug, Copy, Clone)]
struct Acc([XXH64_hash_t; 8]);
#[repr(C)]
#[repr(align(64))]
#[derive(Debug, Copy, Clone)]
struct CustomSecret([u8; XXH3_SECRET_DEFAULT_SIZE as usize]);
#[repr(C)]
#[repr(align(64))]
#[derive(Debug, Copy, Clone)]
struct Buffer([u8; XXH3_INTERNALBUFFER_SIZE as usize]);
#[repr(C)]
#[derive(Debug, Copy, Clone)]
pub struct XXH3_state_s {
    acc: Acc,
    customSecret: CustomSecret,
    buffer: Buffer,
    bufferedSize: XXH32_hash_t,
    useSeed: XXH32_hash_t,
    nbStripesSoFar: usize,
    totalLen: XXH64_hash_t,
    nbStripesPerBlock: usize,
    secretLimit: usize,
    seed: XXH64_hash_t,
    reserved64: XXH64_hash_t,
    extSecret: *const u8,
}
pub type XXH3_state_t = XXH3_state_s;

Test probably segfaults because it allocates state on stack, since struct is invalid, it crashes

It incorrectly generated definitions of state.

Yeah, that doesn't look right. But this means that Clang cannot parse xxhash source code correctly, which should be a problem in its own ...

Test probably segfaults because it allocates state on stack, since struct is invalid, it crashes

Makes sense.
Either way: The original issue I had with compiling this crate happened with 0.8.1, but I cannot reproduce the same problem with 0.8.2 or 0.8.3, so some change between 0.8.1 and 0.8.2 seems to have fixed the struct size mismatch on i686.

Yeah, 0.8.1 is the only one that seems broken on i686.
Here are builds of unmodified sources of xxhash-c-sys for multiple architectures:
https://copr.fedorainfracloud.org/coprs/decathorpe/sequoia-test-builds/package/rust-xxhash-c-sys/
You can see that 0.8.1 failed on i686:
https://copr.fedorainfracloud.org/coprs/decathorpe/sequoia-test-builds/build/4221704/
With this error message:
     Running unittests (target/release/deps/xxhash_c_sys-c76e559b2bcbaa0f)
running 4 tests
test bindings::bindgen_test_layout_XXH128_canonical_t ... ok
test bindings::bindgen_test_layout_XXH32_canonical_t ... ok
test bindings::bindgen_test_layout_XXH128_hash_t ... FAILED
test bindings::bindgen_test_layout_XXH64_canonical_t ... ok
failures:
---- bindings::bindgen_test_layout_XXH128_hash_t stdout ----
thread 'bindings::bindgen_test_layout_XXH128_hash_t' panicked at 'assertion failed: `(left == right)`
  left: `4`,
 right: `8`: Alignment of XXH128_hash_t', src/bindings.rs:267:5
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
failures:
    bindings::bindgen_test_layout_XXH128_hash_t
test result: FAILED. 3 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s

The later versions succeeded.

@decathorpe Ah I understand why
These layout tests are target dependent hence(I mention it again, but I don't trust bindgen to do work properly)
I probably removed them because they were useless anyway
    assert_eq!(
        ::core::mem::align_of::<XXH128_hash_t>(),
        8usize,
        concat!("Alignment of ", stringify!(XXH128_hash_t))
    );

Imagine hardcoding 8 instead of doing sum of size_of of each field 😄

I suggest to use my modified bindgen bindings.
They are completely cross-platform

These layout tests are target dependent

Well, of course they are. Which is why they are also re-generated for the target platform when running bindgen at build-time ;)

I suggest to use my modified bindgen bindings.

I will consider doing that. Thanks for helping me investigate.

Ok, I'll yank 0.8.1 just in case.
Bindings themself are valid, but tests broken so hopefully no one will encounter it again


Add DeleteHost func to service pkg

We have some automation that deletes hosts matching some predefined filters to avoid a build up of dead hosts.
The client struct doesn't currently expose a function for calling the delete api. This PR adds such a function and matches the style of the existing delete functions for other kolide objects.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: zwass:x: IainSteersYou have signed the CLA already but the status is still pending? Let us recheck it.

Hey @zwass I've signed the CLA
Apologies about the import ordering, my IDE must have re-arranged

No worries and thank you for the contribution!


matplotlib raises [WinError 10054] in visual code debugging session

I'm debugging with visual code locally and trying to plot with matplotlib. after executing any plot command, say: plt.plot([0,1,2,3])
This error shuts down the debug session:
[WinError 10054] An existing connection was forcibly closed by the remote host
visual code pyhton version: v2022.10.1
python version: 3.7.13
anaconda version: 4.13.0
matplotlib: 3.5.1
OS Name 	Microsoft Windows 11 Pro
Version	10.0.22000 Build 22000
This seems to persist regardless of my local pc connection.
Does anyone know what may cause this?

/extPython

It looks like this is caused by the Python extension. Please file the issue to the Python extension repository. Make sure to check their issue reporting template and provide them relevant information such as the extension version you're using. See also our issue reporting guidelines for more information.
Happy Coding!

Thank you


feat(commerce): Create PLP v2 facet & facet generator controllers

This is a productized version of facet and facet generator controllers as introduced in https://github.com/coveo/ui-kit/pull/3116
The facets in PLP v2 behave a bit like automatic facets, in the sense that the backend decides which facets should be displayed. Therefore, the facet controller for PLP v2 should never be used directly, only the facet generator controller.
CAPI-87

Superseded by https://github.com/coveo/ui-kit/pull/3332


[Feature improvement] Disable preview window from shellscript

[x] I have read through the manual page (man fzf)
[x] I have the latest version of fzf
[x] I have searched through the existing issues

Info

OS

[x] Linux
[ ] Mac OS X
[ ] Windows
[ ] Etc.

Shell

[ ] bash
[x] zsh
[ ] fish

Problem / Steps to reproduce
I don't want to display the preview window when shellscript returns empty string.
I want to always display the preview window, But I want to control only the specific pattern from shellscript.
export FZF_DEFAULT_OPTS='--preview "~/.zsh/rc/myplugins/fzf-preview.sh {}"'

if [[ -e ${input} && $(file --mime ${input}) =~ /directory ]]; then
  ls -1 --color=always ${input}
elif [[ -e ${input} && $(file --mime ${input}) =~ binary ]]; then
  echo -ne "" # I don't want to show the preview window
elif [[ ${input} =~ .*:[[:digit:]]*:.* ]]; then
  # etc
fi

I was about to write a similar feature request.
Two issues I can see here is having the preview open and close when having a list where only some items have a preview.
Also when using cat an empty file wouldn't show a preview. This could be confusing.

Hide preview window, when preview is empty string?


Exclusive ranges

Is it possible to create a Doubles generator that does not include +Infinite and -Infinite? All the between/range methods take inclusive parameters. Would it be possible to have methods are exclusive? Obviously, you can't something like between(Double.NEGATIVE_INFINITY + 1, Double.POSITIVE_INFINITY - 1)

For Doubles, I believe you can use new DoublesDSL().between(-Double.MAX_VALUE, Double.MAX_VALUE).


#1090 Show refused offers endpoint

after rebase master

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Thanks so much for the PR, left some comments for you

I added master changes, but I am not sure how to really improve it by changing TaskBuilder.

@tmmi Thanks for the PR. We have a similar change on our roadmap and expect to address it soon. Because it will also be involved with the pods work, I'd suggest we close this PR out and we will address it.

@jasongilanfarr thx for info. I'm curious what you come up with.


Rename Twine.register to Twine.afterBound

Twine.register is poorly named and is confusing people about what it actually does. This renames it to afterBound so it's more explicit about what it does.
@qq99 @kristianpd @dfmcphee

postBind?  I like the idea, but it's a bit much to type afterBindingsFinish?

And is it:

after all bindings finish binding?
after all bindings have finished firing?

After the bindings on the current node (and its subtree) have finished

Not liking postBind, especially in a web context does that mean like POSTing something to the server?

What about the other suggestions like afterBound?  cc @Shopify/tnt

I like onBind.

:+1: afterBound
onBind isn't really accurate either

Updated to afterBound

want to re-write your commit message too?  Going to bump the version to 0.1.0 because this is a non backwards compatible change

0.2.0*

And now I notice that I messed up the version numbers a couple releases ago. It went from 0.0.16 to 0.1.17. Doh

lol!  no worries
we can just bump to 0.2.0

Actually the packages and everything were correct. It was just the release names that were off so I edited them

:clap:


.scaledToFit() with maxWidth

Hi,
I'm trying to scale in image to fix the content but without exceeding the original size of the image (to not loose quality).
This works as expected:
Image(uiImage: image)
    .resizable()
    .scaledToFit()
    .frame(maxWidth: image.size.width/UIScreen.main.scale, maxHeight: image.size.height/UIScreen.main.scale)

I'm having trouble replicating the same behaviour with WebImage
WebImage(url: image)
    .resizable()
    .scaledToFit()
//  .frame(maxWidth: image.size.width/UIScreen.main.scale, maxHeight: image.size.height/UIScreen.main.scale)

Am I missing something? Is there a way to get the size of the downloaded image?

If you need the information of downloaded image, use onSuccess to get the image, and then refresh the state to update the view's frame modifier

Awesome, thank you.
This did the trick:

var image: URL?

@State var imageSize: CGSize = .zero

var body: some View {

    WebImage(url: image)
        .onSuccess { image, _, _ in
            imageSize = image.size
        }
        .resizable()
        .scaledToFit()
        .frame(maxWidth: imageSize.width/UIScreen.main.scale, maxHeight: imageSize.height/UIScreen.main.scale)
}


New Action Template uses deprecated is_string param

When you create a new action using fastlane new_action, the action that is produced from the template uses the is_string parameter to FastLaneCore::ConfigItem. This is produced from this template:
https://github.com/fastlane/fastlane/blob/a6641e6e4b990cbf7e421384ada0f11b21d42930/fastlane/lib/assets/custom_action_template.rb#L52
The template should use the type parameter instead as documented here: https://github.com/fastlane/fastlane/blob/master/fastlane_core/lib/fastlane_core/configuration/config_item.rb#L14

That's interesting. I was looking at how to fix this properly on top of #3707 but realized that I would probably need to add tests to make sure the lack of Boolean type doesn't cause strange issues.
In fact, according to my tests, if you want a boolean, you need to pass is_string: false otherwise data_type is set to String (because there's no data_type for Booleans.)
Maybe @KrauseFx  has some input on that ?

Thanks @marcomorain, nice catch! Unfortunately there is no type for Boolean in Ruby, so we can't just use type: Bool as far as I know.

We could

ask people to use TrueClass or FalseClass for boolean but that would make some weird code / config
create a Boolean class ...
forget about this ?

Maybe not show a deprecated warning and lave it like is?

Maybe. I just find the API confusing. One tells to not use is_string but it's compulsory for booleans...

I also ran into this issue recently. I was trying to create a parameter that expected an Array object, but initially thought it wasn't possible due to the template's usage of is_string. Only through some searching was I able to find that the type parameter should be used and that it has built-in support for converting string input into an Array if the ConfigItem's type is equal to Array.
I think using type instead of the deprecated is_string would help to expose this functionality to new users.
To @lacostej's point about Boolean, I've been using type: Object which works. It's not really clear, but neither is is_string: false - I think the other benefits of using type make up for this.


Fixes for ina219/ina226

For both drivers shell code has warning in new compilers
For INA219 voltage calculation was not correct for 32V or 16V range depending on
random bit.

Stats indent complain is not worth fixing. Style checker should be updated if anyone can do this.


linear classification bug fix: kv may be None

@eric-haibin-lin @piiswrong

being fixed in another pr

Thanks anyway :)


kubernetes cni plugin + flannel + docker networking issues

Sort of related to https://github.com/coreos/coreos-kubernetes/issues/572. In this issue rkt containers couldn't contact service IPs because docker was creating a docker0 bridge with an IP that was passed in from flannel (for direct docker + flannel configuration). I disabled this bridge ip option and rkt cni networking was fixed.
However, docker networking with cni remains broken. docker0 and cni0 are both created. Presumably pods being created from kubernetes are just told to use the cni0 bridge, but, I think there is something I don't understand here. Interestingly enough if you configure the USE_CALICO option, docker appears to work and cni0 is never created.
This is reproducible from my rktnetes PR since it configures both rkt and docker through a cni config passed to the kubelet. Pods not using --net=host such as dns and the dashboard will crashloop.
@steveeJ @euank

/cc @tomdee

To be clear, is the old method of using flannel directly via docker being disabled entirely (the subnet and bip bits) in favor of CNI?

Disabling only in the sense that we don't pass certain options into dockerd that we used to do. Not sure if there are other hooks here I am missing.

@pbx0 Doing some log diving, the dns image is trying to access the <IP_ADDRESS> service ip. That ip indeed does not appear to be routable. I think the root cause of that is a lack of a running kube-proxy.

Ack yes, sadly this was PEBKAK type of error where a misconfigured slipped that was causing the proxy not to run for docker. Closing.

Sorry, I was on vacation for the last week this missed this issue. Glad you solved it, ping me if I can provide any other help.

@pbx0 I just converted over to using rktnetes+CNI, and I'm now hitting this too (related https://github.com/coreos/coreos-kubernetes/issues/572).  What was the misconfiguration you found?  I'm thinking something is left over from the old flannel only config.
interfaces:
cni0: <IP_ADDRESS>/24
docker0: <IP_ADDRESS>/24

@TerraTech I'm not sure if your having the same issue as I did in this issue but, I have run into this before! See: https://github.com/coreos/coreos-kubernetes/issues/698#issuecomment-250633015
Basically, flannel is passing two environment variables to the docker daemon that is no longer needed with CNI. If those variables aren't removed the docker0 bridge will come up with the same IP as the cni0 bridge and cause problems. The fix is in these two commits:
Original Change: 7ad1347
A followup commit that works with docker 1.11 and 1.12: 00591a2
The first commit adds a drop-in to the docker.service that leaves out the DOCKER_OPT_BIP
DOCKER_OPT_IPMASQ environment variables that are set by flannel. The second commit just overrides those variables with an Environment file because the dockerd command line changed recently making the first fix obsolete.
Let me know if this doesn't solve your problem.

@pbx0 thanks for the followup!
My attention got diverted to https://github.com/coreos/coreos-kubernetes/issues/707 and at this point, I just shutdown docker on the master and workers since the cluster is based on rktnetes.  So far, the regular podnet is working fine with no collisions, though I'm having a major problem with the service IPs.


Remove using namespace std; from files

ModelLoader.hpp is the only file this applies to

fixed by community pull request


Metadata again..

Metadata/tags has been sadly overlooked, as it is now every integration patches its own.
I suggest we address this by making metadata available in the audio_backend.
Ex. Pulseaudio has a more or less well defined API where it uses properties, Airplay supports its own tags, for the stdout backend we can continue to use stderr as the simple "Track loading" stuff does today but should be expanded with more tags. Currently metadata is not a part of the audio backend API at all as far as I can tell.
Also, all the basic tags should be available without having to lookup in Spotify again as that would push complexity into audio distribution (Pulseaudio, Snapcast). Adding a tag for Spotify reference would be nice to enable elaborate UI's (ex Kodi with a lot of track info) but basic info should be available without complexity.
Any ideas?

Hmm, is this maintained at all anymore? Or moved somewhere else?
Anyone?

See the readme here:
https://github.com/plietar/librespot#unmaintained

Ye, have any1 come forward to take ownership or do we all fragment it into our own special versions?
 :)

Tempting but my rust skills are more than rusty S
We are probably better off with someone who can evaluate pulls...


Install translation/localization plugin to the website (English Version)

WPML or another option...
Necessary functionality:

Ability to input translated versions of UI
Ability to switch the language

Not sure whether it's best/easiest to translate text in-context or just create separate page in English - thoughts?

I know you probably already have this handled @antoinewolff I'm just updating it for the i18n board! https://github.com/orgs/dis-moi/projects/2

@christpet : You can see a exemple with contact page :

fr : https://www.dismoi.io/contact/
en : https://www.dismoi.io/en/contact/

Looking great @antoinewolff ! I will close this and we can create a new issue for other translations as they come in.


Grid container spacing not working (weird behavior)

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Current behavior 😯
Currently the items inside a grid container do not respect the spacing passed to the container component.
The only effect when adding spacing is that the items change in size/position on the screen.
CSB: https://codesandbox.io/s/thirsty-cerf-kjhi4s?file=/src/App.js
Expected behavior 🤔
Items inside a grid container should respect the spacing prop passed to the container.
Steps to reproduce 🕹
Steps:

Start a react project and install material's and its dependencies latest verions
Create a <Grid container> with 2 <Grid item> inside
Give, for example, spacing={4} to the container
It doesn't space out items

Simplest reproducible CSB: https://codesandbox.io/s/thirsty-cerf-kjhi4s?file=/src/App.js
Context 🔦
Simple issue, no context needed IMO.
Your environment 🌎

npx @mui/envinfo
System:
    OS: Linux 5.10 Ubuntu 20.04.4 LTS (Focal Fossa)
  Binaries:
    Node: 16.14.2 - ~/.nvm/versions/node/v16.14.2/bin/node
    Yarn: Not Found
    npm: 8.5.0 - ~/.nvm/versions/node/v16.14.2/bin/npm
  Browsers:
    Chrome: 103.0.5060.134
    Firefox: Not Found
  npmPackages:
    @emotion/react: ^11.10.0 => 11.10.0
    @emotion/styled: ^11.10.0 => 11.10.0
    @mui/base:  5.0.0-alpha.91
    @mui/icons-material: ^5.8.4 => 5.8.4
    @mui/lab: ^5.0.0-alpha.93 => 5.0.0-alpha.93
    @mui/material: ^5.9.2 => 5.9.2
    @mui/private-theming:  5.9.3
    @mui/styled-engine:  5.8.7
    @mui/system:  5.9.3
    @mui/types:  7.1.5
    @mui/utils:  5.9.3
    @types/react: ^18.0.15 => 18.0.15
    react: ^18.2.0 => 18.2.0
    react-dom: ^18.2.0 => 18.2.0
    typescript: ^4.6.4 => 4.7.4

It works. See https://codesandbox.io/s/exciting-brown-67sve2?file=/src/App.js.
The item prop in Grid will have the flex item behaviour. The spacing prop applies padding at the item level. By adding custom styles to grid item component itself (via the sx prop) you are customizing the padding and it's inbuilt styles. You need to apply your custom styles to the child components (Typography).


[google_maps_flutter] Trying to create an already created platform view

Hi,
When using the google_maps_flutter plugin I'm encountering some weirdness.
When running the app in debug first time everything is fine, but attempts to load the map after a rebuild (just hitting Play on AndroidStudio) the following error is being thrown and the map is blacked out:
E/flutter (23023): [ERROR:flutter/lib/ui/ui_dart_state.cc(157)] Unhandled Exception: PlatformException(error, java.lang.IllegalStateException: Trying to create an already created platform view, view id: 0
E/flutter (23023): 	at io.flutter.plugin.platform.PlatformViewsController$1.createPlatformView(PlatformViewsController.java:85)
E/flutter (23023): 	at io.flutter.embedding.engine.systemchannels.PlatformViewsChannel$1.create(PlatformViewsChannel.java:96)
E/flutter (23023): 	at io.flutter.embedding.engine.systemchannels.PlatformViewsChannel$1.onMethodCall(PlatformViewsChannel.java:60)
E/flutter (23023): 	at io.flutter.plugin.common.MethodChannel$IncomingMethodCallHandler.onMessage(MethodChannel.java:231)
E/flutter (23023): 	at io.flutter.embedding.engine.dart.DartMessenger.handleMessageFromDart(DartMessenger.java:93)
E/flutter (23023): 	at io.flutter.embedding.engine.FlutterJNI.handlePlatformMessage(FlutterJNI.java:642)
E/flutter (23023): 	at android.os.MessageQueue.nativePollOnce(Native Method)
E/flutter (23023): 	at android.os.MessageQueue.next(MessageQueue.java:326)
E/flutter (23023): 	at android.os.Looper.loop(Looper.java:160)
E/flutter (23023): 	at android.app.ActivityThread.main(ActivityThread.java:6718)
E/flutter (23023): 	at java.lang.reflect.Method.invoke(Native Method)
E/flutter (23023): 	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
E/flutter (23023): 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)
E/flutter (23023): , null)
E/flutter (23023): #0      StandardMethodCodec.decodeEnvelope (package:flutter/src/services/message_codecs.dart:569:7)
E/flutter (23023): #1      MethodChannel.invokeMethod (package:flutter/src/services/platform_channel.dart:321:33)
E/flutter (23023): <asynchronous suspension>
E/flutter (23023): #2      AndroidViewController._create (package:flutter/src/services/platform_views.dart:640:54)
E/flutter (23023): #3      AndroidViewController.setSize (package:flutter/src/services/platform_views.dart:557:14)
E/flutter (23023): #4      RenderAndroidView._sizePlatformView (package:flutter/src/rendering/platform_view.dart:174:29)
E/flutter (23023): #5      RenderAndroidView.performResize (package:flutter/src/rendering/platform_view.dart:155:5)
E/flutter (23023): #6      RenderObject.layout (package:flutter/src/rendering/object.dart:1703:9)
E/flutter (23023): #7      RenderProxyBoxMixin.performLayout (package:flutter/src/rendering/proxy_box.dart:105:13)
E/flutter (23023): #8      RenderObject.layout (package:flutter/src/rendering/object.dart:1724:7)
E/flutter (23023): #9      RenderStack.performLayout (package:flutter/src/rendering/stack.dart:505:15)
E/flutter (23023): #10     RenderObject.layout (package:flutter/src/rendering/object.dart:1724:7)
E/flutter (23023): #11     RenderProxyBoxMixin.performLayout (package:flutter/src/rendering/proxy_box.dart:105:13)
E/flutter (23023): #12     RenderObject.layout (package:flutter/src/rendering/object.dart:1724:7)
E/flutter (23023): #13     RenderProxyBoxMixin.performLayout (package:flutter/src/rendering/proxy_box.dart:105:13)
E/flutter (23023): #14     RenderObject.layout (package:flutter/src/rendering/object.dart:1724:7)
E/flutter (23023): #15     RenderProxyBoxMixin.performLayout (package:flutter/src/rendering/proxy_box.dart:105:13)
E/flutter (23023): #16     RenderObject.layout (package:flutter/src/rendering/object.dart:1724:7)
E/flutter (23023): #17     RenderProxyBoxMixin.performLayout (package:flutter/src/rendering/proxy_box.dart:105:13)
E/flutter (23023): #18     RenderObject.layout (package:flutter/src/rendering/object.dart:1724:7)
E/flutter (23023): #19     RenderProxyBoxMixin.performLayout (package:flutter/src/rendering/proxy_box.dart:105:13)
E/flutter (23023): #20     RenderObject.layout (package:flutter/src/rendering/object.dart:1724:7)
E/flutter (23023): #21     RenderProxyBoxMixin.performLayout (package:flutter/src/rendering/proxy_box.dart:105:13)
E/flutter (23023): #22     RenderObject.layout (package:flutter/src/rendering/object.dart:1724:7)
E/flutter (23023): #23     RenderProxyBoxMixin.performLayout (package:flutter/src/rendering/proxy_box.dart:105:13)
E/flutter (23023): #24     RenderObject.layout (package:flutter/src/rendering/object.dart:1724:7)
E/flutter (23023): #25     RenderOffstage.performLayout (package:flutter/src/rendering/proxy_box.dart:3166:14)
E/flutter (23023): #26     RenderObject.layout (package:flutter/src/rendering/object.dart:1724:7)
E/flutter (23023): #27     RenderStack.performLayout (package:flutter/src/rendering/stack.dart:505:15)
E/flutter (23023): #28     RenderObject._layoutWithoutResize (package:flutter/src/rendering/object.dart:1584:7)
E/flutter (23023): #29     PipelineOwner.flushLayout (package:flutter/src/rendering/object.dart:844:18)
E/flutter (23023): #30     RendererBinding.drawFrame (package:flutter/src/rendering/binding.dart:344:19)
E/flutter (23023): #31     WidgetsBinding.drawFrame (package:flutter/src/w

If I hit the Stop button then rebuild it after a few moments the error is displayed again but the app loads and works just fine. It seems weird that an error is occurring during runtime then reoccurring during a build. Any advice on this? Sorry that I'm not more technically versed with this sort of thing.

Hi @Pebsie
could you please provide your updated  flutter doctor -v ?
Thank you

I switched from stable to master and this issue is no longer occurring.

Same here. I upgraded to the master channel and the error remained.
flutter doctor -v:
[√] Flutter (Channel master, v1.13.4-pre.3, on Microsoft Windows [versÃ£o 10.0.18363.535], locale pt-BR)
    • Flutter version 1.13.4-pre.3 at C:\dev\flutter
    • Framework revision bd25f70c66 (7 hours ago), 2019-12-19 09:45:02 -0800
    • Engine revision 0f90e6546b
    • Dart version 2.8.0 (build 2.8.0-dev.0.0 aa6709974d)

[√] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at C:\AndroidSDK
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-29, build-tools 29.0.2
    • ANDROID_HOME = C:\AndroidSDK
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b03)
    • All Android licenses accepted.

[√] Android Studio (version 3.5)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin version 42.1.1
    • Dart plugin version 191.8593
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b03)

[√] Connected device (1 available)
    • ONEPLUS A3000 • e1636bc6 • android-arm64 • Android 9 (API 28)

• No issues found!

Hi,@thiagotalma! Same here.Have you did this problem?

same here, didnt found any solution for this

[✓] Flutter (Channel master, v1.13.6-pre.25, on Linux, locale en_IN)
    • Flutter version 1.13.6-pre.25 at /home/asus/Documents/Flutter_SDK/flutter
    • Framework revision b7af5e714d (72 minutes ago), 2019-12-25 23:49:55 -0800
    • Engine revision 33813929e3
    • Dart version 2.8.0 (build 2.8.0-dev.0.0 886615d0f9)

[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at /home/asus/Android/Sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-29, build-tools 29.0.2
    • Java binary at: /snap/android-studio/81/android-studio/jre/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)
    • All Android licenses accepted.

[✗] Chrome - develop for the web (Cannot find chrome executable at google-chrome)
    ! Cannot find Chrome. Try setting CHROME_EXECUTABLE to a Chrome executable.

[✓] Android Studio (version 3.5)
    • Android Studio at /snap/android-studio/81/android-studio
    • Flutter plugin version 42.1.1
    • Dart plugin version 191.8593
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)

[✓] Connected device (2 available)
    • vivo 1723  • 49269ad3   • android-arm64  • Android 9 (API 28)
    • Web Server • web-server • web-javascript • Flutter Tools

! Doctor found issues in 1 category.

Hello @cn-Meepo ! I also couldn't solve this problem. Let's wait for the expert opinion.
Probably best to open a new issue.
What do you think, @iapicca ?

I have the same issue

i have the same issu here ? How to solve it ?

I have the same issue

Same here from long time, but i'm trying to solve it now ...
i didn't try Master channel yet too ..

Stackoverflow issue link

I have the same issue

i have the same issue

i have the same issue

I have the same issue, anyone got solution for this one?

Hi all,
can you please provide your flutter doctor -v
and your flutter run --verbose?
Thank you

@iapicca hi!
flutter doctor -v
D:\project\juant_base>flutter doctor -v
[√] Flutter (Channel stable, v1.12.13+hotfix.5, on Microsoft Windows [Version 10.0.14393], locale zh-CN)
• Flutter version 1.12.13+hotfix.5 at D:\java\flutter
• Framework revision 27321ebbad (3 weeks ago), 2019-12-10 18:15:01 -0800
• Engine revision 2994f7e1e6
• Dart version 2.7.0
[√] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
• Android SDK at D:\java\android-sdk
• Android NDK location not configured (optional; useful for native profiling support)
• Platform android-29, build-tools 29.0.2
• ANDROID_HOME = D:\java\android-sdk
• Java binary at: C:\Users\meepo\AppData\Local\JetBrains\Toolbox\apps\AndroidStudio\ch-0\191.6010548\jre\bin\java
• Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b03)
• All Android licenses accepted.
[√] Android Studio (version 3.5)
• Android Studio at C:\Users\meepo\AppData\Local\JetBrains\Toolbox\apps\AndroidStudio\ch-0\191.6010548
• Flutter plugin version 42.1.1
• Dart plugin version 191.8593
• Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b03)
[√] IntelliJ IDEA Ultimate Edition (version 2019.3)
• IntelliJ at C:\Users\meepo\AppData\Local\JetBrains\Toolbox\apps\IDEA-U\ch-0\193.5662.53
• Flutter plugin version 35.3.3
• Dart plugin version 191.7221
[√] Connected device (1 available)
• MI 6 • bc840644 • android-arm64 • Android 9 (API 28)
• No issues found!
E/flutter (31354): [ERROR:flutter/lib/ui/ui_dart_state.cc(157)] Unhandled Exception: PlatformException(error, java.lang.IllegalStateException: Trying to create an already created platform view, view id: 0
E/flutter (31354):      at io.flutter.plugin.platform.PlatformViewsController$1.createPlatformView(PlatformViewsController.java:85)
E/flutter (31354):      at io.flutter.embedding.engine.systemchannels.PlatformViewsChannel$1.create(PlatformViewsChannel.java:96)
E/flutter (31354):      at io.flutter.embedding.engine.systemchannels.PlatformViewsChannel$1.onMethodCall(PlatformViewsChannel.java:60)
E/flutter (31354):      at io.flutter.plugin.common.MethodChannel$IncomingMethodCallHandler.onMessage(MethodChannel.java:231)
E/flutter (31354):      at io.flutter.embedding.engine.dart.DartMessenger.handleMessageFromDart(DartMessenger.java:93)
E/flutter (31354):      at io.flutter.embedding.engine.FlutterJNI.handlePlatformMessage(FlutterJNI.java:642)
E/flutter (31354):      at android.os.MessageQueue.nativePollOnce(Native Method)
E/flutter (31354):      at android.os.MessageQueue.next(MessageQueue.java:332)
E/flutter (31354):      at android.os.Looper.loop(Looper.java:168)
E/flutter (31354):      at android.app.ActivityThread.main(ActivityThread.java:6878)
E/flutter (31354):      at java.lang.reflect.Method.invoke(Native Method)
E/flutter (31354):      at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:547)
E/flutter (31354):      at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:876)
E/flutter (31354): , null)
E/flutter (31354): #0      StandardMethodCodec.decodeEnvelope (package:flutter/src/services/message_codecs.dart:569:7)
E/flutter (31354): #1      MethodChannel.invokeMethod (package:flutter/src/services/platform_channel.dart:321:33)
E/flutter (31354):
E/flutter (31354): #2      AndroidViewController._create (package:flutter/src/services/platform_views.dart:640:54)
E/flutter (31354): #3      AndroidViewController.setSize (package:flutter/src/services/platform_views.dart:557:14)
E/flutter (31354): #4      RenderAndroidView._sizePlatformView (package:flutter/src/rendering/platform_view.dart:174:29)
E/flutter (31354): #5      RenderAndroidView.performResize (package:flutter/src/rendering/platform_view.dart:155:5)
E/flutter (31354): #6      RenderObject.layout (package:flutter/src/rendering/object.dart:1703:9)
E/flutter (31354): #7      RenderProxyBoxMixin.performLayout (package:flutter/src/rendering/proxy_box.dart:105:13)
E/flutter (31354): #8      RenderObject.layout (package:flutter/src/rendering/object.dart:1724:7)
E/flutter (31354): #9      RenderStack.performLayout (package:flutter/src/rendering/stack.dart:505:15)
E/flutter (31354): #10     RenderObject.layout (package:flutter/src/rendering/object.dart:1724:7)
E/flutter (31354): #11     RenderFlex.performLayout (package:flutter/src/rendering/flex.dart:806:17)
E/flutter (31354): #12     RenderObject.layout (package:flutter/src/rendering/object.dart:1724:7)
E/flutter (31354): #13     MultiChildLayoutDelegate.layoutChild (package:flutter/src/rendering/custom_layout.dart:163:11)
E/flutter (31354): #14     _ScaffoldLayout.performLayout (package:flutter/src/material/scaffold.dart:477:7)
E/flutter (31354): #15     MultiChildLayoutDelegate._callPerformLayout (package:flutter/src/rendering/custom_layout.dart:232:7)
E/flutter (31354): #16     RenderCustomMultiChildLayoutBox.performLayout (package:flutter/src/rendering/custom_layout.dart:391:14)
E/flutter (31354): #17     RenderObject._layoutWithoutResize (package:flutter/src/rendering/object.dart:1584:7)
E/flutter (31354): #18     PipelineOwner.flushLayout (package:flutter/src/rendering/object.dart:844:18)
E/flutter (31354): #19     RendererBinding.drawFrame (package:flutter/src/rendering/binding.dart:344:19)
E/flutter (31354): #20     WidgetsBinding.drawFrame (package:flutter/src/widgets/binding.dart:774:13)
E/flutter (31354): #21     RendererBinding._handlePersistentFrameCallback (package:flutter/src/rendering/binding.dart:283:5)
E/flutter (31354): #22     SchedulerBinding._invokeFrameCallback (package:flutter/src/scheduler/binding.dart:1102:15)
E/flutter (31354): #23     SchedulerBinding.handleDrawFrame (package:flutter/src/scheduler/binding.dart:1041:9)
E/flutter (31354): #24     SchedulerBinding._handleDrawFrame (package:flutter/src/scheduler/binding.dart:957:5)
E/flutter (31354): #25     _rootRun (dart:async/zone.dart:1126:13)
E/flutter (31354): #26     _CustomZone.run (dart:async/zone.dart:1023:19)
E/flutter (31354): #27     _CustomZone.runGuarded (dart:async/zone.dart:925:7)
E/flutter (31354): #28     _invoke (dart:ui/hooks.dart:259:10)
E/flutter (31354): #29     _drawFrame (dart:ui/hooks.dart:217:3)
E/flutter (31354):

I have the same issue

@iapicca
flutter run --verbose
[        ] Notification from VM: {streamId: Isolate, event: {type: Event, kind: ServiceExtensionAdded, isolate: {type: @Isolate, id: isolates/746611116116959, name: main, number:<PHONE_NUMBER>16959}, timestamp:
1577706539960, extensionRPC: ext.flutter.inspector.isWidgetCreationTracked}}
[        ] Notification from VM: {streamId: Isolate, event: {type: Event, kind: ServiceExtensionAdded, isolate: {type: @Isolate, id: isolates/746611116116959, name: main, number:<PHONE_NUMBER>16959}, timestamp:
1577706539960, extensionRPC: ext.flutter.inspector.screenshot}}
[+2148 ms] I/flutter ( 9922): location permission PermissionStatus.granted
[  +19 ms] E/flutter ( 9922): [ERROR:flutter/lib/ui/ui_dart_state.cc(157)] Unhandled Exception: PlatformException(error, java.lang.IllegalStateException: Trying to create an already created platform view, view
id: 0
[   +1 ms] E/flutter ( 9922): 	at io.flutter.plugin.platform.PlatformViewsController$1.createPlatformView(PlatformViewsController.java:85)
[        ] E/flutter ( 9922): 	at io.flutter.embedding.engine.systemchannels.PlatformViewsChannel$1.create(PlatformViewsChannel.java:96)
[        ] E/flutter ( 9922): 	at io.flutter.embedding.engine.systemchannels.PlatformViewsChannel$1.onMethodCall(PlatformViewsChannel.java:60)
[        ] E/flutter ( 9922): 	at io.flutter.plugin.common.MethodChannel$IncomingMethodCallHandler.onMessage(MethodChannel.java:231)
[        ] E/flutter ( 9922): 	at io.flutter.embedding.engine.dart.DartMessenger.handleMessageFromDart(DartMessenger.java:93)
[        ] E/flutter ( 9922): 	at io.flutter.embedding.engine.FlutterJNI.handlePlatformMessage(FlutterJNI.java:642)
[        ] E/flutter ( 9922): 	at android.os.MessageQueue.nativePollOnce(Native Method)
[        ] E/flutter ( 9922): 	at android.os.MessageQueue.next(MessageQueue.java:330)
[        ] E/flutter ( 9922): 	at android.os.Looper.loop(Looper.java:169)
[        ] E/flutter ( 9922): 	at android.app.ActivityThread.main(ActivityThread.java:7135)
[        ] E/flutter ( 9922): 	at java.lang.reflect.Method.invoke(Native Method)
[        ] E/flutter ( 9922): 	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:537)
[        ] E/flutter ( 9922): 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:876)
[        ] E/flutter ( 9922): , null)
[        ] E/flutter ( 9922): #0      StandardMethodCodec.decodeEnvelope (package:flutter/src/services/message_codecs.dart:569:7)
[        ] E/flutter ( 9922): #1      MethodChannel.invokeMethod (package:flutter/src/services/platform_channel.dart:321:33)
[        ] E/flutter ( 9922): <asynchronous suspension>
[        ] E/flutter ( 9922): #2      AndroidViewController._create (package:flutter/src/services/platform_views.dart:640:54)
[        ] E/flutter ( 9922): #3      AndroidViewController.setSize (package:flutter/src/services/platform_views.dart:557:14)
[        ] E/flutter ( 9922): #4      RenderAndroidView._sizePlatformView (package:flutter/src/rendering/platform_view.dart:174:29)
[        ] E/flutter ( 9922): #5      RenderAndroidView.performResize (package:flutter/src/rendering/platform_view.dart:155:5)
[        ] E/flutter ( 9922): #6      RenderObject.layout (package:flutter/src/rendering/object.dart:1703:9)
[        ] E/flutter ( 9922): #7      RenderProxyBoxMixin.performLayout (package:flutter/src/rendering/proxy_box.dart:105:13)
[        ] E/flutter ( 9922): #8      RenderObject.layout (package:flutter/src/rendering/object.dart:1724:7)
[        ] E/flutter ( 9922): #9      MultiChildLayoutDelegate.layoutChild (package:flutter/src/rendering/custom_layout.dart:163:11)
[        ] E/flutter ( 9922): #10     _ScaffoldLayout.performLayout (package:flutter/src/material/scaffold.dart:477:7)
[        ] E/flutter ( 9922): #11     MultiChildLayoutDelegate._callPerformLayout (package:flutter/src/rendering/custom_layout.dart:232:7)
[        ] E/flutter ( 9922): #12     RenderCustomMultiChildLayoutBox.performLayout (package:flutter/src/rendering/custom_layout.dart:391:14)
[        ] E/flutter ( 9922): #13     RenderObject.layout (package:flutter/src/rendering/object.dart:1724:7)
[        ] E/flutter ( 9922): #14     RenderProxyBoxMixin.performLayout (package:flutter/src/rendering/proxy_box.dart:105:13)
[        ] E/flutter ( 9922): #15     RenderObject.layout (package:flutter/src/rendering/object.dart:1724:7)
[        ] E/flutter ( 9922): #16     RenderProxyBoxMixin.performLayout (package:flutter/src/rendering/proxy_box.dart:105:13)
[        ] E/flutter ( 9922): #17     _RenderCustomClip.performLayout (package:flutter/src/rendering/proxy_box.dart:1232:11)
[        ] E/flutter ( 9922): #18     RenderObject.layout (package:flutter/src/rendering/object.dart:1724:7)
[        ] E/flutter ( 9922): #19     RenderProxyBoxMixin.performLayout (package:flutter/src/rendering/proxy_box.dart:105:13)
[        ] E/flutter ( 9922): #20     RenderObject.layout (package:flutter/src/rendering/object.dart:1724:7)
[        ] E/flutter ( 9922): #21     RenderProxyBoxMixin.performLayout (package:flutter/src/rendering/proxy_box.dart:105:13)
[        ] E/flutter ( 9922): #22     RenderObject.layout (package:flutter/src/rendering/object.dart:1724:7)
[        ] E/flutter ( 9922): #23     RenderFlex.performLayout (package:flutter/src/rendering/flex.dart:806:17)
[        ] E/flutter ( 9922): #24     RenderObject.layout (package:flutter/src/rendering/object.dart:1724:7)
[        ] E/flutter ( 9922): #25     RenderConstrainedBox.performLayout (package:flutter/src/rendering/proxy_box.dart:259:13)
[        ] E/flutter ( 9922): #26     RenderObject.layout (package:flutter/src/rendering/object.dart:1724:7)
[        ] E/flutter ( 9922): #27     MultiChildLayoutDelegate.layoutChild (package:flutter/src/rendering/custom_layout.dart:163:11)
[        ] E/flutter ( 9922): #28     _ScaffoldLayout.performLayout (package:flutter/src/material/scaffold.dart:477:7)
[        ] E/flutter ( 9922): #29     MultiChildLayoutDelegate._callPerformLayout (package:flutter/src/rendering/custom_layout.dart:232:7)
[        ] E/flutter ( 9922): #30     RenderCustomMultiChildLayoutB
[+7766 ms] I/flutter (27545): calling api here

I have the same problem too.

Also encountering this issue.
flutter doctor -v

[√] Flutter (Channel master, v1.13.6-pre.38, on Microsoft Windows [Version 10.0.18362.535], locale en-NZ)
    • Flutter version 1.13.6-pre.38 at C:\tools\flutter
    • Framework revision b28dd0c296 (3 days ago), 2019-12-28 10:33:01 +0800
    • Engine revision 5a730c60d3
    • Dart version 2.8.0 (build 2.8.0-dev.0.0 1db1a837f8)

[√] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at C:\Users\Zac\AppData\Local\Android\sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-29, build-tools 28.0.3
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1024-b02)
    • All Android licenses accepted.

[√] Android Studio (version 3.1)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin version 28.0.1
    • Dart plugin version 173.4700
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1024-b02)

[√] VS Code, 64-bit edition (version 1.41.0)
    • VS Code at C:\Program Files\Microsoft VS Code
    • Flutter extension version 3.7.1

[√] Connected device (1 available)
    • ONEPLUS A6000 • a21aff4f • android-arm64 • Android 10 (API 29)

• No issues found!

This only happens for me when i do a full reload while in a page with the GoogleMap.

flutter doctor -v

[✓] Flutter (Channel stable, v1.12.13+hotfix.5, on Linux, locale en_US.UTF-8)
• Flutter version 1.12.13+hotfix.5 at /home/pionix/development/flutter
• Framework revision 27321ebbad (3 weeks ago), 2019-12-10 18:15:01 -0800
• Engine revision 2994f7e1e6
• Dart version 2.7.0
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
• Android SDK at /home/pionix/development/Android
• Android NDK location not configured (optional; useful for native profiling
support)
• Platform android-29, build-tools 29.0.2
• ANDROID_HOME = /home/pionix/development/Android
• Java binary at: /home/pionix/development/android-studio/jre/bin/java
• Java version OpenJDK Runtime Environment (build
1.8.0_202-release-1483-b49-5587405)
• All Android licenses accepted.
[!] Android Studio (version 3.5)
• Android Studio at /home/pionix/development/android-studio
✗ Flutter plugin not installed; this adds Flutter specific functionality.
✗ Dart plugin not installed; this adds Dart specific functionality.
• Java version OpenJDK Runtime Environment (build
1.8.0_202-release-1483-b49-5587405)
[✓] VS Code (version 1.41.1)
• VS Code at /usr/share/code
• Flutter extension version 3.7.1
[✓] Connected device (1 available)
• Android SDK built for x86 • emulator-5554 • android-x86 • Android 10 (API
29) (emulator)
! Doctor found issues in 1 category.

same problem here, anybody has a solution?

So I did a bit of digging and I'm pretty sure this is an issue with the PlatformView implementation.
From my (probably flawed) understanding:

After a reload the AndroidView is rebuilt (lib\src\google_map.dart#226)
Which gets an ID from platformViewsRegistry.getNextPlatformViewId()
This ID is 0 because the platformViewRegistry is disposed during the reload
But the PlatformViewsController is not disposed (for some reason?) so the vdControllers still contains the old platform view

I'm having the same problem
[√] Flutter (Channel stable, v1.12.13+hotfix.5, on Microsoft Windows [Version 10.0.18362.535], locale tr-TR)
• Flutter version 1.12.13+hotfix.5 at C:\src\Android\flutter
• Framework revision 27321ebbad (3 weeks ago), 2019-12-10 18:15:01 -0800
• Engine revision 2994f7e1e6
• Dart version 2.7.0
[√] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
• Android SDK at C:\Users\ThinkPad\AppData\Local\Android\Sdk
• Android NDK location not configured (optional; useful for native profiling support)
• Platform android-29, build-tools 29.0.2
• ANDROID_HOME = C:\Users\ThinkPad\AppData\Local\Android\Sdk
• ANDROID_SDK_ROOT = C:\Users\ThinkPad\AppData\Local\Android\Sdk
• Java binary at: C:\Program Files\Android\Android Studio1\jre\bin\java
• Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b03)
• All Android licenses accepted.
[√] Android Studio (version 3.5)
• Android Studio at C:\Program Files\Android\Android Studio1
• Flutter plugin version 41.1.2
• Dart plugin version 191.8593
• Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b03)
[√] VS Code (version 1.41.1)
• VS Code at C:\Users\ThinkPad\AppData\Local\Programs\Microsoft VS Code
• Flutter extension version 3.7.1
[√] Connected device (2 available)
• Android SDK built for x86 • emulator-5554 • android-x86 • Android 10 (API 29) (emulator)
• Android SDK built for x86 • emulator-5556 • android-x86 • Android 10 (API 29) (emulator)
• No issues found!

I tried to find exactly where this regressed but ran into issues because older project templates are often not compatible with new flutter versions.
I wasn't especially thorough and created a minimal new project where I ran into trouble. I found that this did not exhibit the same problem as a new template on some flutter versions.
Concretely, at 39c5f1ea29e351923fb9bce9ec8719b4ca7cf31c a project created from a recent master will fail, but one created from an earlier flutter version will not.

Based on @zacps comment, I tried a test project with a simple View with old Flutter (1.9.1+hotfix.6) and this crash does not happen. It uses old registerWith(Registrar registrar) static method to register the channel.

According to the API,

Do not change the camera with this camera update until the map has undergone layout (in order for this method to correctly determine the appropriate bounding box and zoom level, the map must have a size). Otherwise an IllegalStateException will be thrown.

I don't know how you have it set up, but you can have the _mapController.complete(controller) in a future and wait for it to finish.
In other words, you need to let the onMapCreated finish its thing before moving around on the map.
For example,
  ...
  onMapCreated: processOnMapCreated,
  ...

 Future<void> processOnMapCreated(GoogleMapController controller) async {
      await waitForMapToComplete(controller);

      //Wait for the map to complete, then do whatever you need to do
      nextThings();
  }

 Future<void> waitForMapToComplete(GoogleMapController controller) async {
    _mapController.complete(controller);
 }

This should address the issue.

Sadly, I encounter this issue with WebView too.

getting same issue!

Based on this answer, I just put Completer<GoogleMapController> mapController = Completer(); outside of the google map class, so there is only one key even if the widget gets rebuilt.
So far, it seems to work just fine.
Give it a try.

Solution:
1 -Add a GlobalKey in your constructur:
HomePage({Key key}) : super(key: key);
2 - Create A global Key in the widget parent
GlobalKey key = GlobalKey();
3 - Send the key when you want to Navigate to this page.
Navigator.of(context).push(
MaterialPageRoute(
builder: () => HomePage(
key: _key,
)),
);

Solution:
1 -Add a GlobalKey in your constructur:
HomePage({Key key}) : super(key: key);
2 - Create A global Key in the widget parent
GlobalKey key = GlobalKey();
3 - Send the key when you want to Navigate to this page.
Navigator.of(context).push(
MaterialPageRoute(
builder: () => HomePage(
key: _key,
)),
);

Can you explain where should I add the key and pass from?

I have the same issue

I have a project using Gmaps, I have the same problem. Time Gmaps works, time the platform bug happens.
Any solution?

Encountered same issue when using GoogleMapController.
Flutter (Channel master, v1.13.9-pre.59, on Microsoft Windows [Version 10.0.18362.535], locale en-US)     • Flutter version 1.13.9-pre.59 at C:\SDK\flutter_remote     • Framework revision ab36346af6 (21 hours ago), 2020-01-11 14:20:05 -0500     • Engine revision 3d37d39d95     • Dart version 2.8.0 (build 2.8.0-dev.0.0 395daaa3ec)

Solution:
1 -Add a GlobalKey in your constructur:
HomePage({Key key}) : super(key: key);
2 - Create A global Key in the widget parent
GlobalKey key = GlobalKey();
3 - Send the key when you want to Navigate to this page.
Navigator.of(context).push(
MaterialPageRoute(
builder: () => HomePage(
key: _key,
)),
);

What if I'm in a tabview (it's a real case), where I can't pass global key from a navigator

What if I'm in a tabview (it's a real case), where I can't pass global key from a navigator

An inherited widget should help there.  The Provider package makes this easy.

According to the API,

Do not change the camera with this camera update until the map has undergone layout (in order for this method to correctly determine the appropriate bounding box and zoom level, the map must have a size). Otherwise an IllegalStateException will be thrown.

I had the same issue and after some debugging, it looks like whenever you hotreload while the map is in view, it will give the error.
But you can prevent the error if you hot reload after disposing the map.
In other words, it is there to prevent multiple instances of maps to be active.
So I would suggest to dispose the map before hot reload while in development.
In a production version, users won't be able to hot reload thus, they won't encounter the platform issue.

Mac....
It may be a Windows-only error?
🤷♂

Scratch that, after updating again I can no longer reproduce it. Not sure what happened 🤷♂.

Scratch that, after updating again I can no longer reproduce it. Not sure what happened 🤷♂.

I just upgraded again and it started to work. What

It seems the issue is resolved after update flutter to master. Closing the issue.

I have the same problem too.

I have the same problem too.

Could everyone who still has this problem please file a new issue with the exact descriptions what happens, logs and the output of 'flutter doctor -v'  please.
All system setups can be slightly different so it's always better to open new issues and reference related issues.

[ERROR:flutter/lib/ui/ui_dart_state.cc(157)] Unhandled Exception: PlatformException(error, java.lang.IllegalStateException: Trying to create an already created platform view, view id: 0
E/flutter (12311): 	at io.flutter.plugin.platform.PlatformViewsController$1.createPlatformView(PlatformViewsController.java:85)
E/flutter (12311): 	at io.flutter.embedding.engine.systemchannels.PlatformViewsChannel$1.create(PlatformViewsChannel.java:96)
E/flutter (12311): 	at io.flutter.embedding.engine.systemchannels.PlatformViewsChannel$1.onMethodCall(PlatformViewsChannel.java:60)
E/flutter (12311): 	at io.flutter.plugin.common.MethodChannel$IncomingMethodCallHandler.onMessage(MethodChannel.java:231)
E/flutter (12311): 	at io.flutter.embedding.engine.dart.DartMessenger.handleMessageFromDart(DartMessenger.java:93)
E/flutter (12311): 	at io.flutter.embedding.engine.FlutterJNI.handlePlatformMessage(FlutterJNI.java:642)
E/flutter (12311): 	at android.os.MessageQueue.nativePollOnce(Native Method)
E/flutter (12311): 	at android.os.MessageQueue.next(MessageQueue.java:326)
E/flutter (12311): 	at android.os.Looper.loop(Looper.java:160)
E/flutter (12311): 	at android.app.ActivityThread.main(ActivityThread.java:6669)
E/flutter (12311): 	at java.lang.reflect.Method.invoke(Native Method)
E/flutter (12311): 	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
E/flutter (12311): 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)
E/flutter (12311): , null)
E/flutter (12311): #0      StandardMethodCodec.decodeEnvelope (package:flutter/src/services/message_codecs.dart:569:7)
E/flutter (12311): #1      MethodChannel.invokeMethod (package:flutter/src/services/platform_channel.dart:321:33)
E/flutter (12311):
E/flutter (12311): #2      AndroidViewController._create (package:flutter/src/services/platform_views.dart:640:54)
E/flutter (12311): #3      AndroidViewController.setSize (package:flutter/src/services/platform_views.dart:557:14)
E/flutter (12311): #4      RenderAndroidView._sizePlatformView (package:flutter/src/rendering/platform_view.dart:174:29)
E/flutter (12311): #5      RenderAndroidView.performResize (package:flutter/src/rendering/platform_view.dart:155:5)
E/flutter (12311): #6      RenderObject.layout (package:flutter/src/rendering/object.dart:1703:9)
E/flutter (12311): #7      RenderProxyBoxMixin.performLayout (package:flutter/src/rendering/proxy_box.dart:105:13)
E/flutter (12311): #8      RenderObject.layout (package:flutter/src/rendering/object.dart:1724:7)
E/flutter (12311): #9      RenderConstrainedBox.performLayout (package:flutter/src/rendering/proxy_box.dart:259:13)
E/flutter (12311): #10     RenderObject.layout (package:flutter/src/rendering/object.dart:1724:7)
E/flutter (12311): #11     RenderPadding.performLayout (package:flutter/src/rendering/shifted_box.dart:206:11)
E/flutter (12311): #12     RenderObject.layout (package:flutter/src/rendering/object.dart:1724:7)
E/flutter (12311): #13     RenderFlex.performLayout (package:flutter/src/rendering/flex.dart:744:15)
E/flutter (12311): #14     RenderObject.layout (package:flutter/src/rendering/object.dart:1724:7)
E/flutter (12311): #15     RenderPadding.performLayout (package:flutter/src/rendering/shifted_box.dart:206:11)
E/flutter (12311): #16     RenderObject.layout (package:flutter/src/rendering/object.dart:1724:7)
E/flutter (12311): #17     RenderProxyBoxMixin.performLayout (package:flutter/src/rendering/proxy_box.dart:105:13)
E/flutter (12311): #18     RenderObject.layout (package:flutter/src/rendering/object.dart:1724:7)
E/flutter (12311): #19     RenderPadding.performLayout (package:flutter/src/rendering/shifted_box.dart:206:11)
E/flutter (12311): #20     RenderObject.layout (package:flutter/src/rendering/object.dart:1724:7)
E/flutter (12311): #21     RenderProxyBoxMixin.performLayout (package:flutter/src/rendering/proxy_box.dart:105:13)
E/flutter (12311): #22     RenderObject.layout (package:flutter/src/rendering/object.dart:1724:7)
E/flutter (12311): #23     RenderProxyBoxMixin.performLayout (package:flutter/src/rendering/proxy_box.dart:105:13)
E/flutter (12311): #24     RenderObject.layout (package:flutter/src/rendering/object.dart:1724:7)
E/flutter (12311): #25     RenderSliverMultiBoxAdaptor.insertAndLayoutChild (package:flutter/src/rendering/sliver_multi_box_adaptor.dart:492:13)
E/flutter (12311): #26     RenderSliverList.performLayout.advance (package:flutter/src/rendering/sliver_list.dart:195:19)
E/flutter (12311): #27     RenderSliverList.performLayout (package:flutter/src/rendering/sliver_list.dart:238:19)
E/flutter (12311): #28     RenderObject.layout (package:flutter/src/rendering/object.dart:1724:7)
E/flutter (12311): #29     RenderSliverEdgeInsetsPadding.performLayout (package:flutter/src/rendering/sliver_padding.dart:134:11)
E/flutter (12311): #30     RenderSliverPadding.performLayout (package:flutter/src/rendering/

I think this issue can be reproduced when you are using hot reload.

well, adding a key (unique one) to the widget (not it's state) solved the issue for me.

me too had the same issue and flutter clean don't solve the issue for me (flutter version 1.12.13+hotfix 8)
Adding a key (unique one) to the widget (not it's state) solved the issue for me.

Can you show a code snippet how you used the key to remove the error?

me too had the same issue and flutter clean don't solve the issue for me (flutter version 1.12.13+hotfix 8)
Adding a key (unique one) to the widget (not it's state) solved the issue for me.

Can you show a code snippet how you used the key to remove the error?

this the minimum i could use to demonstrate. please note that if their is any syntax error or so. i copied the code through mobile
import 'package:flutter/material.dart';
import 'package:google_maps_flutter/google_maps_flutter.dart';
main file
void main() => runApp(MyApp());

class MyApp extednds StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Map not crashing demo',
      debugShowCheckedModeBanner: false,
      theme: ThemeData(
        primarySwatch: Colors.blue,
      ),
      home: LocationScreen(),
    );
  }
}

a screenHolder widget

class LocationScreen extends StatefulWidget
{
  final Key _mapKey = UniqueKey();
  @override
  _LocationScreenState createState() => _LocationScreenState();
}

class _LocationScreenState extends State<LocationScreen>
{
  @override
  Widget build(BuildContext context)
  {
    return Scaffold(
      appBar: AppBar(title: const Text('Map not crashing demo')),
      body: TheMap(key:widget._mapKey)
    );
  }
}

google map code here
class TheMap extends StatefulWidget
{
  ///key is required, otherwise map crashes on hot reload
  TheMap({ @required Key key})
  :
  super(key:key);

  @override
  _MyAppState createState() => _MyAppState();
}

class _MyAppState extends State<TheMap>
{
  GoogleMapController _mapController ;

  void _onMapCreated(GoogleMapController controller) {
    _mapController = controller;
  }
  @override
  Widget build(BuildContext context)
  {
    return Scaffold(
      resizeToAvoidBottomInset: false,
      body: return GoogleMap(
          onMapCreated: _onMapCreated,
          markers: markers,
          initialCameraPosition: CameraPosition(
            target: const LatLng(30.0925973,31.3219982),
            zoom: 11.0,
          ),
        )
    );
  }
}

I have had this same exception Unhandled Exception: PlatformException, in the widget where I am using this Google Maps plugin.
What I have noticed is, if I do a hot re-load (Shift+R), I always get this exception but doing a restart of the app from the terminal flutter run or running the app normally (tapping the app icon and navigating to my google maps screen), I don't get any exception. My guess is, the hot reload is somehow messing up with how flutter and native/plugin code communicate.
My 2cents...

This needs to be reopened

Hi @AbbasKMoussa @flutter2k20
as mentioned above would be ideal to open a new issue
addressing the specific circumstances
in which the issue occurs,
keeping in mind that the current one
apparently has been fixed in master

solved

Hi, could you please give us more specific details about what you did to solve this? thx

Faced the same problem on linux after upgraded Flutter & Dart to the latest versions.

Same issue here just after I have created new project in which I'm using the google map api's.

Mac....
It may be a Windows-only error?

Nope

I am getting the same error . On hot restart

I am also getting this error in the emulator by hot reloading the app and on some older android devices when i restart the app after some time. This wont happen after switching to the master branch but as this is the most unstable branch and you shouldnt use it in production this is not really a fix.

I think this issue can be reproduced when you are using hot reload.
their not problem after build apk???


Release v0.18.0

Bugfixes:

Fix Databricks OAuth M2M on Azure (#513).

Other noteworthy changes:

Use [] instead of None as default list value for deserialising responses (#361).
Support dev and staging workspaces (#514).

API Changes:

Added exists() method for w.tables workspace-level service.
Added w.lakehouse_monitors workspace-level service.
Added databricks.sdk.service.catalog.CreateMonitor dataclass.
Added databricks.sdk.service.catalog.DeleteLakehouseMonitorRequest dataclass.
Added databricks.sdk.service.catalog.ExistsRequest dataclass.
Added databricks.sdk.service.catalog.GetLakehouseMonitorRequest dataclass.
Added databricks.sdk.service.catalog.MonitorCronSchedule dataclass.
Added databricks.sdk.service.catalog.MonitorCronSchedulePauseStatus dataclass.
Added databricks.sdk.service.catalog.MonitorCustomMetric dataclass.
Added databricks.sdk.service.catalog.MonitorCustomMetricType dataclass.
Added databricks.sdk.service.catalog.MonitorDataClassificationConfig dataclass.
Added databricks.sdk.service.catalog.MonitorDestinations dataclass.
Added databricks.sdk.service.catalog.MonitorInferenceLogProfileType dataclass.
Added databricks.sdk.service.catalog.MonitorInferenceLogProfileTypeProblemType dataclass.
Added databricks.sdk.service.catalog.MonitorInfo dataclass.
Added databricks.sdk.service.catalog.MonitorInfoStatus dataclass.
Added databricks.sdk.service.catalog.MonitorNotificationsConfig dataclass.
Added databricks.sdk.service.catalog.MonitorTimeSeriesProfileType dataclass.
Added databricks.sdk.service.catalog.TableExistsResponse dataclass.
Added databricks.sdk.service.catalog.UpdateMonitor dataclass.
Changed create_obo_token() method for w.token_management workspace-level service with new required argument order.
Changed get() method for w.token_management workspace-level service to return databricks.sdk.service.settings.GetTokenResponse dataclass.
Changed lifetime_seconds field for databricks.sdk.service.settings.CreateOboTokenRequest to no longer be required.
Added databricks.sdk.service.settings.GetTokenResponse dataclass.

OpenAPI SHA: e05401ed5dd4974c5333d737ec308a7d451f749f, Date: 2024-01-23

Codecov Report
Attention: 155 lines in your changes are missing coverage. Please review.

Comparison is base (f0b23a5) 57.77% compared to head (3db8929) 57.79%.

Files
Patch %
Lines

databricks/sdk/service/catalog.py
58.77%
148 Missing :warning:

databricks/sdk/service/settings.py
64.70%
6 Missing :warning:

databricks/sdk/__init__.py
75.00%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #515      +/-   ##
==========================================
+ Coverage   57.77%   57.79%   +0.01%
==========================================
  Files          43       43
  Lines       27222    27596     +374
==========================================
+ Hits        15728    15949     +221
- Misses      11494    11647     +153

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


Revise help pages to be consistent with existing functionality

Duplicate of #134
Fix has been merged into develop branch #135

Even on dev help pages are significantly out of sync with functionality.  For example mentions of groups and my-resources pages.  @rayi113 we need to identify a person to help with this.  Pushing back to milestone 1.5 to not hold up 1.4 deploy.

Updated support page when this pull request goes live on dev: https://github.com/hydroshare/hydroshare/commit/94c27cb1af4fbd80dc8630802d18d9b4537d1d68

Should be fixed now - see http://dev.hydroshare.org/help/

I reviewed the help pages.  They are good to go but will need continued updating as new features get added, like explaining how to use the new resource types.