text:
🛑 highlyflammable.tech services is down

In 82fd6aa, highlyflammable.tech services (http://s.highlyflammable.tech) was down:

HTTP code: 0
Response time: 0 ms

Resolved: highlyflammable.tech services is back up in 17fa647 after 19 minutes.

repo: flamableassassin/status


text:
RangeError on Layer.tiles in 0.4.0

A RangeError is generated when accessing the Layer.tiles getter on non-square maps.  Latest 0.4.0 version.  This is due to the _tiles list being [x][y] and the tileMatrix and tileFlips lists being [y][x].  One or the other should be changed, or the addressing changed.  Someone else can decide which way to go with it.
When I tested correcting it, I got past the range errors but tiles in the map still didn't look right.  Its not my map (Flame's test map) so I didn't pursue it further at this time.

@luanpotter can you take a look on this?

source: gharchive/issue

authors: erickzanardo juanitogan

license: MIT

license_type: permissive

license_source: github-api


text:
Use pixi instead of poetry

Click to watch
I created a sample Dockerfile that shows how pixi can install system deps with minimal image setup
running pip install in the environment conextualizes it to the pixi virtualenv so I put pypi deps back into requirements.txt and only have system deps in pixi toml.
pixi pulls deps from conda-forge which is good for binaries e.g. version managed language interpreters

Thank you for the PR!
My first reaction is: I wish we could drop 'instead of poetry' -- in the sense of giving devs/users the option to use either pixi or poetry. This PR seems to almost achieve this? Except that:

requirements.txt is reintroduced, which could cause confusion but is probably OK.
a run script no longer runs 'poetry flask', which makes it so that it won't use poetry anymore. Maybe there's a way to reconcile the two?

Of course I could also move to pixi but it seems quite new and I'd rather not invest in a migration right now.
Wdyt?

Pixi is a python environment manager as well as a package manager so using poetry is redundant. The majority of my PRs are usually proof of concepts and I don't except you to merge them. Mostly "what ifs"

source: gharchive/pull-request

repo: flancian/agora-server


text:
[버그] 서버 접두사를 설정하지 않은 서버에서 접두사 명령어 사용 시 null이라고 뜸

문제 설명
서버 접두사를 설정하지 않은 서버에서 //접두사 명령어 사용 시 null이라고 뜸.
재현 방법

봇을 접두사를 변경한 적이 없는 서버에 초대
//접두사 명령어 실행

예상되는 동작
기본 접두사가 나와야 함
실제 동작
null
버전
v0.8.3 8a57768

v0.8.4에서 해당 문제 수정.

repo: flashbot-discord/flashbot


text:
Add missing package to requirements of auth example

When trying to get the example auth running as described in examples/auth/README.rst the following exception is thrown:
(env) [a@b flask-admin]$ python examples/auth/app.py
Traceback (most recent call last):
  File "/home/m/dev/flask-admin/examples/auth/app.py", line 4, in <module>
    from flask_security import Security, SQLAlchemyUserDatastore, \
  File "/home/m/dev/flask-admin/env/lib/python3.9/site-packages/flask_security/__init__.py", line 13, in <module>
    from .core import Security, RoleMixin, UserMixin, AnonymousUser, current_user
  File "/home/m/dev/flask-admin/env/lib/python3.9/site-packages/flask_security/core.py", line 28, in <module>
    from .forms import ChangePasswordForm, ConfirmRegisterForm, \
  File "/home/m/dev/flask-admin/env/lib/python3.9/site-packages/flask_security/forms.py", line 69, in <module>
    email_validator = Email(message='INVALID_EMAIL_ADDRESS')
  File "/home/m/dev/flask-admin/env/lib/python3.9/site-packages/wtforms/validators.py", line 332, in __init__
    raise Exception("Install 'email_validator' for email validation support.")

With  email_validator is added to requirements.txt it works as expected.

Merged with #2094.

authors: Dosenpfand alanhamlett

repo: flask-admin/flask-admin

license_source: bigquery


text:
merge flatcar-docs into flatcar-website

This is an attempt to merge flatcar-docs into flatcar-website repository - there is no need to have them in 2 separate repos.
What I've done:

Clone flatcar-website and flatcar-docs
In flatcar-docs
2.1 Create branch "docs"  to turn docs/ into the root of the git repo
2.2 Create branch "os"  to turn os/ into the root of the git repo
2.3 Graft the two branches
2.2 Follow https://x3ro.de/integrating-a-submodule-into-the-parent-repository/ to change the path of each file in a git point of view
In flatcar-website
3.1 Add a local remote (sub) targeting the flatcar-docs we modified
3.2 git fetch sub
3.3 git merge --allow-unrelated-histories -s ours --no-commit sub/main
3.4 backport the files into the repo: git clone https://github.com/flatcar/flatcar-docs /tmp/flatcar-docs && mv /tmp/flatcar-docs/docs ./content/docs/latest
3.5 git add content/docs/latest && git commit -s

Relevant commits:

https://github.com/flatcar/flatcar-website/pull/280/commits/6b5a6c446ab0bb99aefb7ed19fd50a0c1c80e00c
https://github.com/flatcar/flatcar-website/pull/280/commits/8132ee7d80c04b54fc39ee8fd7d0d7234dc063ca
https://github.com/flatcar/flatcar-website/pull/280/commits/8b94a713c5ecab205f5687744f8c0574c9a78c72 as proof that it works (to be removed of course)

The review shows 1166 commits. I don't think we need to keep the history, so maybe just one commit merging things is enough?

@joaquimrocha that's the point actually: to keep the history of flatcar-docs

I don't really see the point but that's fine either way. I don't have time to review the full PR but gave a quick look and tried the link and it LGTM. I'll approve it.

repo: flatcar/flatcar-website


text:
screenshots

graph TD
    A[Raw NWB file on DANDI] -->|Dendro Job| B[Derived NWB file]
    B -->|Dendro Job| C[Second Derived NWB file]
    C -->|Dendro Job| D[Upload to DANDI]

repo: flatironinstitute/neurosift


text:
Time Picker "autofill" behaviour does not trigger a change event

When using flatpicker with the properties noCalendar and enableTime and the user clicks into the input field, the timepicker opens as it should. If no defaultDate is specified, the time get's set to 12:00 automatically.
The problem is, that this "autofill" behaviour does not trigger an onChange event, but still fills the input field with a time. In combination with floating labels or custom placeholders (via span and not default placeholder parameter), that leads to a design glitch where the label and the autofilled value are on top of each other, until the user actually changes the time. In the edge case where the user opens the time picker and right away closes it again, the autofilled value stays there on top of the label forever..
Behaviour can be seen here: https://jsfiddle.net/tf214zeu/1/
Expected behaviour:
I would either expect:

The initial autofill also triggers a onChange event
I can disable the initial autofill

Your Environment

flatpickr version used: 4.5.2
Browser name and version: All Browsers
OS and version: Mac OS X

Can confirm this issue. In the meantime made a quick workaround.
Add this as a property on the config object you pass into the flatpickr instance on creation:
 onValueUpdate: () => {       // this._picker is the flatpickr instance       const date = this._picker.parseDate(         this.root.querySelector('input').value, // your <input> value (e.g. '12:00 PM')         this.pickerConfig.dateFormat // dateFormat in config passed to flatpickr instance (e.g. 'h:i K')       );       this._picker.config.onChange[0]([date]);   }

@arikimolloy thanks for sharing. my workaround was actually setting the value manually in the onOpen callback:
onOpen: (selectedDates: Date[], dateStr: string, flatpickrInstance: FlatpickrInstance) => {
	if (dateStr === '') {
		const date = new Date();
		date.setHours(12, 0);
		setDefaultDate(flatpickrInstance, type, date);
	}
},

Here is my workaround, my incoming time format is HH:MM
 onOpen: (selectedDates, dateStr, flatpickrInstance) => {             if (dateStr !== '') {                 flatpickrInstance.config.defaultHour = dateStr.split(":")[0]                 flatpickrInstance.config.defaultMinute = dateStr.split(":")[1]             }         },

Just to throw another solution in there, this worked well for me.
onClose: (_, dateStr, f) => {
                if (dateStr === "") {
                    f.setDate(new Date().setHours(f.config.defaultHour, f.config.defaultMinute, f.config.defaultSeconds, 0), true)
                }
},

Just to throw another solution in there, this worked well for me.
onClose: (_, dateStr, f) => {
                if (dateStr === "") {
                    f.setDate(new Date().setHours(f.config.defaultHour, f.config.defaultMinute, f.config.defaultSeconds, 0), true)
                }
},

authors: allsyed arikimolloy janwidmer robovinnie

repo: flatpickr/flatpickr


text:
Year click and hold to increment

flatpickr version used: 4.6.3
Browser name and version: Chrome 79
OS and version: Windows 10

I know you can type it directly and use the mouse wheel but is it possible to make it increment/decrement continuously when you click and hold the year up/down buttons? Thanks

Another thing I've just noticed is that if you scroll the year input, when you then go to click on a date or change the month the year jumps back to the previous value before you scrolled which is super annoying

Exactly, scrolling the year does not generate an event to update the date value. This is quite annoying. If I scroll to a different year, then change the month or select a day, the year jumps back to the original year and the final date contains the original year. Only using the up/down arrows will actually update the year.
I can see where scrolling changes the year rapidly, and would require intensive re-rendering of the calendar, so a debounce could be implemented in order to avoid too many updates too close together.

Actually I see that scrolling to update the year has been implemented as a plugin.
After importing (or referencing) scrollPlugin.js from the plugins folder , you can then just pass it into the plugins option when instantiating the flatpickr:
flatpickr(element, {
  plugins: [new scrollPlugin({})]
});

Voilà! now the year is updated when you scroll it.

authors: JohnRDOrazio quantumwebco


text:
In time picker input box can i to enter more than 2 numbers, can i able to restrict

https://jsfiddle.net/tj2Lo4z7/
Your Environment

flatpickr version used:
Browser name and version:
OS and version:

Fixed in https://github.com/flatpickr/flatpickr/pull/2262

authors: SivanKarthick chmln


text:
monthSelect plugin: Support "range" mode

Note: This PR consists of eight separate commits. I put in a good amount of effort keeping changes isolated so that the commit history could be used as an instructive reference to help future developers who might wonder, "Why was the code written this way?" (see Telling Stories through Your Commits (2015) and A Branch in Time (2019) for my rationale here). Keeping commits bite-sized and cohesive is crucial to this approach.
To preserve this effort, please keep these commits separate when merging (i.e., do not "squash merge"). Thanks!

This PR adds support for "range" mode to the monthSelect plugin. It also includes various minor refactorings and bugfixes that are not always directly related to range mode functionality.
In virtually every case, there is an extensive commit message detailing the scope and reasons for the changes, as well as any important design considerations. For a deeper look at this PR, check there first.

Pinging @chmln, thoughts on this?

@rlue looks great!
The range code in flatpickr is one of the more complex parts so I'll need to manually test out a few things before approving.

I don't think this is the right place for a feature request but could this work/pr lead to having a multi-month display? Not just for a range but for single date selection.
For example: https://www.kayak.co.uk/

@leads, for general date selection, see the showMonths config option.
Doesn't work for the monthSelect plugin (yet). PRs welcome, but one step at a time, eh? ;)

@chmln any update on this? :)

Thanks for reminding me @rlue will review this asap

Hey, any chance you'd have some time in the near future to look at this? Would still love to see it merged :)

Hey @chmln! It's been over a year since I first submitted this PR, but I'm holding out hope that we can still get it merged.
What is the latest commit activity about?
I was able to merge the latest master against my PR branch without any conflicts, but I did notice that one of the tests I wrote was failing now. I had to fiddle with some things to get it to work. (I don't think anything was functionally broken; it just seems like jest is peculiar with the way it simulates click events.)
A codepen for manual testing
You mentioned last time that you wanted to do some manual tests with it first, so I set up a codepen for you to do just that. It uses a version of flatpickr.js that I compiled myself and have uploaded to a private web server. If you'd like to confirm that I got it right, here are the commands I used to generate the assets:
$ git clone https://github.com/flatpickr/flatpickr
$ cd flatpickr
$ git remote add rlue https://github.com/rlue/flatpickr
$ git fetch rlue
$ git merge rlue/feature/monthSelect/range-mode
$ npm run build
$ scp -r dist <my-remote-server>:<path-to-www>/flatpickr-2297

Let me know what you think.

Thanks so much @rlue for pinging me, I will merge this over the next couple days

Yay! Thanks :)

Hello @rlue , after updating to 4.6.10 + , the month select plugin stops triggering onChange events but updates the input text, might this be related with the change of using  updateValue rather then fb.setDate()

Hello @rlue , after updating to 4.6.10 + , the month select plugin stops triggering onChange events but updates the input text, might this be related with the change of using updateValue rather then fp.setDate()
concerned line :
https://github.com/flatpickr/flatpickr/blob/614568f20daff9fdef906e8451876d8918c68d3c/src/index.ts#L2527

I am experiencing this also.

authors: chmln dianfishekqi leads othercorey rlue


text:
Scrolling from top of the page on History back button

Hi there,
I'm trying out scrollTo on a small woocommerce site where all my products are on a single page. I have got it scrolling nicely between products, up and down the page when I use the navigation based on a 'hashchange' event. However, when I hit the back button in my browser, instead of scrolling FROM the current product to the previous one, the browser jumps to the top of the page and animates down from there! Then having gone back a few times to previous products, when I use the forward button, instead of scrolling it starts to jump. This is happening in current versions of Chrome and Firefox.
Although I could live with this, my site is for an accessible audience and I would like to give them a seamless experience where the forward and back buttons scroll the page up and down in the same way that the on page navigation does.
I was just wondering if anyone here had experience of this issue and whether there is a solution?
Many thanks
Kevin

Hey, maybe it's solvable combining other plugins to monitor history changes and some glue code. You should ask this on sites like StackOverflow, someone might suggest a good solution

authors: flesler thelar


text:
ERROR: ERROR: Failed to build installable wheels for some pyproject.toml based projects (httptools)

Duplicate Check

[X] I have searched the opened issues and there are no duplicates

Describe the bug
Issue Description
I attempted to install flet using pip install flet, but encountered errors when building wheels for the httptools package. This issue occurs while using Python 3.13.0rc2.
Code sample
pip install flet
To reproduce
Steps to Reproduce

Run pip install flet using Python 3.13.0rc2
Encounter the above error during installation.

Expected behavior
No response
Screenshots / Videos

Captures
[Upload media here]

Operating System
Windows
Operating system details
Windows 10
Flet version
v0.24.1
Regression
I'm not sure / I don't know
Suggestions
No response
Logs
Error Logs
Building wheels for collected packages: httptools
Building wheel for httptools (setup.py) ... error
error: subprocess-exited-with-error
× python setup.py bdist_wheel did not run successfully.
│ exit code: 1
╰─> [73 lines of output]
C:\Python313\Lib\site-packages\setuptools_distutils\dist.py:261: UserWarning: Unknown distribution option: 'test_suite'
warnings.warn(msg)
...
httptools/parser/parser.c(9938): error C2198: 'int _PyLong_AsByteArray(PyLongObject *,unsigned char *,size_t,int,int,int)': too few arguments for call
httptools/parser/parser.c(10134): error C2198: 'int _PyLong_AsByteArray(PyLongObject *,unsigned char *,size_t,int,int,int)': too few arguments for call
error: command 'E:\Program Files\Microsoft Visual Studio\2022\Community\VC\Tools\MSVC\14.41.34120\bin\HostX86\x64\cl.exe' failed with exit code 2
note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for httptools
Additional details
System Info

Python version: 3.13.0rc2
Pip version: 24.2
Operating system: Windows 10
Compiler: Microsoft Visual Studio 2022 Community

Issue Resolved
The issue was resolved by downgrading to Python version 3.12.6. It appears the problem was related to Python 3.13.0rc2 compatibility. Installing flet works as expected with Python 3.12.6.
This issue can now be closed. Thank you!

repo: flet-dev/flet


text:
Add support for 403 and 503 TripIt status codes

Per the TripIt API documentation, the oauth client was missing support for the 403 and 503 error codes. I've added to round out support for all documented status codes.

Pulled -- thanks a lot for the contribution Jeff!

authors: akremer jeffarena

repo: flextrip/tripit

license: mit


text:
Flextype Core: Entries - reduce the number of calls to the file system inside fetch methods.

There is possible issue with concurrency requests per page. [need to research]
fetch and fetchAll should be reviewed and should be reduced the number of calls to the file system, especially for fetchAll method. need to research. Possible solution is to store fetchAll result inside class property.

proposition: to load all entries db into the memory to work with all of them.

proposition: move media files from entries into it is own section, for e.g. file library

proposition: to have new type of entities - collection and single

possible issue is here \Twig\Loader\FilesystemLoader
need more time to investigate with AB and other tools

Not issue for now, will investigate this in future releases

Done.

repo: flextype/flextype


text:
EDM-310: Move the CA to an async task

Move the CA to a singleton.
Provide support for multiple signers/CA identities.
Move signing to an async task.
Invoke the async task instead of signing.
Provide support for different CA types.

I have pushed the Vault support to my fork. It is incremental on top of this one.
If we decide to merge this, it can go on top. I still have some questions on e2e there, but they can wait until it is being actively worked on.

repo: flightctl/flightctl


text:
File system scheme 'queue' not implemented

Describe the bug

follow the quick_start tutorial
submit flink job on local cluster
task manager output log: File system scheme 'queue' not implemented (file: ......)
Am I missing something ?

Your environment
Operating system
CentOS 7
flink 1.14.3
TensorFlow 1.15.5
Database

Python version
Python 3.7
Expected behavior

Actual behavior

Screenshots

Additional context
Tensorflow.python.framework.errors_impl.UnimplementedError: From /job:worker/replica:0/task:0:
File system scheme 'queue' not implemented (file: 'queue:///tmp/1644377004835-1/queue-5118498194079552779.output:8392704')
[[{{node MultiDeviceIteratorGetNextFromShard}}]]
[[RemoteCall]]
[[IteratorGetNext]]

Hi @1202zhyl, thanks for reporting the issue. I have investigated the problem. It turns out that Tensorflow has issue loading a Manylinux custom op.
I have uploaded the new snapshot wheel. Could you uninstall the flink-ml-framework and flink-ml-tensorflow and try follow the quick start again. Also make sure that the flink-ml-tensorflow version is 0.4.dev20220209.
#698 should fix this problem.

@Sxnan I have tried again following what u said and it works like a charm. Thanks a loooooot!

repo: flink-extended/dl-on-flink


text:
Implement Giter8 Template

Implement Gitet8 project template for flink-scala-api.

Done: https://github.com/novakov-alexey/flink-scala-api.g8

We should mention the template in the Readme

Agree. I have added a link to the Readme

authors: mzuehlke novakov-alexey

repo: flink-extended/flink-scala-api


text:
Allow camelCase for python standard libraries.

(Unfortunately) some libraries in the python standard library do not follow pep8. This means that people using them are forced to write non pep8-compliant code. This code should be accepted by the pep8-naming plugin.
For example unittest.TestCase is meant to be overridden so setUp and tearDown can be implemented. The same goes for logging.Logger.

@lensvol feel free to try to fix this.

+1

@staeff care to submit a fix?

I'll look into it, but can't promise anything. I just came across this issue, when I was researching the problem.

@staeff then please understand that adding a +1 to a known issue that the maintainers are willing to accept a patch for is patently unhelpful.

@sigmavirus24 oops, sorry.

No worries.

authors: remcohaszing sigmavirus24 staeff


text:
FloatingFocusManager focusout handler - closes when clicking another button, does not close on outside click

I created a small reproduction in a branch in my fork: https://github.com/mihkeleidast/floating-ui/commit/c5b92d4b029d8902e5b5a3178cb4cb4b3072ad37
Ran across an inconsistency in how the focusout handler works. Two different scenarios at play here:
Scenario 1

Open Popover from the button
Click outside of the Popover, observe that it does not close
Click the "Second button", observe that the Popover remains open

Scenario 2

Open Popover from the button
Click the "Second button" observe that the Popover closes

As far as I debugged, the focusout handler fires in both cases when clicking outside of the floating element, but in scenario 1, when clicking the background, relatedTarget is null, so it does not fire the open change event.
It is kind of an edge case, but would be good if the behavior was consistent, to know what I should expect, as from the users perspective a random click outside should not change anything.
Some additional info: in my real usecase, I do not have such Popovers, rather it is a drawer-like component (ex https://shoelace.style/components/drawer) that can be configured to not render on top of other content, rather it would render aside the main page. In this context, I have floating-ui configured to not close the floating element on outside click, but this issue means it still does in some cases. I can create a more realistic sandbox, if necessary, though I think the above describes the issue in enough detail.

I feel like a drawer component should have modal focus management? If it has a backdrop

I know we talked about a similar thing in https://github.com/floating-ui/floating-ui/issues/1771. In there, you said about a potential option to disable the focusout behavior:

I guess the issue is, if there was an option to remove the focusout/blur listeners, how does a tabbing keyboard user have it close for them when navigating out of it? Or it's okay that it gets left open?
If a floating element gets rendered in a portal, it has to be modal otherwise the user's focus will get lost since it teleports to the end of the document not inline

I think the second part is not relevant anymore, as floating-ui now does allow non-modal portaling.
For the first part, I think it would be OK (or even preferred) at least for my scenario that it would remain open. (though the next focused element should be the next from the reference still).

I feel like a drawer component should have modal focus management? If it has a backdrop

Yeah, agree with that, but as I mentioned, my Drawer can be configured to render aside the main page, not on top of it, so it's more like "split screen" view, there is no backdrop covering the main page.

So I guess we have two options:

Add a prop that allows the user to disable focusout behavior.
Detect if a pointerdown event occurred on the related target right before the focusout occurred, if so prevent closing. Keeps keyboard/virtual cursor closing working.

I would go with the first, to allow disabling the focusout behavior, for my usecase this solves more problems actually - I'll try to put a PR together with a testable example, if that sounds good?

Hey, did you manage to get it working properly, when the only difference is that instead of popover we have nested dropdown menu (FloatingTree and FloatingNode)?

authors: adamborowski atomiks mihkeleidast

repo: floating-ui/floating-ui


text:
feat(log): add WarnWrap helper

Adds a WarnWrap helper for logging and returning expected errors with severity=warn prepended to the key/value pairs.

Pull Request Test Coverage Report for Build 2235210547

8 of 8 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.1%) to 97.436%

Totals

Change from base Build 2235201855:
0.1%

Covered Lines:
190

Relevant Lines:
195

💛  - Coveralls

repo: floatme-corp/golflog


text:
Release ubi8 v1.2.3

Description:
Sync with osm 1.2.3

Testing done:
DONE

Affected area:

Functional Area

New Functionality
[ ]

CI System
[ ]

CLI Tool
[ ]

Certificate Management
[ ]

Control Plane
[ ]

Demo
[ ]

Documentation
[ ]

Egress
[ ]

Ingress
[ ]

Install
[ ]

Networking
[ ]

Observability
[ ]

Performance
[ ]

SMI Policy
[ ]

Security
[ ]

Sidecar Injection
[ ]

Tests
[ ]

Upgrade
[ ]

Other
[X]

Please answer the following questions with yes/no.

Does this change contain code from or inspired by another project? no

Is this a breaking change? no

Has documentation corresponding to this change been updated in the osm-edge-docs repo (if applicable)? no

Codecov Report

:exclamation: No coverage uploaded for pull request base (release-v1.2-ubi8@5373174). Click here to learn what that means.
Patch has no changes to coverable lines.

Additional details and impacted files
@@                 Coverage Diff                  @@
##             release-v1.2-ubi8     #136   +/-   ##
====================================================
  Coverage                     ?   63.30%
====================================================
  Files                        ?      216
  Lines                        ?    16391
  Branches                     ?        0
====================================================
  Hits                         ?    10376
  Misses                       ?     5963
  Partials                     ?       52

Flag
Coverage Δ

unittests
63.30% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

authors: codecov-commenter cybwan

repo: flomesh-io/osm-edge


text:
zstd-safe compile error

Problem
Trying to get the voice transcription example up and running and get this error:
no `ZSTD_c_experimentalParam6` in `ZSTD_cParameter`     |             help: a similar name exists in the module: `ZSTD_c_experimentalParam1`
Note that I am trying to implement this in my Tauri app, not sure if that's relevant.
Steps To Reproduce

Follow quick start guide
run npm run tauri dev
error shows in console

Expected behavior
It builds properly.
Environment:

Renderer version: Kalosm 0.2.1
Rust version: 1.79.0
OS info: Windows 11
Tauri: 1.6.0

Questionnaire

[x] I'm interested in fixing this myself but don't know where to start
[ ] I would like to fix and I have a solution
[ ] I don't have time to fix this right now, but maybe later

I also tried all other versions of Kalosm to no avail. I'd be really grateful for any help on this issue, really want to get it added to my app 🤘

You can add zstd-sys = "=2.0.9" to your cargo.toml to avoid the build error. One of the dependencies kalosm uses relied on unstable features that broke in a minor version. This issue should also be fixed in the git version of kalosm

That fixed it thanks! Now I'm getting a different build error, starting a new issue

Update: I fixed the other build error by manually installing clang, but now I'm getting the zstd-safe compile error again, even with your fix implemented. I'm ultimately deeming this library isn't ready for my production app, but still figured I'd let you know. Thanks for the help!

had the same initial error, which disappeared when i use zstd-sys = "=2.0.9". however i'm getting a new error
error[E0133]: call to unsafe function `EnvOpenOptions::open` is unsafe and requires unsafe function or block
   --> /Users/hanselke/.cargo/registry/src/index.crates.io-6f17d22bba15001f/kalosm-language-0.2.2/src/vector_db.rs:98:19
    |
98  |           let env = EnvOpenOptions::new()
    |  ___________________^
99  | |             .map_size(TWENTY_HUNDRED_MIB)
100 | |             .open(path)?;
    | |_______________________^ call to unsafe function
    |
    = note: consult the function's documentation for information on how

Heed also published a minor release which makes a function unsafe in a minor version. kalosm 0.2.2 and kalosm-langauge 0.2.3 were both just published which fixes these issues

authors: DaveyUS ealmloff hanselke

repo: floneum/floneum


text:
template.yaml doesn't pass the sam validate

invalid YAML template: json: unsupported type: map[interface {}]interface {}

The "No function defined..." issue was also reported here: https://github.com/awslabs/aws-sam-local/issues/289
Replacing the ANY http method with GET and POST handlers solves all example cases from the README:
    Events:
        GetRequest:
          Type: Api
          Properties:
            Path: /
            Method: GET
            RestApiId: !Ref ExampleAPI
        PostRequest:
          Type: Api
          Properties:
            Path: /
            Method: POST
            RestApiId: !Ref ExampleAPI


text:
D3D11/GL: need common solution for gl_FragCoord

A common solution would be good which doesn't require the display resolution (e.g. fullscreen quad's UV coords)?

Isn't SV_Position as an input to the PS the exact same thing? I'm not sure on this.

Yes, it it, only difference is that it must be declared as an pixel shader input parameter (I'm always feeding SV_Position into the pixel shader, seems to be removed by the shader compiler if not used in the shader, so no need to complicate the shader code generator with this).

authors: floooh ongamex

repo: floooh/oryol


text:
use per-resource type sg_id types

Instead of a generic sg_id there should be sg_buffer_id, sg_image_id, etc...

...I guess a better name would simply be sg_buffer, sg_image, etc... without the '_id'

done, but I need to figure out how to get the compilers emit warnings when assigning using the wrong type (since everything is uint32_t underneath at least clang doesn't complain when using a sg_image when an sg_buffer is expected, etc...

What about typedef handle like vulkan?

Typedefs are just aliases so they're not going to offer type safety. You'll want a struct for each id type, like struct sg_buffer { int32_t id; };

I'll try this, and also will have a look at the Vulkan headers, thanks!

You can use something similar to VK_DEFINE_HANDLE then have the struct implemented per backend, under opengl it would be, for example sg_buffer_id with gl handle and some other props you need.

Ok I wrapped the id into a struct, and type checking works now... let's see how (in-)convenient this will be with designed-initialisers though...

reminder feedback from @pervognsen:

To reply to your final comment (since I can't reply to closed issues): API users shouldn't need to deal with the id fields.

Just the structs as a whole. And for sentinels, you can do e.g. #define SG_BUFFER_NONE ((sg_buffer){0}) with C99 compound literals.

authors: amerkoleci floooh pervognsen

repo: floooh/sokol

license: Zlib


text:
Feature/observation

Adding new SMDX-Attributes
Adding new SDMX-Dimensions
Adding new SDMX-Concepts
Adding a qb:dimension (measureType)
Resolution of prefix in all the Entity types
Quality Code analysis

LGTM

authors: flopezag jicarretero

repo: flopezag/IoTAgent-Turtle


text:
Allow data to be persisted on disk using the -v flag on runtime

now it is possible to add for example -v /d/gamify-bot/db:/usr/src/app/db in order to persist the data on disk

Rename db to data, and update documentation to explain how to deploy with DB on a separate volume.

authors: florentw rudyattieh

repo: florentw/gamify-bot


text:
Breaks sudo.

When run like this:
sudo apt-get install -y ansible
sudo sh -c "echo '- src: https://github.com/florianutz/ubuntu2004_cis' >> /etc/ansible/requirements.yml"
cd /etc/ansible/
sudo ansible-galaxy install -p roles -r /etc/ansible/requirements.yml

sudo sh -c "cat > /etc/ansible/harden.yml <<EOF
- name: Harden Server
  hosts: localhost
  connection: local
  become: yes
  roles:
    - ubuntu2004_cis
EOF
"
sudo ansible-playbook /etc/ansible/harden.yml

sudo apt-get install cracklib-runtime -y

It breaks sudo.
In order to confirm:
1- install fresh ubuntu 20.04
2- give your user a password, any password.
3- add your user to sudo group
4- run the script above
5- test "sudo su"
6- reboot the machine
7- test "sudo su" now

I think this is a feature and not a bug. Check 5.3.2
You can easily check the status of your failed logon count by executing pam_tally2 as root
This keeps bad guys out of Grayskull.

I am not a bad guy. I enter the correct password that I set, su to another user, you can "sudo su" fine, but on the first user created this will appear.

I did not say that you are a bad guy. But maybe you use a bad ssh client configuration which attempt to use e.g. password before pubkey. Or some other service which will generate a failed logon. Just ssh into your machine. If sudo not works wait for 15 minutes (Timeout set in ansible role) and try it again.

@devatnull any updates on this?

Yes, you are right, you have to wait 15 minutes. Password auth on my server is closed only pubkey, same behavior from terminal and termius ssh client. But in my opinion there should be an indicator about this in the readme. Thanks for your time, we can close the issue.

this error occurs occasionally. sometimes people have stored several ssh keys on there client. the ssh client then tries all keys and generates an incorrect login with each incorrect key.

@devatnull I came across the following link https://access.redhat.com/solutions/29233 . Are you able to verify if disabling ChallengeResponseAuthentication solve the problem?

authors: devatnull florianutz


text:
wget is missing from conda/requirements.txt

wget is a requirement for the sumo setup but is missing from our requirements files

Additionally, brew seems to be a requirement for macs.

repo: flow-project/flow


text:
added mock imports

This should help the generation of documentation in readthedocs

Pull Request Test Coverage Report for Build 2778

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 87.034%

Totals

Change from base Build 2767:
0.0%

Covered Lines:
7404

Relevant Lines:
8507

💛  - Coveralls

LGTM

authors: AboudyKreidieh coveralls fywu85


text:
Using log time instead of fluentd time on kubernetes.

I using fluenbit to collecting log data form pod on kubernetes,  forward log data to fluentd and then output them to aws s3.
The log data forward to fluentd like that:
2020-05-06 01:00:00.055189181 +0000 kube.forward: {"log":"{ name: 'tony', logtime: '2020-05-01T01:00:00.421Z' }\n","stream":"stdout","time":"2020-05-06T08:06:11.055189181Z","kubernetes":{"pod_name":"example-54889df4b6-qdbrw","namespace_name":"logging","container_name":"example","docker_id":"42b7685e63e751f9b4f27b9d34ff8d9e62fc8ae1d82c1876a43db42958f56f26"}}

My fluentd config like that:
kind: ConfigMap
apiVersion: v1
metadata:
  name: fluentd-config
  namespace: logging
data:
  fluent.conf: |-
    <system>
      log_level debug
    </system>

    <source>
      @type forward
      port 24224
      bind 0.0.0.0
      tag kube.forward
    </source>

    <match **>
        @type s3
        s3_region "us-west-2"
        s3_bucket "logdata"
        path "year=%Y/month=%m/day=%d/hour=%H"
    </match>

I expect that the s3 path use log.logtime instead of fluentd time, it mean that I want my log data was stoaged in logdata/2020/05/01/01, instead of logdata/2020/05/06/01. Someone know how to do that?

@repeatedly Please help me.

repo: fluent/fluentd


text:
Adding link to github account of author

Co-Authored-By: Dao Cong Tien tiendc@vn.fujitsu.com
Signed-off-by: Nguyen Hai Truong truongnh@vn.fujitsu.com

Looks good. Thanks!


text:
Liner notes functionality

What is the problem you are trying to solve?
Make it possible to automatically generate PDF-ready liner notes
What solution would you like?
Liner notes build target which will generate an HTML bundle from the lyrics and track information, and which also allows you to insert text fragments like an intro and a preamble, ideally formatted in Markdown.

Some ideas about how this can work:
The album.json can get a section called "notes" which is a key->value mapping to Markdown files or stringlists, and a slot for a Jinja template (with a reasonable default provided, and examples given in documentation).
At encode time, the metadata gets parsed into a keystore with track info and the "notes" map, with all Markdown and lyrics pre-processed into HTML, and this is passed along to Jinja.
Jinja is also provided with some basic image rendition stuff, so that album and track artwork can be formatted into the resulting output.
At the end, the user has a liner notes directory with index.html and images in it, and then can save to PDF for bundling on Bandcamp/itch/etc.

repo: fluffy-critter/bandcrash


text:
fixed (#176)

descriptions
fixed the images to centre from right in all types of devices (bug fixed)
issue
#176  fixed
preview link-
you can preview my code change through this link
https://trusting-swanson-0ef044.netlify.app/
and the image is fixed in all types of devices you can check with any types of screen it fixed through this link
screenshot fixed

@jhung @colinbdclark you can check my code change through this link  https://trusting-swanson-0ef044.netlify.app/
i fixed this bug in all types of devices
thanks i hope you like it

Thanks for your contributions, @Raunaksingh100. I've left comments on the issue you filed, #176, regarding this. At the moment, we're not accepting pull requests for styling issues while the site is being partially redesigned and ported to a static site generator.
For future pull requests, please also ensure that you're following the commit message guidelines for our community, which you can find in the wiki. For example, "Fixed" isn't a very informative commit message when someone is looking back at the history of the code later.

@colinbdclark sure

with the same code the two issues  fixed you can test with any screen or can decrease the text size no bug plz merge this pr
you can test the two issues from the this link -------- https://trusting-swanson-0ef044.netlify.app/
@colinbdclark  thanks


text:
GH-27: Added better feedback on badly formed JSON configuration files (resolves #27).

See #27 for details.

To see an example of the output, use a command like the following in this package/branch:
npm run lint -- --configFile .fluidlintallrc-badJSON

I also found and fixed an issue we missed in #60, namely the line/column number reporting was not correct for JSONlint output.

Thanks, this works brilliantly!

repo: fluid-project/fluid-lint-all


text:
How to preprocess the initialValue?

valueTransformer: (value) => int.tryParse(value) will convert the value to a number, but next time when I open the form the initialValue is a number, this will lead an error: Expected a value of type 'String?', but got one of type 'int'。
Is there an initialValueTransformer or some way I can use to convert the initialValue to a String that the FormBuilderTextFieldexpected？

Just use the .toString() method.
int numbers = 12345;

initialValue: numbers.toString();

@jaxnz
Thanks, but .toString() is not what I want. If the valueTransformer is  valueTransformer: (value) => int.parse(value) /100, so I need something can perform the reverse process initialValueTransformer: (value) => (value * 100).toString(), not only just .toString(). But It seems that there is no such property.

as a workaround , in your controller transform all integers to strings before you set initialValue

@takifouhal The initialValue needs to be preTransformed. Do you mean not to pass the transformed value to initialValue, just keep a reference to it to compare later?

authors: BenjiFarquhar Cinux-Chosan jaxnz


text:
TV SDK could not be found. Trying with Wearable SDK...

Hello Flutter tizen noobie here!
I just want some help in fixing this one. I cannot find enough documentations about this issue. This happened when I try running the app with this webview_flutter_tizen: ^0.3.10 added in the pubspec.yaml (as per plugin documentation says.). I cannot successfully run the app in my TV emulator(don't have physical device). Attached screenshots are my pubspec.yaml configuration and the error. Thanks in advance.

TV SDK could not be found. Trying with Wearable SDK.

This message itself is normal because Samsung TVs do not officially come with native app build support (only web and .NET are supported) and the tool automatically falls back to the Wearable SDK. The message will appear when you build any flutter-tizen plugin but not only webview_flutter_tizen.
Probably your build has failed because webview_flutter_tizen is not supported on emulator devices (see the Device limitations section in the repo's README). Currently there's no web engine binary available for emulator devices (x86) as you can see in https://github.com/flutter-tizen/plugins/tree/master/packages/webview_flutter/tizen/lib. We're sorry for not clearly mentioning this in the plugin README.
@bwikbs @bbrto21 Do you have any plan to add support for the x86 architecture?

TV SDK could not be found. Trying with Wearable SDK.

This message itself is normal because Samsung TVs do not officially come with native app build support (only web and .NET are supported) and the tool automatically falls back to the Wearable SDK. The message will appear when you build any flutter-tizen plugin but not only webview_flutter_tizen.
Probably your build has failed because webview_flutter_tizen is not supported on emulator devices (see the Device limitations section in the repo's README). Currently there's no web engine binary available for emulator devices (x86) as you can see in https://github.com/flutter-tizen/plugins/tree/master/packages/webview_flutter/tizen/lib. We're sorry for not clearly mentioning this in the plugin README.
@bwikbs @bbrto21 Do you have any plan to add support for the x86 architecture?

Alright will be checking the link you have provided and thank you for clarifying things.

@swift-kim @curtlowellv
I'm sorry for late response. WebView for the emulator is currently being prepared.
But it's delayed for other priority issue. and If you want, you can use the following temporary patches.
https://github.com/bwikbs/plugins/commit/2f4e2461dbe8219f3b8b6def7c507c6fbda12e49
I confirmed the operation in the 6.5 TV emulator today.
(Because of the current internal behavior issue, it is recommended that you test on sites like naver, not the apahe license.)

The emulator (x86 architecture) support has been added to webview_flutter_tizen 0.4.0 but it's still in an early stage and has some bugs. More work will be done on the package in the future. I'll close this issue anyway.

authors: bwikbs curtlowellv swift-kim

repo: flutter-tizen/flutter-tizen


text:
[Web] some characters are missing from text

Hi, when i run the code without any renderer some characters are missing from text but Hindi text comes right:

Nut when i run code with html renderer no missing charcters but hindi text don't come right:

Output of flutter docter -v
[√] Flutter (Channel beta, 2.5.0, on Microsoft Windows [Version 10.0.19042.1586], locale en-IN)
• Flutter version 2.5.0 at F:\src\flutter_windows_2.5.0-beta\flutter
• Upstream repository https://github.com/flutter/flutter.git
• Framework revision 4cc385b4b8 (7 months ago), 2021-09-07 23:01:49 -0700
• Engine revision f0826da7ef
• Dart version 2.14.0
[√] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
• Android SDK at C:\Users\lenovo\AppData\Local\Android\sdk
• Platform android-31, build-tools 30.0.3
• Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
• Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)
• All Android licenses accepted.
[√] Chrome - develop for the web
• Chrome at C:\Program Files (x86)\Google\Chrome\Application\chrome.exe
[√] Android Studio (version 2020.3)
• Android Studio at C:\Program Files\Android\Android Studio
• Flutter plugin can be installed from:
https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build 11.0.10+0-b96-7249189)
[√] Connected device (2 available)
• Chrome (web) • chrome • web-javascript • Google Chrome 99.0.4844.84
• Edge (web)   • edge   • web-javascript • Microsoft Edge 97.0.1072.55
• No issues found!

Hi @ArpanaSwarnkar, Thanks for filing the issue.  Are you using any custom font?  Can you check if this issue is related to any specific font?  Also, You seem to be using an older version of flutter. Please try to upgrade to the latest stable version using flutter upgrade, If the issue persists then please write back with a minimal and complete code sample.

Thanks for the update, Please share a minimal and complete reproducible code to investigate further.

authors: ArpanaSwarnkar maheshmnj

repo: flutter/flutter


text:
devicelab win salt states are failing

Most of the win salt states are failing to apply on win-2, seemingly due to some recent changes that might have been made.
-------------
Succeeded:  6
Failed:    22

fixed in go/tircl/519507


text:
FutureBuilder not work when future send a request and response with http status code >=300

Steps to Reproduce

Execute flutter run on the code sample
...
...

Expected results:
builder: (context2, snapshot) is called
Actual results:
nothing hanppend

class _EmailOrMfaCodeVerifyState extends State {
  Future _sendCodeFuture;
@override
void initState() {
super.initState();
_sendCodeFuture = AccountUseCase.sendEmailCode(widget.tempToken);
}
@override
Widget build(BuildContext context) {
return Scaffold(
appBar: OnesAppBar(
title: const Text(OnesStrings.two_factor_auth_title),
),
body: Container(
decoration: const BoxDecoration(
color: OnesColors.largeGray,
),
// padding: const EdgeInsets.symmetric(horizontal: 16.0),
constraints: const BoxConstraints.expand(),
child:
FutureBuilder(
builder: (context2, snapshot) {
Widget verifyCodeStatusLabel;
switch (snapshot.connectionState) {
case ConnectionState.done:
if (snapshot.hasError) {
Toaster.showMessage(
(snapshot.error as HttpError).errorMessage);
}
verifyCodeStatusLabel = Text("error message",
textAlign: TextAlign.left,
style: globalNavigatorKey.textTheme.bodyText2.copyWith(
color: OnesColors.primaryBlue));
break;
case ConnectionState.waiting:
verifyCodeStatusLabel = _buildLoadingWidget(
OnesStrings.email_verify_method_title4,
color: OnesColors.lightGray);
break;
default:
verifyCodeStatusLabel = Container();
break;
}
        return InkWell(
          onTap: () {
            setState(() {
              _sendCodeFuture = AccountUseCase.sendEmailCode(widget.tempToken);
            });
          },
          child: Padding(
            padding: const EdgeInsets.only(top: 16.0),
            child: verifyCodeStatusLabel,
          ),
        );
      },
      future: _sendCodeFuture,
    ),
  ),
);

}
}
2.AccountUseCase.sendEmailCode(widget.tempToken) sent a request and
request:
curl -H 'user-agent: Dart/2.17 (Android/9; Arch/arm64-v8a) AppVersion/1.0.0 (ai.ones.project.android.dev.old; BuildNumber/1)' -H 'content-type: application/json; charset=utf-8' -H 'host: mars-dev.myones.net:15144' --data-binary '{"tempToken":"CPXmARuw","type":"email"}' --compressed 'https://mars-dev.myones.net:15144/api/project/auth/send_code'
response:

Logs

[✓] Flutter (Channel stable, 3.0.4, on macOS 12.3.1 21E258 darwin-arm, locale
    zh-Hans-CN)
    • Flutter version 3.0.4 at /Users/ones/Library/flutter
    • Upstream repository git@github.com:flutter/flutter.git
    • Framework revision 85684f9300 (4 months ago), 2022-06-30 13:22:47 -0700
    • Engine revision 6ba2af10bb
    • Dart version 2.17.5
    • DevTools version 2.12.2
    • Pub download mirror https://pub.flutter-io.cn
    • Flutter download mirror https://storage.flutter-io.cn

[✗] Android toolchain - develop for Android devices
    • Android SDK at /Users/ones/Library/Android/sdk
    ✗ cmdline-tools component is missing
      Run `path/to/sdkmanager --install "cmdline-tools;latest"`
      See https://developer.android.com/studio/command-line for more details.

[!] Xcode - develop for iOS and macOS (Xcode 13.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    ! CocoaPods 1.10.2 out of date (1.11.0 is recommended).
        CocoaPods is used to retrieve the iOS and macOS platform side's plugin
        code that responds to your plugin usage on the Dart side.
        Without CocoaPods, plugins will not work on iOS or macOS.
        For more info, see https://flutter.dev/platform-plugins
      To upgrade see
      https://guides.cocoapods.org/using/getting-started.html#installation for
      instructions.

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[!] Android Studio (not installed)
    • Android Studio not found; download from
      https://developer.android.com/studio/index.html
      (or visit https://flutter.dev/docs/get-started/install/macos#android-setup
      for detailed instructions).

[✓] IntelliJ IDEA Ultimate Edition (version 2022.1.4)
    • IntelliJ at /Applications/IntelliJ IDEA.app
    • Flutter plugin version 69.0.4
    • Dart plugin version 221.6008.15

[✓] Connected device (3 available)
    • JKM AL00a (mobile) • HYJNW18A15002346 • android-arm64  • Android 9 (API
      28)
    • macOS (desktop)    • macos            • darwin-arm64   • macOS 12.3.1
      21E258 darwin-arm
    • Chrome (web)       • chrome           • web-javascript • Google Chrome
      105.0.5195.102
    ! Error: Unable to prepare Ha0 for development.  (code -1)

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 3 categories.

Hi @lyf571321556
This issue doesn't seem to describe a bug or a feature request. Please see https://flutter.dev/community for resources and asking questions like this,
you may also get some help if you post it on Stack Overflow and if you need help with your code, please see https://www.reddit.com/r/flutterhelp/
Closing, as this isn't an issue with Flutter itself. If you disagree, please write in the comments and I will reopen it.
Thank you


text:
Task :app:compileFlutterBuildRelease FAILED  -  Dart snapshot generator failed with exit code -1073741674

I tried building my flutter app using flutter build apk --verbose and i got an error
[+234699 ms] Dart snapshot generator failed with exit code -1073741674
[+46198 ms] > Task :app:compileFlutterBuildRelease FAILED

flutter build apk --verbose Error

[
//Hard to cut the log short to here cause the issue body is too long but This is where the error started from
[+234699 ms] Dart snapshot generator failed with exit code -1073741674
[+46198 ms] > Task :app:compileFlutterBuildRelease FAILED
[   +1 ms] :app:compileFlutterBuildRelease (Thread[Execution worker for ':' Thread 3,5,main]) completed. Took 4 mins 44.685 secs.
[   +1 ms] :video_player_android:generateReleaseRFile (Thread[Execution worker for ':' Thread 2,5,main]) completed. Took 4 mins 49.732 secs.
[  +86 ms] :video_player_android:writeReleaseAarMetadata (Thread[included builds,5,main]) completed. Took 4 mins 45.173 secs.
[ +530 ms] FAILURE: Build failed with an exception.
[ +146 ms] * Where:
[ +234 ms] Script 'C:\Programming\Flutter\Sdk\flutter\packages\flutter_tools\gradle\flutter.gradle' line: 1159
[ +633 ms] * What went wrong:
[  +65 ms] Execution failed for task ':app:compileFlutterBuildRelease'.
[   +3 ms] > Process 'command 'C:\Programming\Flutter\Sdk\flutter\bin\flutter.bat'' finished with non-zero exit value 1
[   +2 ms] * Try:
[   +1 ms] > Run with --debug option to get more log output.
[   +1 ms] > Run with --scan to get full insights.
[   +1 ms] * Exception is:
[   +5 ms] org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':app:compileFlutterBuildRelease'.
[  +22 ms]      at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.lambda$executeIfValid$1(ExecuteActionsTaskExecuter.java:147)
[  +22 ms]      at org.gradle.internal.Try$Failure.ifSuccessfulOrElse(Try.java:282)
[  +25 ms]      at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeIfValid(ExecuteActionsTaskExecuter.java:145)
[  +14 ms]      at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:133)
[   +2 ms]      at org.gradle.api.internal.tasks.execution.CleanupStaleOutputsExecuter.execute(CleanupStaleOutputsExecuter.java:77)
[  +29 ms]      at org.gradle.api.internal.tasks.execution.FinalizePropertiesTaskExecuter.execute(FinalizePropertiesTaskExecuter.java:46)
[  +18 ms]      at org.gradle.api.internal.tasks.execution.ResolveTaskExecutionModeExecuter.execute(ResolveTaskExecutionModeExecuter.java:51)
[  +73 ms]      at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:57)
[   +2 ms]      at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:56)
[   +4 ms]      at org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:36)
[   +1 ms]      at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.executeTask(EventFiringTaskExecuter.java:77)
[   +2 ms]      at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:55)
[   +1 ms]      at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:52)
[   +1 ms]      at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:204)
[   +2 ms]      at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:199)
[   +1 ms]      at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:66)
[   +1 ms]      at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:59)
[   +1 ms]      at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:157)
[   +2 ms]      at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:59)
[ +129 ms]      at org.gradle.internal.operations.DefaultBuildOperationRunner.call(DefaultBuildOperationRunner.java:53)
[  +55 ms]      at org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:73)
[   +2 ms]      at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter.execute(EventFiringTaskExecuter.java:52)
[   +1 ms]      at org.gradle.execution.plan.LocalTaskNodeExecutor.execute(LocalTaskNodeExecutor.java:74)
[   +1 ms]      at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:333)
[   +1 ms]      at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:320)
[   +1 ms]      at
org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:313)
[   +1 ms]      at
org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:299)
[   +2 ms]      at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.lambda$run$0(DefaultPlanExecutor.java:143)
[   +1 ms]      at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.execute(DefaultPlanExecutor.java:227)
[   +1 ms]      at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.executeNextNode(DefaultPlanExecutor.java:218)
[   +1 ms]      at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.run(DefaultPlanExecutor.java:140)
[   +1 ms]      at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64)
[   +1 ms]      at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48)
[   +1 ms]      at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
[   +1 ms]      at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
[   +1 ms]      at java.base/java.lang.Thread.run(Thread.java:833)
[   +1 ms] Caused by: org.gradle.process.internal.ExecException: Process 'command 'C:\Programming\Flutter\Sdk\flutter\bin\flutter.bat'' finished
with non-zero exit value 1
[   +2 ms]      at org.gradle.process.internal.DefaultExecHandle$ExecResultImpl.assertNormalExitValue(DefaultExecHandle.java:414)
[   +3 ms]      at org.gradle.process.internal.DefaultExecAction.execute(DefaultExecAction.java:38)
[   +1 ms]      at org.gradle.process.internal.DefaultExecActionFactory.exec(DefaultExecActionFactory.java:205)
[   +1 ms]      at org.gradle.api.internal.project.DefaultProject.exec(DefaultProject.java:1170)
[   +1 ms]      at org.gradle.api.internal.project.DefaultProject.exec(DefaultProject.java:1165)
[   +1 ms]      at org.gradle.api.Project$exec$9.call(Unknown Source)
[   +1 ms]      at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCall(CallSiteArray.java:47)
[   +1 ms]      at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:125)
[   +1 ms]      at org.codehaus.groovy.runtime.callsite.AbstractCallSite.call(AbstractCallSite.java:139)
[   +1 ms]      at BaseFlutterTask.buildBundle(C:\Programming\Flutter\Sdk\flutter\packages\flutter_tools\gradle\flutter.gradle:1159)
[   +2 ms]      at BaseFlutterTask$buildBundle.callCurrent(Unknown Source)
[   +1 ms]      at org.codehaus.groovy.runtime.callsite.CallSiteArray.defaultCallCurrent(CallSiteArray.java:51)
[   +1 ms]      at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:171)
[   +1 ms]      at org.codehaus.groovy.runtime.callsite.AbstractCallSite.callCurrent(AbstractCallSite.java:176)
[   +1 ms]      at FlutterTask.build(C:\Programming\Flutter\Sdk\flutter\packages\flutter_tools\gradle\flutter.gradle:1284)
[   +1 ms]      at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
[   +1 ms]      at java.base/java.lang.reflect.Method.invoke(Method.java:577)
[   +1 ms]      at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:104)
[   +1 ms]      at org.gradle.api.internal.project.taskfactory.StandardTaskAction.doExecute(StandardTaskAction.java:58)
[   +1 ms]      at org.gradle.api.internal.project.taskfactory.StandardTaskAction.execute(StandardTaskAction.java:51)
[   +1 ms]      at org.gradle.api.internal.project.taskfactory.StandardTaskAction.execute(StandardTaskAction.java:29)
[   +1 ms]      at org.gradle.api.internal.tasks.execution.TaskExecution$3.run(TaskExecution.java:242)
[   +1 ms]      at org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:29)
[   +1 ms]      at org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:26)
[   +1 ms]      at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:66)
[   +2 ms]      at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:59)
[   +1 ms]      at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:157)
[   +1 ms]      at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:59)
[   +1 ms]      at org.gradle.internal.operations.DefaultBuildOperationRunner.run(DefaultBuildOperationRunner.java:47)
[   +1 ms]      at org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:68)
[   +1 ms]      at org.gradle.api.internal.tasks.execution.TaskExecution.executeAction(TaskExecution.java:227)
[   +1 ms]      at org.gradle.api.internal.tasks.execution.TaskExecution.executeActions(TaskExecution.java:210)
[   +1 ms]      at org.gradle.api.internal.tasks.execution.TaskExecution.executeWithPreviousOutputFiles(TaskExecution.java:193)
[   +1 ms]      at org.gradle.api.internal.tasks.execution.TaskExecution.execute(TaskExecution.java:171)
[   +1 ms]      at org.gradle.internal.execution.steps.ExecuteStep.executeInternal(ExecuteStep.java:89)
[   +1 ms]      at org.gradle.internal.execution.steps.ExecuteStep.access$000(ExecuteStep.java:40)
[   +1 ms]      at org.gradle.internal.execution.steps.ExecuteStep$1.call(ExecuteStep.java:53)
[   +2 ms]      at org.gradle.internal.execution.steps.ExecuteStep$1.call(ExecuteStep.java:50)
[   +1 ms]      at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:204)
[   +6 ms]      at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:199)
[   +1 ms]      at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:66)
[   +1 ms]      at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:59)
[   +1 ms]      at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:157)
[   +4 ms]      at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:59)
[   +1 ms]      at org.gradle.internal.operations.DefaultBuildOperationRunner.call(DefaultBuildOperationRunner.java:53)
[   +1 ms]      at org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:73)
[   +1 ms]      at org.gradle.internal.execution.steps.ExecuteStep.execute(ExecuteStep.java:50)
[   +1 ms]      at org.gradle.internal.execution.steps.ExecuteStep.execute(ExecuteStep.java:40)
[   +1 ms]      at org.gradle.internal.execution.steps.RemovePreviousOutputsStep.execute(RemovePreviousOutputsStep.java:68)
[   +1 ms]      at org.gradle.internal.execution.steps.RemovePreviousOutputsStep.execute(RemovePreviousOutputsStep.java:38)
[  +44 ms]      at org.gradle.internal.execution.steps.ResolveInputChangesStep.execute(ResolveInputChangesStep.java:48)
[   +1 ms]      at org.gradle.internal.execution.steps.ResolveInputChangesStep.execute(ResolveInputChangesStep.java:36)
[   +1 ms]      at org.gradle.internal.execution.steps.CancelExecutionStep.execute(CancelExecutionStep.java:41)
[   +1 ms]      at org.gradle.internal.execution.steps.TimeoutStep.executeWithoutTimeout(TimeoutStep.java:74)
[   +1 ms]      at org.gradle.internal.execution.steps.TimeoutStep.execute(TimeoutStep.java:55)
[   +1 ms]      at org.gradle.internal.execution.steps.CreateOutputsStep.execute(CreateOutputsStep.java:51)
[   +1 ms]      at org.gradle.internal.execution.steps.CreateOutputsStep.execute(CreateOutputsStep.java:29)
[   +2 ms]      at org.gradle.internal.execution.steps.CaptureStateAfterExecutionStep.execute(CaptureStateAfterExecutionStep.java:61)
[   +1 ms]      at org.gradle.internal.execution.steps.CaptureStateAfterExecutionStep.execute(CaptureStateAfterExecutionStep.java:42)
[   +1 ms]      at org.gradle.internal.execution.steps.BroadcastChangingOutputsStep.execute(BroadcastChangingOutputsStep.java:60)
[   +1 ms]      at org.gradle.internal.execution.steps.BroadcastChangingOutputsStep.execute(BroadcastChangingOutputsStep.java:27)
[   +1 ms]      at org.gradle.internal.execution.steps.BuildCacheStep.executeWithoutCache(BuildCacheStep.java:180)
[   +2 ms]      at org.gradle.internal.execution.steps.BuildCacheStep.lambda$execute$1(BuildCacheStep.java:75)
[   +1 ms]      at org.gradle.internal.Either$Right.fold(Either.java:175)
[   +2 ms]      at org.gradle.internal.execution.caching.CachingState.fold(CachingState.java:59)
[   +1 ms]      at org.gradle.internal.execution.steps.BuildCacheStep.execute(BuildCacheStep.java:73)
[   +1 ms]      at org.gradle.internal.execution.steps.BuildCacheStep.execute(BuildCacheStep.java:48)
[   +1 ms]      at org.gradle.internal.execution.steps.StoreExecutionStateStep.execute(StoreExecutionStateStep.java:36)
[   +1 ms]      at org.gradle.internal.execution.steps.StoreExecutionStateStep.execute(StoreExecutionStateStep.java:25)
[   +1 ms]      at org.gradle.internal.execution.steps.RecordOutputsStep.execute(RecordOutputsStep.java:36)
[   +1 ms]      at org.gradle.internal.execution.steps.RecordOutputsStep.execute(RecordOutputsStep.java:22)
[   +1 ms]      at org.gradle.internal.execution.steps.SkipUpToDateStep.executeBecause(SkipUpToDateStep.java:110)
[   +1 ms]      at org.gradle.internal.execution.steps.SkipUpToDateStep.lambda$execute$2(SkipUpToDateStep.java:56)
[   +1 ms]      at java.base/java.util.Optional.orElseGet(Optional.java:364)
[   +1 ms]      at org.gradle.internal.execution.steps.SkipUpToDateStep.execute(SkipUpToDateStep.java:56)
[   +1 ms]      at org.gradle.internal.execution.steps.SkipUpToDateStep.execute(SkipUpToDateStep.java:38)
[   +1 ms]      at org.gradle.internal.execution.steps.ResolveChangesStep.execute(ResolveChangesStep.java:73)
[   +1 ms]      at org.gradle.internal.execution.steps.ResolveChangesStep.execute(ResolveChangesStep.java:44)
[   +1 ms]      at org.gradle.internal.execution.steps.legacy.MarkSnapshottingInputsFinishedStep.execute(MarkSnapshottingInputsFinishedStep.java:37)[   +1 ms]      at org.gradle.internal.execution.steps.legacy.MarkSnapshottingInputsFinishedStep.execute(MarkSnapshottingInputsFinishedStep.java:27)[   +1 ms]      at org.gradle.internal.execution.steps.ResolveCachingStateStep.execute(ResolveCachingStateStep.java:89)
[   +2 ms]      at org.gradle.internal.execution.steps.ResolveCachingStateStep.execute(ResolveCachingStateStep.java:50)
[   +1 ms]      at org.gradle.internal.execution.steps.ValidateStep.execute(ValidateStep.java:114)
[   +2 ms]      at org.gradle.internal.execution.steps.ValidateStep.execute(ValidateStep.java:57)
[   +1 ms]      at org.gradle.internal.execution.steps.CaptureStateBeforeExecutionStep.execute(CaptureStateBeforeExecutionStep.java:76)
[   +1 ms]      at org.gradle.internal.execution.steps.CaptureStateBeforeExecutionStep.execute(CaptureStateBeforeExecutionStep.java:50)
[   +3 ms]      at org.gradle.internal.execution.steps.SkipEmptyWorkStep.executeWithNoEmptySources(SkipEmptyWorkStep.java:249)
[   +2 ms]      at org.gradle.internal.execution.steps.SkipEmptyWorkStep.execute(SkipEmptyWorkStep.java:86)
[   +5 ms]      at org.gradle.internal.execution.steps.SkipEmptyWorkStep.execute(SkipEmptyWorkStep.java:54)
[   +2 ms]      at org.gradle.internal.execution.steps.RemoveUntrackedExecutionStateStep.execute(RemoveUntrackedExecutionStateStep.java:32)
[   +1 ms]      at org.gradle.internal.execution.steps.RemoveUntrackedExecutionStateStep.execute(RemoveUntrackedExecutionStateStep.java:21)
[   +1 ms]      at org.gradle.internal.execution.steps.legacy.MarkSnapshottingInputsStartedStep.execute(MarkSnapshottingInputsStartedStep.java:38)
[   +1 ms]      at org.gradle.internal.execution.steps.LoadPreviousExecutionStateStep.execute(LoadPreviousExecutionStateStep.java:43)
[   +1 ms]      at org.gradle.internal.execution.steps.LoadPreviousExecutionStateStep.execute(LoadPreviousExecutionStateStep.java:31)
[   +1 ms]      at org.gradle.internal.execution.steps.AssignWorkspaceStep.lambda$execute$0(AssignWorkspaceStep.java:40)
[   +1 ms]      at org.gradle.api.internal.tasks.execution.TaskExecution$4.withWorkspace(TaskExecution.java:287)
[   +1 ms]      at org.gradle.internal.execution.steps.AssignWorkspaceStep.execute(AssignWorkspaceStep.java:40)
[   +1 ms]      at org.gradle.internal.execution.steps.AssignWorkspaceStep.execute(AssignWorkspaceStep.java:30)
[   +1 ms]      at org.gradle.internal.execution.steps.IdentityCacheStep.execute(IdentityCacheStep.java:37)
[   +1 ms]      at org.gradle.internal.execution.steps.IdentityCacheStep.execute(IdentityCacheStep.java:27)
[        ]      at org.gradle.internal.execution.steps.IdentifyStep.execute(IdentifyStep.java:44)
[   +1 ms]      at org.gradle.internal.execution.steps.IdentifyStep.execute(IdentifyStep.java:33)
[   +1 ms]      at org.gradle.internal.execution.impl.DefaultExecutionEngine$1.execute(DefaultExecutionEngine.java:76)
[   +3 ms]      at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeIfValid(ExecuteActionsTaskExecuter.java:144)
[   +2 ms]      at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:133)
[   +1 ms]      at org.gradle.api.internal.tasks.execution.CleanupStaleOutputsExecuter.execute(CleanupStaleOutputsExecuter.java:77)
[   +2 ms]      at org.gradle.api.internal.tasks.execution.FinalizePropertiesTaskExecuter.execute(FinalizePropertiesTaskExecuter.java:46)
[   +2 ms]      at org.gradle.api.internal.tasks.execution.ResolveTaskExecutionModeExecuter.execute(ResolveTaskExecutionModeExecuter.java:51)
[   +1 ms]      at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:57)
[   +1 ms]      at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:56)
[   +1 ms]      at org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:36)
[   +1 ms]      at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.executeTask(EventFiringTaskExecuter.java:77)
[   +5 ms]      at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:55)
[   +2 ms]      at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:52)
[   +3 ms]      at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:204)
[   +3 ms]      at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:199)
[   +3 ms]      at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:66)
[   +2 ms]      at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:59)
[   +2 ms]      at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:157)
[   +2 ms]      at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:59)
[   +3 ms]      at org.gradle.internal.operations.DefaultBuildOperationRunner.call(DefaultBuildOperationRunner.java:53)
[   +2 ms]      at org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:73)
[   +4 ms]      at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter.execute(EventFiringTaskExecuter.java:52)
[   +2 ms]      at org.gradle.execution.plan.LocalTaskNodeExecutor.execute(LocalTaskNodeExecutor.java:74)
[   +2 ms]      at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:333)
[   +2 ms]      at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:320)
[   +2 ms]      at
org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:313)
[   +3 ms]      at
org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:299)
[   +2 ms]      at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.lambda$run$0(DefaultPlanExecutor.java:143)
[  +29 ms]      at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.execute(DefaultPlanExecutor.java:227)
[   +4 ms]      at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.executeNextNode(DefaultPlanExecutor.java:218)
[   +3 ms]      at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.run(DefaultPlanExecutor.java:140)
[   +8 ms]      at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64)
[   +1 ms]      at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48)
[   +1 ms]      at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
[   +1 ms]      at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
[   +2 ms]      at java.base/java.lang.Thread.run(Thread.java:833)
[   +2 ms] * Get more help at https://help.gradle.org
[   +1 ms] BUILD FAILED in 9m 30s
[   +2 ms] Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.
[   +3 ms] You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.[   +2 ms] See https://docs.gradle.org/7.4/userguide/command_line_interface.html#sec:command_line_warnings
[   +1 ms] 467 actionable tasks: 383 executed, 84 up-to-date
[   +1 ms] Watched directory hierarchies: []
[ +907 ms] Running Gradle task 'assembleRelease'... (completed in 574.9s)
[  +16 ms] "flutter apk" took 580,985ms.
[  +17 ms] Gradle task assembleRelease failed with exit code 1
[   +2 ms]
#0      throwToolExit (package:flutter_tools/src/base/common.dart:10:3)
#1      AndroidGradleBuilder.buildGradleApp (package:flutter_tools/src/android/gradle.dart:408:9)

#2      AndroidGradleBuilder.buildApk (package:flutter_tools/src/android/gradle.dart:184:5)

#3      BuildApkCommand.runCommand (package:flutter_tools/src/commands/build_apk.dart:109:5)

#4      FlutterCommand.run. (package:flutter_tools/src/runner/flutter_command.dart:1209:27)

#5      AppContext.run. (package:flutter_tools/src/base/context.dart:150:19)

#6      CommandRunner.runCommand (package:args/command_runner.dart:209:13)

#7      FlutterCommandRunner.runCommand. (package:flutter_tools/src/runner/flutter_command_runner.dart:281:9)

#8      AppContext.run. (package:flutter_tools/src/base/context.dart:150:19)

#9      FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:229:5)

#10     run.. (package:flutter_tools/runner.dart:62:9)

#11     AppContext.run. (package:flutter_tools/src/base/context.dart:150:19)

#12     main (package:flutter_tools/executable.dart:91:3)

[ +268 ms] ensureAnalyticsSent: 253ms
[   +4 ms] Running shutdown hooks
[   +1 ms] Shutdown hooks complete
[   +2 ms] exiting with code 1

but it works on debug mode without any problem. I have tried running flutter clean and flutter pub get still nothing
I even ran cd android, then ./gradlew clean build --stacktrace and I got the below error.
> Task :app:compileFlutterBuildProfile FAILED

FAILURE: Build failed with an exception.

* Where:
Script 'C:\Programming\Flutter\Sdk\flutter\packages\flutter_tools\gradle\flutter.gradle' line: 1159

* What went wrong:
Execution failed for task ':app:compileFlutterBuildProfile'.
> Process 'command 'C:\Programming\Flutter\Sdk\flutter\bin\flutter.bat'' finished with non-zero exit value 1

* Try:
> Run with --info or --debug option to get more log output.
> Run with --scan to get full insights.

* Exception is:
org.gradle.api.tasks.TaskExecutionException: Execution failed for task ':app:compileFlutterBuildProfile'.
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.lambda$executeIfValid$1(ExecuteActionsTaskExecuter.java:147)
        at org.gradle.internal.Try$Failure.ifSuccessfulOrElse(Try.java:282)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeIfValid(ExecuteActionsTaskExecuter.java:145)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:133)
        at org.gradle.api.internal.tasks.execution.CleanupStaleOutputsExecuter.execute(CleanupStaleOutputsExecuter.java:77)
        at org.gradle.api.internal.tasks.execution.FinalizePropertiesTaskExecuter.execute(FinalizePropertiesTaskExecuter.java:46)
        at org.gradle.api.internal.tasks.execution.ResolveTaskExecutionModeExecuter.execute(ResolveTaskExecutionModeExecuter.java:51)
        at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:57)
        at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:56)
        at org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:36)
        at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.executeTask(EventFiringTaskExecuter.java:77)
        at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:55)
        at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:52)
        at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:204)
        at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:199)
        at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:66)
        at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:59)
        at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:157)
        at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:59)
        at org.gradle.internal.operations.DefaultBuildOperationRunner.call(DefaultBuildOperationRunner.java:53)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:73)
        at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter.execute(EventFiringTaskExecuter.java:52)
        at org.gradle.execution.plan.LocalTaskNodeExecutor.execute(LocalTaskNodeExecutor.java:74)
        at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:333)
        at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:320)
        at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:313)
        at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:299)
        at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.lambda$run$0(DefaultPlanExecutor.java:143)
        at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.execute(DefaultPlanExecutor.java:227)
        at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.executeNextNode(DefaultPlanExecutor.java:218)
        at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.run(DefaultPlanExecutor.java:140)
        at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64)
        at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48)
Caused by: org.gradle.process.internal.ExecException: Process 'command 'C:\Programming\Flutter\Sdk\flutter\bin\flutter.bat'' finished with non-zero
exit value 1
        at org.gradle.process.internal.DefaultExecHandle$ExecResultImpl.assertNormalExitValue(DefaultExecHandle.java:414)
        at org.gradle.process.internal.DefaultExecAction.execute(DefaultExecAction.java:38)
        at org.gradle.process.internal.DefaultExecActionFactory.exec(DefaultExecActionFactory.java:205)
        at org.gradle.api.internal.project.DefaultProject.exec(DefaultProject.java:1170)
        at org.gradle.api.internal.project.DefaultProject.exec(DefaultProject.java:1165)
        at org.gradle.api.Project$exec$8.call(Unknown Source)
        at BaseFlutterTask.buildBundle(C:\Programming\Flutter\Sdk\flutter\packages\flutter_tools\gradle\flutter.gradle:1159)
        at BaseFlutterTask$buildBundle.callCurrent(Unknown Source)
        at FlutterTask.build(C:\Programming\Flutter\Sdk\flutter\packages\flutter_tools\gradle\flutter.gradle:1284)
        at java.base/jdk.internal.reflect.DirectMethodHandleAccessor.invoke(DirectMethodHandleAccessor.java:104)
        at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:104)
        at org.gradle.api.internal.project.taskfactory.StandardTaskAction.doExecute(StandardTaskAction.java:58)
        at org.gradle.api.internal.project.taskfactory.StandardTaskAction.execute(StandardTaskAction.java:51)
        at org.gradle.api.internal.project.taskfactory.StandardTaskAction.execute(StandardTaskAction.java:29)
        at org.gradle.api.internal.tasks.execution.TaskExecution$3.run(TaskExecution.java:242)
        at org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:29)
        at org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:26)
        at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:66)
        at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:59)
        at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:157)
        at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:59)
        at org.gradle.internal.operations.DefaultBuildOperationRunner.run(DefaultBuildOperationRunner.java:47)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:68)
        at org.gradle.api.internal.tasks.execution.TaskExecution.executeAction(TaskExecution.java:227)
        at org.gradle.api.internal.tasks.execution.TaskExecution.executeActions(TaskExecution.java:210)
        at org.gradle.api.internal.tasks.execution.TaskExecution.executeWithPreviousOutputFiles(TaskExecution.java:193)
        at org.gradle.api.internal.tasks.execution.TaskExecution.execute(TaskExecution.java:171)
        at org.gradle.internal.execution.steps.ExecuteStep.executeInternal(ExecuteStep.java:89)
        at org.gradle.internal.execution.steps.ExecuteStep.access$000(ExecuteStep.java:40)
        at org.gradle.internal.execution.steps.ExecuteStep$1.call(ExecuteStep.java:53)
        at org.gradle.internal.execution.steps.ExecuteStep$1.call(ExecuteStep.java:50)
        at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:204)
        at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:199)
        at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:66)
        at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:59)
        at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:157)
        at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:59)
        at org.gradle.internal.operations.DefaultBuildOperationRunner.call(DefaultBuildOperationRunner.java:53)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:73)
        at org.gradle.internal.execution.steps.ExecuteStep.execute(ExecuteStep.java:50)
        at org.gradle.internal.execution.steps.ExecuteStep.execute(ExecuteStep.java:40)
        at org.gradle.internal.execution.steps.RemovePreviousOutputsStep.execute(RemovePreviousOutputsStep.java:68)
        at org.gradle.internal.execution.steps.RemovePreviousOutputsStep.execute(RemovePreviousOutputsStep.java:38)
        at org.gradle.internal.execution.steps.ResolveInputChangesStep.execute(ResolveInputChangesStep.java:48)
        at org.gradle.internal.execution.steps.ResolveInputChangesStep.execute(ResolveInputChangesStep.java:36)
        at org.gradle.internal.execution.steps.CancelExecutionStep.execute(CancelExecutionStep.java:41)
        at org.gradle.internal.execution.steps.TimeoutStep.executeWithoutTimeout(TimeoutStep.java:74)
        at org.gradle.internal.execution.steps.TimeoutStep.execute(TimeoutStep.java:55)
        at org.gradle.internal.execution.steps.CreateOutputsStep.execute(CreateOutputsStep.java:51)
        at org.gradle.internal.execution.steps.CreateOutputsStep.execute(CreateOutputsStep.java:29)
        at org.gradle.internal.execution.steps.CaptureStateAfterExecutionStep.execute(CaptureStateAfterExecutionStep.java:61)
        at org.gradle.internal.execution.steps.CaptureStateAfterExecutionStep.execute(CaptureStateAfterExecutionStep.java:42)
        at org.gradle.internal.execution.steps.BroadcastChangingOutputsStep.execute(BroadcastChangingOutputsStep.java:60)
        at org.gradle.internal.execution.steps.BroadcastChangingOutputsStep.execute(BroadcastChangingOutputsStep.java:27)
        at org.gradle.internal.execution.steps.BuildCacheStep.executeWithoutCache(BuildCacheStep.java:180)
        at org.gradle.internal.execution.steps.BuildCacheStep.lambda$execute$1(BuildCacheStep.java:75)
        at org.gradle.internal.Either$Right.fold(Either.java:175)
        at org.gradle.internal.execution.caching.CachingState.fold(CachingState.java:59)
        at org.gradle.internal.execution.steps.BuildCacheStep.execute(BuildCacheStep.java:73)
        at org.gradle.internal.execution.steps.BuildCacheStep.execute(BuildCacheStep.java:48)
        at org.gradle.internal.execution.steps.StoreExecutionStateStep.execute(StoreExecutionStateStep.java:36)
        at org.gradle.internal.execution.steps.StoreExecutionStateStep.execute(StoreExecutionStateStep.java:25)
        at org.gradle.internal.execution.steps.RecordOutputsStep.execute(RecordOutputsStep.java:36)
        at org.gradle.internal.execution.steps.RecordOutputsStep.execute(RecordOutputsStep.java:22)
        at org.gradle.internal.execution.steps.SkipUpToDateStep.executeBecause(SkipUpToDateStep.java:110)
        at org.gradle.internal.execution.steps.SkipUpToDateStep.lambda$execute$2(SkipUpToDateStep.java:56)
        at org.gradle.internal.execution.steps.SkipUpToDateStep.execute(SkipUpToDateStep.java:56)
        at org.gradle.internal.execution.steps.SkipUpToDateStep.execute(SkipUpToDateStep.java:38)
        at org.gradle.internal.execution.steps.ResolveChangesStep.execute(ResolveChangesStep.java:73)
        at org.gradle.internal.execution.steps.ResolveChangesStep.execute(ResolveChangesStep.java:44)
        at org.gradle.internal.execution.steps.legacy.MarkSnapshottingInputsFinishedStep.execute(MarkSnapshottingInputsFinishedStep.java:37)
        at org.gradle.internal.execution.steps.legacy.MarkSnapshottingInputsFinishedStep.execute(MarkSnapshottingInputsFinishedStep.java:27)
        at org.gradle.internal.execution.steps.ResolveCachingStateStep.execute(ResolveCachingStateStep.java:89)
        at org.gradle.internal.execution.steps.ResolveCachingStateStep.execute(ResolveCachingStateStep.java:50)
        at org.gradle.internal.execution.steps.ValidateStep.execute(ValidateStep.java:114)
        at org.gradle.internal.execution.steps.ValidateStep.execute(ValidateStep.java:57)
        at org.gradle.internal.execution.steps.CaptureStateBeforeExecutionStep.execute(CaptureStateBeforeExecutionStep.java:76)
        at org.gradle.internal.execution.steps.CaptureStateBeforeExecutionStep.execute(CaptureStateBeforeExecutionStep.java:50)
        at org.gradle.internal.execution.steps.SkipEmptyWorkStep.executeWithNoEmptySources(SkipEmptyWorkStep.java:249)
        at org.gradle.internal.execution.steps.SkipEmptyWorkStep.execute(SkipEmptyWorkStep.java:86)
        at org.gradle.internal.execution.steps.SkipEmptyWorkStep.execute(SkipEmptyWorkStep.java:54)
        at org.gradle.internal.execution.steps.RemoveUntrackedExecutionStateStep.execute(RemoveUntrackedExecutionStateStep.java:32)
        at org.gradle.internal.execution.steps.RemoveUntrackedExecutionStateStep.execute(RemoveUntrackedExecutionStateStep.java:21)
        at org.gradle.internal.execution.steps.legacy.MarkSnapshottingInputsStartedStep.execute(MarkSnapshottingInputsStartedStep.java:38)
        at org.gradle.internal.execution.steps.LoadPreviousExecutionStateStep.execute(LoadPreviousExecutionStateStep.java:43)
        at org.gradle.internal.execution.steps.LoadPreviousExecutionStateStep.execute(LoadPreviousExecutionStateStep.java:31)
        at org.gradle.internal.execution.steps.AssignWorkspaceStep.lambda$execute$0(AssignWorkspaceStep.java:40)
        at org.gradle.api.internal.tasks.execution.TaskExecution$4.withWorkspace(TaskExecution.java:287)
        at org.gradle.internal.execution.steps.AssignWorkspaceStep.execute(AssignWorkspaceStep.java:40)
        at org.gradle.internal.execution.steps.AssignWorkspaceStep.execute(AssignWorkspaceStep.java:30)
        at org.gradle.internal.execution.steps.IdentityCacheStep.execute(IdentityCacheStep.java:37)
        at org.gradle.internal.execution.steps.IdentityCacheStep.execute(IdentityCacheStep.java:27)
        at org.gradle.internal.execution.steps.IdentifyStep.execute(IdentifyStep.java:44)
        at org.gradle.internal.execution.steps.IdentifyStep.execute(IdentifyStep.java:33)
        at org.gradle.internal.execution.impl.DefaultExecutionEngine$1.execute(DefaultExecutionEngine.java:76)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeIfValid(ExecuteActionsTaskExecuter.java:144)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.execute(ExecuteActionsTaskExecuter.java:133)
        at org.gradle.api.internal.tasks.execution.CleanupStaleOutputsExecuter.execute(CleanupStaleOutputsExecuter.java:77)
        at org.gradle.api.internal.tasks.execution.FinalizePropertiesTaskExecuter.execute(FinalizePropertiesTaskExecuter.java:46)
        at org.gradle.api.internal.tasks.execution.ResolveTaskExecutionModeExecuter.execute(ResolveTaskExecutionModeExecuter.java:51)
        at org.gradle.api.internal.tasks.execution.SkipTaskWithNoActionsExecuter.execute(SkipTaskWithNoActionsExecuter.java:57)
        at org.gradle.api.internal.tasks.execution.SkipOnlyIfTaskExecuter.execute(SkipOnlyIfTaskExecuter.java:56)
        at org.gradle.api.internal.tasks.execution.CatchExceptionTaskExecuter.execute(CatchExceptionTaskExecuter.java:36)
        at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.executeTask(EventFiringTaskExecuter.java:77)
        at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:55)
        at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter$1.call(EventFiringTaskExecuter.java:52)
        at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:204)
        at org.gradle.internal.operations.DefaultBuildOperationRunner$CallableBuildOperationWorker.execute(DefaultBuildOperationRunner.java:199)
        at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:66)
        at org.gradle.internal.operations.DefaultBuildOperationRunner$2.execute(DefaultBuildOperationRunner.java:59)
        at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:157)
        at org.gradle.internal.operations.DefaultBuildOperationRunner.execute(DefaultBuildOperationRunner.java:59)
        at org.gradle.internal.operations.DefaultBuildOperationRunner.call(DefaultBuildOperationRunner.java:53)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor.call(DefaultBuildOperationExecutor.java:73)
        at org.gradle.api.internal.tasks.execution.EventFiringTaskExecuter.execute(EventFiringTaskExecuter.java:52)
        at org.gradle.execution.plan.LocalTaskNodeExecutor.execute(LocalTaskNodeExecutor.java:74)
        at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:333)
        at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$InvokeNodeExecutorsAction.execute(DefaultTaskExecutionGraph.java:320)
        at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:313)
        at org.gradle.execution.taskgraph.DefaultTaskExecutionGraph$BuildOperationAwareExecutionAction.execute(DefaultTaskExecutionGraph.java:299)
        at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.lambda$run$0(DefaultPlanExecutor.java:143)
        at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.execute(DefaultPlanExecutor.java:227)
        at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.executeNextNode(DefaultPlanExecutor.java:218)
        at org.gradle.execution.plan.DefaultPlanExecutor$ExecutorWorker.run(DefaultPlanExecutor.java:140)
        at org.gradle.internal.concurrent.ExecutorPolicy$CatchAndRecordFailures.onExecute(ExecutorPolicy.java:64)
        at org.gradle.internal.concurrent.ManagedExecutorImpl$1.run(ManagedExecutorImpl.java:48)

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0.

You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.

See https://docs.gradle.org/7.4/userguide/command_line_interface.html#sec:command_line_warnings

Execution optimizations have been disabled for 1 invalid unit(s) of work during this build to ensure correctness.
Please consult deprecation warnings for more details.

BUILD FAILED in 12m 2s
414 actionable tasks: 413 executed, 1 up-to-date

flutter doctor -v

$ flutter doctor -v
[√] Flutter (Channel stable, 3.3.4, on Microsoft Windows [Version 10.0.19045.2486], locale en-US)
    • Flutter version 3.3.4 on channel stable at C:\Programming\Flutter\Sdk\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision eb6d86ee27 (4 months ago), 2022-10-04 22:31:45 -0700
    • Engine revision c08d7d5efc
    • Dart version 2.18.2
    • DevTools version 2.15.0
Checking Android licenses is taking an unexpectedly long time...[√] Android toolchain - develop for Android devices (Android SDK version 33.0.1)
• Android SDK at C:\Users\kcib\AppData\Local\Android\Sdk
• Platform android-33, build-tools 33.0.1
• Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
• Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b03)
• All Android licenses accepted.
[X] Chrome - develop for the web (Cannot find Chrome executable at .\Google\Chrome\Application\chrome.exe)
! Cannot find Chrome. Try setting CHROME_EXECUTABLE to a Chrome executable.
[X] Visual Studio - develop for Windows
X Visual Studio not installed; this is necessary for Windows development.
Download at https://visualstudio.microsoft.com/downloads/.
Please install the "Desktop development with C++" workload, including all of its default components
[√] Android Studio (version 3.5)
• Android Studio at C:\Program Files\Android\Android Studio
• Flutter plugin version 44.0.1
• Dart plugin version 191.8593
• Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b03)
[√] VS Code (version 1.74.3)
• VS Code at C:\Users\kcib\AppData\Local\Programs\Microsoft VS Code
• Flutter extension version 3.58.0
[√] Connected device (2 available)
• Windows (desktop) • windows • windows-x64    • Microsoft Windows [Version 10.0.19045.2486]
• Edge (web)        • edge    • web-javascript • Microsoft Edge 109.0.1518.70
[√] HTTP Host Availability
• All required HTTP hosts are available
! Doctor found issues in 2 categories.

Please tell me if there is anything i should add to make it easier to resolve

@kcibdev Does this issue happen on the new Flutter project? If not so, can you provide a completed and minimal reproducible code sample so that we may verify this?
Also, please share the complete output of flutter build apk --verbose in a file and attach it here or you may share it via pastebin would also be helpful. Thanks!

authors: huycozy kcibdev