SOW-24: pass statusChangeEvent to planViewer

I'm a bit unclear why this is needed, what's causing the viewer component to not be able to get the status change event from the list of events?

I'm a bit unclear why this is needed, what's causing the viewer component to not be able to get the status change event from the list of events?

we are adding the endDate for the old status change only when resolving to CSV so the list of events that the Export page is passing down to PlanViewer has the new status change event but it also has the old one without an endDate


Infer a union from a set of candidates instead of only a super-type

TypeScript Version:  2.1.1 / nightly (2.2.0-dev.201xxxxx)
Consider the following:
function first(items: T[] | Iterable<T>): T {
  for (let item of items) return item;
  throw new Error('No first element');
}

let items: number[] | string[];

let i1 = first(items);

for (let i2 of items) {
  // ...
  break;
}

Desired behavior:
Infer number | string for both i1 and i2.
Actual behavior:
A type cannot be inferred for i1 (candidate number not a sub-type of string). number | string is inferred for i2.
Proposal:
Change 4.15.2 second clause from:

Otherwise, if at least one of the candidate types is a supertype of all of the other candidate types, let C denote the widened form (section 3.12) of the first such candidate type. If C satisfies T's constraint, the inferred type argument for T is C. Otherwise, the inferred type argument for T is T's constraint.

to:

Otherwise, remove all types from the set for which another type in the set is a supertype the type and is not the type itself. Let C denote the union of the widened form (section [3.12]) of the all remaining types. If C satisfies T's constraint, the inferred type argument for T is C. Otherwise, the inferred type argument for T is T's constraint.

It should be clear that in all cases that the previous algorithm produces a type C this change produces the same type C without introducing additional algorithmic complexity. It should also be clear that the above change produces the desired result of number | string for i2.
The current implementation diverges from the specification but it should be clear how to map this change with the current implementation (that is, inferiority does not significantly change it and union factoring helps it).
If this change is implemented, consider removing the special case typing rules for for let x of (declarations in a ForInStatement node) as the current behavior is a direct consequence of the change in typing rule if the element type is inferred as T from the type:
  type NgForOfElementType<T> = Iterable<T> | { readonly length: number; readonly [index: number]: T;

which would then enable abstraction over a for to produce the same type as an inlined for.
Background:
Angular has a type NgFor which we are adding a type parameter to allow inferring element type of the iterated instance. However, there appears to be no way declare  NgFor such that it will infer the same type an equivalent for of would produce. For example,
<ul>
  <li *ngFor="let item of items">
    {{item}}
  </li>
</ul>

The expectation is that the type of item would be number | string. However, there appears to be no way to construct a set of calls that produces the implied instances and infers number | string for item (https://github.com/angular/angular/issues/12398).
We believe this change would be helpful for TypeScript but we are not blocked by its absence.

This is only safe in read positions, but not in write positions. consider:
declare function add<T>(list: T[], value: T): void;

let items: number | string[];
add(items, 2);

Inferring number|string here would result in unsafe code.
We really need in/out annotations on parameters to be able to do this without violating safety.
Is providing an explicit type parameter an option (e.g. typeof items[number]) ?

@mhegazy Perhaps this could work for ReadonlyArray<T>?
Also, I noticed a weird issue.
I tried to work around this using union types and I got this

Based on @ahejlsberg's comment in #13346 this should not happen.

Perhaps this could work for ReadonlyArray?

the issue here is not about Array or ReadonlyArray. the issue is no way to mark parameters in general as readOnly/in, writeOnly/out or readWrite. the type system does not track that, and a full support is needed in the type system first, then we can annotate ReadonlyArray accordingly.

@mhegazy The current algorthim is similarly unsafe as it selects a super-type in the candidate list so your example could easily be written as:
declare function add<T>(list: T[], value: T): void;

let items: number[] | string[] | (number| string)[] = [];

add(items,2);

and type-check because of the candidate types string, number and number | string, number | string is a super-type of all other types and is selected even though it is unsafe used co-variantly.
The whole is really that following type-checks,
add<number|string>(items);

The whole is introduce not by type inference but, rather that array's type parameter is type-check variant instead of invariant (that is T[] is consider a super-type of S[] if T is a super-type of S) . Regardless of the inferencing, treating arrays as variant is a whole. (It should be invariant because T is used in both a variant and co-variant position meaning the only safe typing is invariant).
My change, therefore, doesn't introduce a new whole though it probably makes an existing whole easier to hit. C# and Java have similar wholes, because invariant typing arrays here is a pain, but their VM type-checks the write at runtime.
The issue is really not safety, but rather, whether synthesizing a super-type during type inference is useful and doesn't cause the algorithm to diverge. I believe I have made a case for both.

The type whole does exist. but as you noted it is less likely for sub type reduction to produce an error now than with this proposed change; and i am not sure if the utility resulting from this change overweights the loss of safety introduced.

I don't find using expanding the cases a user can run into the type whole very persuasive as your example is rather a corner case and whole itself is huge. For example, even with no type-inferencing, the following code type-checks:
class A {}
class B extends A {}

let a: A = new A();
let items: B[] = [];
items.push(a);

Even if this was disallowed as obviously wrong you are still left with,
class A {}
class B extends A {}

let a: A = new A();
let items: B[] = [];
let aItems: A[] = items;
aItems.push(a);

which is equally wrong but is allowed because of variant subtype relation. These, I would argue, are much more common errors that a user would run into that can easily be transformed into type inferencing problems with either algorithm.
The reason your example doesn't type-check is not because it is unsafe, rather, it is because a super-type was not found. This only bans a very narrow set of cases and is easily accidentally thwarted. Plus it introduces a false sense of security as the user might think, since some cases are caught, all cases are caught. Preventing new ways to run into the whole seems to be like keeping the back door closed while the front door is wide open.
In TypeScript, writing to an array is not sufficiently checked. The whole is deep and wide and makes TypeScript's type system unsound; but it would be extremely taxing to fix as it would throw co-variance in the users face where they don't expect it. In a customer segment that is already type hostile, adding a feature that makes even type enthusiasts hostile, sounds like something that should be done very carefully.
I would say, given this, that the utility of a change only has to meet a very low bar to cross the threshold to justify itself against increasing the number of paths to the whole. I believe my change, which allows expressing the type relation implied by for...of, meets that bar.

Thinking about this more I believe the potential change in overloading resolution results is not worth the benefit of this change. I still like this idea but the change should be tied together with something else that has more general utility, like type parameter variant declaration as you suggest above, as potentially breaking something like Promise.then() would definitely not be worth this change.


[DO NOT MERGE] apic-extension 1.0.0b5 release

This checklist is used to make sure that common guidelines for a pull request are followed.
Related command
az apic *
General Guidelines

[x] Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
[x] Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)
[x] My extension version conforms to the Extension version schema

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish
There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

Thank you for your contribution! We will review the pull request and get back to you soon.

could you please provide the link of pr in aaz repo?

could you please provide the link of pr in aaz repo?

Thank you, here it is: https://github.com/Azure/aaz/pull/468. Let's sync offline about how to resolve the conflicts..

Finished executing the test plan.


WMA <IP_ADDRESS> release notes

:x: Organization membership check failed
Members of the MicrosoftDocs organization should use the private repo. Please move your changes to https://github.com/MicrosoftDocs/Dynamics-365-Operations, and close this pull request.


Bug , in version target

Execution failed for task ':speech_bubble:verifyReleaseResources'.

A failure occurred while executing com.android.build.gradle.internal.tasks.Workers$ActionFacade
Android resource linking failed

@NilsBacke any chance on merging this and publishing on pub.dev ?
Right now it won't compile with androidX.

@NilsBacke Thank you!


FI-2033 Minor typo and grammar fixes

Summary
Addressed most of the typo and grammar points from the FI-2033 Documentation Review feedback page.
The only thing I did not know how to fix was the string that appears in the browser tab.  If you go to https://inferno-framework.github.io/index_new.html and look at the tab, it is just "Inferno Framework - " instead of something like "Inferno Framework - Home".
Testing Guidance
None

I fixed that title issue in the cutover pr, thanks for pointing that out!


Problems during assembly

We had some issues:

U3 wrong footprint
D4 wrong footprint or we used the wrong part. A datasheet would be great
The rectifier is wrong and must be updated
The buzzing of the flyback is pretty annoying

@odinthenerd could you refactor the design

D4 is a generic part number, many companies produce these diodes with different MPNs and footprints. 1N4148WS or LCSC: C2128 should work.
U3 lol the coilcraft footrint does not match the coilcraft datasheet. footprint fixed in new version
rectifier: yeah that was stupid, I fixed it (we need to fix in a few other places)
buzzing: the ILIM resistor R3 needs to match the transformer, I changed its value as per the formula in the datasheet and now it doesn't buzz (its a miracle)


[MM-15391] Turn auto-launch after installation off

PR to set auto-launch of the desktop app after MSI installation completes to off by default.

This issue has been automatically labelled "stale" because it hasn't had recent activity.
A core team member will check in on the status of the PR to help with questions.
Thank you for your contribution!
/cc @jasonblais @hanzei

Closing in favour of a single branch based off of release-test-msi for all MSI related updates to make further updates more manageable. New PR pending.


Feature/checkbox component

GitHub Issue
Link to the GitHub issue.
Changes
Created checkbox component based on primitave from Radix UI Checkbox Primitive
Packages Added
Brief list of any packages added, and if folks need to rerun yarn install to run locally
"@radix-ui/react-checkbox": "^0.1.5",
Checks
Before making your PR, please check the following:

[x] Critical lint errors are resolved
[x] App runs locally
[x] App builds locally (run the build command for any impacted package and check for any errors before the PR)

@0xRowdy @jordanlesich should we start reviewing this PR? I saw the comment on the other one about merging in the multi work so just wanted to check in. Thanks!

This is the same as the feature/checkbox but doesn't have all the shanagans from when I thought I broke the build. This branch has cleaner git history and is probably better to merge, as far as code they are the exact same.


1.1.4 release

We've been using the queryAll flag for a few months now using a custom build from master. It seems to be working as expected. Can we do a 1.1.4 release to get that support in an official version?

Can we have this merged as soon as possible?

Hi nhamiltontt
QueryAll is not working for me. Can you tell me how you create the custom build and utilise the query all method?
Also do we have any latest release with queryAll options. I am using 1.1.3


Test issue

This is a issue test. No bugs or problems to report at this time.

Thanks for testing! I'm adding a section to the README.md to say report bugs here.


Annoying "Do you want to save the changes?" messages.

VSCode Version:
1.3.1
OS Version:
Linux (64bit)

Steps to Reproduce:
0. close all editors,
set:

"workbench.editor.showTabs": false,

{ "key": "ctrl+w", "command": "workbench.action.closeEditorsInGroup" }

open an existing file

press ctrl+2

open it again in the 2-nd editor and make some changes,

press ctrl+w.

I still have editor 1 with that file opened, I am not closing the file, just 2nd editor (with one command). How to get rid of that message?

https://github.com/Microsoft/vscode/issues/8983


Promote core.gardener.cloud/v1alpha1 to v1beta1

What this PR does / why we need it:
With this PR, every resource except ShootState gets promoted to v1beta1 from core.gardener.cloud/v1alpha1.
In order to finally remove garden.sapcloud.io/v1beta1 we should have at least a beta alternative for our end-users/stakeholders.
Special notes for your reviewer:

All components (controller-manager, scheduler) still work with the v1alpha1 version but will be adapted in a future version to v1beta1 (after extension controllers had some time to be able to work with both v1alpha1 and v1beta1).
Changes compared to v1alpha1:

The .spec.seed field in core.gardener.cloud/v1alpha1.BackupBucket has been renamed to .spec.seedName in core.gardener.cloud/v1beta1.BackupBucket.
The .spec.seed field in core.gardener.cloud/v1alpha1.BackupEntry has been renamed to .spec.seedName in core.gardener.cloud/v1beta1.BackupEntry.
The .spec.blockCIDRs field core.gardener.cloud/v1alpha1.Seed has been moved to .spec.networks.blockCIDRs in core.gardener.cloud/v1beta1.Seed.
The .spec.addons.kubernetes-dashboard field core.gardener.cloud/v1alpha1.Shoot has been renamed to .spec.addons.kubernetesDashboard in core.gardener.cloud/v1beta1.Shoot.
The .spec.addons.nginx-ingress field core.gardener.cloud/v1alpha1.Shoot has been renamed to .spec.addons.nginxIngress in core.gardener.cloud/v1beta1.Shoot.
The .status.seed field core.gardener.cloud/v1alpha1.Shoot has been renamed to .status.seedName in core.gardener.cloud/v1beta1.Shoot.
The .status.lastError field core.gardener.cloud/v1alpha1.Shoot does no longer exist in core.gardener.cloud/v1beta1.Shoot (in favour of .status.lastErrors).

Release note:

As preparation for the final removal of the already deprecated `garden.sapcloud.io/v1beta1` API group, all resources (except `ShootState`) available in `core.gardener.cloud/v1alpha1` are now promoted to `core.gardener.cloud/v1beta1` with the following changes:
* The `.spec.seed` field in `core.gardener.cloud/v1alpha1.BackupBucket` has been renamed to `.spec.seedName` in `core.gardener.cloud/v1beta1.BackupBucket`.
* The `.spec.seed` field in `core.gardener.cloud/v1alpha1.BackupEntry` has been renamed to `.spec.seedName` in `core.gardener.cloud/v1beta1.BackupEntry`.
* The `.spec.blockCIDRs` field `core.gardener.cloud/v1alpha1.Seed` has been moved to `.spec.networks.blockCIDRs` in `core.gardener.cloud/v1beta1.Seed`.
* The `.spec.addons.kubernetes-dashboard` field `core.gardener.cloud/v1alpha1.Shoot` has been renamed to `.spec.addons.kubernetesDashboard` in `core.gardener.cloud/v1beta1.Shoot`.
* The `.spec.addons.nginx-ingress` field `core.gardener.cloud/v1alpha1.Shoot` has been renamed to `.spec.addons.nginxIngress` in `core.gardener.cloud/v1beta1.Shoot`.
* The `.status.seed` field `core.gardener.cloud/v1alpha1.Shoot` has been renamed to `.status.seedName` in `core.gardener.cloud/v1beta1.Shoot`.
* The `.status.lastError` field `core.gardener.cloud/v1alpha1.Shoot` does no longer exist in `core.gardener.cloud/v1beta1.Shoot` (in favour of `.status.lastErrors`).

Developers should re-run `./hack/dev-setup-register-gardener` in order to register the new `core.gardener.cloud/v1beta1` API group.

All Gardener components are still working with `core.gardener.cloud/v1alpha1` but will soon switch to `core.gardener.cloud/v1beta1`. That means that the `extensions.gardener.cloud/v1alpha1.Cluster` resource will then contain the `core.gardener.cloud/v1beta1` resources only. Extension controllers should be prepared to be able to work with both the `v1alpha1` and the `v1beta1` version.

Thanks for your reviews, guys. Rebasing to resolve the conflicting files now and merging after CI passed.


street category

given information does not match the design
"show more" is missed in site while we have"show more" in design

This is already done and this photo is from long time ago !!
be advised to have Fine Art and Street Cat shown you must have the following categories in database + their slug fields:
name= Fine art =>slug =fine-art
name= Street => slug= street
(only the slug spelling matters)


@saolsen => Dont wait for docker stuff to deploy to heroku on Circle 2.0

Currently waiting on a Docker thingie...we can do Heroku deploys right after the test.

good call 👍

I think this is safe to insta-merge.


Stress and Taxes

Your Discord Name
Johncook
Mod name
Stress and Taxes
Mod GUID
Johncook.StressandTaxes
GitHub repository URL
https://github.com/Johncook2/Stress-and-Taxes
Download file name
Source code
Author (optional)
No response
Description (optional)
I started working on this mod before the Pale Reach, then sort of left it alone. I'm hoping if I publish it then I'll work on this more, and potentially get help easier as my code will be visible.

the repo is private :(
you need to make it public

Ah, sorry. Forgot that.

Okay the repo is public and I’m working on doing the step that I missed on the ReadMe. For some reason the build action isn’t working so I’m trying to do that manually.

W

What does it mean by "build your mod using an IDE"?

If you have used your mod ever in game, that means you built. The github action is still preferred though, you probably want to just copy paste https://github.com/DREDGE-Mods/WinchModTemplate/blob/main/.github/workflows/release.yml to your project (I see you modified the file so best to start fresh) and replace "YourName" and "WinchModTemplate" with your "Johncook" and "StressandTaxes".


Fix: Remove duplicate notices

This pull request

[x] removes duplicate notices

Somewhat related to #5.
💁♂ Once should be enough.

Thank you, @drupol!


JSON support may conflict with other libraries

In providing somewhat seamless JSON integration, we're over-riding the built-in encode/decode methods of the library. However, if any other libraries attempt to do the same thing, one of the two will break as a result.
Rather than globally altering the json module, we should use a context manager to wrap calls to json and only achieve the desired functionality when it's needed.

I merged this into the pandas branch, and everything seems to work.  Okay to close this one?

yurp
On Tue, Feb 3, 2015 at 10:47 AM, Brian McFee<EMAIL_ADDRESS>wrote:

I merged this into the pandas branch, and everything seems to work. Okay
to close this one?
—
Reply to this email directly or view it on GitHub
https://github.com/marl/jams/issues/12#issuecomment-72673575.


Comments in threads should be in chronological order

It looks like comments from before the switch are in reverse chronological order, but comments from after the switch are in chronological order.
Compare here:

And here:

At least some new comments are in reverse chronological order too.

@SylvainChevalier I've reviewed links provided in the ticket, as well as several other questions/notebooks. It seems that the issue has already been resolved, or there may have been some misunderstanding based on the initial comment. Currently, when we copy the link to a specific comment, it moves that comment to the top of the comment section to ensure easy navigation. So this order mismatch is expected.

discussed in sync:

top level comments should be sorted according to the drop down menu
replies in a given thread should always be sorted from oldest to newest.

Ready for testing on dev

lgtm.


Unable to call Get-ADGroup

I get this message when I attempt to run any action in the ActiveDirectory app:
The 'Get-ADObject' command was found in the module 'ActiveDirectory', but the module could not be loaded due to the following error: [Could not load type 'System.Management.Automation.PSSnapIn' from assembly 'System.Management.Automation, Version=<IP_ADDRESS>0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.]
For more information, run 'Import-Module ActiveDirectory'.
The ActiveDirectory module is installed, but when I run Import-Module ActiveDirectory, I get this:
[ERROR] Could not load type 'System.Management.Automation.PSSnapIn' from assembly 'System.Management.Automation, Version=<IP_ADDRESS>0, Culture=neutral, PublicKeyToken=31bf3856ad364e35'.

I haven't found any documentation or forum posts that might explain what is going on.
I am running PSU version 4.3.4 on Windows 11.

Not sure what exactly changed but this seems to be working now despite hours of testing and research over the last three days.


Add controller tools back

Description of the problem which is fixed/What is the use case
Downstream Red Hat builds require controller-tools to be in the go.mod so they can be cached due to network limitations. They can easily be removed accidentally with go mod tidy because they are not actually dependencies.

Description for the changelog

I did a go mod download and then ran
go run sigs.k8s.io/controller-tools/cmd/controller-gen object:headerFile="hack/boilerplate.go.txt" paths="./..."
and got
../../../../go/pkg/mod/sigs.k8s.io/controller-tools@v0.9.2/cmd/controller-gen/main.go:25:2: missing go.sum entry for module providing package github.com/spf13/cobra (imported by sigs.k8s.io/controller-tools/cmd/controller-gen); to add:
go get<EMAIL_ADDRESS>This is from a brand new clone of sandboxed-container-operator with the PR branch checked out.  Either something changed or I missed a go get command the last time.  Not sure why we didn't see this previously.  Maybe everyone had a dirty test env.

I don't see that problem, even with a fresh checkout

Added a reference issue to fix it in code - https://github.com/openshift/sandboxed-containers-operator/issues/294

I did a go mod download and then ran
go run sigs.k8s.io/controller-tools/cmd/controller-gen object:headerFile="hack/boilerplate.go.txt" paths="./..."
and got
../../../../go/pkg/mod/sigs.k8s.io/controller-tools@v0.9.2/cmd/controller-gen/main.go:25:2: missing go.sum entry for module providing package github.com/spf13/cobra (imported by sigs.k8s.io/controller-tools/cmd/controller-gen); to add: go get<EMAIL_ADDRESS>
I hit exactly the same error and if I do go get<EMAIL_ADDRESS>as suggested in the error then test succeeds. This go get command simply adds github.com/inconshreveable/mousetrap and github.com/spf13/cobra as indirect dependencies. @jensfr do you see them in your go.mod ?

This is from a brand new clone of sandboxed-container-operator with the PR branch checked out. Either something changed or I missed a go get command the last time. Not sure why we didn't see this previously. Maybe everyone had a dirty test env.

Travelling back today and probably won't get to this. Feel free to send another PR to fix this

Since your PR has Maintainers are allowed to edit this pull request., I could simply force-push to your branch :wink:

Nice, thank you @gkurz


Rename VanillaModelCreator -> ModelCreator

Codecov Report
Patch coverage is 100.00% of modified lines.

Files Changed
Coverage

src/gravitorch/creators/core/advanced.py
ø

src/gravitorch/creators/model/base.py
ø

src/gravitorch/creators/model/compiled.py
ø

src/gravitorch/creators/model/ddp.py
ø

src/gravitorch/creators/model/__init__.py
100.00%

src/gravitorch/creators/model/vanilla.py
100.00%

:loudspeaker: Thoughts on this report? Let us know!.


oembed HTML code should point to code iframe rather simulator

The oembed API is currently displaying the simulator and should be displaying the code instead.

Do we have an URL that displays the code? Right now we send them to --run.

@pelikhan I need a function that given blocksWidth and blocksHeight provided when publishing script, and also maxwidth/maxheight from the oembed call (if given by the user)  gives me HTML that starts with  ?
If you really want to embed it in foreign websites it shouldn't have

See in docsrender
    export function embedUrl(rootUrl: string, id: string, height?: number): string {

This is fixed.


Estimate Saved state size, for 24h at 15min intervals + 1 per day forever

Gather state size data

Gather saved state from a performance test run as close to 10K TPS as practical with a long-ish duration (to generate more entries).
Gather a saved state from mainnet at relatively high (3K-4K) TPS.
Gather a saved state from testnet at low TPS.
Compare the three and determine a "probable" state size and growth rate.
Calculate a few projections for different growth scenarios
Use these to produce low, probable, and high state snapshot size estimates

Calculate disk requirements

Use existing state snapshots to determine a compression ratio using LZMA, zstd, etc...
Document the archive rates (96 "recent", ZZ "daily", YY "weekly?", etc...)
Calculate the required storage for 1, 3, 5, 10 years.

Compression testing results:
ZStd benchmark for compression levels
4# 13 files         : 298183903 ->  70826734 (x4.210), 542.8 MB/s 2475.6 MB/s
5# 13 files         : 298183903 ->  69235349 (x4.307), 296.3 MB/s, 2480.4 MB/s
6# 13 files         : 298183903 ->  67612896 (x4.410), 217.4 MB/s, 2658.5 MB/s
7# 13 files         : 298183903 ->  67337244 (x4.428), 196.5 MB/s, 2696.2 MB/s
8# 13 files         : 298183903 ->  65749797 (x4.535), 162.7 MB/s, 2776.6 MB/s
9# 13 files         : 298183903 ->  62268539 (x4.789), 168.7 MB/s, 2961.4 MB/s
10# 13 files         : 298183903 ->  61976523 (x4.811), 126.5 MB/s, 3006.4 MB/s
11# 13 files         : 298183903 ->  61789285 (x4.826), 86.7 MB/s, 3036.0 MB/s
12# 13 files         : 298183903 ->  61772013 (x4.827), 82.2 MB/s, 3033.3 MB/s
13# 13 files         : 298183903 ->  61679772 (x4.834), 32.2 MB/s, 3020.2 MB/s
14# 13 files         : 298183903 ->  61433825 (x4.854), 23.2 MB/s, 3115.7 MB/s
15# 13 files         : 298183903 ->  61098590 (x4.880), 14.5 MB/s, 3158.4 MB/s
16# 13 files         : 298183903 ->  59947931 (x4.974), 15.6 MB/s, 3021.8 MB/s
17# 13 files         : 298183903 ->  56118447 (x5.313), 11.3 MB/s, 3152.7 MB/s
18# 13 files         : 298183903 ->  55563187 (x5.367), 9.79 MB/s, 3134.4 MB/s
19# 13 files         : 298183903 ->  55253199 (x5.397), 7.63 MB/s, 3160.0 MB/s

Compression above level 9 considered too slow, so other benchmarks limited to
levels 4-9.
May Snapshot
Total size: 9.3G
tar/zst compressed: 4.1G (compression level 9)
ZStd benchmark for tables (both hl and ll files)
4# 39 files         :1972259721 ->1488283970 (x1.325), 2075.1 MB/s, 5597.0 MB/s
5# 39 files         :1972259721 ->1488360699 (x1.325), 1226.1 MB/s, 5598.3 MB/s
6# 39 files         :1972259721 ->1483707567 (x1.329), 809.1 MB/s, 5617.7 MB/s
7# 39 files         :1972259721 ->1483756971 (x1.329), 750.0 MB/s, 5636.6 MB/s
8# 39 files         :1972259721 ->1483665454 (x1.329), 493.9 MB/s, 5610.0 MB/s
9# 39 files         :1972259721 ->1483671662 (x1.329), 491.2 MB/s, 5636.8 MB/s

ZStd benchmark for tables (only ll files)
4# 26 files         : 559434440 ->  75426276 (x7.417), 746.8 MB/s, 1791.8 MB/s
5# 26 files         : 559434440 ->  75503005 (x7.409), 423.9 MB/s, 1794.5 MB/s
6# 26 files         : 559434440 ->  70849873 (x7.896), 261.4 MB/s, 1797.9 MB/s
7# 26 files         : 559434440 ->  70899277 (x7.891), 240.1 MB/s, 1797.3 MB/s
8# 26 files         : 559434440 ->  70807760 (x7.901), 151.7 MB/s, 1797.7 MB/s
9# 26 files         : 559434440 ->  70813969 (x7.900), 151.7 MB/s, 1796.9 MB/s

ZStd benchmark for tables (only pbj files)

Note, this benchmark only tested 2.7G of data (zstd internal limit)

4# 100 files        :2840941909 ->1355408247 (x2.096),  333.3 MB/s, 1681.5 MB/s
5# 100 files        :2840941909 ->1343799144 (x2.114),  175.3 MB/s, 1681.2 MB/s
6# 100 files        :2840941909 ->1326291002 (x2.142),  134.4 MB/s, 1763.7 MB/s
7# 100 files        :2840941909 ->1319775161 (x2.153),  120.8 MB/s, 1729.6 MB/s
8# 100 files        :2840941909 ->1308518250 (x2.171),  101.3 MB/s, 1816.6 MB/s
9# 100 files        :2840941909 ->1299209185 (x2.187),   95.7 MB/s, 1787.5 MB/s

November Snapshot
Total size: 11G
tar/zst compressed: 4.7G (compression level 9)
ZStd benchmark for tables (only ll files) and vmap files
4# 39 files         : 989278117 -> 161344374 (x6.131), 690.2 MB/s 2047.9 MB/s
5# 39 files         : 989278117 -> 159889555 (x6.187), 379.1 MB/s, 2061.7 MB/s
6# 39 files         : 989278117 -> 149430622 (x6.620), 254.6 MB/s, 2102.4 MB/s
7# 39 files         : 989278117 -> 149129946 (x6.634), 232.3 MB/s, 2110.1 MB/s
8# 39 files         : 989278117 -> 147721317 (x6.697), 162.3 MB/s, 2127.3 MB/s
9# 39 files         : 989278117 -> 144549834 (x6.844), 163.3 MB/s, 2143.4 MB/s

ZStd benchmark for tables (only ll files)
4# 26 files         : 604662632 ->  93266125 (x6.483), 680.0 MB/s, 1656.4 MB/s
5# 26 files         : 604662632 ->  92950080 (x6.505), 383.9 MB/s, 1666.6 MB/s
6# 26 files         : 604662632 ->  83992084 (x7.199), 241.5 MB/s, 1674.7 MB/s
7# 26 files         : 604662632 ->  84044019 (x7.195), 220.1 MB/s, 1672.7 MB/s
8# 26 files         : 604662632 ->  83827512 (x7.213), 140.9 MB/s, 1677.0 MB/s
9# 26 files         : 604662632 ->  83851716 (x7.211), 140.5 MB/s, 1675.7 MB/s

ZStd benchmark for tables (only pbj files)

Note, this benchmark only tested 2.7G of data (zstd internal limit)

4# 100 files        :2840941909 ->1222961278 (x2.323), 395.2 MB/s, 2280.2 MB/s
5# 100 files        :2840941909 ->1211503815 (x2.345), 200.7 MB/s, 2271.6 MB/s
6# 100 files        :2840941909 ->1201448093 (x2.365), 160.9 MB/s, 2385.5 MB/s
7# 100 files        :2840941909 ->1195528015 (x2.376), 147.6 MB/s, 2354.2 MB/s
8# 100 files        :2840941909 ->1186107445 (x2.395), 127.9 MB/s, 2466.4 MB/s
9# 100 files        :2840941909 ->1177536359 (x2.413), 118.4 MB/s, 2454.2 MB/s

Additional benchmarks
ZStd benchmark for blended data (vmap, ll, pbj)

Note, we manually selected a smaller sample to ensure all file types were included.

4# 28 files         :1534183736 -> 313989996 (x4.886),  486.1 MB/s, 1313.2 MB/s
5# 28 files         :1534183736 -> 315557357 (x4.862),  261.5 MB/s, 1221.4 MB/s
6# 28 files         :1534183736 -> 291965050 (x5.255),  171.4 MB/s, 1353.5 MB/s
7# 28 files         :1534183736 -> 287474051 (x5.337),  148.2 MB/s, 1431.1 MB/s
8# 28 files         :1534183736 -> 286754682 (x5.350),  111.4 MB/s, 1448.7 MB/s
9# 28 files         :1534183736 -> 282563859 (x5.430),  110.2 MB/s, 1461.7 MB/s

ZStd benchmark for tar files of full tables
Contract storage
4#scstorage.tar     :1213048320 -> 521899493 (x2.324),  565.3 MB/s, 3102.8 MB/s
5#scstorage.tar     :1213048320 -> 521439743 (x2.326),  253.7 MB/s, 3183.2 MB/s
6#scstorage.tar     :1213048320 -> 516749587 (x2.347),  205.9 MB/s, 3469.2 MB/s
7#scstorage.tar     :1213048320 -> 514237631 (x2.359),  187.0 MB/s, 3484.8 MB/s
8#scstorage.tar     :1213048320 -> 512513865 (x2.367),  165.4 MB/s, 3561.2 MB/s
9#scstorage.tar     :1213048320 -> 507221650 (x2.392),  159.5 MB/s, 3532.7 MB/s

Accounts
4#accts.tar         :2013496832 ->1083050108 (x1.859),  476.4 MB/s, 2266.1 MB/s
5#accts.tar         :2013496832 ->1072218386 (x1.878),  228.0 MB/s, 2260.9 MB/s
6#accts.tar         :2013496832 ->1067406534 (x1.886),  178.3 MB/s, 2358.6 MB/s
7#accts.tar         :2013496832 ->1063012383 (x1.894),  161.4 MB/s, 2351.7 MB/s
8#accts.tar         :2013496832 ->1058975442 (x1.901),  134.1 MB/s, 2443.6 MB/s
9#accts.tar         :2013496832 ->1054632014 (x1.909),  128.0 MB/s, 2421.7 MB/s

Rough data volume calculation

All data is assuming tar/zstd at compression level 9.  We might choose to compress individual files, remove some unnecessary indexes, and modify the load process to suit.  At best this might reduce volume 10%, based on relative volume of indexes to actual data in current snapshots, and relative compressibility.
4.7G * 48 = 226G for current day
4.7G * 365 = 1716 for 1 year
compressed CAGR is roughly 11%
Growth Scenarios

In a steady growth scenario, the following totals are likely.
5 years of storage for state snapshots is 12T
10 years of storage for state snapshots is 34T
This represents a predicted lower boundary
For a highly aggressive growth (50% CAGR) scenario, the following totals are likely
5 years of storage for state snapshots is 26T
10 years of storage for state snapshots 350T
Clearly, a 50% annual growth in state size is somewhat extreme, but it demonstrates a useful upper boundary.
Recommended Capacity

A middle road between the two extremes is recommended to ensure there is room for some growth, and time between a significant increase in snapshot size and capacity exhaustion.
For a 5-year expected lifespan, 32T is recommended as a highly reasonable capacity (roughly 2-3 drives) with current technology.  In a lower growth scenario, this might last 10 years.
For a 10-year expected lifespan, 128T is recommended as a reasonable capacity (roughly 8-10 drives) with current technology.  This provides adequate protection against unexpectedly high growth, while avoiding excessive cost for relatively underutilized hardware.
The most cost efficient approach, certainly is the 5-year lifespan scenario, and it may be appropriate to plan on full system replacements near that time horizon.


[image_picker] App restarts every time when picking Image/Video on Android

Hello,
I have implemented image_picker plugin, but everytime i pick an image, it restart the application without log or error.
However :

when i run it on emulator, it works fine. But as soon as I try it (in debug mode or not) on my smartphone, it restart the app.

When i run it on my smartphone, using the debugger and going step by step, it works fine.

My phone : Galaxy S7
Android 8.0.0
My emulator : Nexus 5
Android 7.1.1
Below is my code
main.dart
import 'package:flutter/material.dart';
import 'addImage.dart';

void main() {
  runApp(MyApp());
}

class MyApp extends StatelessWidget {
  // This widget is the root of your application.
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        primarySwatch: Colors.blue,
        visualDensity: VisualDensity.adaptivePlatformDensity,
      ),
      home: MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  MyHomePage({Key key, this.title}) : super(key: key);

  final String title;

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

class _MyHomePageState extends State<MyHomePage> {

  @override
  Widget build(BuildContext context) {

    return Scaffold(
      appBar: AppBar(
        title: Text("add image"),
      ),
      body: Center(
        child: Column(
          children: <Widget>[
            RaisedButton(
              onPressed: () async {
                Navigator.pushReplacement(context,MaterialPageRoute(builder: (context) => AddImage()));
              },
              child: Text("Go to add image"),
              color: Colors.red,
            )
          ],
        ),
      ),
    );
  }
}

addImage.dart
import 'dart:io';

import 'package:flutter/material.dart';
import 'package:image_picker/image_picker.dart';

class AddImage extends StatefulWidget {
  @override
  _AddImageState createState() => _AddImageState();
}

class _AddImageState extends State<AddImage> {

  @override
  void initState() {
    super.initState();
  }

  @override
  void dispose() {
    super.dispose();
  }

  @override
  Widget build(BuildContext context) {
    File imageFile;
    final picker = ImagePicker();

    Widget _buildPictureDisplayer(){
      if(imageFile == null){
        return Text('no selected image');
      }else{
        return Column(
          children: <Widget>[
            Image.file(imageFile),
          ],
        );
      }

    }

    void _getImageFromGallery() async {

      try {

        PickedFile pickedFile = await picker.getImage(source: ImageSource.gallery);

        this.setState(() {
          imageFile = File(pickedFile.path);
        });

      } catch (e) {

        print(e);
      }

    }

    return Scaffold(
      appBar: AppBar(
        title: Text("add image"),
      ),
      body: Center(
        child: Column(
          mainAxisAlignment: MainAxisAlignment.center,
          children: <Widget>[
            IconButton(icon: Icon(Icons.add_a_photo), onPressed: _getImageFromGallery),
            _buildPictureDisplayer(),
          ],
        ),
      ),// This trailing comma makes auto-formatting nicer for build methods.
    );
  }
}

Steps to Reproduce

implement image_picker
get image from gallery

Run flutter create bug.
Update the files as follows: ...
...

Expected results:
Actual results:

Logs

flutter run --verbose result :
[  +15 ms] executing: [C:\flutter/] git -c log.showSignature=false log -n 1 --pretty=format:%H
[  +54 ms] Exit code 0 from: git -c log.showSignature=false log -n 1 --pretty=format:%H
[   +1 ms] b041144f833e05cf463b8887fa12efdec9493488
[        ] executing: [C:\flutter/] git tag --contains HEAD
[ +163 ms] Exit code 0 from: git tag --contains HEAD
[   +1 ms] 1.17.3
[  +13 ms] executing: [C:\flutter/] git rev-parse --abbrev-ref --symbolic @{u}
[  +27 ms] Exit code 0 from: git rev-parse --abbrev-ref --symbolic @{u}
[        ] origin/stable
[        ] executing: [C:\flutter/] git ls-remote --get-url origin
[  +24 ms] Exit code 0 from: git ls-remote --get-url origin
[        ] https://github.com/flutter/flutter.git
[  +75 ms] executing: [C:\flutter/] git rev-parse --abbrev-ref HEAD
[  +26 ms] Exit code 0 from: git rev-parse --abbrev-ref HEAD
[        ] stable
[  +31 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.
[   +4 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.
[  +18 ms] executing: C:\Android\Sdk\platform-tools\adb.exe devices -l
[  +52 ms] List of devices attached
           9a43a7f7               device product:heroqlteue model:SM_G930F device:heroqlteue transport_id:15
[   +5 ms] C:\Android\Sdk\platform-tools\adb.exe -s 9a43a7f7 shell getprop
[  +79 ms] Artifact Instance of 'AndroidMavenArtifacts' is not required, skipping update.
[   +5 ms] Artifact Instance of 'AndroidInternalBuildArtifacts' is not required, skipping update.
[  +11 ms] Artifact Instance of 'IOSEngineArtifacts' is not required, skipping update.
[   +2 ms] Artifact Instance of 'FlutterWebSdk' is not required, skipping update.
[   +4 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.
[  +96 ms] Found plugin flutter_plugin_android_lifecycle at C:\flutter\.pub-cache\hosted\pub.dartlang.org\flutter_plugin_android_lifecycle-1.0.8\
[  +10 ms] Found plugin image_picker at C:\flutter\.pub-cache\hosted\pub.dartlang.org\image_picker-0.6.7+1\
[  +76 ms] Found plugin flutter_plugin_android_lifecycle at C:\flutter\.pub-cache\hosted\pub.dartlang.org\flutter_plugin_android_lifecycle-1.0.8\
[   +5 ms] Found plugin image_picker at C:\flutter\.pub-cache\hosted\pub.dartlang.org\image_picker-0.6.7+1\
[  +64 ms] Generating C:\Users\maclovin\Documents\projets\test_image_gallery\android\app\src\main\java\io\flutter\plugins\GeneratedPluginRegistrant.java
[  +30 ms] ro.hardware = qcom
[  +52 ms] Launching lib\main.dart on SM G930F in debug mode...
[   +9 ms] C:\flutter\bin\cache\dart-sdk\bin\dart.exe C:\flutter\bin\cache\artifacts\engine\windows-x64\frontend_server.dart.snapshot --sdk-root C:\flutter\bin\cache\artifacts\engine\common\flutter_patched_sdk/
--incremental --target=flutter --debugger-module-names -Ddart.developer.causal_async_stacks=true --output-dill C:\Users\maclovin\AppData\Local\Temp\flutter_tool.d059d6c4-ad65-11ea-9f95-80325384f728\app.dill --packages
C:\Users\maclovin\Documents\projets\test_image_gallery\.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-scheme
org-dartlang-root
[  +55 ms] executing: C:\Android\Sdk\build-tools\29.0.3\aapt dump xmltree C:\Users\maclovin\Documents\projets\test_image_gallery\build\app\outputs\apk\app.apk AndroidManifest.xml
[  +40 ms] Exit code 0 from: C:\Android\Sdk\build-tools\29.0.3\aapt dump xmltree C:\Users\maclovin\Documents\projets\test_image_gallery\build\app\outputs\apk\app.apk AndroidManifest.xml
[  +11 ms] N: android=http://schemas.android.com/apk/res/android
             E: manifest (line=2)
               A: android:versionCode(0x0101021b)=(type 0x10)0x1
               A: android:versionName(0x0101021c)="1.0.0" (Raw: "1.0.0")
               A: android:compileSdkVersion(0x01010572)=(type 0x10)0x1c
               A: android:compileSdkVersionCodename(0x01010573)="9" (Raw: "9")
               A: package="com.example.test_image_gallery" (Raw: "com.example.test_image_gallery")
               A: platformBuildVersionCode=(type 0x10)0x1c
               A: platformBuildVersionName=(type 0x10)0x9
               E: uses-sdk (line=7)
                 A: android:minSdkVersion(0x0101020c)=(type 0x10)0x10
                 A: android:targetSdkVersion(0x01010270)=(type 0x10)0x1c
               E: uses-permission (line=14)
                 A: android:name(0x01010003)="android.permission.INTERNET" (Raw: "android.permission.INTERNET")
               E: uses-permission (line=15)
                 A: android:name(0x01010003)="android.permission.READ_EXTERNAL_STORAGE" (Raw: "android.permission.READ_EXTERNAL_STORAGE")
               E: uses-permission (line=16)
                 A: android:name(0x01010003)="android.permission.WRITE_EXTERNAL_STORAGE" (Raw: "android.permission.WRITE_EXTERNAL_STORAGE")
               E: application (line=24)
                 A: android:label(0x01010001)="test_image_gallery" (Raw: "test_image_gallery")
                 A: android:icon(0x01010002)=@0x7f080000
                 A: android:name(0x01010003)="io.flutter.app.FlutterApplication" (Raw: "io.flutter.app.FlutterApplication")
                 A: android:debuggable(0x0101000f)=(type 0x12)0xffffffff
                 A: android:appComponentFactory(0x0101057a)="androidx.core.app.CoreComponentFactory" (Raw: "androidx.core.app.CoreComponentFactory")
                 E: activity (line=30)
                   A: android:theme(0x01010000)=@0x7f0a0000
                   A: android:name(0x01010003)="com.example.test_image_gallery.MainActivity" (Raw: "com.example.test_image_gallery.MainActivity")
                   A: android:launchMode(0x0101001d)=(type 0x10)0x1
                   A: android:configChanges(0x0101001f)=(type 0x11)0x40003fb4
                   A: android:windowSoftInputMode(0x0101022b)=(type 0x11)0x10
                   A: android:hardwareAccelerated(0x010102d3)=(type 0x12)0xffffffff
                   E: meta-data (line=44)
                     A: android:name(0x01010003)="io.flutter.embedding.android.NormalTheme" (Raw: "io.flutter.embedding.android.NormalTheme")
                     A: android:resource(0x01010025)=@0x7f0a0001
                   E: meta-data (line=54)
                     A: android:name(0x01010003)="io.flutter.embedding.android.SplashScreenDrawable" (Raw: "io.flutter.embedding.android.SplashScreenDrawable")
                     A: android:resource(0x01010025)=@0x7f040000
                   E: intent-filter (line=58)
                     E: action (line=59)
                       A: android:name(0x01010003)="android.intent.action.MAIN" (Raw: "android.intent.action.MAIN")
                     E: category (line=61)
                       A: android:name(0x01010003)="android.intent.category.LAUNCHER" (Raw: "android.intent.category.LAUNCHER")
                 E: meta-data (line=68)
                   A: android:name(0x01010003)="flutterEmbedding" (Raw: "flutterEmbedding")
                   A: android:value(0x01010024)=(type 0x10)0x2
                 E: provider (line=72)
                   A: android:name(0x01010003)="io.flutter.plugins.imagepicker.ImagePickerFileProvider" (Raw: "io.flutter.plugins.imagepicker.ImagePickerFileProvider")
                   A: android:exported(0x01010010)=(type 0x12)0x0
                   A: android:authorities(0x01010018)="com.example.test_image_gallery.flutter.image_provider" (Raw: "com.example.test_image_gallery.flutter.image_provider")
                   A: android:grantUriPermissions(0x0101001b)=(type 0x12)0xffffffff
                   E: meta-data (line=77)
                     A: android:name(0x01010003)="android.support.FILE_PROVIDER_PATHS" (Raw: "android.support.FILE_PROVIDER_PATHS")
                     A: android:resource(0x01010025)=@0x7f0c0000
[ +121 ms] executing: C:\Android\Sdk\platform-tools\adb.exe -s 9a43a7f7 shell -x logcat -v time -t 1
[ +249 ms] Exit code 0 from: C:\Android\Sdk\platform-tools\adb.exe -s 9a43a7f7 shell -x logcat -v time -t 1
[   +3 ms] --------- beginning of main
           06-13 13:05:45.782 E/propClient( 6168): PropClient failed to load
[  +61 ms] <- compile package:test_image_gallery/main.dart
[  +20 ms] executing: C:\Android\Sdk\platform-tools\adb.exe version
[  +66 ms] Android Debug Bridge version 1.0.41
           Version 30.0.1-6435776
           Installed as C:\Android\Sdk\platform-tools\adb.exe
[   +3 ms] executing: C:\Android\Sdk\platform-tools\adb.exe start-server
[  +21 ms] Building APK
[  +36 ms] Running Gradle task 'assembleDebug'...
[   +3 ms] gradle.properties already sets `android.enableR8`
[  +23 ms] Using gradle from C:\Users\maclovin\Documents\projets\test_image_gallery\android\gradlew.bat.
[  +28 ms] C:\Users\maclovin\Documents\projets\test_image_gallery\android\gradlew.bat mode: 33279 rwxrwxrwx.
[  +32 ms] executing: C:\Program Files\Android\Android Studio\jre\bin\java -version
[  +92 ms] Exit code 0 from: C:\Program Files\Android\Android Studio\jre\bin\java -version
[        ] openjdk version "1.8.0_242-release"
           OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
           OpenJDK 64-Bit Server VM (build 25.242-b01, mixed mode)
[   +3 ms] executing: [C:\Users\maclovin\Documents\projets\test_image_gallery\android/] C:\Users\maclovin\Documents\projets\test_image_gallery\android\gradlew.bat -Pverbose=true -Ptarget-platform=android-arm64
-Ptarget=C:\Users\maclovin\Documents\projets\test_image_gallery\lib\main.dart -Ptrack-widget-creation=true -Pfilesystem-scheme=org-dartlang-root assembleDebug
[+1263 ms] > Task :app:compileFlutterBuildDebug UP-TO-DATE
[   +2 ms] > Task :app:packLibsflutterBuildDebug UP-TO-DATE
[   +1 ms] > Task :app:preBuild UP-TO-DATE
[  +24 ms] > Task :app:preDebugBuild UP-TO-DATE
[  +36 ms] > Task :flutter_plugin_android_lifecycle:preBuild UP-TO-DATE
[   +2 ms] > Task :flutter_plugin_android_lifecycle:preDebugBuild UP-TO-DATE
[  +35 ms] > Task :image_picker:preBuild UP-TO-DATE
[   +3 ms] > Task :image_picker:preDebugBuild UP-TO-DATE
[        ] > Task :flutter_plugin_android_lifecycle:packageDebugRenderscript NO-SOURCE
[        ] > Task :image_picker:packageDebugRenderscript NO-SOURCE
[        ] > Task :app:checkDebugManifest UP-TO-DATE
[        ] > Task :flutter_plugin_android_lifecycle:compileDebugAidl NO-SOURCE
[        ] > Task :image_picker:compileDebugAidl NO-SOURCE
[  +21 ms] > Task :app:compileDebugAidl NO-SOURCE
[        ] > Task :app:compileDebugRenderscript NO-SOURCE
[        ] > Task :app:generateDebugBuildConfig UP-TO-DATE
[   +1 ms] > Task :app:cleanMergeDebugAssets
[   +2 ms] > Task :app:mergeDebugShaders UP-TO-DATE
[  +19 ms] > Task :app:compileDebugShaders UP-TO-DATE
[   +1 ms] > Task :app:generateDebugAssets UP-TO-DATE
[        ] > Task :flutter_plugin_android_lifecycle:mergeDebugShaders UP-TO-DATE
[   +1 ms] > Task :flutter_plugin_android_lifecycle:compileDebugShaders UP-TO-DATE
[  +23 ms] > Task :flutter_plugin_android_lifecycle:generateDebugAssets UP-TO-DATE
[        ] > Task :flutter_plugin_android_lifecycle:packageDebugAssets UP-TO-DATE
[        ] > Task :image_picker:mergeDebugShaders UP-TO-DATE
[        ] > Task :image_picker:compileDebugShaders UP-TO-DATE
[  +21 ms] > Task :image_picker:generateDebugAssets UP-TO-DATE
[        ] > Task :image_picker:packageDebugAssets UP-TO-DATE
[        ] > Task :app:mergeDebugAssets
[ +180 ms] > Task :app:copyFlutterAssetsDebug
[   +1 ms] > Task :app:mainApkListPersistenceDebug UP-TO-DATE
[   +1 ms] > Task :app:generateDebugResValues UP-TO-DATE
[  +16 ms] > Task :app:generateDebugResources UP-TO-DATE
[   +1 ms] > Task :flutter_plugin_android_lifecycle:generateDebugResValues UP-TO-DATE
[        ] > Task :flutter_plugin_android_lifecycle:compileDebugRenderscript NO-SOURCE
[  +24 ms] > Task :flutter_plugin_android_lifecycle:generateDebugResources UP-TO-DATE
[   +1 ms] > Task :flutter_plugin_android_lifecycle:packageDebugResources UP-TO-DATE
[  +23 ms] > Task :image_picker:generateDebugResValues UP-TO-DATE
[   +1 ms] > Task :image_picker:compileDebugRenderscript NO-SOURCE
[  +27 ms] > Task :image_picker:generateDebugResources UP-TO-DATE
[  +26 ms] > Task :image_picker:packageDebugResources UP-TO-DATE
[        ] > Task :app:mergeDebugResources UP-TO-DATE
[        ] > Task :app:createDebugCompatibleScreenManifests UP-TO-DATE
[        ] > Task :flutter_plugin_android_lifecycle:checkDebugManifest UP-TO-DATE
[        ] > Task :flutter_plugin_android_lifecycle:processDebugManifest UP-TO-DATE
[        ] > Task :image_picker:checkDebugManifest UP-TO-DATE
[        ] > Task :image_picker:processDebugManifest UP-TO-DATE
[        ] > Task :app:processDebugManifest UP-TO-DATE
[   +2 ms] > Task :flutter_plugin_android_lifecycle:parseDebugLibraryResources UP-TO-DATE
[  +35 ms] > Task :flutter_plugin_android_lifecycle:generateDebugRFile UP-TO-DATE
[   +4 ms] > Task :image_picker:parseDebugLibraryResources UP-TO-DATE
[   +2 ms] > Task :image_picker:generateDebugRFile UP-TO-DATE
[  +44 ms] > Task :app:processDebugResources UP-TO-DATE
[        ] > Task :flutter_plugin_android_lifecycle:generateDebugBuildConfig UP-TO-DATE
[        ] > Task :flutter_plugin_android_lifecycle:javaPreCompileDebug UP-TO-DATE
[        ] > Task :flutter_plugin_android_lifecycle:compileDebugJavaWithJavac UP-TO-DATE
[        ] > Task :flutter_plugin_android_lifecycle:bundleLibCompileDebug UP-TO-DATE
[        ] > Task :image_picker:generateDebugBuildConfig UP-TO-DATE
[        ] > Task :image_picker:javaPreCompileDebug UP-TO-DATE
[   +2 ms] > Task :image_picker:compileDebugJavaWithJavac UP-TO-DATE
[  +36 ms] > Task :image_picker:bundleLibCompileDebug UP-TO-DATE
[        ] > Task :app:compileDebugKotlin UP-TO-DATE
[        ] > Task :app:javaPreCompileDebug UP-TO-DATE
[        ] > Task :app:compileDebugJavaWithJavac UP-TO-DATE
[        ] > Task :app:compileDebugSources UP-TO-DATE
[        ] > Task :app:processDebugJavaRes NO-SOURCE
[   +2 ms] > Task :flutter_plugin_android_lifecycle:processDebugJavaRes NO-SOURCE
[  +16 ms] > Task :flutter_plugin_android_lifecycle:bundleLibResDebug UP-TO-DATE
[        ] > Task :image_picker:processDebugJavaRes NO-SOURCE
[        ] > Task :image_picker:bundleLibResDebug UP-TO-DATE
[        ] > Task :app:mergeDebugJavaResource UP-TO-DATE
[        ] > Task :flutter_plugin_android_lifecycle:bundleLibRuntimeDebug UP-TO-DATE
[        ] > Task :flutter_plugin_android_lifecycle:createFullJarDebug UP-TO-DATE
[        ] > Task :image_picker:bundleLibRuntimeDebug UP-TO-DATE
[        ] > Task :image_picker:createFullJarDebug UP-TO-DATE
[        ] > Task :app:desugarDebugFileDependencies UP-TO-DATE
[        ] > Task :app:checkDebugDuplicateClasses UP-TO-DATE
[   +1 ms] > Task :app:mergeExtDexDebug UP-TO-DATE
[  +35 ms] > Task :app:transformClassesWithDexBuilderForDebug UP-TO-DATE
[  +23 ms] > Task :app:mergeDexDebug UP-TO-DATE
[        ] > Task :app:validateSigningDebug UP-TO-DATE
[  +14 ms] > Task :app:signingConfigWriterDebug UP-TO-DATE
[  +24 ms] > Task :app:mergeDebugJniLibFolders UP-TO-DATE
[   +1 ms] > Task :flutter_plugin_android_lifecycle:mergeDebugJniLibFolders UP-TO-DATE
[  +22 ms] > Task :flutter_plugin_android_lifecycle:mergeDebugNativeLibs UP-TO-DATE
[   +1 ms] > Task :flutter_plugin_android_lifecycle:stripDebugDebugSymbols UP-TO-DATE
[   +2 ms] > Task :flutter_plugin_android_lifecycle:transformNativeLibsWithIntermediateJniLibsForDebug UP-TO-DATE
[  +31 ms] > Task :image_picker:mergeDebugJniLibFolders UP-TO-DATE
[   +2 ms] > Task :image_picker:mergeDebugNativeLibs UP-TO-DATE
[  +22 ms] > Task :image_picker:stripDebugDebugSymbols UP-TO-DATE
[        ] > Task :image_picker:transformNativeLibsWithIntermediateJniLibsForDebug UP-TO-DATE
[  +27 ms] > Task :app:mergeDebugNativeLibs UP-TO-DATE
[  +19 ms] > Task :app:stripDebugDebugSymbols UP-TO-DATE
[   +1 ms] Compatible side by side NDK version was not found.
[   +1 ms] > Task :app:packageDebug UP-TO-DATE
[  +20 ms] > Task :app:assembleDebug
[        ] > Task :flutter_plugin_android_lifecycle:extractDebugAnnotations UP-TO-DATE
[        ] > Task :flutter_plugin_android_lifecycle:mergeDebugGeneratedProguardFiles UP-TO-DATE
[        ] > Task :flutter_plugin_android_lifecycle:mergeDebugConsumerProguardFiles UP-TO-DATE
[        ] > Task :flutter_plugin_android_lifecycle:prepareLintJarForPublish UP-TO-DATE
[        ] > Task :flutter_plugin_android_lifecycle:mergeDebugJavaResource UP-TO-DATE
[        ] > Task :flutter_plugin_android_lifecycle:transformClassesAndResourcesWithSyncLibJarsForDebug UP-TO-DATE
[  +22 ms] > Task :flutter_plugin_android_lifecycle:transformNativeLibsWithSyncJniLibsForDebug UP-TO-DATE
[        ] > Task :flutter_plugin_android_lifecycle:bundleDebugAar UP-TO-DATE
[        ] > Task :flutter_plugin_android_lifecycle:compileDebugSources UP-TO-DATE
[        ] > Task :flutter_plugin_android_lifecycle:assembleDebug UP-TO-DATE
[   +2 ms] > Task :image_picker:extractDebugAnnotations UP-TO-DATE
[  +31 ms] > Task :image_picker:mergeDebugGeneratedProguardFiles UP-TO-DATE
[  +21 ms] > Task :image_picker:mergeDebugConsumerProguardFiles UP-TO-DATE
[        ] > Task :image_picker:prepareLintJarForPublish UP-TO-DATE
[        ] > Task :image_picker:mergeDebugJavaResource UP-TO-DATE
[        ] > Task :image_picker:transformClassesAndResourcesWithSyncLibJarsForDebug UP-TO-DATE
[        ] > Task :image_picker:transformNativeLibsWithSyncJniLibsForDebug UP-TO-DATE
[        ] > Task :image_picker:bundleDebugAar UP-TO-DATE
[  +39 ms] > Task :image_picker:compileDebugSources UP-TO-DATE
[        ] > Task :image_picker:assembleDebug UP-TO-DATE
[        ] BUILD SUCCESSFUL in 2s
[   +2 ms] 87 actionable tasks: 4 executed, 83 up-to-date
[ +459 ms] Running Gradle task 'assembleDebug'... (completed in 3,0s)
[  +49 ms] calculateSha: LocalDirectory: 'C:\Users\maclovin\Documents\projets\test_image_gallery\build\app\outputs\apk'/app.apk
[  +73 ms] calculateSha: reading file took 71us
[ +497 ms] calculateSha: computing sha took 496us
[   +6 ms] √ Built build\app\outputs\apk\debug\app-debug.apk.
[   +4 ms] executing: C:\Android\Sdk\build-tools\29.0.3\aapt dump xmltree C:\Users\maclovin\Documents\projets\test_image_gallery\build\app\outputs\apk\app.apk AndroidManifest.xml
[  +60 ms] Exit code 0 from: C:\Android\Sdk\build-tools\29.0.3\aapt dump xmltree C:\Users\maclovin\Documents\projets\test_image_gallery\build\app\outputs\apk\app.apk AndroidManifest.xml
[   +1 ms] N: android=http://schemas.android.com/apk/res/android
             E: manifest (line=2)
               A: android:versionCode(0x0101021b)=(type 0x10)0x1
               A: android:versionName(0x0101021c)="1.0.0" (Raw: "1.0.0")
               A: android:compileSdkVersion(0x01010572)=(type 0x10)0x1c
               A: android:compileSdkVersionCodename(0x01010573)="9" (Raw: "9")
               A: package="com.example.test_image_gallery" (Raw: "com.example.test_image_gallery")
               A: platformBuildVersionCode=(type 0x10)0x1c
               A: platformBuildVersionName=(type 0x10)0x9
               E: uses-sdk (line=7)
                 A: android:minSdkVersion(0x0101020c)=(type 0x10)0x10
                 A: android:targetSdkVersion(0x01010270)=(type 0x10)0x1c
               E: uses-permission (line=14)
                 A: android:name(0x01010003)="android.permission.INTERNET" (Raw: "android.permission.INTERNET")
               E: uses-permission (line=15)
                 A: android:name(0x01010003)="android.permission.READ_EXTERNAL_STORAGE" (Raw: "android.permission.READ_EXTERNAL_STORAGE")
               E: uses-permission (line=16)
                 A: android:name(0x01010003)="android.permission.WRITE_EXTERNAL_STORAGE" (Raw: "android.permission.WRITE_EXTERNAL_STORAGE")
               E: application (line=24)
                 A: android:label(0x01010001)="test_image_gallery" (Raw: "test_image_gallery")
                 A: android:icon(0x01010002)=@0x7f080000
                 A: android:name(0x01010003)="io.flutter.app.FlutterApplication" (Raw: "io.flutter.app.FlutterApplication")
                 A: android:debuggable(0x0101000f)=(type 0x12)0xffffffff
                 A: android:appComponentFactory(0x0101057a)="androidx.core.app.CoreComponentFactory" (Raw: "androidx.core.app.CoreComponentFactory")
                 E: activity (line=30)
                   A: android:theme(0x01010000)=@0x7f0a0000
                   A: android:name(0x01010003)="com.example.test_image_gallery.MainActivity" (Raw: "com.example.test_image_gallery.MainActivity")
                   A: android:launchMode(0x0101001d)=(type 0x10)0x1
                   A: android:configChanges(0x0101001f)=(type 0x11)0x40003fb4
                   A: android:windowSoftInputMode(0x0101022b)=(type 0x11)0x10
                   A: android:hardwareAccelerated(0x010102d3)=(type 0x12)0xffffffff
                   E: meta-data (line=44)
                     A: android:name(0x01010003)="io.flutter.embedding.android.NormalTheme" (Raw: "io.flutter.embedding.android.NormalTheme")
                     A: android:resource(0x01010025)=@0x7f0a0001
                   E: meta-data (line=54)
                     A: android:name(0x01010003)="io.flutter.embedding.android.SplashScreenDrawable" (Raw: "io.flutter.embedding.android.SplashScreenDrawable")
                     A: android:resource(0x01010025)=@0x7f040000
                   E: intent-filter (line=58)
                     E: action (line=59)
                       A: android:name(0x01010003)="android.intent.action.MAIN" (Raw: "android.intent.action.MAIN")
                     E: category (line=61)
                       A: android:name(0x01010003)="android.intent.category.LAUNCHER" (Raw: "android.intent.category.LAUNCHER")
                 E: meta-data (line=68)
                   A: android:name(0x01010003)="flutterEmbedding" (Raw: "flutterEmbedding")
                   A: android:value(0x01010024)=(type 0x10)0x2
                 E: provider (line=72)
                   A: android:name(0x01010003)="io.flutter.plugins.imagepicker.ImagePickerFileProvider" (Raw: "io.flutter.plugins.imagepicker.ImagePickerFileProvider")
                   A: android:exported(0x01010010)=(type 0x12)0x0
                   A: android:authorities(0x01010018)="com.example.test_image_gallery.flutter.image_provider" (Raw: "com.example.test_image_gallery.flutter.image_provider")
                   A: android:grantUriPermissions(0x0101001b)=(type 0x12)0xffffffff
                   E: meta-data (line=77)
                     A: android:name(0x01010003)="android.support.FILE_PROVIDER_PATHS" (Raw: "android.support.FILE_PROVIDER_PATHS")
                     A: android:resource(0x01010025)=@0x7f0c0000
[ +137 ms] Stopping app 'app.apk' on SM G930F.
[  +22 ms] executing: C:\Android\Sdk\platform-tools\adb.exe -s 9a43a7f7 shell am force-stop com.example.test_image_gallery
[ +113 ms] executing: C:\Android\Sdk\platform-tools\adb.exe -s 9a43a7f7 shell pm list packages com.example.test_image_gallery
[ +615 ms] package:com.example.test_image_gallery
[   +3 ms] executing: C:\Android\Sdk\platform-tools\adb.exe -s 9a43a7f7 shell cat /data/local/tmp/sky.com.example.test_image_gallery.sha1
[  +79 ms] a4d200ce6bfef33e18c29a122e3d70b69eed3355
[   +1 ms] Latest build already installed.
[        ] SM G930F startApp
[  +14 ms] executing: C:\Android\Sdk\platform-tools\adb.exe -s 9a43a7f7 shell am start -a android.intent.action.RUN -f 0x20000000 --ez enable-background-compilation true --ez enable-dart-profiling true --ez
enable-checked-mode true --ez verify-entry-points true com.example.test_image_gallery/com.example.test_image_gallery.MainActivity
[ +125 ms] Starting: Intent { act=android.intent.action.RUN flg=0x20000000 cmp=com.example.test_image_gallery/.MainActivity (has extras) }
[   +1 ms] Waiting for observatory port to be available...
[ +803 ms] Observatory URL on device: http://<IP_ADDRESS>:46929/qXm6Kwy3Ri4=/
[   +4 ms] executing: C:\Android\Sdk\platform-tools\adb.exe -s 9a43a7f7 forward tcp:0 tcp:46929
[  +58 ms] 53809
[   +1 ms] Forwarded host port 53809 to device port 46929 for Observatory
[   +8 ms] Connecting to service protocol: http://<IP_ADDRESS>:53809/qXm6Kwy3Ri4=/
[ +512 ms] Successfully connected to service protocol: http://<IP_ADDRESS>:53809/qXm6Kwy3Ri4=/
[  +10 ms] Sending to VM service: getVM({})
[  +38 ms] Result: {type: VM, name: vm, architectureBits: 64, hostCPU: Qualcomm Technologies, Inc MSM8996, operatingSystem: android, targetCPU: arm64, version: 2.8.4 (stable) (Wed Jun 3 12:26:04 2020 +0200) on
"android_arm64", _profilerMode: VM, _nativeZoneMemoryUsa...
[  +22 ms] Sending to VM service: getIsolate({isolateId: isolates/251065860059979})
[  +28 ms] Sending to VM service: _flutter.listViews({})
[  +41 ms] Result: {type: Isolate, id: isolates/251065860059979, name: main, number:<PHONE_NUMBER>59979, _originNumber:<PHONE_NUMBER>59979, startTime:<PHONE_NUMBER>246, _heaps: {new: {type: HeapSpace, name: new, vmName:
Scavenger, collections: 0, avgCollectionPeriodMillis: 0...
[  +32 ms] Result: {type: FlutterViewList, views: [{type: FlutterView, id: _flutterView/0x7066a52f20, isolate: {type: @Isolate, fixedId: true, id: isolates/251065860059979, name: main.dart$main-251065860059979, number:251065860059979}}]}
[  +19 ms] DevFS: Creating new filesystem on the device (null)
[   +1 ms] Sending to VM service: _createDevFS({fsName: test_image_gallery})
[  +61 ms] Result: {type: FileSystem, name: test_image_gallery, uri: file:///data/user/0/com.example.test_image_gallery/code_cache/test_image_gallerySLDYSH/test_image_gallery/}
[        ] DevFS: Created new filesystem on the device (file:///data/user/0/com.example.test_image_gallery/code_cache/test_image_gallerySLDYSH/test_image_gallery/)
[   +1 ms] Updating assets
[  +86 ms] Syncing files to device SM G930F...
[   +1 ms] Scanning asset files
[   +2 ms] <- reset
[  +11 ms] Compiling dart to kernel with 0 updated files
[   +2 ms] <- recompile package:test_image_gallery/main.dart 0e5dce08-d07a-40d0-bafb-f401e6d68d32
[  +13 ms] <- 0e5dce08-d07a-40d0-bafb-f401e6d68d32
[  +91 ms] Updating files
[ +229 ms] DevFS: Sync finished
[   +5 ms] Syncing files to device SM G930F... (completed in 355ms)
[  +36 ms] Synced 0.9MB.
[   +2 ms] Sending to VM service: _flutter.listViews({})
[   +7 ms] Result: {type: FlutterViewList, views: [{type: FlutterView, id: _flutterView/0x7066a52f20, isolate: {type: @Isolate, fixedId: true, id: isolates/251065860059979, name: main.dart$main-251065860059979, number:251065860059979}}]}
[  +17 ms] <- accept
[   +1 ms] Connected to _flutterView/0x7066a52f20.
[   +2 ms] Flutter run key commands.
[  +18 ms] r Hot reload.
[   +1 ms] R Hot restart.
[   +1 ms] h Repeat this help message.
[        ] d Detach (terminate "flutter run" but leave application running).
[  +17 ms] c Clear the screen
[  +21 ms] q Quit (terminate the application on the device).
[   +1 ms] An Observatory debugger and profiler on SM G930F is available at: http://<IP_ADDRESS>:53809/qXm6Kwy3Ri4=/
[+2437 ms] D/ViewRootImpl@17be8f6[MainActivity]( 6217): ViewPostIme pointer 0
[  +39 ms] D/ViewRootImpl@17be8f6[MainActivity]( 6217): ViewPostIme pointer 1
[+1678 ms] D/ViewRootImpl@17be8f6[MainActivity]( 6217): ViewPostIme pointer 0
[  +45 ms] D/ViewRootImpl@17be8f6[MainActivity]( 6217): ViewPostIme pointer 1
[  +68 ms] D/ViewRootImpl@17be8f6[MainActivity]( 6217): MSG_WINDOW_FOCUS_CHANGED 0
[ +220 ms] D/SurfaceView( 6217): BG show() Surface(name=Background for - SurfaceView - com.example.test_image_gallery/com.example.test_image_gallery.MainActivity@1f59e82@0)
io.flutter.embedding.android.FlutterSurfaceView{1f59e82 V.E...... ........ 0,0-1080,1920}
[   +6 ms] D/SurfaceView( 6217): surfaceDestroyed 1 io.flutter.embedding.android.FlutterSurfaceView{1f59e82 V.E...... ........ 0,0-1080,1920}
[  +37 ms] D/SurfaceView( 6217): BG destroy() Surface(name=Background for - SurfaceView - com.example.test_image_gallery/com.example.test_image_gallery.MainActivity@1f59e82@0)
io.flutter.embedding.android.FlutterSurfaceView{1f59e82 V.E...... ........ 0,0-1080,1920}
[   +4 ms] D/OpenGLRenderer( 6217): eglDestroySurface = 0x70404af680
[   +2 ms] D/ViewRootImpl@17be8f6[MainActivity]( 6217): Relayout returned: old=[0,0][1080,1920] new=[0,0][1080,1920] result=0x5 surface={valid=false 0} changed=true
[ +363 ms] V/InputMethodManager( 6217): Starting input: tba=android.view.inputmethod.EditorInfo@27b69e7 nm : com.example.test_image_gallery ic=null
[   +4 ms] I/InputMethodManager( 6217): startInputInner - mService.startInputOrWindowGainedFocus
[  +36 ms] D/ViewRootImpl@17be8f6[MainActivity]( 6217): dispatchDetachedFromWindow
[   +1 ms] D/InputEventReceiver( 6217): channel '5dfccb com.example.test_image_gallery/com.example.test_image_gallery.MainActivity (client)' ~ Disposing input event receiver.
[   +1 ms] D/InputEventReceiver( 6217): channel '5dfccb com.example.test_image_gallery/com.example.test_image_gallery.MainActivity (client)' ~NativeInputEventReceiver.
[ +724 ms] I/zygote64( 6217): Do partial code cache collection, code=25KB, data=29KB
[   +4 ms] I/zygote64( 6217): After code cache collection, code=25KB, data=29KB
[  +40 ms] I/zygote64( 6217): Increasing code cache capacity to 128KB
[   +1 ms] D/ViewRootImpl@2ae85e2[MainActivity]( 6217): setView = DecorView@fe60d73[MainActivity] TM=true MM=false
[   +1 ms] V/InputMethodManager( 6217): Not IME target window, ignoring
[  +22 ms] D/ViewRootImpl@2ae85e2[MainActivity]( 6217): dispatchAttachedToWindow
[   +1 ms] V/Surface ( 6217): sf_framedrop debug : 0x4f4c, game : false, logging : 0
[        ] D/ViewRootImpl@2ae85e2[MainActivity]( 6217): Relayout returned: old=[0,0][0,0] new=[0,0][1080,1920] result=0x7 surface={valid=true<PHONE_NUMBER>96} changed=true
[        ] D/OpenGLRenderer( 6217): eglCreateWindowSurface = 0x70404af680
[        ] D/SurfaceView( 6217): BG show() Surface(name=Background for - SurfaceView - com.example.test_image_gallery/com.example.test_image_gallery.MainActivity@6fef430@0)
io.flutter.embedding.android.FlutterSurfaceView{6fef430 V.E...... ......ID 0,0-1080,1920}
[  +20 ms] V/Surface ( 6217): sf_framedrop debug : 0x4f4c, game : false, logging : 0
[  +35 ms] D/SurfaceView( 6217): surfaceCreated 1 io.flutter.embedding.android.FlutterSurfaceView{6fef430 V.E...... ......ID 0,0-1080,1920}
[  +92 ms] D/SurfaceView( 6217): surfaceChanged (1080,1920) 1 io.flutter.embedding.android.FlutterSurfaceView{6fef430 V.E...... ......ID 0,0-1080,1920}
[   +3 ms] D/ViewRootImpl@2ae85e2[MainActivity]( 6217): MSG_RESIZED_REPORT: frame=Rect(0, 0 - 1080, 1920) ci=Rect(0, 72 - 0, 0) vi=Rect(0, 72 - 0, 0) or=1
[  +27 ms] D/ViewRootImpl@2ae85e2[MainActivity]( 6217): MSG_WINDOW_FOCUS_CHANGED 1
[   +1 ms] V/InputMethodManager( 6217): Starting input: tba=android.view.inputmethod.EditorInfo@614c8a9 nm : com.example.test_image_gallery ic=null
[        ] I/InputMethodManager( 6217): startInputInner - mService.startInputOrWindowGainedFocus
[        ] D/ViewRootImpl@2ae85e2[MainActivity]( 6217): Relayout returned: old=[0,0][1080,1920] new=[0,0][1080,1920] result=0x3 surface={valid=true<PHONE_NUMBER>96} changed=false
[+2878 ms] I/zygote64( 6217): Compiler allocated 8MB to compile void android.view.ViewRootImpl.performTraversals()
[ +117 ms] I/zygote64( 6217): Do partial code cache collection, code=62KB, data=60KB
[   +3 ms] I/zygote64( 6217): After code cache collection, code=62KB, data=60KB
[  +37 ms] I/zygote64( 6217): Increasing code cache capacity to 256KB
[ +941 ms] Application finished.
[   +5 ms] executing: C:\Android\Sdk\platform-tools\adb.exe -s 9a43a7f7 forward --list
[  +50 ms] Exit code 0 from: C:\Android\Sdk\platform-tools\adb.exe -s 9a43a7f7 forward --list
[   +7 ms] 9a43a7f7 tcp:53597 tcp:42573
           9a43a7f7 tcp:53722 tcp:42739
           9a43a7f7 tcp:53809 tcp:46929
[   +2 ms] executing: C:\Android\Sdk\platform-tools\adb.exe -s 9a43a7f7 forward --remove tcp:53597

Analyzing test_image_gallery...
No issues found! (ran in 1.9s)

[√] Flutter (Channel stable, v1.17.3, on Microsoft Windows [version 10.0.19041.329], locale fr-FR)
    • Flutter version 1.17.3 at C:\flutter
    • Framework revision b041144f83 (9 days ago), 2020-06-04 09:26:11 -0700
    • Engine revision ee76268252
    • Dart version 2.8.4

[√] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at C:\Android\Sdk
    • Platform android-R, build-tools 29.0.3
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
    • All Android licenses accepted.

[!] Android Studio (version 4.0)
    • Android Studio at C:\Program Files\Android\Android Studio
    X Flutter plugin not installed; this adds Flutter specific functionality.
    X Dart plugin not installed; this adds Dart specific functionality.
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)

[√] VS Code (version 1.46.0)
    • VS Code at C:\Users\maclovin\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.11.0

[√] Connected device (1 available)
    • SM G930F • 9a43a7f7 • android-arm64 • Android 8.0.0 (API 26)

! Doctor found issues in 1 category.

This is happening to me too with some Android devices. My code is very similar to @alexisbrunet34's, except my image source is the camera. The most recent complaint we had was with a Vivo Z1 Pro device running Android 10.

This is happening to me too with some Android devices. My code is very similar to @alexisbrunet34's, except my image source is the camera. The most recent complaint we had was with a Vivo Z1 Pro device running Android 10.

Hi everyone, I can reproduce on Android, app is restarted (screen is flashed) every time we pick something.
Reproducible using latest image_picker: ^0.6.7+22

flutter doctor -v
[✓] Flutter (Channel master, 1.27.0-2.0.pre.67, on macOS 11.2 20D64 darwin-x64, locale en-GB)
    • Flutter version 1.27.0-2.0.pre.67 at /Users/tahatesser/Code/flutter_master
    • Framework revision 78ce11d7e3 (7 hours ago), 2021-02-11 07:37:57 +0100
    • Engine revision cdc49c575b
    • Dart version 2.13.0 (build 2.13.0-25.0.dev)
[✗] Android toolchain - develop for Android devices
    ✗ Unable to locate Android SDK.
      Install Android Studio from: https://developer.android.com/studio/index.html
      On first launch it will assist you in installing the Android SDK components.
      (or visit https://flutter.dev/docs/get-started/install/macos#android-setup for detailed instructions).
      If the Android SDK has been installed to a custom location, please use
      `flutter config --android-sdk` to update to that location.
[!] Xcode - develop for iOS and macOS
    • Xcode at /Volumes/Extreme/Xcode.app/Contents/Developer
    • Xcode 12.4, Build version 12D4e
    ✗ CocoaPods not installed.
        CocoaPods is used to retrieve the iOS and macOS platform side's plugin code that responds to your plugin usage on the Dart side.
        Without CocoaPods, plugins will not work on iOS or macOS.
        For more info, see https://flutter.dev/platform-plugins
      To install see https://guides.cocoapods.org/using/getting-started.html#installation for instructions.
[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[✓] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6915495)
[✓] VS Code (version 1.53.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.19.0
[✓] Connected device (3 available)
    • Taha’s iPhone (mobile) • 00008020-001059882212002E • ios            • iOS 14.4
    • macOS (desktop)        • macos                     • darwin-x64     • macOS 11.2 20D64 darwin-x64
    • Chrome (web)           • chrome                    • web-javascript • Google Chrome 88.0.4324.150
! Doctor found issues in 2 categories.

Thank you

One of my users complained exactly about this issue and I can only imagine how many didn't complain, but simply stopped using the app. This issue also leaves no traces in Crashlytics. So thanks for managing to reproduce it! Any ideas on a workaround?

Hello, do you have any updates or fixes about this issues? I still reproduce it with flutter 2.0.3 and image_picker: ^0.6.7
Thank you

@alexisbrunet34 @TahaTesser Did you have "don't keep activities" on in the developer setting? https://stackoverflow.com/questions/22400859/dont-keep-activities-what-is-it-for

To me it sounds like your main activity might be getting killed by Android.
To deal with this, the retrieveLostData method is provided. You can read Handling MainActivity destruction on Android on how to use it.
You can use the "don't keep activities" developer setting which @cyanglaz mentioned to test how your application deals with the main activity getting killed while picking an image.

@BeMacized: thanks for pointing to the issue with the main activity being killed by Android (BTW, I can imagine it may happen in iOS as well). Finally I have an idea why my users sometimes complain about the app crashing (in fact restarting) when they try to pick an image and I can't reproduce it. It's easily reproducible with the "don't keep activities" developer setting.
Unfortunately in my case calling the retrieveLostData method is not enough to solve the issue. The whole app state has to be restored. This article Introduction to State Restoration in Flutter helped me to understand how big the problem actually is. I really wish that image picker wouldn't start a new activity, but this seems to be impossible.

Agreed, it is quite an unfortunate situation, but I do not think there is any reasonable alternative to starting a new activity that would prevent the main activity from getting killed. This seems more of an issue with Android as a whole, where it is expected that your app will be able to restore itself in the case of this happening.
As it does not seem to be specific to image_picker, nor to Flutter, I will be closing this issue.
If anyone has any ideas or suggestions on how to improve on this, feel free to comment so we can revisit this.

BTW, I can imagine it may happen in iOS as well

iOS doesn't have an intent system for coordinating between applications; it's a very different architecture. Image picking on iOS uses a system-provided in-app view controller.


Add username's file

created a branch, created a file and made a commit, and opened a pull
request

it was awsome


bundled tangram

closes #419

We decided to move on with bundling Tangram since mapzen.js didn't reach to public api level yet. (https://github.com/mapzen/mapzen.js/issues/419)  now user can grab Tangram Layer through map (https://github.com/mapzen/mapzen.js/blob/hanb/bundle-tangram/test/examples/all-defaults.html#L37-L50) I wonder it is werid  to get the layer through the map for users, but also we anyway delegate all the Tangram works to map layer so maybe it is fine if we just keep our consistency?

That's a good question and I wonder if that's weird, too.  I think it's fine for now, because it's consistent. This may come up again if/when we think about adding additional layers to the map (like a Tangram equivalent to L.geoJSON) on top of the basemap. I'm sure that will affect how we think about "map" and "layers".   Anyway, definitely not a blocker for this.

I just noticed that my isochrone demo (http://localhost:8000/test/examples/isochrone-map.html) doesn't work with Tangram v0.14.  Bundled or otherwise.
"Cannot read property 'dash' of undefined"

@meetar - have you seen anything like this?

@rfriberg Hm, I'm actually able to load that page on both master and hanb/bundle-tangram with:
npm install
npm run build-dev-style

Any hints for reproducing?

Try
npm run build
instead of npm run build-dev-style!
On Nov 6, 2017 9:32 PM, "Peter Richardson"<EMAIL_ADDRESS>wrote:
@rfriberg https://github.com/rfriberg Hm, I'm actually able to load that
page on both master and hanb/bundle-tangram with:
npm install
npm run build-dev-style
Any hints for reproducing?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mapzen/mapzen.js/pull/434#issuecomment-342356543, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AEXxft-P1vl1guXnw-P_6VZwHm3HjJJgks5sz8FMgaJpZM4PRoQD
.

Ah, thanks! I see the errors now in hanb/bundle-tangram, though the page still appears to load correctly with npm run build in master…
It looks like the problem is related to https://github.com/mapzen/mapzen.js/blob/hanb/bundle-tangram/test/examples/resources/isochrone-map.yaml#L27-L28 – there's an outline with a style of "_outline" specified, but a style with that name doesn't exist in the scene file or the imports.
Tracing the comment above that outline block back to refill, it looks like it may originally have been intended to give all outlines the same order, to group them together… was that the goal here too, or was it intended to have a different style called "_outline"?
At any rate, that error appears if a draw block is assigned a style which doesn't have a valid base specified (which includes non-existent styles), there may be a way to improve that error message. (cc @bcamper)

Filed a related issue: https://github.com/tangrams/tangram/issues/618

I think you already sorted out, just fyi: not being able to see this error from master means that this  problem lies in Tangram 0.14 since master is still building from  Tangram 0.13

If @meetar's diagnosis of the YAML is correct, then the behavior might have changed in Tangram 0.14 (and would be useful to have a more helpful error as he has documented), but the problem itself is in the style.

@bcamper I wanted to address the reason why the behavior differs from master to hanb/bundle-tangram since @meetar  mentioned that. Sorry if my previous comment confused the team. Also just to be clear, so this style error is supposed to break map-rendering, but 0.13 didn't catch that before and now is fixed with 0.14? @bcamper

Thanks, all!  It sounds like Tangram had been ignoring some style syntax issues, but as of v0.14.0 those same style syntax issues are now causing the map rendering to break.  Thanks for opening that ticket @meetar.
I'll be sure to update this example.  Looping in @burritojustice as this example was based on our isochrone demo, and I know a few versions of it exist.  (Sure hope we pegged the mapzen.js version in those!)
@hanbyul-here - sorry for hijacking this PR!

After looking through Leaflet api, I thought it would make more sense to return tangramLayer through get method. (map.getTangramLayer()) Any opinion? @rfriberg ?

@hanbyul-here - sounds good to me!

@hanbyul-here - it looks like avoiding comparisons will fix the global is not defined issue we were seeing (similar to this webpack/uglifyjs fix).
Just add: uglifyjs -c comparisons=false
There may be other compression optimizations we could and should be doing, but this will at least fix the problem with minifying Tangram.

Yess that works!  Thanks @rfriberg !


[todo] structure module

in the structure module, the FAPE loss needs to be applied on every iteration, while the rotation needs to have a stop-gradient for all but the last iteration

May i ask what "the rotation needs to have a stop-gradient for all but the last iteration" means?
The FAPE function satisfies the main constraints the methods section outlined: https://github.com/EleutherAI/mp_nerf/blob/master/mp_nerf/ml_utils.py#L102 Do you find something to be missing? i might add it

May i ask what "the rotation needs to have a stop-gradient for all but the last iteration" means?
The FAPE function satisfies the main constraints the methods section outlined: https://github.com/EleutherAI/mp_nerf/blob/master/mp_nerf/ml_utils.py#L102 Do you find something to be missing? i might add it

https://github.com/lucidrains/alphafold2/commit/521415676df4043ed101a882d0eae7a659c774d0 took care of it here :)
just need to apply the FAPE loss every iteration and sum up the auxiliary losses now!

May i ask what "the rotation needs to have a stop-gradient for all but the last iteration" means?
The FAPE function satisfies the main constraints the methods section outlined: https://github.com/EleutherAI/mp_nerf/blob/master/mp_nerf/ml_utils.py#L102 Do you find something to be missing? i might add it

they have this MultiRigidSidechain class https://github.com/deepmind/alphafold/blob/0bab1bf84d9d887aba5cfb6d09af1e8c3ecbc408/alphafold/model/folding.py#L931 and it seems like there's a parameterized transformation before applying the loss itself


feat: rewrite compute_starknet_address in Rust

Feature Request
Describe the Feature Request

For https://github.com/kkrt-labs/kakarot-rpc/issues/345, in order to map the EVM address we call compute_starknet_address in the deployed Kakarot contract. If we want to prefund the EOAs in Madara for the Hive tests, we will need to pre-compute the starknet address, since Kakarot isn't deployed yet, and add them in the genesis config.
Describe Preferred Solution
We have this function in Cairo 0, we need to convert it into Rust that takes in kakarot_address and evm_address and computes the resulting starknet_address
    func compute_starknet_address{syscall_ptr: felt*, pedersen_ptr: HashBuiltin*, range_check_ptr}(
        evm_address: felt
    ) -> (contract_address: felt) {
        alloc_locals;
        let (_deployer_address: felt) = get_contract_address();
        let (_account_proxy_class_hash: felt) = account_proxy_class_hash.read();
        let (constructor_calldata: felt*) = alloc();
        let (hash_state_ptr) = hash_init();
        let (hash_state_ptr) = hash_update_single{hash_ptr=pedersen_ptr}(
            hash_state_ptr=hash_state_ptr, item=Constants.CONTRACT_ADDRESS_PREFIX
        );
        // hash deployer
        let (hash_state_ptr) = hash_update_single{hash_ptr=pedersen_ptr}(
            hash_state_ptr=hash_state_ptr, item=_deployer_address
        );
        // hash salt
        let (hash_state_ptr) = hash_update_single{hash_ptr=pedersen_ptr}(
            hash_state_ptr=hash_state_ptr, item=evm_address
        );
        // hash class hash
        let (hash_state_ptr) = hash_update_single{hash_ptr=pedersen_ptr}(
            hash_state_ptr=hash_state_ptr, item=_account_proxy_class_hash
        );
        let (hash_state_ptr) = hash_update_with_hashchain{hash_ptr=pedersen_ptr}(
            hash_state_ptr=hash_state_ptr, data_ptr=constructor_calldata, data_length=0
        );
        let (contract_address_before_modulo) = hash_finalize{hash_ptr=pedersen_ptr}(
            hash_state_ptr=hash_state_ptr
        );
        let (contract_address) = normalize_address{range_check_ptr=range_check_ptr}(
            addr=contract_address_before_modulo
        );

        return (contract_address=contract_address);
    }

Test against a locally deployed Kakarot contract using test sequencer #365


Add Entry Augmentor and helper.

I'm not sure how useful this is. I find myself using the default augmentation more since they improved the docs, but it might come in handy in some cases.

Thanks @stuartcusackie can you please update the docs to reflect how this is used?

Thanks!


Add sanity test script

Description
This is a python script to running all test queries from a csv file. It calls async query API to submit test query, and generate test reports based on the final results.
Apart from the basic feature, it also has some advanced functionality includes:

Concurrently running test queries. Note that the async query services has limitation on active sessions, don't set too many thread workers, although it already try to reuse the session id of previous task for each thread.
Support configuration of timeout for a running query, it will check query status periodically until it is completed or failed or exceeded the timeout. It will cancel the query if timeout occurs.
Support specify the start rows and end rows of testing queries in the CSV file.
Always can generate report on the completed tests if you want to interrupt the testing progress in advance.

An example to run the test script:
python FlintSanityTest_Concurrency.py --base-url ${URL_ADDRESS} --username *** --password *** --datasource ${DATASOURCE_NAME} --input-csv test_queries.csv --output-file test_report --max-workers 2 --check-interval 10 --timeout 600

For more details, you can see the help manual via command:
python FlintSanityTest_Concurrency.py --help

usage: FlintSanityTest_Concurrency.py [-h] --base-url BASE_URL --username USERNAME --password PASSWORD --datasource DATASOURCE --input-csv INPUT_CSV
                                      --output-file OUTPUT_FILE [--max-workers MAX_WORKERS] [--check-interval CHECK_INTERVAL] [--timeout TIMEOUT]
                                      [--start-row START_ROW] [--end-row END_ROW]

Run tests from a CSV file and generate a report.

options:
  -h, --help            show this help message and exit
  --base-url BASE_URL   Base URL of the service
  --username USERNAME   Username for authentication
  --password PASSWORD   Password for authentication
  --datasource DATASOURCE
                        Datasource name
  --input-csv INPUT_CSV
                        Path to the CSV file containing test queries
  --output-file OUTPUT_FILE
                        Path to the output report file
  --max-workers MAX_WORKERS
                        optional, Maximum number of worker threads (default: 2)
  --check-interval CHECK_INTERVAL
                        optional, Check interval in seconds (default: 10)
  --timeout TIMEOUT     optional, Timeout in seconds (default: 600)
  --start-row START_ROW
                        optionl, The start row of the query to run, start from 0
  --end-row END_ROW     optional, The end row of the query to run

Related Issues
Resolves https://github.com/opensearch-project/opensearch-spark/issues/877
Check List

[ ] Updated documentation (docs/ppl-lang/README.md)
[ ] Implemented unit tests
[ ] Implemented tests for combination with other commands
[x] New added source code should include a copyright header
[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

@qianheng-aws this looks good - please add

documentation with all the above description and instructions + results of a running report
what are the prerequisites for running the script - docker ?
what are the data prerequisites for running the script - import content process ?
export the results to a file including :

ppl version
performance time
coverage

plz also add a folder for CSV tests

@qianheng-aws this looks good - please add

documentation with all the above description and instructions + results report example

what are the prerequisites for running the script - docker ?

what are the data prerequisites for running the script - import content process ?

export the results to a file including :

ppl version
performance time
coverage

plz also add a folder for CSV tests

I address most part  of the comment and add them in the README.md, except some points:

the data prerequisites. I haven't got the background of where the data comes from and how to ingest them to flint yet. Left a TODO in the README.
ppl version. Do you mean the version returns from API GET _cat/plugins?v?  I think it should always be the same as the opensearch version. Will it help to add that in the report?


Update postgresql to 42.2.11

Updates org.postgresql:postgresql from 42.2.2 to 42.2.11.
Changelog
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.postgresql", artifactId = "postgresql" } ]

labels: library-update, semver-patch

Superseded by #64.


Crash in WASM app because of calls to filesystem functions

JSON schema crashes at WASM app startup during the initialization of the drafts. The reason is the call to stat function, which is not implemented for the WASM platform. The call is in toAbs function where it calls filepath.Abs.

relative urls are resolved against the document url. in case of draft, the document url is of type http url. so it never lands up using filesystem calls.
try the sample i mentioned above at your end and check if it still fails

BTW, I am using safari on mac

I tested on chrome on mac. it works fine.

As I said, in my case it is not even hittingmain. It crashed before that, in init(). I added some printlns, and the last thing it prints is one of the meta/ components of the schema drafts. It is a relative reference in the draft text.

Are you using V5 version

It is the v5 version. Here's the stack trace, obtained by commenting out my fix:
path is:  annotations.json  // This fmt.Println is just before this in isAbs(): if s, err = filepath.Abs(s); err != nil {
wasm_exec.js:51 panic: stat .: not implemented on js
wasm_exec.js:51
wasm_exec.js:51 goroutine 1 [running]:
wasm_exec.js:51 github.com/santhosh-tekuri/jsonschema/v5.MustCompileString({0x15dbc0, 0x10}, {0x15102e, 0x2})
wasm_exec.js:51 	/home/bserdar/github.com/cloudprivacylabs/lsa-playground/vendor/github.com/santhosh-tekuri/jsonschema/v5/compiler.go:68 +0x1c
wasm_exec.js:51 github.com/cloudprivacylabs/lsa/pkg/json.init()
wasm_exec.js:51 	/home/bserdar/github.com/cloudprivacylabs/lsa-playground/vendor/github.com/cloudprivacylabs/lsa/pkg/json/import.go:90 +0x2

Turns out annotations.json is one of my files. And using mem://annotations.json fixes the problem.
So we can close this ticket and the PR if you want, or the PR can still stay so that it works for relative JSON schemas in WASM.
Sorry for the trouble,

Without PR it works for relative json also

yes. you have to use absolute url like mem://annotations.json. because relative path is assumed to be file relative to current working directory.
but any relative paths used inside annotations.json are resolve against mem://annotations.json. Only the root resource is interpreted as file if relative path is given.

in case anybody else is wondering how to use this lib with wasm I'll leave those snippets here:
@bserdar did you happen to get this to work with tinygo insteand of go? The binary size of the generated .wasm file is around 4MB, which is a lot for the browser.
TinyGo compiles without errors on my machine, but the generated wasm file does not load in the browser because of an error reflect.Type.NumMethod() is unimplemented (see https://github.com/tinygo-org/tinygo/issues/2660 for reference)
package main

import (
	"encoding/json"
	"syscall/js"

	"github.com/santhosh-tekuri/jsonschema/v5"
)

func main() {
	js.Global().Set("JSONSchemaValidate", js.FuncOf(validate))
	<-make(chan bool)
}

func validate(this js.Value, args []js.Value) interface{} {
	compiler := jsonschema.NewCompiler()
	compiler.Draft = jsonschema.Draft2020

	// get an object
	schema := args[0].String()
	instance := args[1].String()

	compiledSchema, err := jsonschema.CompileString("mem://schema.json", schema)
	if err != nil {
		panic(err)
	}

	var parsedJSON interface{}
	if err := json.Unmarshal([]byte(instance), &parsedJSON); err != nil {
		panic(err)
	}

	err = compiledSchema.Validate(parsedJSON)
	if err != nil {
		if validationError, ok := err.(*jsonschema.ValidationError); ok {
			b, _ := json.Marshal(validationError.DetailedOutput())
			return string(b)
		} else {
			panic(err)
		}

	}

	return nil
}

<!DOCTYPE html>
<html>
  <head>
    <meta charset="utf-8" />
    <title>Go wasm</title>
  </head>

  <body>
    <script src="wasm_exec.js"></script>
    <script>
      const go = new Go();

      WebAssembly.instantiateStreaming(
        fetch("./main.wasm"),
        go.importObject
      ).then((res) => {
        go.run(res.instance);

        console.time("validate");
        const result = JSONSchemaValidate(
          `{"properties": { "val": {"const": 10}, "val2": {"const": 5}}, "required": ["val", "val2"]}`,
          `{"val": 9, "val2": 1}`
        );
        console.timeEnd("validate");
        console.log({ result: JSON.parse(result) });
      });
    </script>
  </body>
</html>

@manuschillerdev I did not try this with tinygo. This is part of a rather large project, and my binary size is around 15M.


Keogram failed on when overexposed images exists

It fails with this error:
OpenCV Error: Assertion failed (channels() == CV_MAT_CN(dtype)) in copyTo, file /build/opencv-L65chJ/opencv-3.2.0+dfsg/modules/core/src/copy.cpp, line 259
terminate called after throwing an instance of 'cv::Exception'
what():  /build/opencv-L65chJ/opencv-3.2.0+dfsg/modules/core/src/copy.cpp:259: error: (-215) channels() == CV_MAT_CN(dtype) in function copyTo
Maybe such images should be skipped?

Are your overexposed images saved as grayscale instead of RGB?

Closing issue - no reply from user in a year.


TypeError: preview() missing 2 required positional arguments: 'content' and 'name'

I am getting that error "TypeError: preview() missing 2 required positional arguments: 'content' and 'name'" on frapecloud in wikipage xxx.frappe.cloud/app/wiki-page-patch/new-wiki-page-patch-1
the same is on my local server but sometimes in some other places. It may be somehow connected with update v13.14 ?

can you share traceback from browser's console?

can you share traceback from browser's console?

sure

Same error i am also getting in erpnext v13

I have almost the same error TypeError: preview() missing 1 required positional argument: 'content' and TypeError: object of type 'NoneType' has no len()
App Versions
"erpnext": "14.13.0",
"frappe": "14.23.0",
"wiki": "0.0.1"

@asemoq can you explain a bit more about what you were trying to do?

@asemoq can you explain a bit more about what you were trying to do?

I tried to open wiki page patcher


IRC Logs for #laravel-dev

Are there plans to log #laravel-dev also? Since the new Contributing Guide suggests discussing development here (http://laravel.com/docs/contributions#core-development-discussion)

Any update on this?

I did some research a couple of weeks ago to find out who's managing the logs atm. I think @JesseObrien manages the #laravel and #laravel-offtopic ones.
I don't really have the time atm anymore to manage these things anymore so I think it's best that if you want this to happen that you contact Jesse or the channel owner (Taylor) to set it up.