Rename portal_*Gossip JSON-RPC endpoint to portal_*PutContent

I suggest that we rename the portal_*Gossip JSON-RPC endpoint to portal_*PutContent and also update the method definition to include storing the content in the local database after performing some basic validations.
Changes in this PR:

Renamed portal_*Gossip JSON-RPC endpoint to portal_*PutContent
Updated the endpoint spec definition to include validation and storage in the local db

This is a similar update to https://github.com/ethereum/portal-network-specs/pull/344. My reasoning for this change is that I think we should have a high level endpoint counterpart to portal_*GetContent with similar naming and implementation storing in the local database when it makes sense to do so.

cc @KolbyML @kdeme

Gossip's main usecase is gossiping to other nodes on the network. Normally this is done via bridges. I am not sure if this is an endpoint high level users would actual use.
Because gossip is normal used by bridges which don't want to store that content I am not sure if I see the utility of that.
Also validation would be limited via this API call as for example if we are gossiping block bodies we can't validate canonicalness without a network look on the bridge side, which I don't think we should do that as bandwidth is very limited.
Anyways I am very open to what others think. I think portal_GetContent really makes sense for users, but I don't see how that is the same with gossip

Gossip's main usecase is gossiping to other nodes on the network. Normally this is done via bridges. I am not sure if this is an endpoint high level users would actual use.
Because gossip is normal used by bridges which don't want to store that content I am not sure if I see the utility of that.
Also validation would be limited via this API call as for example if we are gossiping block bodies we can't validate canonicalness without a network look on the bridge side, which I don't think we should do that as bandwidth is very limited.
Anyways I am very open to what others think. I think portal_GetContent really makes sense for users, but I don't see how that is the same with gossip

Yes, it is used by bridges and in that case the bridge is usually connected to a local portal client node which is also participating in the network so it makes sense to store the content locally if it falls within the local nodes radius so that the content can be shared with other nodes on request. If disabling local storage is a requirement then clients can set their storage capacity to zero to prevent the local storage.
For the validation, I agree we shouldn't do network calls so we can't validate canonicalness but other local validations should still be done.
The purpose for the rename was to bring some symmetry and a counterpart to the portal_GetContent but not necessarily that it would be used by end users.

@bhartnett
Anyways I will probably get used to the name portal_*PutContent over time.
I think we should be more specific what we mean by validation in the RPC's description. With the examples given I understand where you guys are coming from for the storage example now. Also we wouldn't want to set a bridges radius to 0 or it would be easily detectable which is bad. So storing it first isn't a bad thing thinking more about it.
Other then that the PR looks good

Regarding validation, I don't have strong opinion. It can be either fully validated (as if content came from other node on the network)
That would add a lot of overhead in terms of my block body or block receipt example. Also if a node offers you not provable data maybe that is something peerscore should handle. It could be dangerous though if an dos attack was to occur on the network. So I think a flag or no network-call are the only 2 feasible options. Maybe the flag approach could prevent naive users from doing weird stuff if it is enabled by default.

That would add a lot of overhead in terms of my block body or block receipt example. Also if a node offers you not provable data maybe that is something peerscore should handle. It could be dangerous though if an dos attack was to occur on the network. So I think a flag or no network-call are the only 2 feasible options. Maybe the flag approach could prevent naive users from doing weird stuff if it is enabled by default.

@KolbyML I agree full validation would slow down the bridge significantly and if we did end up deciding to do full validation then yes it should be configurable and perhaps enabled by default to prevent surprises.
Having said that, I think this PR shouldn't try to cover categorizing the types of validation because that needs to be done for all the endpoints and it probably should be handled as a separate PR. It would be good to have the types/categories of validation clearly defined.
Regarding the validation wording, sure I'm happy to update to something more clear. My suggestions is that for this PR, the validation should be the same type as done in portal_*GetContent.

Regarding the validation wording, sure I'm happy to update to something more clear. My suggestion is that for this PR, the validation should be the same type as done in portal_*GetContent.

maybe for

portal_*GetContent we can call it "Full Validation"
portal_*PutContent we can call it "Local Validation"
in the descriptions for the respective endpoints

I think that is a simple enough scheme which gets the point across

Regarding the validation wording, sure I'm happy to update to something more clear. My suggestion is that for this PR, the validation should be the same type as done in portal_*GetContent.

maybe for

portal_*GetContent we can call it "Full Validation"
portal_*PutContent we can call it "Local Validation"

in the descriptions for the respective endpoints
I think that is a simple enough scheme which gets the point across

Yes something like this could work well enough for now I guess but one issue I see is that 'full validation' should probably include checking if the data is canonical which would include a network call. For example if you look up a trie node from an uncle block which shouldn't exist in the portal network a malicious node could return it to you if you don't check it in some way. This is very much an edge case and I'm not suggesting we actually need to do this kind of validation but my point is that 'full validation' should probably include canonical checks which we shouldn't do in this case. So probably a different type of validation is needed here.
In my last update I'm describing the validation in portal_*GetContent as 'validation for correctness' and the validation in portal_*PutContent as 'validate that the content is well formed'. Hopefully this is ok for now.

In my last update I'm describing the validation in portal_*GetContent as 'validation for correctness' and the validation in portal_*PutContent as 'validate that the content is well formed'. Hopefully this is ok for now.

Both examples sound like the same thing but worded differently. I don't think it clear enough. If we are specifying validation here, we should specify it. If we want to properly write the description for validation for portal_*PutContent in a future PR, which should add the word validation to the portal_*PutContent in that follow up PR.

Yes something like this could work well enough for now I guess but one issue I see is that 'full validation' should probably include checking if the data is canonical which would include a network call. For example if you look up a trie node from an uncle block which shouldn't exist in the portal network a malicious node could return it to you if you don't check it in some way. This is very much an edge case and I'm not suggesting we actually need to do this kind of validation but my point is that 'full validation' should probably include canonical checks which we shouldn't do in this case. So probably a different type of validation is needed here.

I think Full Validation would mean the fullest validation possible. portal_*GetContent is unlikely to be used on the State network other than maybe the wallet use case. Where I assume eth_* calls would be used to reduce code duplication and complexity.
If the validation part isn't relevant to this PR we shouldn't add it to the description and properly do it in a follow up PR. If the validation description is an important part and wants to be kept in this PR people should be able to understand what it means.

In my last update I'm describing the validation in portal_*GetContent as 'validation for correctness' and the validation in portal_*PutContent as 'validate that the content is well formed'. Hopefully this is ok for now.

Both examples sound like the same thing but worded differently. I don't think it clear enough. If we are specifying validation here, we should specify it. If we want to properly write the description for validation for portal_*PutContent in a future PR, which should add the word validation to the portal_*PutContent in that follow up PR.

Yes something like this could work well enough for now I guess but one issue I see is that 'full validation' should probably include checking if the data is canonical which would include a network call. For example if you look up a trie node from an uncle block which shouldn't exist in the portal network a malicious node could return it to you if you don't check it in some way. This is very much an edge case and I'm not suggesting we actually need to do this kind of validation but my point is that 'full validation' should probably include canonical checks which we shouldn't do in this case. So probably a different type of validation is needed here.

I think Full Validation would mean the fullest validation possible. portal_*GetContent is unlikely to be used on the State network other than maybe the wallet use case. Where I assume eth_* calls would be used to reduce code duplication and complexity.
If the validation part isn't relevant to this PR we shouldn't add it to the description and properly do it in a follow up PR. If the validation description is an important part and wants to be kept in this PR people should be able to understand what it means.

I understand where you are coming from and agree with your points above in general but I would argue the the terms 'Full validation' and 'Local validation' are also not completely clear until we define these terms/categories in another location in the spec. I agree that should be done in a separate PR.
In that case, I'm happy to remove the references to validation if that is preferred. Note that portal_*GetContent already mentions validation and I didn't introduce that in this PR (previous PR) so one could argue that mentioning validation in portal_*PutContent at the same level of detail does no harm as we know it will require some form of validation.

In that case, I'm happy to remove the references to validation if that is preferred. Note that portal_*GetContent already mentions validation and I didn't introduce that in this PR (previous PR) so one could argue that mentioning validation in portal_*PutContent at the same level of detail does no harm as we know it will require some form of validation.

I think the distinguishing factor here is now validation means 2 different things for 2 different endpoints. If its meaning was consistent I would be more lenient with it. I was lenient with it in the portal_*GetContent call because at the time it was the only usage of the word "validation" in our json-rpc schema.
Well, of course, it wouldn't be too hard for us to figure out what that means; I think the specs should be written explicitly so even an outsider could understand what is implied.
In short I think using the same word to define 2 different expectations is misleading and does harm to people trying to use our specs.
If this is a high level call I don't think we should say the call does validation as that isn't really relevant to the person making the call it is more of an implementation detail in that case I think it would make more sense to define it https://github.com/ethereum/portal-network-specs/pull/345 here. And instead try to focus on higher level description in our JSON-RPC schema then leave implementation details like how validation is handle in the Specification.md per method.
If that is the case though in our json-rpc schema all of the endpoints would contain the word validation in their description to the point it is implicit and since validation would mean a different thing per endpoint I don't think any endpoint should specify it in their description as it would be happening for every JSON-RPC method, but validation would mean different things for most of them or their would be groups of endpoints which do the same form of validation but you get the point.

In that case, I'm happy to remove the references to validation if that is preferred. Note that portal_*GetContent already mentions validation and I didn't introduce that in this PR (previous PR) so one could argue that mentioning validation in portal_*PutContent at the same level of detail does no harm as we know it will require some form of validation.

I think the distinguishing factor here is now validation means 2 different things for 2 different endpoints. If its meaning was consistent I would be more lenient with it. I was lenient with it in the portal_*GetContent call because at the time it was the only usage of the word "validation" in our json-rpc schema.
Well, of course, it wouldn't be too hard for us to figure out what that means; I think the specs should be written explicitly so even an outsider could understand what is implied.
In short I think using the same word to define 2 different expectations is misleading and does harm to people trying to use our specs.
If this is a high level call I don't think we should say the call does validation as that isn't really relevant to the person making the call it is more of an implementation detail in that case I think it would make more sense to define it #345 here. And instead try to focus on higher level description in our JSON-RPC schema then leave implementation details like how validation is handle in the Specification.md per method.
If that is the case though in our json-rpc schema all of the endpoints would contain the word validation in their description to the point it is implicit and since validation would mean a different thing per endpoint I don't think any endpoint should specify it in their description as it would be happening for every JSON-RPC method, but validation would mean different things for most of them or their would be groups of endpoints which do the same form of validation but you get the point.

This sounds reasonable to me. I've just pushed another change which removes the references to validation from the method descriptions for both rpc methods portal_*GetContent  and portal_*PutContent .

@KolbyML Any thoughts on getting this one in the specs?

@KolbyML Any thoughts on getting this one in the specs?

I would try and get @kdeme to review it.
I think @pipermerriam would be for this as it makes the RPC commands simpler and requires less domain specific knowledge.
After they take a look I don't really see a blocker for this PR

@pipermerriam Did you have any thoughts on this PR?

I think I'm in favor of this. Is this endpoint in use anywhere? I think my only concern, which is minor is that without an active use case, it's difficult to know if we're getting the API correct. This concern isn't a blocker and I'm fine with moving this forward.

Yes, the Fluffy State and History Bridges both use this endpoint to gossip/send content into the network. Other bridges will likely also be using it for sending content into the network.

I've applied the updates as suggested by @pipermerriam


Using ConcurrentHashMap for synchronizing LTI user login

This Pull Request is correcting
https://github.com/opencast/opencast/pull/1532
and
https://github.com/opencast/opencast/pull/1622
Now we simple using a ConcurrentHashMap to synchronize the user authenticated by LTI.
We save the username in the map and removing it in the finally block after user is added or updated.
The fix is related to https://github.com/opencast/opencast/pull/1532 and the mentioned exceptions.
The code of the patches above is not needed anymore.

Hopefully, this should now build properly.

I haven't had a chance to test, but it looks good to me too.

Okay, everyone approves 🎉
Then, if no one complains until EOD tomorrow I'll merge this.


Dart WebSocket Server does not pass all AutoBahn tests

The common standard to test WebSocket implementations is the AutoBahn test suite.
http://autobahn.ws/testsuite/
It looks like Dart doesn't pass a decent amount of them, especially WebSocket compression related tests.
Here are the results as of commit 8a445a3f01c1d1e8f3cfb4175150b549f944bae3 on a x64 Mac release build.
http://files.directcode.io/dartwstest/
CC @butlermatt

@kaendfinger Do you have details on how you ran the Autobahn test? I'm starting to look at this today. A sample of the websock server you used?

Bind an echoing WebSocket server to port 9001 locally.
Make sure you have Python installed.
Run:
pip install autobahntestsuite
wstest -m fuzzingclient

It should run through all the tests and generate reports.

Patch submitted for review here:
https://codereview.chromium.org/1579343003/

Great with the compression part fixed.
@kaendfinger https://github.com/kaendfinger the running instructions you
posted only tests the server side as far as I can see. Is there a way to
test the client as well - I assume that it would require writing the client
part of the test suite in Dart.

Søren Gjesse
Software Engineer, Google Denmark
CVR nr. 28 86 69 84
On Wed, Jan 13, 2016 at 7:12 PM, Matthew Butler<EMAIL_ADDRESS>wrote:

Patch submitted for review here:
https://codereview.chromium.org/1579343003/
—
Reply to this email directly or view it on GitHub
https://github.com/dart-lang/sdk/issues/25317#issuecomment-171383599.

It took me a little to get it figured out but I'm currently running the client side tests for this now

Just to follow up. The client tests were showing a couple of errors in Websocket compression. I'm running final tests on a patch now and will submit it shortly. I'll also provide repository to see the tests I used and the results from them.

Patch to resolve client issues is:
https://codereview.chromium.org/1583933007/
Test repository:
https://github.com/butlermatt/dart-autobahn-testing
Test results:
Websocket Client Test Results
Websocket Server Test Results

Thanks Matthew,
The patch has landed. Could you share how to run the client tests?
/Søren
On Thu, Jan 14, 2016 at 6:24 PM, Matthew Butler<EMAIL_ADDRESS>wrote:

Patch to resolve client issues is:
https://codereview.chromium.org/1583933007/
Test repository:
https://github.com/butlermatt/dart-autobahn-testing
Test results:
Websocket Client Test Results
http://butlermatt.github.io/dart-autobahn-testing/clients/
Websocket Server Test Results
http://butlermatt.github.io/dart-autobahn-testing/servers/
—
Reply to this email directly or view it on GitHub
https://github.com/dart-lang/sdk/issues/25317#issuecomment-171713220.

Hi Søren,
As I mention in the test repository I linked to above, to run the client tests:

Start the wstest server: wstest -m fuzzingserver
Run the dart client: dart bin\wsclient.dart

Report will be generated in reports/clients/index.html from where the wstest command was run.
The wsclient.dart will first open a websocket to query the Autobahn test server that is started. Once it has the total number of tests, it will iterate through each performing a simple echo response to anything since by the server. Finally it will query to the server to generate the reports based on the test results it creates.
See the client directly here:
https://github.com/butlermatt/dart-autobahn-testing/blob/master/bin/wsclient.dart
This way when isolating on a specific set of tests, or single test with the server, the client does not need to be updated for each test.

Per comments in CL: https://codereview.chromium.org/1583933007/ I have created another patch
https://codereview.chromium.org/1584653008/
This patch addresses 3 areas:

Optimize client and server side no take over handling to discard encoder and decoders appropriate.
Resolves an issue where client would not request headers based on the provided CompressionOptions at creation (and adds tests)
Resolves an issue where server was enabling 'no context takeover' yet did not advertise it in a response and was not configured in CompressionOptions. (And adds tests)

Verified all green for websocket compression in Autobahn in 4 tests:

Server without "no context takeover" options enabled.
Server with "no context takeover" options enabled.
Client without "no context takeover" options enabled.
Client with "no context takeover" options enabled.

Patch landed and scheduled for merge to 1.14-dev.
On Fri, Jan 15, 2016 at 9:54 PM, Matthew Butler<EMAIL_ADDRESS>wrote:

Per comments in CL: https://codereview.chromium.org/1583933007/ I have
created another patch
https://codereview.chromium.org/1584653008/
This patch addresses 3 areas:

Optimize client and server side no take over handling to discard
encoder and decoders appropriate.
Resolves an issue where client would not request headers based on
the provided CompressionOptions at creation (and adds tests)
Resolves an issue where server was enabling 'no context takeover'
yet did not advertise it in a response and was not configured in
CompressionOptions. (And adds tests)

Verified all green for websocket compression in Autobahn in 4 tests:

Server without "no context takeover" options enabled.
Server with "no context takeover" options enabled.
Client without "no context takeover" options enabled.
Client with "no context takeover" options enabled.

—
Reply to this email directly or view it on GitHub
https://github.com/dart-lang/sdk/issues/25317#issuecomment-172090085.


adding some anisotropy calculations

adding Tandon & Weng 1984 method for calculating anisotropic moduli for oblate spheroidal inclusions. Experimental for now, for this to be merged will need:

[ ] needs tests
[ ] needs examples

For reference, the following reproduces fig 2 of Tandon and Weng:
import numpy as np
import matplotlib.pyplot as plt
from pyVBRc.anisotropy import anisotropy

mat0_glass = anisotropy.IsotropicMedium(0.35, 2.76, 'youngs')
mat1_epoxy = anisotropy.IsotropicMedium(0.2, 72.4, 'youngs')

c = np.linspace(0.00001, 1, 100)
for alpha in (0.01, 1.0, 10, 25, 100):
    composite = anisotropy.AlignedInclusions(alpha)
    E11, E22 = composite.effective_youngs_modulus(mat0_glass, mat1_epoxy, c)
    plt.plot(c, E11/mat0_glass.youngs_modulus, label=f"{alpha}")

plt.xlim([0, 1])
plt.legend()
plt.ylabel('E11/E_o')
plt.xlabel('volume fraction')

Still to do:

add velocity outputs

big rewrite. now includes:

full stiffness matrix calculation for transverse isotropic materials, following sayers 1992.
phase velocity calculations following thomsen (both weak anisotropy approx and full calc, but full calc not really used...)

need to :

add more tests
convince myself it's working


[1935] Fix missing course subject 2 & 3 from timeline

Context
https://trello.com/c/dyEZOnTS/1935-bug-course-subject-2-3-not-displayed-in-timeline
Changes proposed in this pull request

Add subject_two anf subject_three to Trainees::CreateTimelineEvents::FIELDS
Update Trainees::CreateTimelineEvents to handle the course age range as one timeline entry instead of separate min/max events

Result

 Bug: course subject 2 & 3 not displayed in timeline

Could these say Course subject X updated? to match other course items?


chore(rules): moves rules related things into the rules module

This is a mix of things that is partly finishing up recent past work and getting ready to continue on with ongoing work.

We've recently split off some things into a @/app/rules module, so I moved the Rules related /data and sources.ts into this module. I'm also looking to refactor and combine as much as possible to do with listing of our rules (we currently use an AccordionList to do that), so I've moved and reduced some things around a little to make it easier to see where I can do that.
Lastly, once i"d done that reduction/move around, I also spotted I could also close https://github.com/kumahq/kuma-gui/issues/2302 pretty easily, so I've done that here also. Due to this I also reorganized the tests around this to make them easier to read i.e. reduced the mocking required, hoisted the CSS selectors to apply to the entire file, reordered the tests to put tests of the same type together etc. The coverage is/should be the same.
Closes https://github.com/kumahq/kuma-gui/issues/2302

@johncowen Can you please rebase this one?

Oh hey, sorry yeah, just finishing up one more 2.7 thing (https://github.com/kumahq/kuma-gui/issues/2371) then I'll come back and rebase this, gimme 30mins or so

@kleinfreund this one has been rebased


CI failed and doesn't find the multiqc file anymore

https://github.com/laminlabs/snakemake-lamin-usecases/actions/runs/6248584656/job/16963502662

Same thing seems to have happened on the nextflow notebook just now, but not for Sunny's PR.

https://github.com/laminlabs/nextflow-lamin-usecases/issues/15

I re triggered the CI earlier and it fixed itself.
Sep 20, 2023 7:08:10 PM Alex Wolf @.***>:

Same thing seems to have happened on the nextflow notebook just now, but not for Sunny's PR.
—
Reply to this email directly, view it on GitHub[https://github.com/laminlabs/snakemake-lamin-usecases/issues/4#issuecomment-1728129459], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AFHQA2BITIZS4E6IBFGFAYTX3MPHRANCNFSM6AAAAAA476WRQA].
You are receiving this because you were assigned.
[Tracking image][https://github.com/notifications/beacon/AFHQA2BQCHNVTAYMSCXUIGTX3MPHRA5CNFSM6AAAAAA476WRQCWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTHAEU3G.gif]


Rename test per review comment

Goal

Testing

Release Notes

WHAT:
WHY:

#1182  👈
master

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

Join @bidetofevil and the rest of your teammates on  Graphite

Merge activity

Aug 5, 4:18 AM EDT: Graphite rebased this pull request as part of a merge.


I think there is a bug in Imagenet_example folder.

Error at application/imagenet_example/main.py, line 22.
Function repare_qat_fx_by_platform cannot be referred. However prepare_by_platform can be referred.
Possibly, the same error is at application/imagenet_example/main.py , line 153.

Yes, it will be fixed soon.


Atlas docker build failure

Currently the atlas docker build is failing with
[ERROR] Failed to execute goal com.spotify:dockerfile-maven-plugin:1.4.10:build (build-and-tag-latest) on project open-metadata-docker-apache-atlas: Could not build image: COPY failed: stat /data/docker/overlay2/b4a55456d93e44b2a51a0859098bbf9b5448ee8b3249fc3af0041f2b96bae6e0/merged/root/atlas-bin: no such file or directory -> [Help 1]

This was briefly touched on in https://github.com/odpi/egeria/pull/1178 . It is still present after recent merges (backlog of changes to docker/charts)

done


source request

Source name
RuriDragon
Source link
https://ruridragon.com/
Source language
English
Other details
No response
Acknowledgements

[X] I have checked that the extension does not already exist by searching the extension listing and verified it does not appear there.
[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a meaningful title with the source name.
[X] I will fill out all of the requested information in this form.

Add a :+1: reaction to issues you find important.

/edit-title "Source request: RuriDragon"


integration issue

Hi, Can i connect with you via skype...because i wanna discuss about briefly regarding this API..

Hi, I can't speak English fluently, you can contact me by mail if you prefer. Anyway we can talk about it here. Regards!

i want to know how this API will work and how the device connects with the application

i want to develop this in PHP

Hello, you can see the following example coyotevz/anviz-sync to see how the API works, the connection with the device is made using the socket library, this software works with devices that are no longer sold, the firmware version must be 01.74.A2 or less.
You can see CommsProtocol for more information.
Regards!


Customizing the name when running parallel tests

I have been using Protractor to run my test suite in parallel for various languages. For example, I will run 3 instances of Chrome with the browser language set to English, Spanish, or French. Currently, in the output from Protractor it states "Chrome #1", "Chrome #2", or so on. I would like to customize the output and pass it in as a config property like "Chrome - French Canadian".
This process name is defined by the variable shortName in the reportSummary function. Please see the source code here:
https://github.com/angular/protractor/blob/9891d430aff477c5feb80ae01b48356866820132/lib/launcher.js#L68
I have included a screenshot of this (I am using the Cucumber options with Protractor):

I would be happy to work on adding this feature (and related testing) but wanted to check with the core team and see if there is interest in adding this functionality before I spent time to create a PR.

Sounds good to me

Customized name for parallel processes would be a useful feature for Protractor test.
For my project, I need to run a test with 15 Chrome instances concurrent run parallel, and each with different DOM manipulation test. It would be nice to give each instances with specific name instead of 'Chrome #1', "Chrome #2"... etc.

@sjelin I don't see any unit tests for the launcher or taskLogger. Do you need tests with this PR?


Start Async failed / MQTT Core Service has not started

Hi All,
When trying to set this up, I entered my MQTT broker details that work in other things, such as zigbee2MQTT:
AutoConfig: false
Host: mqtt://192.168.[redacted].[redacted]
Port: "1883" (If I had it as 1883 then it shows as RED, so hence, I leave the "" around it)
Id: [redacted]
Pw: [redacted]
Tls: false
I think it's something with the port number, but it is the correct port; I just don't get why its showing up as red and I get the following errors:
00:53:21 fail: SwitchBotMqttApp.Services.MqttCoreService[0] StartAsync  failed. System.Net.Http.HttpRequestException: Response status code does not indicate success: 400 (Bad Request).    at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode()    at System.Net.Http.Json.HttpClientJsonExtensions.GetFromJsonAsyncCore[T](Task`1 taskResponse, JsonSerializerOptions options, CancellationToken cancellationToken)    at HomeAssistantAddOn.Mqtt.SupervisorApi.GetServicesMqtt() in C:\github\hsakoh\switchbot-mqtt\src\HomeAssistant\HomeAssistantAddOn.Mqtt\SupervisorApi.cs:line 16    at HomeAssistantAddOn.Mqtt.MqttService.StartAsync() in C:\github\hsakoh\switchbot-mqtt\src\HomeAssistant\HomeAssistantAddOn.Mqtt\MqttService.cs:line 46    at SwitchBotMqttApp.Services.MqttCoreService.StartAsync(CancellationToken cancellationToken) in C:\github\hsakoh\switchbot-mqtt\src\SwitchBotMqttApp\Services\MqttCoreService.cs:line 46
00:53:21 warn: SwitchBotMqttApp.Services.PollingService[0] MqttCoreService has not started
Any ideas as to what is wrong? Is it something I'm doing?
Edit: I'm using a standalone MQTT broker on a VM hosted on Proxmox.

Thank you for the feedback.
The error occurred when attempting to automatically read the configuration using the Supervisor API, resulting in a 400 BadRequest response and a failure to start the MqttCoreService.
The program was trying to read Mqtt.UseAutoConfig internally, but the addon configuration was actually under Mqtt.AutoConfig.
I have released v1.0.10, which has been modified to read Mqtt.AutoConfig.
Please check and confirm the functionality on your end.

Additional information:
Please enter the addon configuration as follows.
(It is normal for the numerical values of the port numbers to be displayed in a reddish color.)


feat: define quasispectrum for non-unital algebras

This defines the quasispectrum of an element a : A where A is a non-unital R-algebra. When A is unital and R is a semifield, then quasispectrum R a = spectrum R a ∪ {0}. The definition proceeds via quasiregular elements, which are also defined herein. The quasispectrum will serve as the domain of the continuous functions appearing in the continuous functional calculus for non-unital algebras.

bors merge


fix: define flagsChanged on ConfigurationChanged details

Before this change the flagsChanged prop on EventDetails was of type unknown for all event types, and a cast was needed.
After this change, flagsChanged is ONLY defined on ProviderEvents.ConfigurationChanged, where it should be, as (string[] | undefined) . In other words:
client.addHandler(ProviderEvents.Ready, (details) => {
  expect(details?.flagsChanged?.length).toEqual(1);  // does not compile
});

client.addHandler(ProviderEvents.ConfigurationChanged, (details) => {
  expect(details?.flagsChanged?.length).toEqual(1);  // DOES compile
});

Additionally, flagsChanged does not autocomplete for events handlers other than ProviderEvents.ConfigurationChanged.

I'm going to rebase this on https://github.com/open-feature/js-sdk/pull/795 when it's merged.


add bucketco to ecosystem

This PR

adds Bucket to the ecosystem

Notes
I've removed the fill from the SVG logo so that it works in both light and dark modes.
Direct link to the preview: https://deploy-preview-674--openfeature.netlify.app/ecosystem?instant_search[refinementList][vendor][0]=Bucket

Perfect! thanks.


I can't see new courses

I finished several new courses almost a track in one day (without making ex), only for ability download but I can't see those courses in list. In datacamp I can see that courses are finished and certificates are also available. Refresh option I tried.

that happened because wrong version of browser, now it's ok


Typos in documentation

Opening this in lieu of #1680

Is this issue yet to be resolved ? PR is closed but issue is still open. I would like to create PR if nobody is doing.


Converting current time to PST using moment.js

I am using the following code to change the current time to PST like this:
var now = moment().tz("America/Los_Angeles").format('YYYY-MM-DD HH:mm:00');
console.log(now);
On an IST machine, it gives me the current time.
But on a machine which has GMT+7, it gives different current time.
On the IST time: 2015-01-09 13:00:00
it returns: 2015-01-08 23:30:00 (which is correct)
Where as, on GMT+7 machine,
current time: 2015-01-09 07:28:09
it returns: 2015-01-09 06:28:00 (which should have been 2015-01-08 23:30:00)

I know this is old, but FWIW, you definitely want to put this ticket in the moment-timezone project, not the moment core one.


Update to stable chokidar.

Lots of improvements & much more stable.

+1

LGTM

LGTM

Superseded by #1412


fix(TabPanel): move react-transition-group functions to metadata in hook

Followup to https://github.com/react-bootstrap/react-bootstrap/pull/6276. Essentially moves react-transition-group functions to meta in useTabPanel hook. Also added a test to make sure it works.
Had to add @types/react-transition-group since the tests are in typescript

Thanks!


AI Model Switcher

Allows users to switch language models for chat conversations quickly. Toggle menu is displayed when users tap the toggle button.
Supports:

Icon
Name
Description

We may need to revisit the design and expand upon this feature. Currently shown in fullscreen use cases, but may be needed for smaller display modes too.


{
                     "simulator" : true,
                     "operatingSystemVersion" : "13.4.1 (17E8260)",
                     "available" : true,
                     "platform" : "com.apple.platform.iphonesimulator",
                     "modelCode" : "iPad11,3",
                     "identifier" : "42CF57BA-656E-43C9-9FC8-8FD9CF28EB14",
                     "architecture" : "x86_64",
                     "modelUTI" : "com.apple.ipad-air3-wifi-1",
                     "modelName" : "iPad Air (3rd generation)",
                     "name" : "iPad Air (3rd generation)"
                   },
                   {
                     "simulator" : true,
                     "operatingSystemVersion" : "6.2 (17T256)",
                     "available" : true,
                     "platform" : "com.apple.platform.watchsimulator",
                     "modelCode" : "Watch4,4",
                     "identifier" : "8D039C4C-BAEA-4026-9267-8DCF6CB08C20",
                     "architecture" : "i386",
                     "modelUTI" : "com.apple.watch-series4-1",
                     "modelName" : "Apple Watch Series 4 - 44mm",
                     "name" : "Apple Watch Series 4 - 44mm"
                   },
                   {
                     "simulator" : true,
                     "operatingSystemVersion" : "12.2 (16E226)",
                     "available" : true,
                     "platform" : "com.apple.platform.iphonesimulator",
                     "modelCode" : "iPhone8,1",
                     "identifier" : "FF51EB03-CB5E-4FB4-8723-48C7A7D58F92",
                     "architecture" : "x86_64",
                     "modelUTI" : "com.apple.iphone-6s-b9b7ba",
                     "modelName" : "iPhone 6s",
                     "name" : "iPhone 6s"
                   },
                   {
                     "simulator" : true,
                     "operatingSystemVersion" : "12.2 (16E226)",
                     "available" : true,
                     "platform" : "com.apple.platform.iphonesimulator",
                     "modelCode" : "iPad6,4",
                     "identifier" : "D448C539-E73F-452F-A994-2E84267FCCFA",
                     "architecture" : "x86_64",
                     "modelUTI" : "com.apple.ipad-pro-9point7-a1674-b9b7ba",
                     "modelName" : "iPad Pro (9.7-inch)",
                     "name" : "iPad Pro (9.7-inch)"
                   },
                   {
                     "simulator" : true,
                     "operatingSystemVersion" : "13.4.1 (17E8260)",
                     "available" : true,
                     "platform" : "com.apple.platform.iphonesimulator",
                     "modelCode" : "iPhone10,4",
                     "identifier" : "5E9F33C5-1A61-4DC4-A61B-48E1ED660344",
                     "architecture" : "x86_64",
                     "modelUTI" : "com.apple.iphone-8-2",
                     "modelName" : "iPhone 8",
                     "name" : "iPhone 8"
                   }
                 ]
[  +16 ms] Artifact Instance of 'AndroidMavenArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[   +6 ms] executing: unzip -t -qq
/Users/mariusi/apps/flutter/bin/cache/downloads/storage.googleapis.com/flutter_infra/flutter/d96f962ca21a104b08836f34814eb6b267937511/flutter-web-sdk-darwin-x64.zip
[  +15 ms] Downloading Web SDK...
[   +9 ms] Downloading: https://storage.googleapis.com/flutter_infra/flutter/d96f962ca21a104b08836f34814eb6b267937511/flutter-web-sdk-darwin-x64.zip
[ +636 ms] Received response from server, collecting bytes...
[+2081 ms] Downloading Web SDK... (completed in 2.7s)
[        ] executing: unzip -o -q
/Users/mariusi/apps/flutter/bin/cache/downloads/storage.googleapis.com/flutter_infra/flutter/d96f962ca21a104b08836f34814eb6b267937511/flutter-web-sdk-darwin-x64.zip -d
/Users/mariusi/apps/flutter/bin/cache/flutter_web_sdk
[ +436 ms] Exit code 0 from: unzip -o -q
/Users/mariusi/apps/flutter/bin/cache/downloads/storage.googleapis.com/flutter_infra/flutter/d96f962ca21a104b08836f34814eb6b267937511/flutter-web-sdk-darwin-x64.zip -d
/Users/mariusi/apps/flutter/bin/cache/flutter_web_sdk
[ +497 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required, skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required, skipping update.
[ +220 ms] Generating /Users/mariusi/dev/devisions-gh/flutter_playground/hello_world/android/app/src/main/java/io/flutter/plugins/GeneratedPluginRegistrant.java
[ +176 ms] Launching lib/main.dart on Chrome in debug mode...
[  +47 ms] Updating assets
[ +110 ms] Syncing files to device Chrome...
[  +44 ms] Generating /Users/mariusi/dev/devisions-gh/flutter_playground/hello_world/android/app/src/main/java/io/flutter/plugins/GeneratedPluginRegistrant.java
[  +24 ms] <- reset
[   +7 ms] /Users/mariusi/apps/flutter/bin/cache/dart-sdk/bin/dart /Users/mariusi/apps/flutter/bin/cache/artifacts/engine/darwin-x64/frontend_server.dart.snapshot --sdk-root
/Users/mariusi/apps/flutter/bin/cache/flutter_web_sdk/ --incremental --target=dartdevc --debugger-module-names -Ddart.developer.causal_async_stacks=true --output-dill
/var/folders/d7/n4gq4j2946z8z7cm4x8qmk740000gq/T/flutter_tool.goCS7I/app.dill --libraries-spec file:///Users/mariusi/apps/flutter/bin/cache/flutter_web_sdk/libraries.json
--packages .packages -Ddart.vm.profile=false -Ddart.vm.product=false
--bytecode-options=source-positions,local-var-info,debugger-stops,instance-field-initializers,keep-unreachable-code,avoid-closure-call-instructions --enable-asserts
--track-widget-creation --filesystem-root /var/folders/d7/n4gq4j2946z8z7cm4x8qmk740000gq/T/flutter_tools.cmpyjW --filesystem-scheme org-dartlang-app --initialize-from-dill
build/cache.dill.track.dill --platform file:///Users/mariusi/apps/flutter/bin/cache/flutter_web_sdk/kernel/flutter_ddc_sdk.dill
[   +7 ms] <- compile org-dartlang-app:/web_entrypoint.dart
[+16000 ms] Syncing files to device Chrome... (completed in 16,082ms, longer than expected)
[   +1 ms] Synced 22.5MB.
[        ] <- accept
[ +708 ms] [CHROME]:
[        ] [CHROME]:DevTools listening on ws://<IP_ADDRESS>:50642/devtools/browser/98f4c081-4996-4972-9ce6-1b77810dbf66
[+2523 ms] Debug service listening on ws://<IP_ADDRESS>:50677/88JQ6S770J4=

[ +525 ms] Debug service listening on ws://<IP_ADDRESS>:50677/88JQ6S770J4=
[   +1 ms] Warning: Flutter's support for web development is not stable yet and hasn't
[        ] been thoroughly tested in production environments.
[        ] For more information see https://flutter.dev/web
[        ] 🔥  To hot restart changes while running, press "r". To hot restart (and refresh the browser), press "R".
[   +1 ms] For a more detailed help message, press "h". To quit, press "q".
[ +879 ms] A null value was passed into a non-nullable parameter value
                 This will become a failure when runtime null safety is enabled.

[+7183 ms] Performing hot restart...
[   +5 ms] Scanned through 477 files in 4ms
[        ] Syncing files to device Chrome...
[   +2 ms] <- recompile org-dartlang-app:/web_entrypoint.dart 715438f4-c6b2-474c-81c3-ad13bf3df8c7
[        ] <- 715438f4-c6b2-474c-81c3-ad13bf3df8c7
[   +8 ms] Syncing files to device Chrome... (completed in 10ms)
[        ] Synced 0.0MB.
[        ] <- accept
[  +19 ms] Null is not a subtype of Future<dynamic>.
        This will become a failure when runtime null safety is enabled.

[  +29 ms] Performing hot restart... (completed in 64ms)
[        ] Restarted application in 65ms.
[+5690 ms] Performing hot restart...
[   +5 ms] Scanned through 477 files in 5ms
[        ] Syncing files to device Chrome...
[        ] <- recompile org-dartlang-app:/web_entrypoint.dart 2086166e-4322-4eac-a116-e945834fd2f7
[        ] <- 2086166e-4322-4eac-a116-e945834fd2f7
[   +7 ms] Syncing files to device Chrome... (completed in 8ms)
[        ] Synced 0.0MB.
[        ] <- accept
[  +36 ms] Null is not a subtype of Future<dynamic>.
        This will become a failure when runtime null safety is enabled.

[  +15 ms] Performing hot restart... (completed in 67ms)
[        ] Restarted application in 68ms.
[  +12 ms] Error: Invalid argument(s): Extension already registered: ext.flutter.disassemble
            at Object.throw_ [as throw] (http://localhost:50614/dart_sdk.js:4461:11)
            at Object.registerExtension$ [as registerExtension] (http://localhost:50614/dart_sdk.js:48563:17)
            at Object.webOnlyInitializeEngine (http://localhost:50614/dart_sdk.js:164007:15)
            at _initializePlatform (http://localhost:50614/dart_sdk.js:134269:15)
            at _initializePlatform.next (<anonymous>)
            at runBody (http://localhost:50614/dart_sdk.js:36923:34)
            at Object._async [as async] (http://localhost:50614/dart_sdk.js:36951:7)
            at Object._initializePlatform (http://localhost:50614/dart_sdk.js:134265:18)
            at Object.webOnlyInitializePlatform (http://localhost:50614/dart_sdk.js:134257:35)
            at main$ (http://localhost:50614/web_entrypoint.dart.lib.js:13:16)
            at main$.next (<anonymous>)
            at runBody (http://localhost:50614/dart_sdk.js:36923:34)
            at Object._async [as async] (http://localhost:50614/dart_sdk.js:36951:7)
            at main$ (http://localhost:50614/web_entrypoint.dart.lib.js:12:18)
            at <anonymous>:1:8
            at Object.runMain (http://localhost:50614/dwds/src/injected/client.js:8343:15)
            at http://localhost:50614/dwds/src/injected/client.js:22335:19
            at _wrapJsFunctionForAsync_closure.$protected (http://localhost:50614/dwds/src/injected/client.js:3636:15)
            at _wrapJsFunctionForAsync_closure.call$2 (http://localhost:50614/dwds/src/injected/client.js:10848:12)
            at Object._asyncStartSync (http://localhost:50614/dwds/src/injected/client.js:3600:20)
            at main__closure1.$call$body$main__closure (http://localhost:50614/dwds/src/injected/client.js:22347:16)
            at main__closure1.call$1 (http://localhost:50614/dwds/src/injected/client.js:22279:19)
            at StaticClosure._rootRunUnary [as call$2$5] (http://localhost:50614/dwds/src/injected/client.js:3958:16)
            at _CustomZone.runUnary$2$2 (http://localhost:50614/dwds/src/injected/client.js:12164:39)
            at _CustomZone.runUnaryGuarded$1$2 (http://localhost:50614/dwds/src/injected/client.js:12092:14)
            at _ControllerSubscription._sendData$1 (http://localhost:50614/dwds/src/injected/client.js:11642:19)
            at _DelayedData.perform$1 (http://localhost:50614/dwds/src/injected/client.js:11796:59)
            at _PendingEvents_schedule_closure.call$0 (http://localhost:50614/dwds/src/injected/client.js:11845:14)
            at Object._microtaskLoop (http://localhost:50614/dwds/src/injected/client.js:3801:21)
            at StaticClosure._startMicrotaskLoop (http://localhost:50614/dwds/src/injected/client.js:3807:11)
            at _AsyncRun__initializeScheduleImmediate_internalCallback.call$1 (http://localhost:50614/dwds/src/injected/client.js:10720:9)
            at invokeClosure (http://localhost:50614/dwds/src/injected/client.js:1172:26)
            at MutationObserver.<anonymous> (http://localhost:50614/dwds/src/injected/client.js:1191:18)

Hi @devisions
I stand corrected
I just needed to hot-reload a second time,
(actually happens every second time I hot-reload)
 nevercode@Nevercodes-Air  ~/Desktop/projects/master  flutter_master run -d chrome --verbose
[  +15 ms] executing: [/Users/nevercode/development/flutter_master/] git -c
log.showSignature=false log -n 1 --pretty=format:%H
[  +68 ms] Exit code 0 from: git -c log.showSignature=false log -n 1
--pretty=format:%H
[   +1 ms] 793e6a48a1e679074da7f47813c138abb2f0a6f6
[   +1 ms] executing: [/Users/nevercode/development/flutter_master/] git tag
--contains HEAD
[ +494 ms] Exit code 0 from: git tag --contains HEAD
[   +9 ms] executing: [/Users/nevercode/development/flutter_master/] git
describe --match *.*.*-*.*.pre --first-parent --long --tags
[ +215 ms] Exit code 0 from: git describe --match *.*.*-*.*.pre --first-parent
--long --tags
[   +1 ms] 1.19.0-0.0.pre-26-g793e6a48a
[  +20 ms] executing: [/Users/nevercode/development/flutter_master/] git
rev-parse --abbrev-ref --symbolic @{u}
[  +18 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[        ] origin/master
[        ] executing: [/Users/nevercode/development/flutter_master/] git
ls-remote --get-url origin
[  +13 ms] Exit code 0 from: git ls-remote --get-url origin
[        ] https://github.com/flutter/flutter.git
[  +86 ms] executing: [/Users/nevercode/development/flutter_master/] git
rev-parse --abbrev-ref HEAD
[  +15 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[        ] master
[  +15 ms] executing: sw_vers -productName
[  +26 ms] Exit code 0 from: sw_vers -productName
[        ] Mac OS X
[        ] executing: sw_vers -productVersion
[  +23 ms] Exit code 0 from: sw_vers -productVersion
[        ] 10.15.4
[        ] executing: sw_vers -buildVersion
[  +19 ms] Exit code 0 from: sw_vers -buildVersion
[        ] 19E287
[  +84 ms] Artifact Instance of 'AndroidMavenArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping
update.
[        ] Artifact Instance of 'FlutterWebSdk' is not required, skipping
update.
[  +17 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping
update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping
update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required,
skipping update.
[  +27 ms] executing: /Users/nevercode/Library/Android/sdk/platform-tools/adb
devices -l
[   +9 ms] executing: /usr/bin/xcode-select --print-path
[  +10 ms] Exit code 0 from: /usr/bin/xcode-select --print-path
[        ] /Applications/Xcode.app/Contents/Developer
[   +1 ms] executing: /usr/bin/xcodebuild -version
[ +280 ms] Exit code 0 from: /usr/bin/xcodebuild -version
[        ] Xcode 11.3.1
           Build version 11C504
[   +9 ms] executing: xcrun --find xcdevice
[  +11 ms] Exit code 0 from: xcrun --find xcdevice
[        ] /Applications/Xcode.app/Contents/Developer/usr/bin/xcdevice
[        ] executing: xcrun xcdevice list --timeout 2
[   +7 ms] /usr/bin/xcrun simctl list --json devices
[        ] executing: /usr/bin/xcrun simctl list --json devices
[  +74 ms] List of devices attached
[ +113 ms] {
                      "devices" : {
                        "com.apple.CoreSimulator.SimRuntime.watchOS-6-1" : [
                          {
                            "state" : "Shutdown",
                            "isAvailable" : true,
                            "name" : "Apple Watch Series 4 - 40mm",
                            "udid" : "7F389A7F-C267-412A-8DB8-63A83386A06F"
                          },
                          {
                            "state" : "Shutdown",
                            "isAvailable" : true,
                            "name" : "Apple Watch Series 4 - 44mm",
                            "udid" : "3568E5A3-98A0-414B-9A79-5CC234FA6E2B"
                          },
                          {
                            "state" : "Shutdown",
                            "isAvailable" : true,
                            "name" : "Apple Watch Series 5 - 40mm",
                            "udid" : "3B543693-444A-4E3D-BD8A-9BD2AE2EDD2F"
                          },
                          {
                            "state" : "Shutdown",
                            "isAvailable" : true,
                            "name" : "Apple Watch Series 5 - 44mm",
                            "udid" : "AF6A4F31-535E-4FE6-A062-49A81AB5AAE3"
                          }
                        ],
                        "com.apple.CoreSimulator.SimRuntime.tvOS-13-3" : [
                          {
                            "state" : "Shutdown",
                            "isAvailable" : true,
                            "name" : "Apple TV",
                            "udid" : "8EC4E84F-BA3E-4251-8351-8324AC08E126"
                          },
                          {
                            "state" : "Shutdown",
                            "isAvailable" : true,
                            "name" : "Apple TV 4K",
                            "udid" : "8FFD5279-9EEA-49AE-83CA-8736CB3E61AB"
                          },
                          {
                            "state" : "Shutdown",
                            "isAvailable" : true,
                            "name" : "Apple TV 4K (at 1080p)",
                            "udid" : "8A1D2EC5-B2B9-474D-81DF-E6A3D0DB84EF"
                          }
                        ],
                        "com.apple.CoreSimulator.SimRuntime.iOS-13-3" : [
                          {
                            "state" : "Shutdown",
                            "isAvailable" : true,
                            "name" : "iPhone 8",
                            "udid" : "D5F70F31-B488-4454-9539-320B5551D92A"
                          },
                          {
                            "state" : "Shutdown",
                            "isAvailable" : true,
                            "name" : "iPhone 8 Plus",
                            "udid" : "62B827A3-68BD-46BD-8E92-DE5297DF3840"
                          },
                          {
                            "state" : "Shutdown",
                            "isAvailable" : true,
                            "name" : "iPhone 11",
                            "udid" : "D1B95CB0-D10B-4983-9AFE-6DB7C4006D15"
                          },
                          {
                            "state" : "Shutdown",
                            "isAvailable" : true,
                            "name" : "iPhone 11 Pro",
                            "udid" : "8B67BA47-2EED-4956-B383-17112E09F7BC"
                          },
                          {
                            "state" : "Shutdown",
                            "isAvailable" : true,
                            "name" : "iPhone 11 Pro Max",
                            "udid" : "A1664A8D-8DB6-4659-B012-18746A2DB8C3"
                          },
                          {
                            "state" : "Shutdown",
                            "isAvailable" : true,
                            "name" : "iPad Pro (9.7-inch)",
                            "udid" : "A7BC437A-C1AB-4DDC-B723-5BC2411FF606"
                          },
                          {
                            "state" : "Shutdown",
                            "isAvailable" : true,
                            "name" : "iPad (7th generation)",
                            "udid" : "50905834-EA49-46D1-9282-2BFD80B002C9"
                          },
                          {
                            "state" : "Shutdown",
                            "isAvailable" : true,
                            "name" : "iPad Pro (11-inch)",
                            "udid" : "C37B8020-20B5-44D3-BB6B-1E34569A3E57"
                          },
                          {
                            "state" : "Shutdown",
                            "isAvailable" : true,
                            "name" : "iPad Pro (12.9-inch) (3rd generation)",
                            "udid" : "BBD1E939-BE74-444C-825D-6DA528EF37D0"
                          },
                          {
                            "state" : "Shutdown",
                            "isAvailable" : true,
                            "name" : "iPad Air (3rd generation)",
                            "udid" : "609AAB06-1510-466F-82F8-1951E7EAFCD2"
                          }
                        ]
                      }
                    }
[+3693 ms] [
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "13.3 (17K446)",
                        "available" : true,
                        "platform" : "com.apple.platform.appletvsimulator",
                        "modelCode" : "AppleTV6,2",
                        "identifier" : "8FFD5279-9EEA-49AE-83CA-8736CB3E61AB",
                        "architecture" : "x86_64",
                        "modelName" : "Apple TV 4K",
                        "name" : "Apple TV 4K"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "13.3 (17C45)",
                        "available" : true,
                        "platform" : "com.apple.platform.iphonesimulator",
                        "modelCode" : "iPad8,1",
                        "identifier" : "C37B8020-20B5-44D3-BB6B-1E34569A3E57",
                        "architecture" : "x86_64",
                        "modelName" : "iPad Pro (11-inch)",
                        "name" : "iPad Pro (11-inch)"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "13.3 (17K446)",
                        "available" : true,
                        "platform" : "com.apple.platform.appletvsimulator",
                        "modelCode" : "AppleTV6,2",
                        "identifier" : "8A1D2EC5-B2B9-474D-81DF-E6A3D0DB84EF",
                        "architecture" : "x86_64",
                        "modelName" : "Apple TV 4K (at 1080p)",
                        "name" : "Apple TV 4K (at 1080p)"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "13.3 (17C45)",
                        "available" : true,
                        "platform" : "com.apple.platform.iphonesimulator",
                        "modelCode" : "iPhone12,5",
                        "identifier" : "A1664A8D-8DB6-4659-B012-18746A2DB8C3",
                        "architecture" : "x86_64",
                        "modelName" : "iPhone 11 Pro Max",
                        "name" : "iPhone 11 Pro Max"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "13.3 (17C45)",
                        "available" : true,
                        "platform" : "com.apple.platform.iphonesimulator",
                        "modelCode" : "iPad6,4",
                        "identifier" : "A7BC437A-C1AB-4DDC-B723-5BC2411FF606",
                        "architecture" : "x86_64",
                        "modelName" : "iPad Pro (9.7-inch)",
                        "name" : "iPad Pro (9.7-inch)"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "6.1.1 (17S445)",
                        "available" : true,
                        "platform" : "com.apple.platform.watchsimulator",
                        "modelCode" : "Watch4,4",
                        "identifier" : "3568E5A3-98A0-414B-9A79-5CC234FA6E2B",
                        "architecture" : "i386",
                        "modelName" : "Apple Watch Series 4 - 44mm",
                        "name" : "Apple Watch Series 4 - 44mm"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "13.3 (17C45)",
                        "available" : true,
                        "platform" : "com.apple.platform.iphonesimulator",
                        "modelCode" : "iPad11,3",
                        "identifier" : "609AAB06-1510-466F-82F8-1951E7EAFCD2",
                        "architecture" : "x86_64",
                        "modelName" : "iPad Air (3rd generation)",
                        "name" : "iPad Air (3rd generation)"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "13.3 (17K446)",
                        "available" : true,
                        "platform" : "com.apple.platform.appletvsimulator",
                        "modelCode" : "AppleTV5,3",
                        "identifier" : "8EC4E84F-BA3E-4251-8351-8324AC08E126",
                        "architecture" : "x86_64",
                        "modelName" : "Apple TV",
                        "name" : "Apple TV"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "13.3 (17C45)",
                        "available" : true,
                        "platform" : "com.apple.platform.iphonesimulator",
                        "modelCode" : "iPhone10,4",
                        "identifier" : "D5F70F31-B488-4454-9539-320B5551D92A",
                        "architecture" : "x86_64",
                        "modelName" : "iPhone 8",
                        "name" : "iPhone 8"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "13.3 (17C45)",
                        "available" : true,
                        "platform" : "com.apple.platform.iphonesimulator",
                        "modelCode" : "iPad8,5",
                        "identifier" : "BBD1E939-BE74-444C-825D-6DA528EF37D0",
                        "architecture" : "x86_64",
                        "modelName" : "iPad Pro (12.9-inch) (3rd generation)",
                        "name" : "iPad Pro (12.9-inch) (3rd generation)"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "13.3 (17C45)",
                        "available" : true,
                        "platform" : "com.apple.platform.iphonesimulator",
                        "modelCode" : "iPhone12,3",
                        "identifier" : "8B67BA47-2EED-4956-B383-17112E09F7BC",
                        "architecture" : "x86_64",
                        "modelName" : "iPhone 11 Pro",
                        "name" : "iPhone 11 Pro"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "6.1.1 (17S445)",
                        "available" : true,
                        "platform" : "com.apple.platform.watchsimulator",
                        "modelCode" : "Watch5,3",
                        "identifier" : "3B543693-444A-4E3D-BD8A-9BD2AE2EDD2F",
                        "architecture" : "i386",
                        "modelName" : "Apple Watch Series 5 - 40mm",
                        "name" : "Apple Watch Series 5 - 40mm"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "13.3 (17C45)",
                        "available" : true,
                        "platform" : "com.apple.platform.iphonesimulator",
                        "modelCode" : "iPhone10,5",
                        "identifier" : "62B827A3-68BD-46BD-8E92-DE5297DF3840",
                        "architecture" : "x86_64",
                        "modelName" : "iPhone 8 Plus",
                        "name" : "iPhone 8 Plus"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "13.3 (17C45)",
                        "available" : true,
                        "platform" : "com.apple.platform.iphonesimulator",
                        "modelCode" : "iPhone12,1",
                        "identifier" : "D1B95CB0-D10B-4983-9AFE-6DB7C4006D15",
                        "architecture" : "x86_64",
                        "modelName" : "iPhone 11",
                        "name" : "iPhone 11"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "13.3 (17C45)",
                        "available" : true,
                        "platform" : "com.apple.platform.iphonesimulator",
                        "modelCode" : "iPad7,12",
                        "identifier" : "50905834-EA49-46D1-9282-2BFD80B002C9",
                        "architecture" : "x86_64",
                        "modelName" : "iPad (7th generation)",
                        "name" : "iPad (7th generation)"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "6.1.1 (17S445)",
                        "available" : true,
                        "platform" : "com.apple.platform.watchsimulator",
                        "modelCode" : "Watch4,3",
                        "identifier" : "7F389A7F-C267-412A-8DB8-63A83386A06F",
                        "architecture" : "i386",
                        "modelName" : "Apple Watch Series 4 - 40mm",
                        "name" : "Apple Watch Series 4 - 40mm"
                      },
                      {
                        "simulator" : true,
                        "operatingSystemVersion" : "6.1.1 (17S445)",
                        "available" : true,
                        "platform" : "com.apple.platform.watchsimulator",
                        "modelCode" : "Watch5,4",
                        "identifier" : "AF6A4F31-535E-4FE6-A062-49A81AB5AAE3",
                        "architecture" : "i386",
                        "modelName" : "Apple Watch Series 5 - 44mm",
                        "name" : "Apple Watch Series 5 - 44mm"
                      }
                    ]
[  +22 ms] Artifact Instance of 'AndroidMavenArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'AndroidGenSnapshotArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping
update.
[   +5 ms] Artifact Instance of 'WindowsEngineArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'MacOSEngineArtifacts' is not required, skipping
update.
[        ] Artifact Instance of 'LinuxEngineArtifacts' is not required, skipping
update.
[        ] Artifact Instance of 'LinuxFuchsiaSDKArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'MacOSFuchsiaSDKArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'FlutterRunnerSDKArtifacts' is not required,
skipping update.
[        ] Artifact Instance of 'FlutterRunnerDebugSymbols' is not required,
skipping update.
[ +355 ms] Generating
/Users/nevercode/Desktop/projects/master/android/app/src/main/java/io/flutter/pl
ugins/GeneratedPluginRegistrant.java
[ +157 ms] Launching lib/main.dart on Chrome in debug mode...
[ +230 ms] Updating assets
[ +367 ms] Syncing files to device Chrome...
[ +161 ms] Generating
/Users/nevercode/Desktop/projects/master/android/app/src/main/java/io/flutter/pl
ugins/GeneratedPluginRegistrant.java
[  +77 ms] <- reset
[  +18 ms]
/Users/nevercode/development/flutter_master/bin/cache/dart-sdk/bin/dart
/Users/nevercode/development/flutter_master/bin/cache/artifacts/engine/darwin-x6
4/frontend_server.dart.snapshot --sdk-root
/Users/nevercode/development/flutter_master/bin/cache/flutter_web_sdk/
--incremental --target=dartdevc --debugger-module-names
-Ddart.developer.causal_async_stacks=true --output-dill
/var/folders/c3/l5jpznsj5k37yrj47l__xpw40000gn/T/flutter_tool.NAGE4u/app.dill
--libraries-spec
file:///Users/nevercode/development/flutter_master/bin/cache/flutter_web_sdk/lib
raries.json --packages .packages -Ddart.vm.profile=false -Ddart.vm.product=false
--bytecode-options=source-positions,local-var-info,debugger-stops,instance-field
-initializers,keep-unreachable-code,avoid-closure-call-instructions
--enable-asserts --track-widget-creation --filesystem-root
/var/folders/c3/l5jpznsj5k37yrj47l__xpw40000gn/T/flutter_tools.R1II0p
--filesystem-scheme org-dartlang-app --initialize-from-dill
build/cache.dill.track.dill --platform
file:///Users/nevercode/development/flutter_master/bin/cache/flutter_web_sdk/ker
nel/flutter_ddc_sdk.dill
[  +71 ms] <- compile org-dartlang-app:/web_entrypoint.dart
[+24600 ms] Syncing files to device Chrome... (completed in 24,913ms, longer than expected)
[   +2 ms] Synced 22.5MB.
[   +2 ms] <- accept
[ +621 ms] [CHROME]:
[   +4 ms] [CHROME]:DevTools listening on ws://<IP_ADDRESS>:50319/devtools/browser/ebb19b19-c88b-4b1b-82f0-fd1251bd14cc
[+6091 ms] Debug service listening on ws://<IP_ADDRESS>:50352/NgGGcMnRhwM=

[ +778 ms] Debug service listening on ws://<IP_ADDRESS>:50352/NgGGcMnRhwM=
[   +2 ms] Warning: Flutter's support for web development is not stable yet and hasn't
[        ] been thoroughly tested in production environments.
[   +1 ms] For more information see https://flutter.dev/web
[   +1 ms] 🔥  To hot restart changes while running, press "r". To hot restart (and refresh the browser), press "R".
[   +2 ms] For a more detailed help message, press "h". To quit, press "q".
[+1251 ms] A null value was passed into a non-nullable parameter value
                    This will become a failure when runtime null safety is enabled.

[+26445 ms] Performing hot restart...
[  +12 ms] Scanned through 477 files in 11ms
[        ] Syncing files to device Chrome...
[   +3 ms] <- recompile org-dartlang-app:/web_entrypoint.dart e7d6cf89-2240-46b7-9335-0ed3e7ea30a5
[        ] package:master/main.dart
[        ] <- e7d6cf89-2240-46b7-9335-0ed3e7ea30a5
[  +51 ms] Syncing files to device Chrome... (completed in 55ms)
[        ] Synced 0.0MB.
[        ] <- accept
[  +63 ms] Null is not a subtype of Future<dynamic>.
           This will become a failure when runtime null safety is enabled.

[ +111 ms] Performing hot restart... (completed in 243ms)
[        ] Restarted application in 244ms.
[+29269 ms] Performing hot restart...
[  +23 ms] Scanned through 477 files in 21ms
[        ] Syncing files to device Chrome...
[   +1 ms] <- recompile org-dartlang-app:/web_entrypoint.dart 585fbce3-212b-4a32-a4dc-116d8a8af1ca
[        ] package:master/main.dart
[        ] <- 585fbce3-212b-4a32-a4dc-116d8a8af1ca
[  +43 ms] Syncing files to device Chrome... (completed in 44ms)
[        ] Synced 0.0MB.
[        ] <- accept
[  +56 ms] Null is not a subtype of Future<dynamic>.
           This will become a failure when runtime null safety is enabled.

[  +87 ms] Performing hot restart... (completed in 212ms)
[        ] Restarted application in 213ms.
[  +32 ms] Error: Invalid argument(s): Extension already registered: ext.flutter.disassemble
               at Object.throw_ [as throw] (http://localhost:50296/dart_sdk.js:4461:11)
               at Object.registerExtension$ [as registerExtension] (http://localhost:50296/dart_sdk.js:48563:17)
               at Object.webOnlyInitializeEngine (http://localhost:50296/dart_sdk.js:163999:15)
               at _initializePlatform (http://localhost:50296/dart_sdk.js:134269:15)
               at _initializePlatform.next (<anonymous>)
               at runBody (http://localhost:50296/dart_sdk.js:36923:34)
               at Object._async [as async] (http://localhost:50296/dart_sdk.js:36951:7)
               at Object._initializePlatform (http://localhost:50296/dart_sdk.js:134265:18)
               at Object.webOnlyInitializePlatform (http://localhost:50296/dart_sdk.js:134257:35)
               at main$ (http://localhost:50296/web_entrypoint.dart.lib.js:13:16)
               at main$.next (<anonymous>)
               at runBody (http://localhost:50296/dart_sdk.js:36923:34)
               at Object._async [as async] (http://localhost:50296/dart_sdk.js:36951:7)
               at Object.main$ [as main] (http://localhost:50296/web_entrypoint.dart.lib.js:12:18)
               at RequireRestarter__reload_closure.call$0 (http://localhost:50296/dwds/src/injected/client.js:22818:15)
               at Object.Primitives_applyFunction (http://localhost:50296/dwds/src/injected/client.js:860:30)
               at Object.Function_apply (http://localhost:50296/dwds/src/injected/client.js:5012:16)
               at _callDartFunctionFast (http://localhost:50296/dwds/src/injected/client.js:7001:16)
               at http://localhost:50296/dwds/src/injected/client.js:6992:18
               at <anonymous>:1:8
               at Object.runMain (http://localhost:50296/dwds/src/injected/client.js:8343:15)
               at http://localhost:50296/dwds/src/injected/client.js:22335:19
               at _wrapJsFunctionForAsync_closure.$protected (http://localhost:50296/dwds/src/injected/client.js:3636:15)
               at _wrapJsFunctionForAsync_closure.call$2 (http://localhost:50296/dwds/src/injected/client.js:10848:12)
               at Object._asyncStartSync (http://localhost:50296/dwds/src/injected/client.js:3600:20)
               at main__closure1.$call$body$main__closure (http://localhost:50296/dwds/src/injected/client.js:22347:16)
               at main__closure1.call$1 (http://localhost:50296/dwds/src/injected/client.js:22279:19)
               at StaticClosure._rootRunUnary [as call$2$5] (http://localhost:50296/dwds/src/injected/client.js:3958:16)
               at _CustomZone.runUnary$2$2 (http://localhost:50296/dwds/src/injected/client.js:12164:39)
               at _CustomZone.runUnaryGuarded$1$2 (http://localhost:50296/dwds/src/injected/client.js:12092:14)
               at _ControllerSubscription._sendData$1 (http://localhost:50296/dwds/src/injected/client.js:11642:19)
               at _DelayedData.perform$1 (http://localhost:50296/dwds/src/injected/client.js:11796:59)
               at _PendingEvents_schedule_closure.call$0 (http://localhost:50296/dwds/src/injected/client.js:11845:14)
               at Object._microtaskLoop (http://localhost:50296/dwds/src/injected/client.js:3801:21)
               at StaticClosure._startMicrotaskLoop (http://localhost:50296/dwds/src/injected/client.js:3807:11)
               at _AsyncRun__initializeScheduleImmediate_internalCallback.call$1 (http://localhost:50296/dwds/src/injected/client.js:10720:9)
               at invokeClosure (http://localhost:50296/dwds/src/injected/client.js:1172:26)
               at MutationObserver.<anonymous> (http://localhost:50296/dwds/src/injected/client.js:1191:18)

I just set a background color to the Scaffold,
hot-reloaded, changed the color
and hot-reloaded again and to get the error.
Thank you for reporting this

Sure, glad to help. You don't even have to change something in the code: just trigger the restart (any of it, the "r" or "R" mode) and the issue happens.

This behavior started with the Dart NNBD unfork (https://github.com/flutter/engine/commit/9b905d3f03f27a332ad861934da0f5111c24d347)

\cc @jakemac53

This is happening due to new lazy field initialization behavior introduced in https://github.com/dart-lang/sdk/commit/8fb4645cae272f198d85b477b9aa029764d83369
That PR adds a new implementation of defineLazyField that sets an executed flag after the first read of a lazy field.  Subsequent reads see that executed is true and do not add a reset function to the _resetFields list.
So after the first hot restart the reset handler for developer._extensions runs and clears the extensions map.  But on the second hot restart the reset handler is not present and developer._extensions retains its old value.
Later, the call to registerExtension(ext.flutter.disassemble) after the hot restart sees that ext.flutter.disassemble is already in the map and throws.
I was able to get repeated hot restarts to work by patching defineLazyField to clear the executed flag in the field's reset handler.
@Markzipan @sigmundch Would that provide the right semantics?

Thanks @jason-simmons! Yes, I believe that would be the appropriate fix to do here.
@Markzipan we should also file for a cherry-pick for this... if we have other static fields in the sdk, I can expect this to affect hotrestart in surprising ways.

Nice catch! Hopefully that oversight wasn't too dreadful to track down. I can put together a fix + tests here.

The issue's been fixed. It may not be worth cherrypicking, as it'll show up in the next roll. Thanks @jason-simmons!

@Markzipan That's great! Thank you all for the quick feedback.
I would love to close this ticket myself, but before that ... when/how could I test again?
Asking mainly to see if I can help.

Since you are using the master flutter branch, it could be at any moment now. There is an automated process that rolls the Dart changes into flutter periodically (often I see 3 a day). The last one was 6 hours ago (https://github.com/flutter/engine/pull/18347) but @Markzipan change didn't make it on that roll, so I expect it will be part of the next one.

I don't think an alibaba fork merge should have closed this...

Currently seeing this issue in dev branch version 1.19.0-1.0.pre. Reverting my local SDK to 1.19.0-0.0.pre is a temporary fix for me.

@jmagman Looks like it's made its way upstream and was merged into dart-lang/sdk.
https://github.com/dart-lang/sdk/commit/e2ebfeafa08717195d063c3636a88e4647718df1
https://github.com/dart-lang/sdk/commit/17efd727788fd88bf1fa8599ba6d66208b8c8743
Perhaps this ticket should be closed once the dart roll brings it into master.

https://github.com/flutter/engine/pull/18373
https://github.com/flutter/flutter/pull/57252

https://github.com/flutter/flutter/pull/57252 has merged and this fix is now available in the master channel.
Closing.

I am on master channel to be able to build/test with Windows and using current version 1.19.0-2.0.pre.71. I still have hot reload issues, it drops random asset images (after a few reloads, randomly when it start doing that too), maybe there is an issue for that too?
Only way to get asset images back after that is to do full rebuild. Really annoying to be honest.

Continuing the comment above me^ I'm also on the newest commit on master, hot restart isn't working, at all.

Using Flutter 1.19.0-2.0.pre.71 on Web (using Chrome):

at each restart we have the warning:Null is not a subtype of FutureOr<ByteData>.
This will become a failure when runtime null safety is enabled.

now there is the following warning message that keeps polluting the console whenever you move the mourse over the (+) button of the counter (default) app:Overflow on channel: flutter/mousecursor.  Messages on this channel are being discarded in FIFO fashion.  The engine may not be running or you need to adjust the buffer size if of the channel.

The hot restart does not work, just the a cold restart that wipes away the current state.

@jmagman From the issue perspective, I could understand why the ticket has been closed. But then, the "hot restart not working" case should be addressed in a different issue?
Thanks

@Markzipan @slightfoot @sigurdm Does this need to be reopened?  I am not familiar at all with this issue, I just hopped in because it incorrectly popped up in the Flutter tools team issue pile and I removed the label.

@jmagman thanks, I opened a new issue on the ddc side to generally track that hot restart on flutter web doesn't regress.
@jonahwilliams feel free to reopen here if you also want to track it on the flutter repo.

A null value was passed into a non-nullable parameter value
This will become a failure when runtime null safety is enabled.
the warning is still here
[√] Flutter (Channel dev, 1.19.0-1.0.pre, on Microsoft Windows [version 10.0.18363.836], locale fr-FR)
• Flutter version 1.19.0-1.0.pre at TOTO
• Framework revision 456d80b9dd (7 days ago), 2020-05-11 11:45:03 -0400
• Engine revision d96f962ca2
• Dart version 2.9.0 (build 2.9.0-7.0.dev 092ed38a87)

Does it have something to do with:
visualDensity: VisualDensity.adaptivePlatformDensity,
const VisualDensity({
this.horizontal = 0.0,
this.vertical = 0.0,
}) : assert(horizontal != null),
assert(vertical != null),
assert(vertical <= maximumDensity),
assert(vertical >= minimumDensity),
assert(horizontal <= maximumDensity),
assert(horizontal >= minimumDensity);

Null is not a subtype of Future

Error: Invalid argument(s): Extension already registered: ext.flutter.disassemble
at Object.throw_ [as throw] (http://localhost:62236/dart_sdk.js:4461:11)
at Object.registerExtension$ [as registerExtension] (http://localhost:62236/dart_sdk.js:48563:17)
at Object.webOnlyInitializeEngine (http://localhost:62236/dart_sdk.js:164007:15)
at _initializePlatform (http://localhost:62236/dart_sdk.js:134269:15)
at _initializePlatform.next ()
at runBody (http://localhost:62236/dart_sdk.js:36923:34)
at Object._async [as async] (http://localhost:62236/dart_sdk.js:36951:7)
at Object._initializePlatform (http://localhost:62236/dart_sdk.js:134265:18)
at Object.webOnlyInitializePlatform (http://localhost:62236/dart_sdk.js:134257:35)
at main$ (http://localhost:62236/web_entrypoint.dart.lib.js:13:16)
at main$.next ()
at runBody (http://localhost:62236/dart_sdk.js:36923:34)
at Object._async [as async] (http://localhost:62236/dart_sdk.js:36951:7)
at main$ (http://localhost:62236/web_entrypoint.dart.lib.js:12:18)
at :1:8
at Object.runMain (http://localhost:62236/dwds/src/injected/client.js:8343:15)
at http://localhost:62236/dwds/src/injected/client.js:22335:19
at _wrapJsFunctionForAsync_closure.$protected (http://localhost:62236/dwds/src/injected/client.js:3636:15)
at _wrapJsFunctionForAsync_closure.call$2 (http://localhost:62236/dwds/src/injected/client.js:10848:12)
at Object._asyncStartSync (http://localhost:62236/dwds/src/injected/client.js:3600:20)
at main__closure1.$call$body$main__closure (http://localhost:62236/dwds/src/injected/client.js:22347:16)
at main__closure1.call$1 (http://localhost:62236/dwds/src/injected/client.js:22279:19)
at StaticClosure._rootRunUnary [as call$2$5] (http://localhost:62236/dwds/src/injected/client.js:3958:16)
at _CustomZone.runUnary$2$2 (http://localhost:62236/dwds/src/injected/client.js:12164:39)
at _CustomZone.runUnaryGuarded$1$2 (http://localhost:62236/dwds/src/injected/client.js:12092:14)
at _ControllerSubscription._sendData$1 (http://localhost:62236/dwds/src/injected/client.js:11642:19)
at _DelayedData.perform$1 (http://localhost:62236/dwds/src/injected/client.js:11796:59)
at _PendingEvents_schedule_closure.call$0 (http://localhost:62236/dwds/src/injected/client.js:11845:14)
at Object._microtaskLoop (http://localhost:62236/dwds/src/injected/client.js:3801:21)
at StaticClosure._startMicrotaskLoop (http://localhost:62236/dwds/src/injected/client.js:3807:11)
at _AsyncRun__initializeScheduleImmediate_internalCallback.call$1 (http://localhost:62236/dwds/src/injected/client.js:10720:9)
at invokeClosure (http://localhost:62236/dwds/src/injected/client.js:1172:26)
at MutationObserver. (http://localhost:62236/dwds/src/injected/client.js:1191:18)A null value was passed into a non-nullable parameter value
This will become a failure when runtime null safety is enabled.

Performing hot restart...                                              |Null is not a subtype of Future.
This will become a failure when runtime null safety is enabled.
THE SAME ON MASTER CHANNEL
Doctor summary (to see all details, run flutter doctor -v):
[√] Flutter (Channel master, 1.19.0-2.0.pre.114, on Microsoft Windows [version 10.0.18363.836], locale fr-FR)

@benedicte69 - I don't believe the fix from "Extension already registered: ext.flutter.disassemble" has reached the dev channel, but you should not see that in master.
It may be possible that the issue with the warning has not been fixed in master yet? The change to hide the warnings (https://github.com/dart-lang/sdk/commit/ab0d67d8dbe59d2430678988471d818fbd7a5dac) landed in the dart SDK this afternoon and needs to be rolled into flutter. I see a PR that indicates that the change was rolled (https://github.com/flutter/engine/pull/18495), but it's fairly recent (2 hours ago).

@sigmundch - Although the change might have already landed, I've just now, upgraded flutter and saw no difference - meaning, both the null safety and the hot restart bug - still exist.
(I'm on master, lastest version and no errors reported by the doctor :) )

I had to step down to 18.x to be able to do anything sensible on master when building for Windows desktop target. Simply because 19.x was not restarting, hot-reload was flaky and after a few of either, it started dropping image assets as well and needed a full rebuild to work again. Very frustrating to use. Trust me if there was an option to not use master, if Windows target was available on dev, I would be happy to stop using master in blue second.
Still before 19.x using master had been mostly smooth sailing since mid 2019, with only the occasional minor hick-up, never seen it this broken before.
Hope it all gets sorted out soon! As soon as someone claims Windows Desktop target on master 19.x is more usable again, I  will be happy to give it a spin once again. Been on 18 for a while now, some issues there too, 17 was the best so far, windows desktop builds.

hii, all when i am running web app. i am getting following error
Launching lib/main.dart on Chrome in debug mode...
Syncing files to device Chrome...
20,013ms (!)
Debug service listening on ws://<IP_ADDRESS>:38219/UKUqz4SsnNU=
Warning: Flutter's support for web development is not stable yet and hasn't
been thoroughly tested in production environments.
For more information see https://flutter.dev/web
🔥  To hot restart changes while running, press "r". To hot restart (and refresh the browser), press "R".
For a more detailed help message, press "h". To quit, press "q".
A null value was passed into a non-nullable parameter value
This will become a failure when runtime null safety is enabled
actually i made responsive website on which we can upload image. but when i click on image uploader button .it does not response anything,please help me?

@sigmundch Thanks for your quick  answer I will check tomorrow or the day after if it is better. The only difference I noticed is that in master channel you can use 'r' as much as you want but the error was still appearing in both channel. In dev channel after a few 'r',  'r' was no longer working. Keep in touch, have a nice day and I hope you will find where this 'null' has been put
Envoyé depuis Yahoo Mail pour Android
Le mar., mai 19, 2020 à 5:42<EMAIL_ADDRESS>a écrit :
@benedicte69 - I don't believe the fix from "Extension already registered: ext.flutter.disassemble" has reached the dev channel, but you should not see that in master.
It may be possible that the issue with the warning has not been fixed in master yet? The change to hide the warnings (dart-lang/sdk@ab0d67d) landed in the dart SDK this afternoon and needs to be rolled into flutter. I see a PR that indicates that the change was rolled (flutter/engine#18495), but it's fairly recent (2 hours ago).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

No change(dev and master channel:
|Null is not a subtype of Future.
This will become a failure when runtime null safety is enabled.

@benedicte69 I thought our fixes have been rolled into flutter master and the warning should've disappeared there.
@jonahwilliams - We are not very familiar with the autoroll process, is dart-lang/sdk@ab0d67d visible on the master channel at this time?

We haven't done a dev release, so it may only be on master

Yes, https://github.com/flutter/flutter/pull/57252 is still only on master.


use constraint for CIT

Until now we had a small 'hack' of a special test-run flag to prevent CIT tests from being run in other circumstances such as the repo-wide presubmit. Switch to using a custom build constraint, which satisfies the same and sets us up for tests on tests.

Proof the constraint works is given by the fact the gotest presubmit passed, but just to be 100% explicit about it:
guest-test-infra/imagetest$ go test ./...
ok  	github.com/GoogleCloudPlatform/guest-test-infra/imagetest	(cached)
?   	github.com/GoogleCloudPlatform/guest-test-infra/imagetest/cmd/manager	[no test files]
?   	github.com/GoogleCloudPlatform/guest-test-infra/imagetest/cmd/wrapper	[no test files]
?   	github.com/GoogleCloudPlatform/guest-test-infra/imagetest/test_suites/disk	[no test files]
?   	github.com/GoogleCloudPlatform/guest-test-infra/imagetest/test_suites/image_boot	[no test files]
?   	github.com/GoogleCloudPlatform/guest-test-infra/imagetest/test_suites/image_validation	[no test files]
?   	github.com/GoogleCloudPlatform/guest-test-infra/imagetest/test_suites/network	[no test files]
?   	github.com/GoogleCloudPlatform/guest-test-infra/imagetest/test_suites/security	[no test files]
?   	github.com/GoogleCloudPlatform/guest-test-infra/imagetest/test_suites/ssh	[no test files]
?   	github.com/GoogleCloudPlatform/guest-test-infra/imagetest/utils	[no test files]


MySQL 5.6 is not supported

Laravel Version: 7.18.0
PHP Version: 7.4.7
Database Driver & Version: MySQL 5.6.44

Description:
The documentation states that MySQL 5.6+ is supported, however this isn't the case since several json_* methods that are currently used were only added in version 5.7.
I chose to create this issue here instead of in the docs repo because I'm not sure if the best solution is to just change the documentation or change the code, since some users might have chosen their requirements based on the docs.
Steps To Reproduce:
Use any MySQL grammar that calls JSON methods.

The documentation states:

Laravel also supports querying JSON column types on databases that provide support for JSON column types. Currently, this includes MySQL 5.7, PostgreSQL, SQL Server 2016, and SQLite 3.9.0 (with the JSON1 extension).

If you have a database installed that supports JSON column types then you can use those features, if you do not then they are not supported. The part of the docs that you linked is correct, since MySQL 5.6 is supported. It makes no mention of JSON column types there.

Yes, you're right. I should have read it better. Thanks and sorry!


Update project identity after BOM upload

When uploading a BOM Dependency Track does not fill in the project identity fields (e.g. group, PURL).
It looks like Dependency Track cannot update the project details based on the BOM: https://github.com/DependencyTrack/dependency-track/discussions/1156#discussioncomment-1220078
It would be nice if the plugin would use the /v1/project API to update the project with information from the metadata/component section in the BOM it just uploaded.

I started on a branch to implement this feature: https://github.com/elmuerte/dependency-track-maven-plugin/tree/update-project-info

Hey, what version of Dependency Track does this affect?  I assume all versions?

The project info not being filling based on SBOM data? I don't think I've ever seen this working in 3.x or 4.x.

This has been shipped in v1.3.0.  Please let me know if any issues.  Thanks for the contribution!


How do I prevent the environment variables shown in phpinfo()

How do I prevent the environment variables shown in phpinfo() page?

I'm not sure there's a way to do this. Perhaps ask on some forums, as it's not related to this package?