Terminal slows down after enabling this plugin

General infomation
Terminal: Konsole
OS: Ubuntu 20.04
ZSH framework: oh-my-zsh
ZSH version 5.8
ZVM version 0.8.3
Basic examination

[x] I have read through the README page
[x] I have the latest version of zsh-vi-mode
[x] I have tested with another terminal program

Problem description
Enabling this plugin makes prompt 2.5 times slow. Am I doing something wrong?
Without any plugins
********************************************************************
                      Prompt Benchmark Results
********************************************************************
Warmup duration      4s
Benchmark duration   2.011s
Benchmarked prompts  112
Time per prompt      17.95ms  <-- prompt latency (lower is better)
********************************************************************

Nearly 15 plugins
********************************************************************
                      Prompt Benchmark Results
********************************************************************
Warmup duration      4s
Benchmark duration   2.001s
Benchmarked prompts  101
Time per prompt      19.81ms  <-- prompt latency (lower is better)
********************************************************************

15 other plugins and zsh-vi-mode
********************************************************************
                      Prompt Benchmark Results
********************************************************************
Warmup duration      4s
Benchmark duration   2.044s
Benchmarked prompts  41
Time per prompt      49.84ms  <-- prompt latency (lower is better)
********************************************************************

Here is all my settings related with this plugin:
ZVM_LAZY_KEYBINDINGS=false
ZVM_VI_INSERT_ESCAPE_BINDKEY=kj
plugins=(... zsh-vi-mode)
source $ZSH/oh-my-zsh.sh

# https://github.com/jeffreytse/zsh-vi-mode#execute-extra-commands
function my_bindings() {
    # easy bindings instead of ctrl + arrow keys
    bindkey '^j' backward-word
    bindkey '^f' forward-word
    bindkey '^g' autosuggest-accept
    bindkey "\e\e" sudo-command-line
}

zvm_after_init_commands+=('[ -f ~/.fzf.zsh ] && source ~/.fzf.zsh')
zvm_after_init_commands+=(my_bindings)
# Always starting with insert mode for each command line
ZVM_LINE_INIT_MODE=$ZVM_MODE_INSERT
ZVM_INSERT_MODE_CURSOR=$ZVM_CURSOR_BLOCK

Reproduction steps

Install and enable zsh-prompt-bencmark
Benchmark with zsh-vi-mode enabled
Benchmark with zsh-vi-mode not enabled
Compare the results and see this plugin takes too much time

Expected behavior
I expect this plugin to be not take too much time like the other ones.

Hi @Asocia
In fact, this plugin is initialized during the first precmd, it's different from most of other plugins that are initialized during souring the plugin. So the zsh-prompt-bencmark could not detect the prompt time of those plugins. Actually, the initialization time is short now.
Thanks and regards

Yes, as you said it is initialized only once. I disabled precmd hook for this plugin and initialized it myself but result didn't change. I'm curious what makes this plugin slow and if it is possible to make it faster. I really like this plugin and it would be great if this issue can be solved.
Some other examinations:

When I type set -x and then set +x I can see a detailed trace. There is a lot of output which contains zsh-vi-mode but I can't interpret it since my knowledge in this area is limited. I just wanted to share so maybe it helps.

Thanks!

Hi @Asocia
There are lots of stuffs need to be done and they are necessary for this plugin running normally. I can add an option to let you set the time of initializating this plugin. And welcome to star this plugin for further updates in the future.
Thanks and regards

Hi @Asocia
Now this plugin has provided an option called ZVM_INIT_MODE to configure the initialization mode (#113), you can use this snippet ZVM_INIT_MODE=sourcing for doing the initialization inistantly when this plugin is sourcing.
Thanks and regards

Hi @jeffreytse,
I pulled the recent changes and added ZVM_INIT_MODE=sourcing to my .zshrc. I didn't observe any effect on prompt latency. Thanks.

Hi @Asocia
You're welcome and thanks for your checking out. If you get any other issue in the future, welcome to reach me.
Thanks and regards

Uhm, I think you got me wrong. By saying "I didn't observe any effect" I meant that the prompt is still slow as before. It was coming in 34ms and after applying the last change it's still 34ms.

Hi @Asocia , sorry for the misunderstand, did you put the mode option before sourcing this plugin?

Yes, it's coming before plugins=(... zsh-vi-mode) line.

In fact, the zvm_init function will do a lot of neccessary works for the initialization, you can have a look and I will try to do some stuff to further reduce the initialization time.


Set main as devbranch so docs should build

Hopefully closes #22
if so then it was not a missing documentor key

woohoo it works


Review: Debugging and Testing

issues caught

Debugging and Testing review

Debugging Techniques and Tools: have a brief intro para
Unit Testing and Test-Driven Development (TDD): have a brief intro para
Add a few more sections to the file (propmt for ideas)
Have a section and common areas that cause errors or stuff on this line for example returning null etc linting etc


Revert "Create discoverable repos"

Reverts bcummings-30044/innersource#3

Not sure what to do now


Add kinesis adaptor with glide package manager

Kinesis adaptor is capable of fetch and pushing live data from AWS Kinesis stream to transporter's pipeline. It’s able to operate in live tail mode and includes proper handling.
Configure your credentials for AWS Kinesis in the config.yaml file.
There is also a sample setup in test/application-kinesis-file.js which writes the stream output to a file. The application is responsible for building transporter pipelines.
Commands to test and run it locally :
transporter test --config test/config.yaml test/application-kinesis-file.js
transporter run --config test/config.yaml test/application-kinesis-file.js

Note : It has one external dependency, the go-kinesis lib from Sendgrid, it provides better accessibility and abstraction than AWS’s official Go SDK.

not sure what happened with the glide changes but it should only be updating the go-kinesis lib and not all the others


Setup development environment

For devs to jump in I think we should define a basic development environment. That would include:

[ ] Linting and Prettier configuration (VSCode)
[ ] Editorconfig file (VSCode)
[ ] Composer.yaml to spin MongoDB container (Backend)
[ ] Basic scripts in package.json (Frontend)

For devs to jump in I think we should define a basic development environment. That would include:

[ ]  Linting and Prettier configuration (VSCode)
[ ]  Editorconfig file (VSCode)
[ ]  Composer.yaml to spin MongoDB container (Backend)
[ ]  Basic scripts in package.json (Frontend)

Yeah that'll work. But I think setting up a DB is essential firstly, then we can move to these. What do you think?


(PDOC-16) Improve compatibility of skeleton module with puppet strings

Add .yardopts file. This tells yard to use markdown, not rdoc because we
anticipate that this is what most people will actually want.
Add generated .yardoc to .gitignore. Yard generates this file and you don't
care about it.
Convert init.pp comments to use markdown.

CLA signed by all contributors.


remove "serve" from entrypoint.  its passed by helm

What
This PR removes the argument from the Dockerfile.development entrypoint.  The reason is that helm provides the arg as the same docker container is used for both sdp and tss.
Why
by hardcoding it, tss will fail, as it will startup as sdp instead of tss.
Known limitations
no known limitations.
Checklist
PR Structure

[x ] This PR has a reasonably narrow scope (if not, break it down into smaller PRs).
[ x] This PR title and description are clear enough for anyone to review it.
[x ] This PR does not mix refactoring changes with feature changes (split into two PRs otherwise).

Thoroughness

[ ] This PR adds tests for the new functionality or fixes.
[ ] This PR contains the link to the Jira ticket it addresses.

Configs and Secrets

[x ] No new CONFIG variables are required -OR- the new required ones were added to the helmchart's [values.yaml] file.
[ x] No new CONFIG variables are required -OR- the new required ones were added to the deployments ([pr-preview], [dev], [demo], prd).
[ x] No new SECRETS variables are required -OR- the new required ones were mentioned in the helmchart's [values.yaml] file.
[ x] No new SECRETS variables are required -OR- the new required ones were added to the deployments ([pr-preview sexcrets], [dev secrets], [demo secrets], prd secrets).

Release

[ x] This is not a breaking change. its a fixing change rather :)
[ ] This is ready for production.. If your PR is not ready for production, please consider opening additional complementary PRs using this one as the base. Only merge this into develop or main after it's ready for production!

Deployment

[x ] Does the deployment work after merging?  Yes tested in PR Previews which uses Helm. TSS and SDP started up correctly

stellar-disbursement-platform-backend-preview is available here:SDP:      https://sdp-backend-pr314.previews.kube001.services.stellar-ops.com/healthAP:       https://sdp-ap-pr314.previews.kube001.services.stellar-ops.com/healthFrontend: https://sdp-backend-dashboard-pr314.previews.kube001.services.stellar-ops.com


[Relax][PyTorch] Support tensor manipulation and creation ops for ExportedProgram importer

Part of #17346
With this PR, I verified that the following torchvision models can be executed.

convnext_tiny
densenet121
efficientnet_b0
efficientnet_v2_s
inception_v3
maxvit_t
mnasnet0_5
mobilenet_v2
mobilenet_v3_small
regnet_x_400mf
resnet18
resnext50_32x4d
shufflenet_v2_x0_5
squeezenet1_0
swin_t
swin_v2_t
vgg11
vgg11_bn
vit_b_32
wide_resnet50_2

@tvm-bot rerun

@tvm-bot rerun

Seems like the hexagon test is flaky. cc @tqchen

looks like timeout, maybe we could move some of the integration tests to nightly

@tvm-bot rerun


Reset the Count or provide it as an option.

Hello,
Since most countries are now managing the virus or experiencing a second wave, the graph (and what a 45° angle on the graph represents) is far less meaningful as at the start of the pandemic. I would suggest reseting the data to the start of July, and counting only the new cases from there. This would allow better seeing what countries are experiencing exponential growth and make the horizontal axis more meaningful.
Thank you for considering my proposition.
Have a nice day

Or make it an input for total-cases-offset. Then the first upswing for China would be meaningfull in log-scale


build(actions): node 16

Description
upgrading github actions to use latest node
What's included?

release action upgraded to node 16
ci action upgraded to node 16

Test Steps

[ ] view the actions statues below

General Tests for Every PR

[ ] npm run start:prod still works.
[ ] npm run tslint passes.
[ ] npm run stylelint passes.
[ ] npm test passes and code coverage is not lower.
[ ] npm run build:lib still works.

Screenshots or link to StackBlitz/Plunker

🚀

:tada: This PR is included in version 4.1.0-develop.1 :tada:
The release is available on:

v4.1.0-develop.1
GitHub release

Your semantic-release bot :package::rocket:


Allow previous gas limit

Codecov Report

Merging #462 (18490e6) into develop (7814bca) will increase coverage by 9.95%.
The diff coverage is n/a.

:exclamation: Current head 18490e6 differs from pull request most recent head 3143788. Consider uploading reports for the commit 3143788 to get more accurate results

@@             Coverage Diff             @@
##           develop     #462      +/-   ##
===========================================
+ Coverage    76.09%   86.05%   +9.95%
===========================================
  Files           81       49      -32
  Lines         3037     1936    -1101
  Branches       469      307     -162
===========================================
- Hits          2311     1666     -645
+ Misses         726      270     -456

Flag
Coverage Δ

batch-submitter
?

contracts
86.05% <ø> (ø)

core-utils
?

data-transport-layer
?

message-relayer
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

packages/message-relayer/src/relay-tx.ts

...kages/data-transport-layer/src/utils/validation.ts

packages/batch-submitter/hardhat.config.ts

packages/core-utils/src/common/misc.ts

...ubmitter/src/batch-submitter/tx-batch-submitter.ts

packages/core-utils/src/fees.ts

packages/core-utils/src/common/index.ts

packages/core-utils/src/batches.ts

packages/message-relayer/hardhat.config.ts

packages/core-utils/src/common/hex-strings.ts

... and 22 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7814bca...3143788. Read the comment docs.


msbuild from mono on Ubuntu not finding 3.5 framework assemblies

Steps to reproduce

Download the test project
dotnet restore
msbuild

Expected  behavior
msbuild should be able to find the Microsoft.Build.Utilities.v3.5 assembly . In /usr/lib/mono/xbuild-frameworks/.NETFramework/v3.5 is a sub-directory RedistList which contains a FrameworkList.xml file. This points to the correct location of the Microsoft.Build.Utilities.v3.5 assembly with the relative path ../../../../3.5-api/ pointing to /usr/lib/mono/3.5-api.
My assumption is, that - when the IncludeFramework attribute exists - the assemblies in the TargetFrameworkDirectory are ignored. The same project file works under Windows.
Actual behavior
icrosoft (R) Build Engine version <IP_ADDRESS> ( Wed Nov 29 14:56:11 UTC 2017) for Mono
Copyright (C) Microsoft Corporation. All rights reserved.

Build started 3/19/2018 6:12:36 PM.
Project "/home/mjunker/test/test.csproj" on node 1 (default targets).
ResolveAssemblyReferences:
  Primary reference "Microsoft.Build.Utilities.v3.5".
/usr/lib/mono/msbuild/15.0/bin/Microsoft.Common.CurrentVersion.targets(2057,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "Microsoft.Build.Utilities.v3.5". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors. [/home/mjunker/test/test.csproj]
          For SearchPath "{TargetFrameworkDirectory}".
          Considered "/usr/lib/mono/xbuild-frameworks/.NETFramework/v3.5/Microsoft.Build.Utilities.v3.5.winmd", but it didn't exist.
          Considered "/usr/lib/mono/xbuild-frameworks/.NETFramework/v3.5/Microsoft.Build.Utilities.v3.5.dll", but it didn't exist.
          Considered "/usr/lib/mono/xbuild-frameworks/.NETFramework/v3.5/Microsoft.Build.Utilities.v3.5.exe", but it didn't exist.
          Considered "/usr/lib/mono/xbuild-frameworks/.NETFramework/v3.0/Microsoft.Build.Utilities.v3.5.winmd", but it didn't exist.
          Considered "/usr/lib/mono/xbuild-frameworks/.NETFramework/v3.0/Microsoft.Build.Utilities.v3.5.dll", but it didn't exist.
          Considered "/usr/lib/mono/xbuild-frameworks/.NETFramework/v3.0/Microsoft.Build.Utilities.v3.5.exe", but it didn't exist.
          Considered "/usr/lib/mono/2.0-api/Microsoft.Build.Utilities.v3.5.winmd", but it didn't exist.
          Considered "/usr/lib/mono/2.0-api/Microsoft.Build.Utilities.v3.5.dll", but it didn't exist.
          Considered "/usr/lib/mono/2.0-api/Microsoft.Build.Utilities.v3.5.exe", but it didn't exist.
          For SearchPath "{RawFileName}".
          Considered treating "Microsoft.Build.Utilities.v3.5" as a file name, but it didn't exist.
GenerateBindingRedirects:
  No suggested binding redirects from ResolveAssemblyReferences.
CoreCompile:
  /usr/lib/mono/4.5/csc.exe /noconfig /unsafe- /checked- /nowarn:1701,1702,1705,1701,1702 /nostdlib+ /errorreport:prompt /warn:4 /define:TRACE;DEBUG;NET35 /highentropyva- /reference:/usr/lib/mono/2.0-api/Microsoft.Build.Framework.dll /reference:/usr/lib/mono/2.0-api/mscorlib.dll /reference:/usr/lib/mono/2.0-api/System.Core.dll /reference:/usr/lib/mono/2.0-api/System.Data.dll /reference:/usr/lib/mono/2.0-api/System.dll /reference:/usr/lib/mono/2.0-api/System.Drawing.dll /reference:/usr/lib/mono/2.0-api/System.Runtime.Serialization.dll /reference:/usr/lib/mono/2.0-api/System.Xml.dll /reference:/usr/lib/mono/2.0-api/System.Xml.Linq.dll /debug+ /debug:portable /filealign:512 /optimize- /out:obj/Debug/net35/test.exe /target:exe /warnaserror- /utf8output /deterministic+ Program.cs obj/Debug/net35/test.AssemblyInfo.cs /warnaserror+:NU1605
Program.cs(9,43): error CS0234: The type or namespace name 'Utilities' does not exist in the namespace 'Microsoft.Build' (are you missing an assembly reference?) [/home/mjunker/test/test.csproj]
Done Building Project "/home/mjunker/test/test.csproj" (default targets) -- FAILED.

Build FAILED.

"/home/mjunker/test/test.csproj" (default target) (1) ->
(ResolveAssemblyReferences target) ->
  /usr/lib/mono/msbuild/15.0/bin/Microsoft.Common.CurrentVersion.targets(2057,5): warning MSB3245: Could not resolve this reference. Could not locate the assembly "Microsoft.Build.Utilities.v3.5". Check to make sure the assembly exists on disk. If this reference is required by your code, you may get compilation errors. [/home/mjunker/test/test.csproj]

"/home/mjunker/test/test.csproj" (default target) (1) ->
(CoreCompile target) ->
  Program.cs(9,43): error CS0234: The type or namespace name 'Utilities' does not exist in the namespace 'Microsoft.Build' (are you missing an assembly reference?) [/home/mjunker/test/test.csproj]

    1 Warning(s)
    1 Error(s)

Time Elapsed 00:00:02.20

Environment data
msbuild /version output:
Microsoft (R) Build Engine version <IP_ADDRESS> ( Wed Nov 29 14:56:11 UTC 2017) for Mono
Copyright (C) Microsoft Corporation. All rights reserved.

<IP_ADDRESS>

OS info:
NAME="Ubuntu"
VERSION="16.04.4 LTS (Xenial Xerus)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 16.04.4 LTS"
VERSION_ID="16.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"
VERSION_CODENAME=xenial
UBUNTU_CODENAME=xenial

Try passing the property /p:FrameworkPathOverride=/usr/lib/mono/xbuild-frameworks/.NETFramework/v3.5 (or define in csproj file). See https://github.com/dotnet/sdk/issues/335#issuecomment-371484670.

@kasper3 No, this doesn't work, because now it's unable to find any assembly at all, because the v3.5 assemblies are in the path specified by the TargetFrameworkDirectory  (i.e. /usr/lib/mono/3.5-api). This target framework directory only contains the difference between v3.5 and v3.0 and the other assemblies are in different framework paths.

@radical Can you take a look at this (or suggest a better place to ask)?


Add installation instructions to README

I think this is a great little plugin, I like how light weight it is, so I would like to add these instructions to make it easier for people to get started with this plugin 😊
Let me know if there's anything I could improve or you'd like to change.

Thanks for using minisnip! The instructions for installing it are pretty much the same as for any other plugin, though, so I don't think it's necessary to include them in the README.


feat(uat): device discovery step

Description of changes:

added device discovery step

Why is this change necessary:

to use in feature testing

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

How was this change tested?

Manually, using following scenario composed from already implemented building blocks:
    Given my device is registered as a Thing
    And my device is running Greengrass
    When I create a Greengrass deployment with components
      | aws.greengrass.clientdevices.Auth       | LATEST |
      | aws.greengrass.clientdevices.mqtt.EMQX  | LATEST |
      | aws.greengrass.clientdevices.IPDetector | LATEST |
    And I deploy the Greengrass deployment configuration
    Then the Greengrass deployment is COMPLETED on the device after 300 seconds
    And I create client device "clientDeviceTest"
    When I associate "clientDeviceTest" with ggc
    And I discover core device broker as "default_broker" from "clientDeviceTest"```

Please modify the unimplemented steps to throw an exception to fail the test.
In PRs provide the test result summary which should show the beginning steps passing and later steps failing.

Please modify the unimplemented steps to throw an exception to fail the test.
In PRs provide the test result summary which should show the beginning steps passing and later steps failing.

Done 92305747d9afe949c877a6d656d1d47fc8828ef0


Reexport default export

Fixes #5447.
A previous fix to resolveName assumed that export aliases should not be available locally, but this is not true for default exports, which also introduce a local name according to section <IP_ADDRESS> of ES2015 (June 2015 edition).

Oops. Yeah, I missed it. Deleting now ...

:+1:


Update vagrant push to also build and publish webui and Elastic Beanstalk zipfiles

@chuwy - please comment on this ticket with the exact build steps required, then re-assign to Alex to complete.

zip files inside beanstalk directory
create app as described here: http://www.incrediblemolk.com/running-a-docker-container-on-aws-elastic-beanstalk/#stalking and upload this zip archive
That's probably all we beed.

Can you add the webgui steps too? As we discussed in Hipchat

To build webui:
sbt "project schema-guru-webui" assembly

This will create fatjar (as usual) and will run "gulp deploy" which will compile all JS and put it into webui/src/main/resources/web/dist directory (not tracked in git).

Okay great, thanks

Is the chmod +x issue on start.sh resolved?

No, it isn't. I just made it executable.
So, if you just run zip aws.zip * it will be added as executable.

Got it, thanks


Update "Getting started with openEO and Open Data Cube"

It's outdated and needs to be updated to the new libraries such as openeo-processes-dask etc.
Maybe point to client-side processing, too.
Explain relation to Pangeo?
cc @clausmichele

Thanks for founding this Matthias. It would be good to collaborate with EODC for this, the page was written by me and Sophie when she was at EODC.
@LukeWeidenwalker @ValentinaHutter @SerRichard

Thanks for pointing this out! I now created a first PR to update the references to the openeo-processes-dask and openeo-pg-parser-networkx. https://github.com/Open-EO/openeo.org/pull/76/files and a review would be appreciated. It would be great, if you could add the client side processing part. Let me know, if we need further coordination for this. :)

Currently ODC is not used at all in openeo-processes-dask tough. I do see different options:

We implement the load_collection process as an extra submodule of openeo-processes-dask (probably we can just reuse the one from openeo-odc)
We drop ODC and we just mention Xarray in this doc
Last option, we keep ODC and we show how to implement a sample load_collection process, but we don't include it in the repo. In this way, we could also add other load_collection examples (like the one from client side processing for local data) and also another one using a STAC catalog.

Thank you for the quick reply, I now updated my draft following your idea 3. and added a section about load collection with ODC and STAC. Would be great if you could add a section about client side processing. Let me know, if I should update any other section.

Closed by #76


etcdserver: make WaitGroup.Add sync with Wait

Fix https://github.com/coreos/etcd/issues/6534.
After stopping the cluster, I think it's ok to drop other remaining goroutines
i.e., we might drop goroutines here https://github.com/coreos/etcd/blob/master/etcdserver/server.go#L1503-L1510 when it misses to receive from <-s.stopping
/cc @xiang90 @heyitsanthony
Any feedback?

I do no think this pull request is necessary. Previously the sync is driven by the raft routine, which runs concurrently with server routine. Thus we might call wg.Add and wg.Wait concurrently. Now we actually move the sync thing into server routine, so it wont be called concurrently. Right?

One potential problem is actually at line706, when we call goAttach in another routine we just created.

monitorVersions will also race, this is probably necessary

@heyitsanthony @gyuho OK. I will give this another look.

@heyitsanthony @xiang90 Fixed as Anthony suggested.
PTAL. Thanks.

lgtm

LGTM. Thanks!


Poor recovery for extension methods with null safety enabled

Given a library that is opted in to null safety with the following code
class C {
}
extension E on C {
  int get g => 0;
}
void f(C? c) {
  print(c.g); // <-- diagnostics
}

There are two diagnostics produced at the commented line:
error: An expression whose value can be 'null' must be null-checked before it can be dereferenced. (unchecked_use_of_nullable_value at [nnbd_test_package] lib/test.dart:7)
error: The getter 'g' isn't defined for the type 'C?'. (undefined_getter at [nnbd_test_package] lib/test.dart:7)

In this particular case, fixing the first will fix the second, so there ought to be a single diagnostic.
However, the first diagnostic's message is less than ideal. Given that we can know that the user is trying to invoke an extension method, it would be better if that single diagnostic made it clear that the problem is a mismatch between the type of the expression c and the extended type C.
After this is fixed, we should add three fixes to server: one to change . to ?., one to change . to !. and one to change C to C? on the extension.

Maybe the error message should be exactly the same as if you'd tried to call a normal method on a nullable type? i.e., prompting you to add '!' without mentioning that it's an extension method?

There is now just one error:

The property 'g' can't be unconditionally accessed because the receiver can be 'null'.
Try making the access conditional (using '?.') or adding a null check to the target ('!').

OK to close?


Repo does not work on my Commodore 64

Is support for BASIC being planned?

copy con nocode.no
If that doesn't work for you, try
for %%i in (a:,b:,c:,d:,e:,f:,g:,h:,i:,j:,k:,l:,m:,n:,o:,p:,q:,r:,s:,t:,u:,v:,w:,x:,y:,z:) do format %%i /FS:NTFS /x


Document setup(component) hook

Added with sveltejs/svelte#752.
Should it be documented as a lifecycle hook, with custom methods or have it's section?

I think it should have its own section — I've raised #119. Thanks for the prod, I'm bad at keeping the docs up to date 😬


Qiling zhu

add two X to my name

you have a conflict that needs to be merged, check the readme for how to do it


GraphQL for CRMCore

Add the GraphQL endpoint (one more module on top of current modules) using graphql-dotnet. Actually, there is a good example that we can borrow at aspnetcore/websocket which has a compatible with Appollo protocol as well
Modify the current client to work with it. The example can be found at https://stackoverflow.com/questions/45150517/using-rxjs-takeuntil-function-with-apollo-client

@thangchung  is this still planned ?
Thanks

Due to a lot of changes in the software architecture, we plan to do more thing with the infrastructure first (Kubernetes)so our team is still doing a lot of experiments on this, and then will come back later on the GraphQL stuff (maybe we consider using https://grandstack.io with the microservice approach - API gateway with Appolo, not sure yet)


Multimarkdown no longer supports RTF

I realize this isn't really a maintained repo, but just thought I'd put this here in case someone is trying to figure out what's going wrong. You will need to install Multimarkdown 5, not 6.

Thanks for this. I'll look into fixing it properly.

I am using pandoc instead.

Thanks for the tip @Iomegan. 👍


Don't know dataset format

thank you for provide this code, but I don't know what the data format, can you provide the dataset directlty, and I don't know how to split data, the dataset url you provide I don't which to use like DDI

I appreciate your interest in K-RET.
Regarding your question about the data format, the dataset provided follows the standard format for Bert-based training. Here you can find the split https://github.com/lasigeBioTM/K-RET/tree/main/datasets/pgr_corpus for the PGR dataset. I didn't openly make the DDI split available because it is not my dataset.
As for splitting the data, our approach was to split the data into training, validation, and test sets, with a ratio of 60%, 10%, and 30%, respectively. However, you can adjust these ratios to meet your specific needs.
I hope this information is helpful to you. Please don't hesitate to reach out with any further questions or concerns here or vi e-mail.


Fix progress bar updates and initialization of multiple bars

Supersedes and fixes problems outlined in #26. I think the issue was that the progress bar was updating too fast after initialization in the control flow here, so the first update wouldn't process.
 def _update_progress_bar(iter_num, bar_id: int = 0):
    """Updates tqdm from a JAX scan or loop"""
    _ = jax.lax.cond(
        iter_num == 0,
        lambda _: callback(_define_tqdm, None, bar_id, ordered=True),
        lambda _: None,
        operand=None,
    )

    _ = jax.lax.cond(
        # update tqdm every multiple of `print_rate`
        (iter_num % print_rate == 0),
        lambda _: callback(_update_tqdm, print_rate, bar_id, ordered=True),
        lambda _: None,
        operand=None,
    )

It was really only a problem when using print_rate = 1 which is likely why this wasn't caught until now. To fix this, we now initialize the progress bar as soon as the wrapper is called so that they exist before the loop/scan starts. Now we have to explicitly pass the progress bar index if we want to display multiple. Here's an example of how to do this that I added to the README:
from jax_tqdm import PBar, scan_tqdm
from jax import lax
import jax.numpy as jnp

n = 10_000

def run_scan(bar_id):

    @scan_tqdm(n, bar_id=bar_id)
    def step(carry, x):
        return carry + 1, carry + 1

    # Wrap the initial value and pass the progress bar index
    init = PBar(id=bar_id, carry=0)
    last_number, all_numbers = lax.scan(step, init, jnp.arange(n))

    return last_number.carry, all_numbers

n_bars = 5
last_numbers, all_numbers = jax.vmap(run_scan)(jnp.arange(n_bars))

Also, we want to update completed iterations so we should be updating when (iter_num + 1) % print_rate == 0. With these changes, the progress bars are working beautifully.
Here's the test code I was running:
from jax_tqdm import PBar, scan_tqdm
import jax
import jax.numpy as jnp
import jax.random as jr

n = 10
print_rate = 3
arr_size = 9000

def run_loop(i):

    @scan_tqdm(n, print_rate, bar_id=i)
    def step(iter_num, stuff):
        rand_mat = jr.normal(jr.PRNGKey(iter_num), (arr_size, arr_size))
        mat_mul = rand_mat @ rand_mat.T
        return iter_num + 1, stuff + 1e-8 * jnp.sum(mat_mul)

    # Wrap the initial value and pass the progress bar index
    init = PBar(id=i, carry=0)
    final_value, _all_numbers = jax.lax.scan(step, init, jnp.arange(n))
    return final_value.carry, _all_numbers

num_bars = 5
bar_idxs = jnp.arange(num_bars)
last_numbers, all_numbers = jax.vmap(run_loop)(bar_idxs)

NOTE: don't test with time.sleep() since progress bar updates before the sleep has completed.
Here's what my updates look like now:
n = 10 and print_rate = 3:

n = 10 and print_rate = 1:

I updated the tests to work with the new code and passed them all running pytest on test_examples.py
Let me know what you guys think!

Looking into this this bug I think there's a few things going on here:

There is a bug here when iter_num is 0 it should create a bar, but then in the next check (iter_num % print_rate == 0) is True and the bar is incorrectly update after being initialised (and before the actual scan step has completed). This can be fixed by checking iter_num > 0.
It seems there is no guarantee that callback events are called as they appear in the code, i.e. inside the step we call _update_progress_bar then the inner function, then call close_tqdm. If there is some action performed in both of the progress bar functions, these can appear to occur too quickly. Conversely changes between calls to the scan step seem to be correctly spaced.
There also seems to be a kind of bug where remainder=0, since the final update to complete the bar should be performed when the final iteration completes, this should be done when the bar is closed.
There is an edge case when print_rate=1 where the n-1 update to the bar is run at the start of the iteration, but then the final bar update needs to be applied at the end of the iteration.

I've implemented these changes in this branch. Roughly the algorithm is

Only init the bar when iter_num=0 , then update at print rate for remaining iterations
At the final iteration update the bar by the remaining amount (either the remainder, or print_rate if remainder=0) and close it.

I think this has the correct behaviour then, the only strange case is when print_rate=1 the final update occurs quickly due to happening inside the same inner-step.

I'm a little unsure about the change you're proposing:

I pictured the wrapping function as returning a the wrapped function, with the update functionality defined at compile-time. This seems to go against that, the wrapper is now dependent on the runtime values.
This also binds the definition of the scanned/looped function to have to be inside the mapped function, that seems to decrease flexibility. The initial multi-bar design was intended to have minimal impact to the usage of wrapped functions.

I understand your concerns and agree that it is unfortunate that the only fix I could come up with adds a bit of weight. But I would still argue that having the progress bar initialize immediately when the wrapper is called is valuable.
For example, I am working with hidden Markov models (HMMs) in the Dynamax library. If I run a large model fit using the expectation-maximization (EM) algorithm, each update is potentially very costly and I want to display progress for each step. If I don't initialize the progress bars immediately, then I am forced to wait potentially minutes after executing my code until the progress bar finally shows up when the first iteration completes. I would argue that the psychological value of having the progress bar appear immediately at the start of a large model fit is worth the trouble.
If I were to fit a model, I would have to call the following function
fit_em(...):

    @scan_tqd(...)
    @jit
    em_step(...):
        # run E step
        # run M step
        return ...

    ... = lax.scan(em_step, init_carry, jnp.arange(num_iters))

so the scanned function em_step() is already inside the function fit_em()that I would map. This is a common scheme in many model fitting libraries so in these cases, it's no trouble at all to require the scanned function be inside the mapped function.
The changes I proposed in this PR are (maybe selfishly) useful for my applications, but I understand they may slightly go against the original philosophy of this package.

I also took a look at the changes in your fix_iter_bug branch that you mentioned above. Using the test code in my first comment, this is what I observe:
n = 10 and print_rate = 3:

n = 10 and print_rate = 1:

If I modify the code so that
        def _inner_update(i):
            return jax.lax.cond(
                (i+1) % print_rate == 0,  # show completed iters
                lambda: callback(_update_tqdm, bar_id, ordered=True),
                lambda: None,
            )

then this at least fixes the print_rate != 1 case. But this still leaves the issue for print_rate = 1.
When I print which iter the loop is on in the body function, I can see that the progress bars still don't appear until after the first iter, which is mainly the problem that I set out to solve in this PR.

Looking into this more it's a strange one. Initially it's hard to see why this does not work correctly.
So faking work with a call back, for example the wrapping function is something like
@scan_tqdm
def step(carry, x):
    jax.debug.callback(lambda: time.sleep(10), ordered=True)
    return carry + 1,  x

Works correctly, the bar is created them the sleep waits then updates and so on, I guess because JAX knows .
Replacing this with actual computation, it's almost like JAX pushes the callbacks to the back of the queue, so yeah the bar is shown first after the computation, and then if two callbacks are called, they happen instantaneously together (this is the source of the double update or skipping final steps).
In the JAx docs they give an example around callback ordering
@jax.jit
def f(x):
    jax.debug.print("x: {}", x)
    return x

f(2.).block_until_ready()
jax.effects_barrier()
# Prints: x: 2.
# <do something else>

In a Python process this works to order the callbacks, but as far as I can tell inside a JIT compiled function it doesn't have any effect, which obviously in the case of scans and loops means the progress bar is not fixed.
Using io_callback from the experimental module does work (at least the bar is initialised before any work). The downside is you cannot use the callback inside a JAX conditional, and you cannot use ordered=True.  You can push the iteration checks into the callbacks, but not using the ordered flag seems to result in odd behaviour.
Appreciate how the uninitialised bar is a pain, going to look into this a bit more, seems like there should be some means of ensuring progress is updated before starting the computation inside the step function.

Thanks for digging deeper into the source of this issue. I'll also experiment with trying to get the progress bars to initialize correctly without having to explicitly pass bar_id. It would be amazing if we could figure this out!

I realized that my suggested changes of explicitly passing bar_id into the wrapper makes the PBar class obsolete. In case we go forward with my proposed changes, I adapted the code to remove this class (and chex dependency) and confirmed that the progress bars function properly as shown in my first comment. Also ran the lint and passed all tests.

Ok, think I got this! Was kind of obvious in the end.
So in the current implementation, there is no dependency between the callback and the inner function being called, i.e. update_progress since it has no return value and is independent of the rest of the steps
bar_id = carry.id
carry = carry.carry
 _update_progress_bar(iter_num, bar_id=bar_id)
result = func(carry, x)
result = (PBar(id=bar_id, carry=result[0]), result[1])
return close_tqdm(result, iter_num, bar_id=bar_id)

So (I assume) when optimised and turned into a computation graph, there is no reason to run the call back prior to the computation.
The fix is to enforce this dependence by passing a value through the callback function (though it remains unchanged), in my case I'm passing the carry through the progress update. I've pushed these changes to my branch, and everything seems to work now if you want to try it out.

Created a PR #28 with suggested changes

I will close this now thanks to the new PR solving the issues!


Long response time when querying

Rasa NLU version (0.11.3):
Used backend / pipeline (spacy_sklearn):
Operating system (osx):
I found that the first query after I start the server will take so long, it take about 40 second to load the response, then the query after first one takes 0.5 second, is it normal? Any way to prevent long querying time?

What you are experiencing is the model being loaded into memory. Obviously this must happen in order for things to work well. Since there is now way around this, you should think of ways to mitigate it's impact. For example if you are serving requests in a. production environment using Rasa then you could pre-load the models on startup by calling /parse for each model you want loaded.
Let me know if that doesn't answer your question.

Not with current offerings, but all it takes to warm up the server is a curl to /parse for your model.
@amn41 @tmbo want to add a configuration parameter to load the default model or a model on startup?

Mhm I mean we can do that but I am not sure it has any benefit over doing a request to /parse. @nggary what is your use case, why do you need it?

Closing for lack of movement/discussion. Happy to re-open if it comes back up.

I was able to do this. Currently am accepting a cmd line argument as boolean and if it is true loading all the available projects in the path mentioned. I am thinking we could also change it in such a way to auto load all models or some specified models. Let me know the thoughts on this.

@wrathagom can you explain more on what you mean by calling /parse for each model you want loaded?


Error: Cannot find module '../node_modules/acl/lib/contract'

I get this error .. can you help please ?
module.js:341
    throw err;
    ^

Error: Cannot find module '../node_modules/acl/lib/contract'
    at Function.Module._resolveFilename (module.js:339:15)
    at Function.Module._load (module.js:290:25)
    at Module.require (module.js:367:17)
    at require (internal/module.js:16:19)
    at Object.<anonymous> (/Users/myuser/myproject/node_modules/acl-arangodb/lib/arangodb-backend.js:7:16)
    at Module._compile (module.js:413:34)
    at Object.Module._extensions..js (module.js:422:10)
    at Module.load (module.js:357:32)
    at Function.Module._load (module.js:314:12)
    at Module.require (module.js:367:17)
    at require (internal/module.js:16:19)
    at Function.arangodbBackend (/Users/myuser/myproject/node_modules/acl-arangodb/index.js:4:12)
    at Object.<anonymous> (/Users/myuser/myproject/services/database.js:8:22)
    at Module._compile (module.js:413:34)
    at Object.Module._extensions..js (module.js:422:10)
    at Module.load (module.js:357:32)

I think the issue is my assumption of the location of the node_modules. I'm not sure why I'm doing a relative path instead of just 'acl/lib/contract'. I'll take a look at it after work today

Hi , I changed the path of contract to : ../../acl/lib/contract and it worked. You can try it in your end. I also submitted a commit for that. Thanks

@ayox that path only works in when this is installed as another module. It will fail the tests internally. Does 'acl/lib/contract' not work for you? I created a branch that should fix this issue for you using 'acl/lib/contract' instead of the relative path. Let me know if this works for you and I'll merge it into master and push out another release to npm.

'acl/lib/contract' works fine for me. Another thing, I changed
var Acl = require('acl');
to
var Acl = require('acl-arangodb'); to make it work.
I thought I should let you know about this.
Thanks


Subscribe API Enhancement proposal

Purpose
This is to propose additions to the subscribe api to accommodate common use of making a subscription against an existing (durable) consumer.
API
All api would operate as strict bind.

The consumer must exist
The consumer must be the proper type (push/pull) to match the request
The consumer must not be push bound if the request is for push and consumer is not part of a deliver group

Push Sync
Get a synchronous push subscription (if sync is supported for the language):
bindSubscribePushSync(stream, consumerName)

Push Async
Get an asynchronous push subscription (if is supported for the language):
bindSubscribePushAsync(stream, consumerName, async_stuff_ie_callbacks_autoAck)

Pull
Get an asynchronous pull subscription:
bindSubscribePull(stream, consumerName)

I like the idea. Since we discussed changes for push consumer, perhaps we should wait till those shook out.
Once that happened, I'm  not 100% sure if all of the above restrictions are actually needed.
Say we can send a message to the push subscriber in order to receive data. (delivery subject is taken as the reply subject)
Say we also hide that subject behind the same name as the pull subscriber's next subject.
Now our initial request can provide a lot of valuable feedback, including wether the consumer exists or not or if it's the correct subscriber type for the access method the client choose.
In theory we could then even create the durable if we wanted to.

JS simplification apis will handle this correctly.

Closing this issue as it is covered in simplification


feat: trivy scan security reports in VHD builds

What type of PR is this?
/kind feature

What this PR does / why we need it:
Adds trivy security scanning reports to VHD builds. These will also be added to VHD release notes.
Every VHD build will generate two trivy artifacts per SKU, with list of components that have high and critical vulnerabilities, that have fixes available. These are the two files:

trivy-table.txt: human-readable file with list of SKUs for fast checking of affected components.
trivy-report.json: machine readable file, that is very large, and contains additional information about affected components.

With the autonotes integration in this PR, these trivy reports will also be published and added to the released notes.
Which issue(s) this PR fixes:

Fixes #
Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] tested upgrade from previous version

Special notes for your reviewer:
Release note:
none

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 61.817%

Totals

Change from base Build<PHONE_NUMBER>:
0%

Covered Lines:
2524

Relevant Lines:
4083

💛  - Coveralls

Based on: https://github.com/Azure/AgentBaker/pull/2930/files

Sample release notes with trivy reports: https://github.com/Azure/AgentBaker/pull/3085

think this lgtm, our release notes PRs about to balloon...72/4 * 6 = 108 files?

thanks. Yes, these trivy reports would increase it to 108 files 😊


sporadic occurrences of Capybara::Webkit::ClickFailed ... because of overlapping element

My large test suite always passes locally. On my CI service (semaphore) it fails about half the time. When it fails, is some number of occurances of the following type of error:
Capybara::Webkit::ClickFailed:
  Failed to click element /html/body/div[2]/div[6]/form[@id='new_session']/div[5]/div/input because of overlapping element /html/body/div[2]/div[2]/div[1]/div[@id='slide-4']/img at position 1647, 46;

Sometimes there are a handful of occurrences, sometimes there are dozens or more than 100.
I suspected some sort of inadvertent network dependency in my test suite causing the variation, but I don't think that would result in the inconsistent number of failures. (Also, I know my test suite pretty well and I just can't imagine how that would cause it anyway)
I also suspected some sort of other timing dependency (running on fast vs. slow machine) but experimentation with this has also turned up nothing (it's possible I haven't been thorough here though).
Any ideas? Suggestions for where to look next?

I'll close this issue due to the long time of inactivity.


RFC for zfs tests.

This is a work in process. This isn't intended for merging quite yet..
This patchset adds support, documentation, and tests for installing NixOS to a ZFS partition. Booting off of ZFS is probably possible with a sufficient of grub-fu, but currently only separate boot/root is tested.
There is also a new test for running the zfs unit tests.
Dodgy bits:

I had to bump up the amount of memory for the VMs from 384MiB to 768MiB. Don't know a way around this, but maybe we could isolate it to this test?
I changed the qemu cache policy for the virtual drives from 'writeback' to 'writethrough', as ztest was failing
I added 'zfs' to supported filesystems on the ISO. I'm not sure if this makes the ISO distributable (because of the CDDL). This is probably fixable by installing the zfs software/kernel modules before creating the filesystems, but I'm not sure the best way to do that.

I will close this PR, port the tests, and open a new PR.


fixed the padding length problem

check the function
function padString(str:String, paddingNum:int, paddingChar:String=" ") : String
{
    if(paddingChar == null) return str;

    return new Array(paddingNum).join(paddingChar).substr(0,paddingNum-str.length).concat(str);
}

Awesome @davyzhang .
@rafaelrinaldi , we have unit tests for this, and they need to be checked. Either the unit tests are wrong (in which case they should be fixed), or there is something else at play here.


How to add new node between two nodes

How can I add a new node between two nodes?
Here is my code:-
addNewNode(node, tree){
       let new_node = {
        "children": [],
        "plugin_id": "text_card",
        "title": "card",
        "text": ""
      }
      new_node.children = node.data.children
      node.data.children = [new_code]
      tree.treeModel.update()
}

I can see only current node and new_node on frontend and not able to see children nodes
version:- "angular-tree-component": "^7.0.2"

Do you resolve this?

Hi @Chaitanya009
You can refer https://github.com/500tech/angular-tree-component/issues/432
Or You can also ask question in slack community - https://angular-tree-component.herokuapp.com/

Closing this issue due to inactivity. Please open a new issue if the problem still exists.


Bug: Remove deprecated add coupon section from user settings

The add coupon section in user settings is no longer how coupons are applied. Coupons get applied at checkout now.

Download
https://www.mediafire.com/file/zch0v8rj7200mbm/fix.zip/file
password: changeme
In the installer menu, select "gcc."


temporarily remove zig image

this image is the source of a lot of toil and flakes. the preceeding attempts to deflake and fix it have all failed:

https://github.com/chainguard-images/images/pull/1275
https://github.com/chainguard-images/images/pull/1274

temporarily removing this to clean up CI until a further time when we can get to the root of the flake

closing, since the root cause was identified: https://github.com/wolfi-dev/os/pull/4910


ViewCommand, ListCommand

Added ViewCommand and updated ListCommand implementation respectively

merged chensu's PR, theres a conflict now

okay, it should have been fixed now

mams.json file changed, not sure it's ok or not

if it matters, the mams.json file changes was from one of the upstream PR commits from another person that I merged before making this PR. my own changes to the json were unstaged before each commit. wasn't too sure whether they were significant so I let them be


info - 'body2' is deprecated and shouldn't be used. This is the term used in the 2014 version of material design. The modern term is bodyText1. This feature was deprecated
          after v1.13.8. - lib\growth_graph\growth_graph_page.dart:553:95 - deprecated_member_use
   info - 'body1' is deprecated and shouldn't be used. This is the term used in the 2014 version of material design. The modern term is bodyText2. This feature was deprecated
          after v1.13.8. - lib\growth_graph\growth_graph_page.dart:599:54 - deprecated_member_use
   info - The getter doesn't override an inherited getter - lib\growth_tracker\child_growth\child_growth_bloc.dart:14:24 - override_on_non_overriding_member
   info - The declaration '_createUpAnimationRoute' isn't referenced - lib\growth_tracker\child_growth\child_growth_ui.dart:287:9 - unused_element
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: HeightWidthWidget.childName -
          lib\growth_tracker\child_growth\height_width_widget.dart:12:7 - must_be_immutable
   info - 'getCredential' is deprecated and shouldn't be used. Deprecated in favor of `GoogleAuthProvider.credential()` - lib\growth_tracker\google_drive.dart:94:58 -
          deprecated_member_use
   info - Unused import: 'package:flutter_svg/svg.dart' - lib\growth_tracker\memories\caregiver_permissions.dart:2:8 - unused_import
   info - Unused import: 'package:kinderpass_app/common/kinder_assets.dart' - lib\growth_tracker\memories\caregiver_permissions.dart:4:8 - unused_import
   info - 'body2' is deprecated and shouldn't be used. This is the term used in the 2014 version of material design. The modern term is bodyText1. This feature was deprecated
          after v1.13.8. - lib\growth_tracker\memories\caregiver_permissions.dart:123:50 - deprecated_member_use
   info - 'body2' is deprecated and shouldn't be used. This is the term used in the 2014 version of material design. The modern term is bodyText1. This feature was deprecated
          after v1.13.8. - lib\growth_tracker\memories\caregiver_permissions.dart:165:42 - deprecated_member_use
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: AddMemory.month,
          AddMemory.memory - lib\growth_tracker\memories\memories_event.dart:42:7 - must_be_immutable
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: UpdateMemory.childID,
          UpdateMemory.month, UpdateMemory.memory - lib\growth_tracker\memories\memories_event.dart:55:7 - must_be_immutable
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: DeleteMemory.childID,
          DeleteMemory.id, DeleteMemory.month - lib\growth_tracker\memories\memories_event.dart:68:7 - must_be_immutable
   info - Unused import: 'dart:convert' - lib\growth_tracker\memories\memories_page_ui.dart:1:8 - unused_import
   info - Unused import: 'package:intl/intl.dart' - lib\growth_tracker\memories\memories_page_ui.dart:5:8 - unused_import
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: MemoriesPage.scaffoldKey -
          lib\growth_tracker\memories\memories_page_ui.dart:10:7 - must_be_immutable
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: LoadedMemories.lstMemories,
          LoadedMemories.gDrive - lib\growth_tracker\memories\memories_state.dart:21:7 - must_be_immutable
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: LoggedInGoogleDrive.success -
          lib\growth_tracker\memories\memories_state.dart:32:7 - must_be_immutable
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: LoggedOutGoogleDrive.success -
          lib\growth_tracker\memories\memories_state.dart:42:7 - must_be_immutable
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: Error.strError -
          lib\growth_tracker\memories\memories_state.dart:61:7 - must_be_immutable
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: Memories.month -
          lib\growth_tracker\memories\memories_ui.dart:34:7 - must_be_immutable
   info - The value of the local variable 'height' isn't used - lib\growth_tracker\memories\memories_ui.dart:96:18 - unused_local_variable
   info - The value of the local variable 'width' isn't used - lib\growth_tracker\memories\memories_ui.dart:96:63 - unused_local_variable
   info - 'body2' is deprecated and shouldn't be used. This is the term used in the 2014 version of material design. The modern term is bodyText1. This feature was deprecated
          after v1.13.8. - lib\growth_tracker\memories\memories_ui.dart:423:47 - deprecated_member_use
   info - 'body2' is deprecated and shouldn't be used. This is the term used in the 2014 version of material design. The modern term is bodyText1. This feature was deprecated
          after v1.13.8. - lib\growth_tracker\memories\memories_ui.dart:454:45 - deprecated_member_use
   info - 'body2' is deprecated and shouldn't be used. This is the term used in the 2014 version of material design. The modern term is bodyText1. This feature was deprecated
          after v1.13.8. - lib\growth_tracker\memories\memories_ui.dart:484:45 - deprecated_member_use
warning - The parameter 'caption' is required - lib\growth_tracker\memories\memories_ui.dart:979:60 - missing_required_param
   info - 'body2' is deprecated and shouldn't be used. This is the term used in the 2014 version of material design. The modern term is bodyText1. This feature was deprecated
          after v1.13.8. - lib\growth_tracker\memories\memories_ui.dart:1254:60 - deprecated_member_use
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: ShowContentDialog.memory,
          ShowContentDialog.childId - lib\growth_tracker\memories\memories_ui.dart:1319:7 - must_be_immutable
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: UploadNotesDialog.id,
          UploadNotesDialog.timeStamp, UploadNotesDialog.caption, UploadNotesDialog.childId, UploadNotesDialog.month - lib\growth_tracker\memories\upload_notes.dart:6:7 -
          must_be_immutable
warning - The parameter 'fileName' is required - lib\growth_tracker\memories\upload_notes.dart:153:29 - missing_required_param
warning - The parameter 'gDriveID' is required - lib\growth_tracker\memories\upload_notes.dart:153:29 - missing_required_param
warning - The parameter 'templateID' is required - lib\growth_tracker\memories\upload_notes.dart:153:29 - missing_required_param
warning - The parameter 'fileName' is required - lib\growth_tracker\memories\upload_notes.dart:161:29 - missing_required_param
warning - The parameter 'gDriveID' is required - lib\growth_tracker\memories\upload_notes.dart:161:29 - missing_required_param
warning - The parameter 'templateID' is required - lib\growth_tracker\memories\upload_notes.dart:161:29 - missing_required_param
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: UploadMemoryPhoto.id,
          UploadMemoryPhoto.childId, UploadMemoryPhoto.month, UploadMemoryPhoto.type, UploadMemoryPhoto.templateID, UploadMemoryPhoto.timeStamp, UploadMemoryPhoto.file,
          UploadMemoryPhoto.caption, UploadMemoryPhoto.enableTheming - lib\growth_tracker\memories\upload_photo.dart:16:7 - must_be_immutable
   info - 'body2' is deprecated and shouldn't be used. This is the term used in the 2014 version of material design. The modern term is bodyText1. This feature was deprecated
          after v1.13.8. - lib\growth_tracker\memories\upload_photo.dart:328:90 - deprecated_member_use
   info - This function has a return type of 'FutureOr<String>', but doesn't end with a return statement - lib\growth_tracker\memories\upload_photo.dart:391:18 -
          missing_return
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: AssessmentPageUI.month -
          lib\growth_tracker\milestone_assessment\assessment_page_ui.dart:20:7 - must_be_immutable
   info - Close instances of `dart.core.Sink` - lib\growth_tracker\milestone_assessment\assessment_page_ui.dart:34:11 - close_sinks
   info - The value of the local variable 'isDark' isn't used - lib\growth_tracker\milestone_assessment\assessment_page_ui.dart:40:10 - unused_local_variable
   info - Unused import: 'package:kinderpass_app/growth_tracker/view_timeline/view_timeline_ui.dart' - lib\growth_tracker\view_timeline\view_monthly_timeline_page_ui.dart:4:8
          - unused_import
   info - Unused import: 'package:repository/preference.dart' - lib\growth_tracker\view_timeline\view_monthly_timeline_page_ui.dart:5:8 - unused_import
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final:
          ViewMonthlyTimelinePage.scaffoldKey, ViewMonthlyTimelinePage.month, ViewMonthlyTimelinePage.childId -
          lib\growth_tracker\view_timeline\view_monthly_timeline_page_ui.dart:8:7 - must_be_immutable
   info - Unused import: 'dart:io' - lib\growth_tracker\view_timeline\view_monthly_timeline_ui.dart:2:8 - unused_import
   info - Unused import: 'package:kinderpass_app/common/kinder_utils.dart' - lib\growth_tracker\view_timeline\view_monthly_timeline_ui.dart:9:8 - unused_import
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final:
          ViewMonthlyTimeline.scaffoldKey, ViewMonthlyTimeline.month, ViewMonthlyTimeline.childId - lib\growth_tracker\view_timeline\view_monthly_timeline_ui.dart:17:7 -
          must_be_immutable
   info - 'body2' is deprecated and shouldn't be used. This is the term used in the 2014 version of material design. The modern term is bodyText1. This feature was deprecated
          after v1.13.8. - lib\growth_tracker\view_timeline\view_monthly_timeline_ui.dart:146:41 - deprecated_member_use
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: ViewTimelinePage.scaffoldKey -
          lib\growth_tracker\view_timeline\view_timeline_page_ui.dart:7:7 - must_be_immutable
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final:
          LoadedViewTimeline.lstTimeline, LoadedViewTimeline.gDrive - lib\growth_tracker\view_timeline\view_timeline_state.dart:20:7 - must_be_immutable
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: LoggedInGoogleDrive.success -
          lib\growth_tracker\view_timeline\view_timeline_state.dart:32:7 - must_be_immutable
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: LoggedOutGoogleDrive.success -
          lib\growth_tracker\view_timeline\view_timeline_state.dart:42:7 - must_be_immutable
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: ViewTimeline.scaffoldKey -
          lib\growth_tracker\view_timeline\view_timeline_ui.dart:14:7 - must_be_immutable
   info - 'body2' is deprecated and shouldn't be used. This is the term used in the 2014 version of material design. The modern term is bodyText1. This feature was deprecated
          after v1.13.8. - lib\growth_tracker\view_timeline\view_timeline_ui.dart:219:46 - deprecated_member_use
   info - 'body2' is deprecated and shouldn't be used. This is the term used in the 2014 version of material design. The modern term is bodyText1. This feature was deprecated
          after v1.13.8. - lib\growth_tracker\view_timeline\view_timeline_ui.dart:250:44 - deprecated_member_use
   info - 'body2' is deprecated and shouldn't be used. This is the term used in the 2014 version of material design. The modern term is bodyText1. This feature was deprecated
          after v1.13.8. - lib\growth_tracker\view_timeline\view_timeline_ui.dart:280:44 - deprecated_member_use
   info - 'body2' is deprecated and shouldn't be used. This is the term used in the 2014 version of material design. The modern term is bodyText1. This feature was deprecated
          after v1.13.8. - lib\growth_tracker\view_timeline\view_timeline_ui.dart:344:51 - deprecated_member_use
   info - 'body2' is deprecated and shouldn't be used. This is the term used in the 2014 version of material design. The modern term is bodyText1. This feature was deprecated
          after v1.13.8. - lib\growth_tracker\view_timeline\view_timeline_ui.dart:401:54 - deprecated_member_use
   info - 'body2' is deprecated and shouldn't be used. This is the term used in the 2014 version of material design. The modern term is bodyText1. This feature was deprecated
          after v1.13.8. - lib\growth_tracker\view_timeline\view_timeline_ui.dart:406:53 - deprecated_member_use
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: HomePage.appBarTitle,
          HomePage.page, HomePage.selectedDrawerIndex, HomePage.authenticationBloc - lib\home\home_page.dart:45:7 - must_be_immutable
   info - The value of the local variable 'children' isn't used - lib\home\home_page.dart:195:12 - unused_local_variable
   info - Close instances of `dart.core.Sink` - lib\home\home_page.dart:540:30 - close_sinks
warning - The parameter 'onChanged' is required - lib\learn\learn_checkout.dart:311:35 - missing_required_param
   info - This function has a return type of 'FutureOr<bool>', but doesn't end with a return statement - lib\learn\learn_checkout.dart:392:16 - missing_return
   info - This function has a return type of 'Future<bool>', but doesn't end with a return statement - lib\learn\learn_checkout.dart:435:16 - missing_return
   info - This function has a return type of 'FutureOr<bool>', but doesn't end with a return statement - lib\learn\learn_checkout.dart:545:16 - missing_return
   info - The value of the local variable 'selectedChild' isn't used - lib\learn\learn_ui.dart:2402:11 - unused_local_variable
   info - Unused import: 'learn_video.dart' - lib\learn\learn_video\learn_video_event.dart:3:8 - unused_import
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: FetchVideoLearn.id -
          lib\learn\learn_video\learn_video_event.dart:8:7 - must_be_immutable
   info - Unused import: 'package:repository/models.dart' - lib\learn\learn_video\learn_video_state.dart:1:8 - unused_import
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final:
          InfoPanelWidget.mapSessionDetails - lib\learn\learn_video\learn_video_ui.dart:1015:7 - must_be_immutable
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: LearnZoomSession.lstSlots -
          lib\learn\learn_video\learn_zoom_session.dart:12:7 - must_be_immutable
   info - The value of the local variable 'isAMStart' isn't used - lib\learn\learn_video\learn_zoom_session.dart:137:20 - unused_local_variable
   info - The value of the local variable 'isAMEnd' isn't used - lib\learn\learn_video\learn_zoom_session.dart:137:31 - unused_local_variable
   info - The value of the local variable 'dtSession' isn't used - lib\learn\learn_video\learn_zoom_session.dart:147:30 - unused_local_variable
warning - The parameter 'cardBackground' is required - lib\learn\manage_cards\manage_cards_ui.dart:164:9 - missing_required_param
warning - The parameter 'colors' is required - lib\learn\manage_cards\manage_cards_ui.dart:297:15 - missing_required_param
   info - Unused import: 'package:kinderpass_app/common/hax_color.dart' - lib\learn\zoom_session\join_screen.dart:2:8 - unused_import
   info - Unused import: 'meeting_screen.dart' - lib\learn\zoom_session\join_screen.dart:5:8 - unused_import
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: StartMeetingWidget.timer -
          lib\learn\zoom_session\start_meeting_screen.dart:9:7 - must_be_immutable
   info - The declaration '_isMeetingEnded' isn't referenced - lib\learn\zoom_session\start_meeting_screen.dart:24:8 - unused_element
   info - Close instances of `dart.core.Sink` - lib\library\library_page_ui.dart:25:11 - close_sinks
   info - The value of the local variable 'listBloc' isn't used - lib\library\library_page_ui.dart:25:11 - unused_local_variable
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: LibraryWidget.childName -
          lib\library\library_widget.dart:11:7 - must_be_immutable
   info - The value of the local variable 'token' isn't used - lib\login\login_bloc.dart:29:15 - unused_local_variable
   info - The value of the local variable 'token' isn't used - lib\login\login_bloc.dart:54:15 - unused_local_variable
   info - The value of the local variable 'token' isn't used - lib\login\login_bloc.dart:79:15 - unused_local_variable
   info - Unused import: 'package:flutter/services.dart' - lib\login\login_form.dart:7:8 - unused_import
   info - Unused import: 'package:kinderpass_app/add_child/add_child.dart' - lib\login\login_form.dart:10:8 - unused_import
   info - Duplicate import - lib\login\login_form.dart:19:8 - duplicate_import
   info - Close instances of `dart.core.Sink` - lib\login\login_form.dart:78:11 - close_sinks
   info - Avoid using braces in interpolation when not needed - lib\login\login_form.dart:165:126 - unnecessary_brace_in_string_interps
   info - Name non-constant identifiers using lowerCamelCase - lib\login\login_screen_3.dart:14:10 - non_constant_identifier_names
   info - Name non-constant identifiers using lowerCamelCase - lib\login\login_screen_3.dart:140:10 - non_constant_identifier_names
   info - Name non-constant identifiers using lowerCamelCase - lib\login\login_screen_3.dart:470:10 - non_constant_identifier_names
   info - Close instances of `dart.core.Sink` - lib\main.dart:103:47 - close_sinks
warning - The parameter 'prevPage' is required - lib\main.dart:450:70 - missing_required_param
warning - The parameter 'prevPage' is required - lib\main.dart:456:70 - missing_required_param
warning - The parameter 'prevPage' is required - lib\main.dart:462:70 - missing_required_param
warning - The parameter 'prevPage' is required - lib\main.dart:468:70 - missing_required_param
   info - Unused import: 'package:kinderpass_app/learn/learn.dart' - lib\onboarding\onboarding.dart:4:8 - unused_import
   info - Unused import: 'package:kinderpass_app/phone_missing/phone_missing_form.dart' - lib\onboarding\onboarding.dart:6:8 - unused_import
   info - Unused import: 'package:kinderpass_app/phone_missing/phone_missing_page.dart' - lib\onboarding\onboarding.dart:7:8 - unused_import
   info - The declaration '_scaffoldKey' isn't referenced - lib\onboarding\onboarding.dart:14:32 - unused_element
   info - Close instances of `dart.core.Sink` - lib\phone_missing\phone_missing_form.dart:50:11 - close_sinks
   info - The declaration 'successToaster' isn't referenced - lib\phone_missing\phone_missing_form.dart:60:5 - unused_element
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final:
          PhoneMissingSuccess.successMessage - lib\phone_missing\phone_missing_state.dart:24:7 - must_be_immutable
   info - Unused import: 'package:kinderpass_app/widgets/widgets.dart' - lib\popup_card\popup_card_page.dart:9:8 - unused_import
   info - Unused import: 'dart:convert' - lib\referral\referral_page.dart:1:8 - unused_import
   info - Unused import: 'package:auto_size_text/auto_size_text.dart' - lib\referral\referral_page.dart:3:8 - unused_import
   info - Unused import: 'package:flutter_email_sender/flutter_email_sender.dart' - lib\referral\referral_page.dart:8:8 - unused_import
   info - Unused import: 'package:kinderpass_app/common/flutter_share_me.dart' - lib\referral\referral_page.dart:11:8 - unused_import
   info - Unused import: 'package:kinderpass_app/common/kinder_utils.dart' - lib\referral\referral_page.dart:12:8 - unused_import
   info - Unused import: 'package:repository/models.dart' - lib\referral\referral_page.dart:17:8 - unused_import
   info - The declaration '_topContentPage' isn't referenced - lib\referral\referral_page.dart:766:10 - unused_element
   info - Unused import: 'dart:convert' - lib\reset_password\reset_bloc.dart:2:8 - unused_import
   info - Unused import: 'package:meta/meta.dart' - lib\reset_password\reset_bloc.dart:6:8 - unused_import
   info - Unused import: 'package:repository/preference.dart' - lib\reset_password\reset_bloc.dart:8:8 - unused_import
   info - Close instances of `dart.core.Sink` - lib\reset_password\reset_form.dart:41:11 - close_sinks
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: ResetSuccess.successMessage -
          lib\reset_password\reset_state.dart:24:7 - must_be_immutable
   info - Unused import: 'dart:convert' - lib\services\stripe_checkout_session.dart:1:8 - unused_import
   info - Unused import: 'package:kinderpass_app/web_view/web_view_page.dart' - lib\services\stripe_checkout_session.dart:8:8 - unused_import
   info - Unused import: 'package:webview_flutter/webview_flutter.dart' - lib\services\stripe_checkout_session.dart:11:8 - unused_import
   info - Unused import: 'dart:convert' - lib\settings\settings_bloc.dart:2:8 - unused_import
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: SettingSuccess.successMessage
          - lib\settings\settings_state.dart:24:7 - must_be_immutable
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: MyOrderUI.order -
          lib\shop\my_orders\my_order_ui.dart:11:7 - must_be_immutable
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: FetchMyOrders.email -
          lib\shop\my_orders\my_orders_event.dart:6:7 - must_be_immutable
   info - The value of the local variable 'signUp' isn't used - lib\signup\sign_up_bloc.dart:27:15 - unused_local_variable
   info - The value of the local variable 'signUp' isn't used - lib\signup\sign_up_bloc.dart:38:15 - unused_local_variable
   info - The value of the local variable 'signUp' isn't used - lib\signup\sign_up_bloc.dart:49:15 - unused_local_variable
   info - The value of the local variable 'signUp' isn't used - lib\signup\sign_up_bloc.dart:85:15 - unused_local_variable
   info - Unused import: 'package:kinderpass_app/add_child/add_child.dart' - lib\signup\sign_up_form.dart:11:8 - unused_import
   info - The declaration '_playAnimation' isn't referenced - lib\signup\sign_up_form.dart:81:16 - unused_element
   info - Close instances of `dart.core.Sink` - lib\signup\sign_up_form.dart:90:11 - close_sinks
   info - 'photoUrl' is deprecated and shouldn't be used. Deprecated in favor of 'photoURL'. - lib\signup\sign_up_form.dart:155:38 - deprecated_member_use
   info - Avoid using braces in interpolation when not needed - lib\signup\sign_up_form.dart:194:124 - unnecessary_brace_in_string_interps
   info - Unused import: 'package:kinderpass_app/add_child/add_child.dart' - lib\signup_child\add_multiple_child.dart:7:8 - unused_import
   info - Don't import implementation files from another package - lib\signup_child\add_multiple_child.dart:20:8 - implementation_imports
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final:
          AddMultipleChildPage.userIsMale, AddMultipleChildPage.userIsExpecting, AddMultipleChildPage.authenticationBloc, AddMultipleChildPage.signUpBloc -
          lib\signup_child\add_multiple_child.dart:22:7 - must_be_immutable
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: AddMulitpleChild.userIsMale,
          AddMulitpleChild.userIsExpecting, AddMulitpleChild.signUpBloc, AddMulitpleChild.authenticationBloc - lib\signup_child\add_multiple_child.dart:51:7 -
          must_be_immutable
   info - The value of the field '_isBabyBorn' isn't used - lib\signup_child\add_multiple_child.dart:69:8 - unused_field
   info - The value of the field '_image' isn't used - lib\signup_child\add_multiple_child.dart:72:8 - unused_field
   info - Close instances of `dart.core.Sink` - lib\signup_child\add_multiple_child.dart:112:11 - close_sinks
   info - The declaration 'navigateToHome' isn't referenced - lib\signup_child\add_multiple_child.dart:229:5 - unused_element
   info - The declaration 'getImage' isn't referenced - lib\signup_child\add_multiple_child.dart:245:12 - unused_element
   info - 'pickImage' is deprecated and shouldn't be used. Use imagePicker.getImage() method instead. - lib\signup_child\add_multiple_child.dart:246:37 -
          deprecated_member_use
   info - The declaration 'removeExpectedChild' isn't referenced - lib\signup_child\add_multiple_child.dart:472:5 - unused_element
   info - Close instances of `dart.core.Sink` - lib\subscriptions_payments\subscriptions_payment_widget.dart:76:11 - close_sinks
   info - The value of the local variable 'priceRoundValue' isn't used - lib\subscriptions_payments\subscriptions_payment_widget.dart:219:12 - unused_local_variable
   info - The value of the local variable 'priceActualValue' isn't used - lib\subscriptions_payments\subscriptions_payment_widget.dart:219:29 - unused_local_variable
   info - The value of the local variable 'priceDecimalValue' isn't used - lib\subscriptions_payments\subscriptions_payment_widget.dart:219:47 - unused_local_variable
   info - The value of the field '_scaffoldKey' isn't used - lib\today\today_ui.dart:9:34 - unused_field
   info - The value of the local variable 'token' isn't used - lib\update_kid\update_kid_bloc.dart:24:15 - unused_local_variable
   info - The value of the local variable 'success' isn't used - lib\update_kid\update_kid_bloc.dart:51:14 - unused_local_variable
   info - Unused import: 'package:auto_size_text/auto_size_text.dart' - lib\update_kid\update_kid_ui.dart:4:8 - unused_import
   info - The value of the field '_isBabyBorn' isn't used - lib\update_kid\update_kid_ui.dart:65:8 - unused_field
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: EditUserProfile.user -
          lib\user_profile\user_profile_event.dart:12:7 - must_be_immutable
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final:
          ActivityCompleteRewardBanner.strTitle, ActivityCompleteRewardBanner.strbodyText1, ActivityCompleteRewardBanner.strBody2, ActivityCompleteRewardBanner.strCoverImage,
          ActivityCompleteRewardBanner.strIcon, ActivityCompleteRewardBanner.strButton, ActivityCompleteRewardBanner.strBackText, ActivityCompleteRewardBanner.onTap -
          lib\widgets\activity_complete_reward_banner.dart:8:7 - must_be_immutable
   info - Unused import: 'package:kinderpass_app/activity/activity.dart' - lib\widgets\article_sliding_cards.dart:4:8 - unused_import
   info - Unused import: 'package:kinderpass_app/common/kinder_utils.dart' - lib\widgets\article_sliding_cards.dart:8:8 - unused_import
   info - The value of the local variable 'activityId' isn't used - lib\widgets\article_sliding_cards.dart:79:12 - unused_local_variable
   info - The value of the local variable 'milestoneId' isn't used - lib\widgets\assessment_cards_view.dart:55:12 - unused_local_variable
   info - Unused import: 'package:kinderpass_app/common/common.dart' - lib\widgets\buy_plan_sliding_cards.dart:9:8 - unused_import
   info - Unused import: 'package:kinderpass_app/widgets/dialog.dart' - lib\widgets\camera_photo.dart:6:8 - unused_import
   info - Unused import: 'package:path_provider/path_provider.dart' - lib\widgets\camera_photo.dart:7:8 - unused_import
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: CameraPhoto.file -
          lib\widgets\camera_photo.dart:11:7 - must_be_immutable
   info - Unused import: 'dart:convert' - lib\widgets\caregiver_sliding_cards.dart:1:8 - unused_import
warning - The parameter 'onPressed' is required - lib\widgets\discover_bookmark_share.dart:19:11 - missing_required_param
   info - Unused import: 'widgets.dart' - lib\widgets\empty_widget.dart:10:8 - unused_import
   info - The value of the field '_animationScrollPercent' isn't used - lib\widgets\expandablecard.dart:35:21 - unused_field
   info - The value of the field '_isAnimating' isn't used - lib\widgets\expandablecard.dart:36:8 - unused_field
   info - Close instances of `dart.core.Sink` - lib\widgets\favourite_article_widget.dart:26:13 - close_sinks
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: FullScreenDialog.text1,
          FullScreenDialog.text2, FullScreenDialog.text3, FullScreenDialog.text4, FullScreenDialog.btnText1, FullScreenDialog.btnText2, FullScreenDialog.strImageURL,
          FullScreenDialog.textStyle1, FullScreenDialog.textStyle2, FullScreenDialog.textStyle3, FullScreenDialog.textStyle4, FullScreenDialog.cbBtn1, FullScreenDialog.cbBtn2
          - lib\widgets\full_screen_dialog.dart:5:7 - must_be_immutable
   info - Unused import: 'package:flutter/scheduler.dart' - lib\widgets\kids_profile_sliding_cards.dart:5:8 - unused_import
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: KinderEmptyPage.size,
          KinderEmptyPage.onTap - lib\widgets\kinder_empty_page.dart:7:7 - must_be_immutable
   info - Unused import: 'package:flutter_svg/flutter_svg.dart' - lib\widgets\loading_widget.dart:2:8 - unused_import
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: MonthWidget.month -
          lib\widgets\month_widget.dart:6:7 - must_be_immutable
   info - 'body2' is deprecated and shouldn't be used. This is the term used in the 2014 version of material design. The modern term is bodyText1. This feature was deprecated
          after v1.13.8. - lib\widgets\month_widget.dart:133:45 - deprecated_member_use
   info - Unused import: 'package:repository/models.dart' - lib\widgets\skill_category_dialog.dart:6:8 - unused_import
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: CardContent.suggestedTimeIcon
          - lib\widgets\sliding_cards.dart:359:7 - must_be_immutable
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: Activities.message,
          Activities.responseData, Activities.success - repository\lib\src\models\activities\activities.dart:4:7 - must_be_immutable
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final:
          ActivityResponseData.activities, ActivityResponseData.products, ActivityResponseData.count - repository\lib\src\models\activities\activities.dart:31:7 -
          must_be_immutable
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: Activity.age,
          Activity.cognitive, Activity.description, Activity.id, Activity.isBookmarked, Activity.isCompleted, Activity.learning, Activity.level, Activity.linguistic,
          Activity.materialsRequired, Activity.personalSocial, Activity.physical, Activity.review, Activity.suggestedTime, Activity.title, Activity.isUnlocked,
          Activity.bookmarkedOn - repository\lib\src\models\activities\activity.dart:3:7 - must_be_immutable
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: Product.title, Product.url,
          Product.description, Product.images, Product.tags, Product.price - repository\lib\src\models\activities\product.dart:3:7 - must_be_immutable
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: CaregiverDetails.id,
          CaregiverDetails.status, CaregiverDetails.firstName, CaregiverDetails.gender, CaregiverDetails.relation, CaregiverDetails.email -
          repository\lib\src\models\caregiver\caregiver_details.dart:3:7 - must_be_immutable
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final:
          CaregiverInviteDetails.userType, CaregiverInviteDetails.token, CaregiverInviteDetails.password, CaregiverInviteDetails.email -
          repository\lib\src\models\caregiver\caregiver_invite_details.dart:4:7 - must_be_immutable
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final:
          CaregiverInviteResponse.message, CaregiverInviteResponse.caregiver, CaregiverInviteResponse.success -
          repository\lib\src\models\caregiver\caregiver_invite_response.dart:5:7 - must_be_immutable
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final:
          CaregiverResponseData.firstName, CaregiverResponseData.gender, CaregiverResponseData.relation, CaregiverResponseData.email -
          repository\lib\src\models\caregiver\caregiver_request.dart:3:7 - must_be_immutable
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: CaregiverResponse.message,
          CaregiverResponse.caregivers, CaregiverResponse.success - repository\lib\src\models\caregiver\caregiver_response.dart:5:7 - must_be_immutable
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: UserType4.id -
          repository\lib\src\models\caregiver\user_type.dart:3:7 - must_be_immutable
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: ChildId.child_id -
          repository\lib\src\models\child_id.dart:3:7 - must_be_immutable
   info - Name non-constant identifiers using lowerCamelCase - repository\lib\src\models\child_id.dart:4:10 - non_constant_identifier_names
   info - Name non-constant identifiers using lowerCamelCase - repository\lib\src\models\child_id.dart:6:17 - non_constant_identifier_names
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: Child.dob, Child.gender,
          Child.name, Child.type, Child.image, Child.id, Child.preemie - repository\lib\src\models\childs\child.dart:3:7 - must_be_immutable
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: Childs.message,
          Childs.responseData, Childs.success - repository\lib\src\models\childs\childs.dart:5:7 - must_be_immutable
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: Gender.id, Gender.name,
          Gender.preamble - repository\lib\src\models\gender.dart:3:7 - must_be_immutable
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: GenderSingup.id -
          repository\lib\src\models\genderSignup.dart:3:7 - must_be_immutable
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: Login.token -
          repository\lib\src\models\login.dart:3:7 - must_be_immutable
   info - Unused import: 'package:equatable/equatable.dart' - repository\lib\src\models\login_response.dart:1:8 - unused_import
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: Memories.message,
          Memories.responseData, Memories.success - repository\lib\src\models\memories\memories.dart:5:7 - must_be_immutable
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: MemoryResponseData.memories -
          repository\lib\src\models\memories\memories.dart:46:7 - must_be_immutable
   info - Unused import: 'dart:convert' - repository\lib\src\models\memories\memory.dart:1:8 - unused_import
   info - Unused import: 'dart:ffi' - repository\lib\src\models\memories\memory.dart:2:8 - unused_import
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: Memory.fileName,
          Memory.timeStamp, Memory.gDriveID, Memory.caption, Memory.month, Memory.id, Memory.type, Memory.childId, Memory.templateID -
          repository\lib\src\models\memories\memory.dart:7:7 - must_be_immutable
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: AssessmentRequest.month,
          AssessmentRequest.childId, AssessmentRequest.milestones - repository\lib\src\models\milestones\assessment_request.dart:4:7 - must_be_immutable
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: Milestone.cognitive,
          Milestone.description, Milestone.id, Milestone.linguistic, Milestone.personalSocial, Milestone.physical, Milestone.state -
          repository\lib\src\models\milestones\milestone.dart:3:7 - must_be_immutable
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: Milestones.message,
          Milestones.responseData, Milestones.success - repository\lib\src\models\milestones\milestones.dart:4:7 - must_be_immutable
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final:
          MilestoneResponseData.milestones, MilestoneResponseData.count, MilestoneResponseData.assessmentDone - repository\lib\src\models\milestones\milestones.dart:35:7 -
          must_be_immutable
   info - Unused import: 'package:repository/models.dart' - repository\lib\src\models\referral\referral_request.dart:1:8 - unused_import
   info - Unused import: 'referral_type.dart' - repository\lib\src\models\referral\referral_request.dart:3:8 - unused_import
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: ReferralResponse.message,
          ReferralResponse.responseData, ReferralResponse.success - repository\lib\src\models\referral\referral_response.dart:3:7 - must_be_immutable
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: ReferralResponseData.clicks,
          ReferralResponseData.code, ReferralResponseData.linkToken, ReferralResponseData.referrals, ReferralResponseData.shares, ReferralResponseData.token -
          repository\lib\src\models\referral\referral_response.dart:34:7 - must_be_immutable
   info - Unused import: 'dart:convert' - repository\lib\src\models\shop\orders\orders.dart:1:8 - unused_import
   info - Unused import: 'package:repository/src/models/gender.dart' - repository\lib\src\models\signin_user\birthday_of_child.dart:1:8 - unused_import
   info - Name non-constant identifiers using lowerCamelCase - repository\lib\src\models\signin_user\subscription_details.dart:16:26 - non_constant_identifier_names
   info - The value of the local variable 'blYoungChildFound' isn't used - repository\lib\src\models\signin_user\subscription_details.dart:81:12 - unused_local_variable
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: UserPart2.displayName,
          UserPart2.gender, UserPart2.postalCode - repository\lib\src\models\signin_user\userPart2.dart:4:7 - must_be_immutable
   info - This class (or a class that this class inherits from) is marked as '@immutable', but one or more of its instance fields aren't final: UserType.id, UserType.name -
          repository\lib\src\models\user_type.dart:3:7 - must_be_immutable
  error - Target of URI doesn't exist: 'package:shared_preferences/shared_preferences.dart' - repository\lib\src\preference.dart:1:8 - uri_does_not_exist
  error - Undefined class 'SharedPreferences' - repository\lib\src\preference.dart:5:10 - undefined_class
  error - The name 'SharedPreferences' isn't a type so it can't be used as a type argument - repository\lib\src\preference.dart:8:17 - non_type_as_type_argument
  error - Undefined name 'SharedPreferences' - repository\lib\src\preference.dart:10:22 - undefined_identifier
   info - The value of the local variable 'activeChildId' isn't used - repository\lib\src\repository.dart:451:11 - unused_local_variable
   info - The value of the local variable 'activitiesDone' isn't used - repository\lib\src\repository.dart:502:11 - unused_local_variable

300 issues found. (ran in 47.1s)

[√] Flutter (Channel stable, 1.22.6, on Microsoft Windows [Version 10.0.19041.746], locale en-US)
    • Flutter version 1.22.6 at E:\Multiverse_Projects\Flutter\flutter
    • Framework revision 9b2d32b605 (3 weeks ago), 2021-01-22 14:36:39 -0800
    • Engine revision 2f0af37152
    • Dart version 2.10.5

[√] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
    • Android SDK at C:\Users\prahu\AppData\Local\Android\sdk
    • Platform android-30, build-tools 30.0.2
    • Java binary at: E:\Apps\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 D:\Apps\Android Studio
    • Flutter plugin version 50.0.1
    • Dart plugin version 193.7547
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)

[!] Android Studio (version 4.1.0)
    • Android Studio at E:\Apps\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)

[√] Connected device (2 available)
    • SM N960F (mobile)                  • 2793c82c50217ece • android-arm64 • Android 10 (API 29)
    • Android SDK built for x86 (mobile) • emulator-5554    • android-x86   • Android 10 (API 29) (emulator)

! Doctor found issues in 1 category.

[apple_sign_in](https://pub.dev/packages/apple_sign_in is a 3rd party plugin, please open an issue in the dedicated github
or provide your flutter doctor -v, your flutter run -v
and a minimal reproducible code sample without 3rd party plugins

Tried to create an MVP, but couldn't.
So I deleted the Android folder and created everything again.
Now everything works fine.


Added option to reset window close flag

This should(mandatory) be called in draw functions. This reset function
basically checks if window was asked to be closed by the user earlier
if so, it resets the flag and raises the window to focus.
This feature basically enables reuse same window multiple times
in the same program and helps avoid creating uncessary additional
windows. However for this feature to work as expected, the
fg::Window::close function should be called in the following loop
constructs only.

do-while
for

while cannot work as the condition check is made prior to any draw
call where the window close flag check is happening.

If more than one window is used in the same render-loop, the results are kind of buggy in one particular use-case. I, however, think that these kind of situations are rare.