Display error reason, in case GIT repository being corrupted.

Gitea version (or commit ref):     image: gitea/gitea:1.12.3
Git version: 2.28.0
Operating system: RosberyPi64
Database (use [x]):

[ ] PostgreSQL
[ ] MySQL
[ ] MSSQL
[X] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[X] No
[ ] Not relevant

Log gist:

Description
Hi People,
I wonder if you can add a description on what's going on when a certain repository cannot be reached due to the fact that data is corrupted. This day I found out that one of my local repositories returning 500 whenever I try to see it in the web. The issue was unclear until I tried to push/pull from that repo.
As revealed some objects were corrupted/empty inside of the container, but they're seems to be NOT empty and fine in the local copy. Still not sure why, perhaps due to the power outage/improperly powering off RosberyPi.
PS: I tried to git fisck --full/removing corrupted/empty objects - still no way to reach repository.
Screenshots

If you run gitea in development mode, it will be displayed.


pocketbase: 0.15.3 -> 0.16.3

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/pocketbase/pocketbase/releases.
meta.description for pocketbase is: Open Source realtime backend in 1 file
meta.homepage for pocketbase is: https://github.com/pocketbase/pocketbase
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.16.2 with grep in /nix/store/wnhwn0srzmbfpr02332lz79x6x0nvbww-pocketbase-0.16.2
found 0.16.2 in filename of file in /nix/store/wnhwn0srzmbfpr02332lz79x6x0nvbww-pocketbase-0.16.2

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
pocketbase

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/wnhwn0srzmbfpr02332lz79x6x0nvbww-pocketbase-0.16.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A pocketbase https://github.com/r-ryantm/nixpkgs/archive/7fe68594c3d0633a74406fb3fc52719be13381ef.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/wnhwn0srzmbfpr02332lz79x6x0nvbww-pocketbase-0.16.2
ls -la /nix/store/wnhwn0srzmbfpr02332lz79x6x0nvbww-pocketbase-0.16.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

pocketbase

Maintainer pings
cc @dit7ya for testing.

Related https://github.com/NixOS/nixpkgs/pull/233615/.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/pocketbase/pocketbase/releases.
meta.description for pocketbase is: Open Source realtime backend in 1 file
meta.homepage for pocketbase is: https://github.com/pocketbase/pocketbase
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 0.16.3 with grep in /nix/store/a4f6kv1j1vq9rnb4bhgb4dpnz354z53j-pocketbase-0.16.3
found 0.16.3 in filename of file in /nix/store/a4f6kv1j1vq9rnb4bhgb4dpnz354z53j-pocketbase-0.16.3

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
pocketbase

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/a4f6kv1j1vq9rnb4bhgb4dpnz354z53j-pocketbase-0.16.3 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A pocketbase https://github.com/r-ryantm/nixpkgs/archive/65092de111b3f3ebb43abb9571add1da23bf4301.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/a4f6kv1j1vq9rnb4bhgb4dpnz354z53j-pocketbase-0.16.3
ls -la /nix/store/a4f6kv1j1vq9rnb4bhgb4dpnz354z53j-pocketbase-0.16.3/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

pocketbase

Maintainer pings
cc @dit7ya for testing.


Introduction of the Gtk struct to guarantee that Gtk is used within a single thread.

Initial implementation of the proposal in issue #3:

Introduces a Gtk struct which should be instantiated to use gtk functions.
Introduces Builder traits for each of the widgets to introduce constructors, that are implemented for the Gtk struct.
Makes the old constructors and main gtk functions unavailable.
Integrates these changes within the examples.

Note: not all of the widgets do implement Builder traits yet.

Woah. I'm afraid, starting this from converting the constructors is premature and likely to cause pointless busywork. That's why I created that issue - so we could discuss strategy.

I think what was proposed within that issue was already a good way of limiting the use of GTK+ to a single thread: changing the functions to be methods of a struct that cannot be sent to another thread. The changes within this pull request yield very usable results, at least, in my opinion (see the examples to get an idea). Furthermore, I have to say that this is probably the most straight-forward method, that doesn't involve checking the context at run-time.
To add to that issue, I don't think it is necessary to have method chaining, as it already seems to be simple enough as it is (e.g. gtk.button_with_label(...)).
However, I do get your concern with the amount of work involved with these changes. It would be nice to get the most common widgets in shape first (especially when integrating the new signal system). If that is desired, I can split this change up in smaller steps to work and contemplate at a slower pace.

Or would we still be expecting some major structural changes to the widgets in general?

Moving slower would be more comfortable.
Chaining does add a bit of complication but dumping all of the constructors into one namespace doesn't seem ideal either. Consider also this PR where I explore adding some structure to the modules layout. It may or may not be worthwhile to mimic that structure with these methods so the invocation would be along the lines of gtk.dialog().about(...), but we should move away from the flat organization.
A couple of smaller remarks:

the constructors shouldn't return Option, that convention was a mistake, there pointer is never NULL;
as is, the Builder suffix doesn't seem right, the traits make Gtk a factory not a builder;
rehashing the constructors is a good occasion to get rid of the separation between widgets and traits, see the linked PR.

As to major structural changes, I would like to reorganize the inheritance system, some prototypes I explore here and here

The other major category of widgets to apply that to would be buttons.
That convention could best be removed within its own pull request. Similar to the explicit casts that the compiler can infer nowadays.
On the Builder name, I agree with you that Factory would be a better naming choice.
Thanks for the links, I'll be reading through the material posted there.

I really don't like it this way. Having a factory seems so unnatural to me...

@GuillaumeGomez
Yes, it does seem awkward, possibly no other GUI library has made us deal with this. But we need to anchor the widgets to a thread and the choice seems to be between passing a reference to Gtk as the first argument to every constructor or making it a factory. And these two alternatives are almost one and the same because the first argument of a method is the receiver.
@StephanvanSchaik
There's another complication I hadn't recalled yesterday: one may want to create widgets in a signal handler and sneaking a Gtk reference in manually seems like a hassle. If the handler were to have access to a Gtk reference automatically, it would require every widget to actually carry that reference (or a clone of the struct).

I add as "against argument" that we can create a thread_local in gtk::init which set a value when it's created in the main thread. Then, every created widget after that check if it's created in the main thread by looking at the thread_local data. With that, we avoid all that factory (I really don't like it).
@jeremyletang: good for you ? (he's also against that factory)

Okay, so you prefer runtime checks then?

Totally.

Would you please state your and @jeremyletang's preference in #3 for the record?

Hi,
I think that make a big Gtk factory is not rusty at all. A better way to do this will be I think to create a thread_local storage during the first call of gtk::init(we consider that the user call it in the main thread, the behaviour stay the same between the two methods).
Then at each instantiation of a widget we can check if the thread_local storage is already set. If not I think we can fail() we an error message like `widget MUST be instantiates inside main thread as this will only be saw be the developer when he make it's tests.
According to the Gtk documentation, widgets instantiation cannot fail, so maybe we can not return an option on widget construction.
So we can fail if:

The c pointer == null
The user don't instantiate the widget in the main thread.

One might argue that employing dynamic checks may not be very Rusty either, but okay, that can work.


Quandl returns NaN data

Hi,
I've no trouble pulling in OHLC fields from quandl's WIKI  and CHRIS  databases while CFTC or YALE databases return the field names and date range but NaN data?
Following this ticket , I've added the new field names to the time_series_fields_list.csv but no dice...
This code works:
import datetime
from findatapy.util import SwimPool; SwimPool()
from findatapy.market import Market, MarketDataGenerator, MarketDataRequest
from findatapy.util.loggermanager import LoggerManager

logger = LoggerManager().getLogger(__name__)
market = Market(market_data_generator=MarketDataGenerator())

md_request = MarketDataRequest(
                start_date = "01 Jan 2000",
                data_source = 'quandl',
                category= 'fx',
                tickers = ['EC1'],
                fields = ['close', 'open', 'high', 'low'],
                vendor_tickers = ['CHRIS/CME_EC1'],
                vendor_fields = ['last', 'open', 'high', 'low'])

df = market.fetch_market(md_request)
print(df.tail(n=5))

But this returns NaN
import datetime
from findatapy.util import SwimPool; SwimPool()
from findatapy.market import Market, MarketDataGenerator, MarketDataRequest
from findatapy.util.loggermanager import LoggerManager

logger = LoggerManager().getLogger(__name__)
market = Market(market_data_generator=MarketDataGenerator())

md_request = MarketDataRequest(
                start_date = "01 Jan 1970",
                data_source = 'quandl',
                tickers = ['US_CONF_INDEX_VAL_INST'],
                fields = ['index value', 'standard error'],
                vendor_fields= ['index value', 'standard error'],
                vendor_tickers= ['YALE/US_CONF_INDEX_VAL_INST'])

df = market.fetch_market(md_request)
print(df.tail(n=5))

Thanks in advance

From memory, it doesn't allow field names with spaces (findatapy, will convert spaces in field names to underscore returned by Quandl?). However, let me double check this.


[NEEDS UPDATE] Exploring APIs with Postman and Azure AD authentication

First of all, the newest Postman (I use the 10.18.6, not sure the changes applied since what version) now uses different way to store the credential.
Major changes are the credential must be put first before the "Get New Access Token" button is pressed.
The correct way is now:

Select Type: OAuth 2.0 in Authorization tab
Go to "Configure New Token"
Fill the "Token Name" as you wish
Select Client Credentials as Grant Type
Access Token URL: must be https://login.microsoftonline.com/<tenant_id>/oauth2/v2.0/token , it won't work otherwise
Client ID: same as before
Client Secret: same as before
The most important thing is Scope (not sure why it's left out blank in the current manual): enter https://api.businesscentral.dynamics.com/.default
Try to get a new token by pressing "Get New Access Token" button, should all information inputted are correct then a token will be retrieved by Postman

Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: e026c87e-6bbe-9e7c-5ecc-e6f2943e2655
Version Independent ID: 81cb7f00-6d48-4d29-b47c-b9bc36ad87d8
Content: Getting Started Developing Connect Apps for Dynamics 365 Business Central - Business Central
Content Source: dev-itpro/developer/devenv-develop-connect-apps.md
Service: dynamics365-business-central
GitHub Login: @SusanneWindfeldPedersen
Microsoft Alias: solsen

It's an incomplete phrase in Step 3 "In the Scope field,"

This "scope" in the guide is empty, it should be https://api.businesscentral.dynamics.com/.default


[BUG]: onPlaybackRateChange and onPlaybackStateChange not called  iOS or Android when the user stops and restarts the video via native controls.

Version
v6 (Beta)
What platforms are you having the problem on?
No response
Architecture
Old architecture
What happened?
A bug happened!
Reproduction
repository link
Reproduction
Step to reproduce this bug are: just wire up these callbacks and see they don't ever get called.  I'd be happy to see an existence proof that they work.

added in the sample from this PR: https://github.com/react-native-video/react-native-video/pull/3651
seems to work on android and ios

PR merged, to be retested on V6.0.0-beta.9


[NEW ALGORITHM] Next Greater Node in Linked List

Issue will be closed if:

You mention more than one algorithm. You can create a separate issue for each algorithm once the current one is completed.
You propose an algorithm that is already present or has been mentioned in a previous issue.
You create a new issue without completing your previous issue.

Note: These actions will be taken seriously. Failure to follow the guidelines may result in the immediate closure of your issue.

Name:
[Next Greater Node in Linked List]
About:
We are given the head of a linked list with n nodes.
For each node in the list, find the value of the next greater node. That is, for each node, find the value of the first node that is next to it and has a strictly larger value than it.
Return an integer array answer where answer[i] is the value of the next greater node of the ith node (1-indexed). If the ith node does not have a next greater node, set answer[i] = 0.
Input: head = [2,1,5]
Output: [5,5,0]
Labels:
new algorithm, gssoc-ext, level1

Assignees:

[x] Contributor in GSSoC-ext
[x] Want to work on it

assigned


Introduce caching mechanism during compile semantics tree

toward https://github.com/flutter/flutter/issues/150234
There are two expansive part when updating a semantics subtree.

_getSemanticsForParent to get the _SemanticsFragment
_SemanticsFragment.compileChildren to get the actual semantics node.

This pr introduced caching for both steps.
First, this pr make a _RenderObjectSemantics wrapper to handle any semantics related compilation and move all the properties from RenderObject to this class. RenderObject is only responsible for provide semantics property through describeSemanticsConfiguration and assembleSemanticsNode.
_RenderObjectSemantics caches _SemanticsFragment, when someone tries to get the semantics fragment

If not cached, create a fragment and cache it
If cached, grab the cache and update the inherited Semantics Data (i.e blockUserActions or mergeIntoParent) before returning.

_SemanticsFragment caches semanticsNodes. When someone try to compile _SemanticsFragment

If not cached, create a fragment and cache it
If cached, grab the cache and update the geometry

before

after

getsemantics + compileChildren
530 + 470     ~= 900           before
34 + 187 ~= 200       after
about 78% reduce in compile time
Pre-launch Checklist

[ ] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[ ] I read the Tree Hygiene wiki page, which explains my responsibilities.
[ ] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[ ] I signed the CLA.
[ ] I listed at least one issue that this PR fixes in the description above.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] I added new tests to check the change I am making, or this PR is test-exempt.
[ ] I followed the breaking change policy and added Data Driven Fixes where supported.
[ ] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

latest
before
877us + 807us in 3118us frame
after
57us + 273us in 2200us frame

some thoughts after working on reducing semantics compiling time. This is one of the most exhausting pr I have worked on. There are so many corner cases that ain't previously present since we used to recompile entire subtree, and each of them is very hard to debug because the code is too convoluted.
There are somethings I noticed that are very hard to make changes to this part of the code.

parent inherited property like mergeintoparent and blocksUserActions and geometry is very hard to update when it changes. It not only has to update its own semantics fragment, it also has to update caches such as semanticsConfiguration and SemanticsNode it creates. It also needs to conditional update the entire subtree. It feels like I have to write one off logic for each properties.

fragment creates a mutable version of SemanticsConfiguration and uses it to generate semantics node. Previously, fragment is recreated every time and this is mostly fine. but now we caches fragment. This makes things hard when updating fragment, it needs to figure out when and whether to update its mutable SemanticsConfiguration, and sometimes i need to reset it in a tricky way so a parent fragment can still make sense of a child fragment's semantics configuration. Also sometimes it has to look up original semantics configuration instead of the mutable copy. This creates a bunch of corner cases that I have to write a one off logic for it.

for 1, The caches should probably have a more unify API for updating child fragments, and we can also think about changing how implicit merging work. This will be a big breaking change though.
For 2, I think in the future we should probably do something to keep a single source of true and avoid mutating SemanticsConfiguration. Though this ties to 1 where some modification to SemanticsConfiguration is due to implicit merge.
Fixing all these problem and adding caches seems too dramatic for a single change. so I decided to leave these problem for a later time.

is very hard to debug because the code is too convoluted.

I 100% agree with this. This is getting very complex and I am not confident that we are hitting all possible cases and update the caches correctly. There are too many paths through the code and each path is very, very complex. I wonder if we have to clean up this code first before we can confidently optimize this. Maybe we need to change the data model here a little more to make this more manageable and separate out the different aspects of the data. There is data that's only decided by a renderobject itself (its semantics configuration) and then there is data that's imposed on it by parent/children. If we separate those out into immutable objects, it may make it easier to manage the data: e.g. when a parent needs to update its semantics, it can 100% re-use the child's semantics configuration. We can also compare the data the parent wants to impose onto a child with the old data it imposed to quickly decide if we need to update that data.
Do you have a mental model of all the data pieces that go into the semantics tree and what their source is or how they are computed? e.g. geometry is imposed by a parent, but something like isButton is decided locally. Maybe it would be worthwhile to write this down in a document and segment it into the different update categories (i.e. does the data change when the renderobject itself changes, or is the data imposed by a parent, etc).

This pr is ready for review


Implement 'no-color' option

Work for this issue will begin begin on branch work-liquid-labs/cloudsite/132.


[SIG planning] Projects in flight: 2018Q2

Projects in flight: 2018 Q2
This issue is an aggregator for all SIG Docs projects currently in flight (2018 Q2).
Please add your projects to the list. Please add or correct details as appropriate.
Why this list matters
A list of in-flight projects will help SIG Docs prioritize yearly goals—OKRs and KPIs—at the SIG Docs Summit (Portland, OR, May 9, 2018).
In-flight project history

2018 Q1: #6935
2018 Q2: #7978

Projects
Writing, maintaining and improving content

Project
Contributor(s)
Description
Q2, Q3, Later, Ongoing

Increase developer happiness
All contributors
Explain complex information in helpful and effective ways to a variety of user journeys, empathetically and in anticipation of need
Ongoing

User journeys
@Bradamant3, @chenopis, @steveperry-53, @heckj, @alexcontini
Continue maintaining and optimizing existing user journeys
Q2

Create new content
All contributors
Document new features, create new conceptual content, create new user paths
Ongoing

Maintain existing content
All contributors
Reduce editorial debt, improve consistency of style
Ongoing

Mature the Kubernetes style guide
@zacharysarah, @steveperry-53
Deepen the Kubernetes style guide as needed to:- improve contributions- make contributor onboarding easier
Q2, Q3

Review Kubernetes blog posts
@zacharysarah
Review/approve blog posts for the K8s blog
Ongoing

Repo health
@zacharysarah, @chenopis
- Oversee general repo health- Maintain PR wrangler schedule
Ongoing

Better contribution guidelines
@mistyhacks, @heckj, @Rajakavitha1, @steveperry-53, @tallt0m
- Add guidelines for joining K8s org- Add guidelines for becoming a SIG Docs maintainer- Revise information architecture for contribution guidelines
Q2

K8s release

Project
Contributor(s)
Description
Q2, Q3, Later, Ongoing

Review release-related blog entries
@zacharysarah, Docs release meister
Review quarterly blog posts specific for each major release
Ongoing

Release notes
TBD, chosen per release- v1.11: @nickchase
- Organize submissions and edit content for release notes for major releases- Continue improving release note process- Include and automate application of a tag for user-facing release note content
Q2, Q3, Later

Docs release process
@Bradamant3
Revise and improve guidelines for docs quarterly release process
Q2

v1.11 docs
TBD
Quarterly release
Q2

v1.12 docs
TBD
Q3

v1.13 docs
TBD
Later

Doc tooling

Project
Contributor(s)
Description
Q2, Q3, Later, Ongoing

Branch strategy
@Bradamant3, @chenopis, @heckj, @mistyhacks, @steveperry-53, @zacharysarah
Investigate improvements to k/w's release and publishing branch strategies
Q2, Q3

Auto generated/imported docs
@heckj, @steveperry-53, @chenopis
- Q2: Investigate importing provider hosted content into Setup/other docs- Ongoing: Continue refining autogeneration scripts
Q2, Ongoing

i18n framework
@chenopis, @zacharysarah
- Implement an i18n workflow and language selector for languages in Hugo- Perform a one-time refresh of content on kubernetes.io/cn in time for KubeCon EU
Q2, Q3

Community section redesign
@parispittman
Provide a strategy for redesigning kubernetes.io/community
Q2

Metrics
@chenopis, @jaredbhatti, @zacharysarah
Establish site metrics for user happiness
Q2, Q3

Migrate to Hugo
@Bradamant3, @chenopis, @heckj, @jaredbhatti, @steveperry-53, @zacharysarah
Migrate k8s.io from Jekyll to Hugo
Q2

Community outreach

Project
Contributor(s)
Description
Q2, Q3, Later, Ongoing

Docs sprints
@zacharysarah, @jaredbhatti, @chenopis
- KubeCon EU (May 2-4, Copenhagen)- WriteTheDocs PDX (May 6-8, Portland, OR)- KubeCon China (November 14-15, Shanghai)
Q2, Q3, Later

Team building and SIG development

Project
Contributor(s)
Description
Q2, Q3, Later, Ongoing

Hire another LF technical writer
@zacharysarah, @caniszczyk
Find and onboard a full-time technical writer to focus specifically on content improvements for Kubernetes (85%) and other LF projects (%15)
Q2, Q3

K8s member hiring commitments
@zacharysarah, @jaredbhatti, @caniszczyk
Follow through with Kubernetes member commitments to hiring full-time documentation contributors
Ongoing

Docs training
@Bradamant3, @zacharysarah, @parispittman
Add relnotes, docs training to mentoring for new core reviewers, approvers
Q2

Onboard 1-3 more SIG docs maintainers
All SIG docs maintainers
Grow the number of SIG docs maintainers, reviewers, and approvers by 1-3
Q2

Some overlapping thoughts:

i18n

CN workflow
add KR

User Journeys, Phase II
Analytics refresh

update tracking code
add events

SEO improvements for findability
Fundamental Modeling Concepts

rigorous definitions of concepts and terms
layered diagrams to help build better mental models

Improve style guide

make it easier, more discoverable, useable
prezo @ doc sprints


add function to simplify post requests

Currently there is a method to write simple GET requests. This PR adds the ability for POST requests too.
Example usage:
Uri uri = parse("http://httpbin.org/post");
Request request = post(uri, { Parameter("param", "33333") });
Response response = request.execute();
print(response.contents);

Output:
{
  "args": {},
  "data": "",
  "files": {},
  "form": {
    "param": "33333"
  },
  "headers": {
    "Accept": "*/*",
    "Accept-Charset": "UTF-8",
    "Connection": "close",
    "Content-Length": "11",
    "Content-Type": "application/x-www-form-urlencoded; charset=UTF-8",
    "Host": "httpbin.org",
    "User-Agent": "curl/7.21.6 (x86_64-pc-linux-gnu) libcurl/7.21.6 OpenSSL/1.0.0e zlib/<IP_ADDRESS> libidn/1.22 librtmp/2.3"
  },
  "json": null,
  "origin": "xxx.xxx.xxx.xxx",
  "url": "http://httpbin.org/post"
}

Can one of the admins verify this patch? (see README)

This seems not to work correctly. Can anybody verify?

This works, sorry

Can one of the admins verify this patch? (see README)

ok to test

Thanks.


providers/sentry: add environment support

use channel configuration for sentry environment to re-use the same DSN for multiple clusters
created this as a separate PR to not clash with the other sentry PR

sorry for the flood of PRs, I have one other PR prepared after this one is merged

Can you please add a note in here to how Channel is used for sentry? Without docs no one would guess this.

Of course, you reckon I should just create a new category somewhere along line 217?


[Autocomplete] Controlled input doesn't change

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯

Autocomplete's value doesn't get changed
Expected Behavior 🤔

Autocomplete's value gets changed
Steps to Reproduce 🕹
https://codesandbox.io/s/material-demo-tz0pp

Steps:

Pass initial undefined value to  component
Pass some another value later (country in case of country-picker)
Autocomplete's value doesn't get changed, although parent passed the correct value

Context 🔦

We are trying to use the country  within the form, where its value is fetched asynchronously. On the first form render the value is undefined. On the 2nd+ the proper country is passed.
Your Environment 🌎

Tech
Version

Material-UI-core
v4.6.0

Material-UI-lab
v4.0.0-alpha-31

React
16.11.0

Browser
Version 70.0.3538.77 (Official Build) (64-bit)

TypeScript
-

etc.

@goodwin64 I think that we can move the discussion to #18173. thanks for the report.


React App Internationalization

Description
Adds i18n to React App.
Also simplifies importing of files (partly explains the amount of changed files).
Fixes Internationalization support
Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[ ] Unittest
[x] Cypress e2e -tests

Caveats?
Does this introduce new warnings or are linter rules suppressed? Why? Is only manual testing applicable for this feature? Is there something special that the reviewer should take into account?
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

Also one more thing I forgot to test. If user refreshes page, do we still persist the language? It could be nice to have in the sessionStorage maybe =p

Yes @rottabonus, the language persists when you refresh the page 👍


az cosmosdb create errors with DB names greater than 36 characters

Description
Outline the issue here:
STR:

create a cosmosdb instance with a DB name greater than 36 characters

EXPECTED:

The CLI says CosmosDB names can be between 3 and 50 characters, so I'd expect this to work

ACTUAL:

Errors with "DatabaseAccount name must be at least 3 characters and at most 50characters"

Environment summary
Install Method: How did you install the CLI? (e.g. pip, interactive script, apt-get, Docker, MSI, nightly)
Answer here: pip
CLI Version: What version of the CLI and modules are installed? (Use az --version)
Answer here:
azure-cli (2.0.14)

acr (2.0.10)
acs (2.0.13)
appservice (0.1.13)
batch (3.1.1)
billing (0.1.3)
cdn (0.0.6)
cloud (2.0.7)
cognitiveservices (0.1.6)
command-modules-nspkg (2.0.1)
component (2.0.7)
configure (2.0.10)
consumption (0.1.3)
container (0.1.8)
core (2.0.13)
cosmosdb (0.1.11)
dla (0.0.10)
dls (0.0.12)
eventgrid (0.1.2)
feedback (2.0.6)
find (0.2.6)
interactive (0.3.7)
iot (0.1.10)
keyvault (2.0.8)
lab (0.0.9)
monitor (0.0.8)
network (2.0.12)
nspkg (3.0.1)
profile (2.0.10)
rdbms (0.0.5)
redis (0.2.7)
resource (2.0.12)
role (2.0.10)
sf (1.0.6)
sql (2.0.9)
storage (2.0.12)
vm (2.0.12)

Python (Darwin) 2.7.13 (default, Aug 18 2017, 10:14:30)
[GCC 4.2.1 Compatible Apple LLVM 8.1.0 (clang-802.0.42)]

Python location '/Users/seknox/lib/azure-cli/bin/python'

OS Version: What OS and version are you using?
Answer here: MacOS Sierra
Shell Type: What shell are you using? (e.g. bash, cmd.exe, Bash on Windows)
Answer here: zsh

@seanknox are you trying to create an account or a database within an existing account?
Could u plz let me know which?

Here's the full command I ran:
az cosmosdb create -g sk5-hcp-underlay-southcentralus-cosmosdb -n sk5-hcp-underlay-southcentralus-cosmosdb --kind MongoDB --default-consistency-level Strong -o json

This is account management API which Digvijay owns it.
@tjprescott please assign this to Digvijay.

Spent a while bashing my head against this as well. You also need to consider multiple regions for geo-redundant deployments. Can get quite annoying when the initial deployment works and then Terraform gets a build error because the failover location does not work. Then Terraform falls out of sync with Azure.
In our case the region is '-australiaeast' and failover is '-australiasoutheast', so account names between 36 and 31 characters only partially succeed. Account names longer than 36 characters fail entirely.

Thank you all for the feedback. Account creation in the portal validates that the account name is less than 32 characters. We are now tracking a fix (Bug 445256) that will do this validation as well through our API, which the CLI uses. Our ETA for adding this validation is August.

Hi all, thank you for your patience. This change is something that we are making in our resource provider, so it does not follow the CLI release schedule. The change should be deployed in the next 2-3 weeks. I will update this issue when it is in production.
After the change, you will be able to create database accounts with names up to 44 characters long. The error message will better reflect the hard limits.

Hi everyone. The change has been deployed and you can now create accounts with global database account name length of 44 and region ids of up to 63 characters.


[add-to-app] SystemChrome.setDeviceOrientations + use of cached flutter engine shows black screen when starting Flutter activity

Steps to reproduce

Create an Android app
Integrate a Flutter module (https://docs.flutter.dev/add-to-app/android/project-setup?tab=without-android-studio)
Add a button to open a Flutter screen (https://docs.flutter.dev/add-to-app/android/add-flutter-screen?tab=prewarm-engine-kotlin-tab)
Follow step 3 to use a cached FlutterEngine (https://docs.flutter.dev/add-to-app/android/add-flutter-screen?tab=prewarm-engine-kotlin-tab#step-3-optional-use-a-cached-flutterengine)
On the Flutter module side, open the lib/main.dart file and try to set device orientation with SystemChrome API before runApp()

Future<void> main() async {
  WidgetsFlutterBinding.ensureInitialized();
  await SystemChrome.setPreferredOrientations([DeviceOrientation.portraitUp]);
  runApp(const MyApp());
}

Expected results
Flutter activity opens without issue
Actual results
Black screen, the future returned from setDeviceOrientations seems to never complete
Either remove the call to setDeviceOrientations or do not use the cached FlutterEngine remove the issue
Code sample
I have an entire repository example here : https://github.com/woprandi/MyApplication
Code sample (Flutter module main.dart)
import 'package:flutter/material.dart';
import 'package:flutter/services.dart';

Future<void> main() async {
  WidgetsFlutterBinding.ensureInitialized();
  await SystemChrome.setPreferredOrientations([DeviceOrientation.portraitUp]);
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  // This widget is the root of your application.
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        // This is the theme of your application.
        //
        // Try running your application with "flutter run". You'll see the
        // application has a blue toolbar. Then, without quitting the app, try
        // changing the primarySwatch below to Colors.green and then invoke
        // "hot reload" (press "r" in the console where you ran "flutter run",
        // or press Run > Flutter Hot Reload in a Flutter IDE). Notice that the
        // counter didn't reset back to zero; the application is not restarted.
        primarySwatch: Colors.blue,
      ),
      home: const MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  const MyHomePage({super.key, required this.title});

  // This widget is the home page of your application. It is stateful, meaning
  // that it has a State object (defined below) that contains fields that affect
  // how it looks.

  // This class is the configuration for the state. It holds the values (in this
  // case the title) provided by the parent (in this case the App widget) and
  // used by the build method of the State. Fields in a Widget subclass are
  // always marked "final".

  final String title;

  @override
  State<MyHomePage> createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  int _counter = 0;

  void _incrementCounter() {
    setState(() {
      // This call to setState tells the Flutter framework that something has
      // changed in this State, which causes it to rerun the build method below
      // so that the display can reflect the updated values. If we changed
      // _counter without calling setState(), then the build method would not be
      // called again, and so nothing would appear to happen.
      _counter++;
    });
  }

  @override
  Widget build(BuildContext context) {
    // This method is rerun every time setState is called, for instance as done
    // by the _incrementCounter method above.
    //
    // The Flutter framework has been optimized to make rerunning build methods
    // fast, so that you can just rebuild anything that needs updating rather
    // than having to individually change instances of widgets.
    return Scaffold(
      appBar: AppBar(
        // Here we take the value from the MyHomePage object that was created by
        // the App.build method, and use it to set our appbar title.
        title: Text(widget.title),
      ),
      body: Center(
        // Center is a layout widget. It takes a single child and positions it
        // in the middle of the parent.
        child: Column(
          // Column is also a layout widget. It takes a list of children and
          // arranges them vertically. By default, it sizes itself to fit its
          // children horizontally, and tries to be as tall as its parent.
          //
          // Invoke "debug painting" (press "p" in the console, choose the
          // "Toggle Debug Paint" action from the Flutter Inspector in Android
          // Studio, or the "Toggle Debug Paint" command in Visual Studio Code)
          // to see the wireframe for each widget.
          //
          // Column has various properties to control how it sizes itself and
          // how it positions its children. Here we use mainAxisAlignment to
          // center the children vertically; the main axis here is the vertical
          // axis because Columns are vertical (the cross axis would be
          // horizontal).
          mainAxisAlignment: MainAxisAlignment.center,
          children: <Widget>[
            const Text(
              'You have pushed the button this many times:',
            ),
            Text(
              '$_counter',
              style: Theme.of(context).textTheme.headlineMedium,
            ),
          ],
        ),
      ),
      floatingActionButton: FloatingActionButton(
        onPressed: _incrementCounter,
        tooltip: 'Increment',
        child: const Icon(Icons.add),
      ), // This trailing comma makes auto-formatting nicer for build methods.
    );
  }
}

Code sample (MainActivity.kt)
package com.example.myapplication

import android.os.Bundle
import androidx.activity.ComponentActivity
import androidx.activity.compose.setContent
import androidx.compose.foundation.layout.fillMaxSize
import androidx.compose.material3.Button
import androidx.compose.material3.MaterialTheme
import androidx.compose.material3.Surface
import androidx.compose.material3.Text
import androidx.compose.runtime.Composable
import androidx.compose.ui.Modifier
import androidx.compose.ui.tooling.preview.Preview
import com.example.myapplication.ui.theme.MyApplicationTheme
import io.flutter.embedding.android.FlutterActivity

class MainActivity : ComponentActivity() {
    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)
        setContent {
            MyApplicationTheme {
                // A surface container using the 'background' color from the theme
                Surface(
                    modifier = Modifier.fillMaxSize(),
                    color = MaterialTheme.colorScheme.background
                ) {
                    Button(onClick = {
                        //startActivity(FlutterActivity.createDefaultIntent(this))
                        startActivity(
                            FlutterActivity
                                .withCachedEngine("my_engine_id")
                                .build(this)
                        )
                    }) {
                      Text("Open Flutter module")
                    }
                }
            }
        }
    }
}

package com.example.myapplication

import android.app.Application
import io.flutter.embedding.engine.FlutterEngine
import io.flutter.embedding.engine.FlutterEngineCache
import io.flutter.embedding.engine.dart.DartExecutor

class App : Application() {
    lateinit var flutterEngine : FlutterEngine

    override fun onCreate() {
        super.onCreate()

        // Instantiate a FlutterEngine.
        flutterEngine = FlutterEngine(this)

        // Start executing Dart code to pre-warm the FlutterEngine.
        flutterEngine.dartExecutor.executeDartEntrypoint(
            DartExecutor.DartEntrypoint.createDefault()
        )

        // Cache the FlutterEngine to be used by FlutterActivity.
        FlutterEngineCache
            .getInstance()
            .put("my_engine_id", flutterEngine)
    }
}

Screenshots or Video

Screenshots / Video demonstration
untitled.webm

Logs
Logs
2024-01-25 16:26:49.754 16767-16767 nativeloader            com.example.myapplication            D  Configuring clns-6 for other apk /data/app/~~H7Feiqs7V1W4pLThKFI-YQ==/com.example.myapplication-XcJLIQOcl4SmDgR8THMtUA==/base.apk. target_sdk_version=34, uses_libraries=, library_path=/data/app/~~H7Feiqs7V1W4pLThKFI-YQ==/com.example.myapplication-XcJLIQOcl4SmDgR8THMtUA==/lib/x86_64:/data/app/~~H7Feiqs7V1W4pLThKFI-YQ==/com.example.myapplication-XcJLIQOcl4SmDgR8THMtUA==/base.apk!/lib/x86_64, permitted_path=/data:/mnt/expand:/data/user/0/com.example.myapplication
2024-01-25 16:26:49.770 16767-16767 GraphicsEnvironment     com.example.myapplication            V  Currently set values for:
2024-01-25 16:26:49.770 16767-16767 GraphicsEnvironment     com.example.myapplication            V    angle_gl_driver_selection_pkgs=[]
2024-01-25 16:26:49.770 16767-16767 GraphicsEnvironment     com.example.myapplication            V    angle_gl_driver_selection_values=[]
2024-01-25 16:26:49.772 16767-16767 GraphicsEnvironment     com.example.myapplication            V  ANGLE GameManagerService for com.example.myapplication: false
2024-01-25 16:26:49.772 16767-16767 GraphicsEnvironment     com.example.myapplication            V  com.example.myapplication is not listed in per-application setting
2024-01-25 16:26:49.772 16767-16767 GraphicsEnvironment     com.example.myapplication            V  Neither updatable production driver nor prerelease driver is supported.
2024-01-25 16:26:49.923 16767-16825 ResourceExtractor       com.example.myapplication            I  Found extracted resources res_timestamp-1-1706196335560
2024-01-25 16:26:49.923 16767-16825 ResourceExtractor       com.example.myapplication            I  Resource version mismatch res_timestamp-1-1706196408109
2024-01-25 16:26:50.580 16767-16825 ResourceExtractor       com.example.myapplication            I  Extracted baseline resource assets/flutter_assets/kernel_blob.bin
2024-01-25 16:26:50.582 16767-16825 ResourceExtractor       com.example.myapplication            I  Extracted baseline resource assets/flutter_assets/vm_snapshot_data
2024-01-25 16:26:50.725 16767-16825 ResourceExtractor       com.example.myapplication            I  Extracted baseline resource assets/flutter_assets/isolate_snapshot_data
2024-01-25 16:26:50.734 16767-16767 e.myapplication         com.example.myapplication            W  type=1400 audit(0.0:1928): avc:  denied  { read } for  name="max_map_count" dev="proc" ino=126972 scontext=u:r:untrusted_app:s0:c193,c256,c512,c768 tcontext=u:object_r:proc_max_map_count:s0 tclass=file permissive=0 app=com.example.myapplication
2024-01-25 16:26:50.753 16767-16767 libEGL                  com.example.myapplication            D  loaded /vendor/lib64/egl/libEGL_emulation.so
2024-01-25 16:26:50.758 16767-16767 libEGL                  com.example.myapplication            D  loaded /vendor/lib64/egl/libGLESv1_CM_emulation.so
2024-01-25 16:26:50.765 16767-16767 libEGL                  com.example.myapplication            D  loaded /vendor/lib64/egl/libGLESv2_emulation.so
2024-01-25 16:26:51.057 16767-16837 flutter                 com.example.myapplication            I  The Dart VM service is listening on http://<IP_ADDRESS>:39909/gL_eo2m52IU=/
2024-01-25 16:26:51.147 16767-16767 Compatibil...geReporter com.example.myapplication            D  Compat change id reported: 237531167; UID 10193; state: DISABLED
2024-01-25 16:26:51.150 16767-16767 OpenGLRenderer          com.example.myapplication            W  Unknown dataspace 0
2024-01-25 16:26:51.165 16767-16767 Choreographer           com.example.myapplication            I  Skipped 82 frames!  The application may be doing too much work on its main thread.
2024-01-25 16:26:51.386 16767-16767 e.myapplication         com.example.myapplication            W  Method java.lang.Object androidx.compose.runtime.snapshots.SnapshotStateMap.mutate(kotlin.jvm.functions.Function1) failed lock verification and will run slower.
                                                                                Common causes for lock verification issues are non-optimized dex code
                                                                                and incorrect proguard optimizations.
2024-01-25 16:26:51.387 16767-16767 e.myapplication         com.example.myapplication            W  Method void androidx.compose.runtime.snapshots.SnapshotStateMap.update(kotlin.jvm.functions.Function1) failed lock verification and will run slower.
2024-01-25 16:26:51.388 16767-16767 e.myapplication         com.example.myapplication            W  Method boolean androidx.compose.runtime.snapshots.SnapshotStateMap.removeIf$runtime_release(kotlin.jvm.functions.Function1) failed lock verification and will run slower.
2024-01-25 16:26:51.521 16767-16767 e.myapplication         com.example.myapplication            W  Method boolean androidx.compose.runtime.snapshots.SnapshotStateList.conditionalUpdate(kotlin.jvm.functions.Function1) failed lock verification and will run slower.
2024-01-25 16:26:51.522 16767-16767 e.myapplication         com.example.myapplication            W  Method java.lang.Object androidx.compose.runtime.snapshots.SnapshotStateList.mutate(kotlin.jvm.functions.Function1) failed lock verification and will run slower.
2024-01-25 16:26:51.523 16767-16767 e.myapplication         com.example.myapplication            W  Method void androidx.compose.runtime.snapshots.SnapshotStateList.update(kotlin.jvm.functions.Function1) failed lock verification and will run slower.
2024-01-25 16:26:51.637 16767-16838 OpenGLRenderer          com.example.myapplication            W  Failed to choose config with EGL_SWAP_BEHAVIOR_PRESERVED, retrying without...
2024-01-25 16:26:51.638 16767-16838 OpenGLRenderer          com.example.myapplication            W  Failed to initialize 101010-2 format, error = EGL_SUCCESS
2024-01-25 16:26:51.654 16767-16838 Gralloc4                com.example.myapplication            I  mapper 4.x is not supported
2024-01-25 16:26:51.815 16767-16838 OpenGLRenderer          com.example.myapplication            E  Unable to match the desired swap behavior.
2024-01-25 16:26:51.882 16767-16780 OpenGLRenderer          com.example.myapplication            I  Davey! duration=2078ms; Flags=1, FrameTimelineVsyncId=972730, IntendedVsync=47232369184667, Vsync=47233735851279, InputEventId=0, HandleInputStart=47233742473526, AnimationStart=47233742480381, PerformTraversalsStart=47233742674979, DrawStart=47234394056571, FrameDeadline=47232385851333, FrameInterval=47233741309039, FrameStartTime=16666666, SyncQueued=47234406392966, SyncStart=47234411526866, IssueDrawCommandsStart=47234414025803, SwapBuffers=47234442699573, FrameCompleted=47234452702949, DequeueBufferDuration=8836, QueueBufferDuration=573432, GpuCompleted=47234452702949, SwapBuffersCompleted=47234450214045, DisplayPresentTime=0, CommandSubmissionCompleted=47234442699573,
2024-01-25 16:26:52.008 16767-16767 Choreographer           com.example.myapplication            I  Skipped 44 frames!  The application may be doing too much work on its main thread.
2024-01-25 16:26:56.416 16767-16848 ProfileInstaller        com.example.myapplication            D  Installing profile for com.example.myapplication
2024-01-25 16:26:58.088 16767-16838 EGL_emulation           com.example.myapplication            D  app_time_stats: avg=2071.22ms min=31.24ms max=5185.25ms count=3
2024-01-25 16:26:58.184 16767-16767 AutofillManager         com.example.myapplication            D  Fill dialog is enabled:false, hints=[password, passwordAuto, creditCardNumber, creditCardSecurityCode, creditCardExpirationDate]
2024-01-25 16:26:58.206 16767-16767 e.myapplication         com.example.myapplication            W  Accessing hidden method Landroid/view/accessibility/AccessibilityNodeInfo;->getSourceNodeId()J (unsupported,test-api, reflection, allowed)
2024-01-25 16:26:58.206 16767-16767 e.myapplication         com.example.myapplication            W  Accessing hidden method Landroid/view/accessibility/AccessibilityRecord;->getSourceNodeId()J (unsupported, reflection, allowed)
2024-01-25 16:26:58.206 16767-16767 e.myapplication         com.example.myapplication            W  Accessing hidden field Landroid/view/accessibility/AccessibilityNodeInfo;->mChildNodeIds:Landroid/util/LongArray; (unsupported, reflection, allowed)
2024-01-25 16:26:58.207 16767-16767 e.myapplication         com.example.myapplication            W  Accessing hidden method Landroid/util/LongArray;->get(I)J (unsupported, reflection, allowed)
2024-01-25 16:26:58.369 16767-16838 OpenGLRenderer          com.example.myapplication            E  Unable to match the desired swap behavior.

Flutter Doctor output
Doctor output
[✓] Flutter (Channel stable, 3.16.8, on Fedora Linux 39 (Workstation Edition) 6.6.12-200.fc39.x86_64, locale fr_FR.UTF-8)
    • Flutter version 3.16.8 on channel stable at /home/william/Documents/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 67457e669f (il y a 9 jours), 2024-01-16 16:22:29 -0800
    • Engine revision 6e2ea58a5c
    • Dart version 3.2.5
    • DevTools version 2.28.5

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /home/william/Android/Sdk
    • Platform android-34, build-tools 34.0.0
    • Java binary at: /home/william/.local/share/JetBrains/Toolbox/apps/android-studio/jbr/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.7+0-17.0.7b1000.6-10550314)
    • All Android licenses accepted.

[✓] Chrome - develop for the web
    • Chrome at google-chrome

[✓] Linux toolchain - develop for Linux desktop
    • clang version 17.0.6 (Fedora 17.0.6-1.fc39)
    • cmake version 3.27.7
    • ninja version 1.11.1
    • pkg-config version 1.9.5

[✓] Android Studio (version 2023.1)
    • Android Studio at /home/william/.local/share/JetBrains/Toolbox/apps/android-studio
    • Flutter plugin version 77.1.2
    • Dart plugin version 222.4582
    • Java version OpenJDK Runtime Environment (build 17.0.7+0-17.0.7b1000.6-10550314)

[✓] IntelliJ IDEA Community Edition (version 2023.3)
    • IntelliJ at /home/william/.local/share/JetBrains/Toolbox/apps/intellij-idea-community-edition
    • 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

[✓] VS Code (version 1.85.2)
    • VS Code at /usr/share/code
    • Flutter extension version 3.80.0

[✓] Connected device (3 available)
    • sdk gphone64 x86 64 (mobile) • emulator-5554 • android-x64    • Android 14 (API 34) (emulator)
    • Linux (desktop)              • linux         • linux-x64      • Fedora Linux 39 (Workstation Edition) 6.6.12-200.fc39.x86_64
    • Chrome (web)                 • chrome        • web-javascript • Google Chrome 120.0.6099.224

[✓] Network resources
    • All expected network resources are available.

• No issues found!

Thanks for the report. I can reproduce this issue with your sample project.
I also checked this on my old project (non-Compose) at issue_142227_blackscreen, the issue is not reproduced.
Labeling this for more insights. May be related: https://github.com/flutter/flutter/issues/113595

flutter doctor -v (stable and master)
[✓] Flutter (Channel stable, 3.16.8, on macOS 14.1 23B74 darwin-x64, locale en-VN)
    • Flutter version 3.16.8 on channel stable at /Users/huynq/Documents/GitHub/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 67457e669f (27 hours ago), 2024-01-16 16:22:29 -0800
    • Engine revision 6e2ea58a5c
    • Dart version 3.2.5
    • DevTools version 2.28.5

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/huynq/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • ANDROID_HOME = /Users/huynq/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.0.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15A507
    • CocoaPods version 1.14.3

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

[✓] Android Studio (version 2023.1)
    • Android Studio at /Applications/Android Studio Hedgehog.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.7+0-17.0.7b1000.6-10550314)

[✓] Android Studio (version 2022.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • android-studio-dir = /Applications/Android Studio.app/
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)

[✓] VS Code (version 1.85.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.80.0

[✓] Connected device (3 available)
    • iPhone (mobile) • d9a94afe2b649fef56ba0bfeb052f0f2a7dae95e • ios            • iOS 15.8 19H370
    • macOS (desktop) • macos                                    • darwin-x64     • macOS 14.1 23B74 darwin-x64
    • Chrome (web)    • chrome                                   • web-javascript • Google Chrome 120.0.6099.234

[✓] Network resources
    • All expected network resources are available.

• No issues found!

[!] Flutter (Channel master, 3.19.0-9.0.pre.139, on macOS 14.1 23B74 darwin-x64, locale en-VN)
    • Flutter version 3.19.0-9.0.pre.139 on channel master at /Users/huynq/Documents/GitHub/flutter_master
    ! Warning: `flutter` on your path resolves to /Users/huynq/Documents/GitHub/flutter/bin/flutter, which is not inside your current Flutter SDK checkout at /Users/huynq/Documents/GitHub/flutter_master. Consider adding /Users/huynq/Documents/GitHub/flutter_master/bin to the front of your path.
    ! Warning: `dart` on your path resolves to /Users/huynq/Documents/GitHub/flutter/bin/dart, which is not inside your current Flutter SDK checkout at /Users/huynq/Documents/GitHub/flutter_master. Consider adding /Users/huynq/Documents/GitHub/flutter_master/bin to the front of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 703e12f524 (83 minutes ago), 2024-01-24 17:49:08 -0800
    • Engine revision 4880592ca5
    • Dart version 3.4.0 (build 3.4.0-69.0.dev)
    • DevTools version 2.31.0
    • If those were intentional, you can disregard the above warnings; however it is recommended to use "git" directly to perform update checks and upgrades.

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /Users/huynq/Library/Android/sdk
    • Platform android-34, build-tools 34.0.0
    • ANDROID_HOME = /Users/huynq/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 15.0.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 15A507
    • CocoaPods version 1.14.3

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

[✓] Android Studio (version 2023.1)
    • Android Studio at /Applications/Android Studio Hedgehog.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.7+0-17.0.7b1000.6-10550314)

[✓] Android Studio (version 2022.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • android-studio-dir = /Applications/Android Studio.app/
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b802.4-9586694)

[✓] VS Code (version 1.85.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.80.0

[✓] Connected device (4 available)
    • RMX2001 (mobile) • EUYTFEUSQSRGDA6D                         • android-arm64  • Android 11 (API 30)
    • iPhone (mobile)  • d9a94afe2b649fef56ba0bfeb052f0f2a7dae95e • ios            • iOS 15.8 19H370
    • macOS (desktop)  • macos                                    • darwin-x64     • macOS 14.1 23B74 darwin-x64
    • Chrome (web)     • chrome                                   • web-javascript • Google Chrome 120.0.6099.234

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.

@huycozy I initially noticed this bug on a old, non-compose (traditionnal XML layout) Android app so I think it should be reproductible too.

Could you please try forking my demo issue_142227_blackscreen and producing the error?

I'm unable to build it :

Could not find com.example.my_flutter:flutter_debug:1.0.

Executing tasks: [:app:assembleDebug, :app:assembleDebugUnitTest, :app:assembleDebugAndroidTest] in project /home/william/Documents/Repos/Flutter-add-to-app-Android-native-sample

> Configure project :flutter
Build was configured to prefer settings repositories over project repositories but repository 'maven' was added by plugin class 'FlutterPlugin'
Build was configured to prefer settings repositories over project repositories but repository 'maven' was added by script '/home/william/Documents/flutter/packages/flutter_tools/gradle/module_plugin_loader.gradle'
AGPBI: {"kind":"warning","text":"We recommend using a newer Android Gradle plugin to use compileSdk = 34\n\nThis Android Gradle plugin (8.0.0) was tested up to compileSdk = 33.\n\nYou are strongly encouraged to update your project to use a newer\nAndroid Gradle plugin that has been tested with compileSdk = 34.\n\nIf you are already using the latest version of the Android Gradle plugin,\nyou may need to wait until a newer version with support for compileSdk = 34 is available.\n\nTo suppress this warning, add/update\n    android.suppressUnsupportedCompileSdk=34\nto this project's gradle.properties.","sources":[{}]}

> Task :app:createDebugVariantModel UP-TO-DATE
> Task :app:preBuild UP-TO-DATE
> Task :app:preDebugBuild UP-TO-DATE
> Task :app:mergeDebugNativeDebugMetadata NO-SOURCE
> Task :flutter:compileFlutterBuildDebug
> Task :flutter:packLibsflutterBuildDebug UP-TO-DATE
> Task :app:dataBindingMergeDependencyArtifactsDebug FAILED
> Task :app:generateDebugResValues UP-TO-DATE
> Task :app:generateDebugResources UP-TO-DATE
> Task :flutter:preBuild UP-TO-DATE
> Task :flutter:preDebugBuild UP-TO-DATE
> Task :flutter:generateDebugResValues UP-TO-DATE
> Task :flutter:generateDebugResources UP-TO-DATE
> Task :flutter:packageDebugResources UP-TO-DATE
> Task :app:mergeDebugResources FAILED
> Task :app:packageDebugResources UP-TO-DATE
> Task :app:parseDebugLocalResources UP-TO-DATE
> Task :flutter:parseDebugLocalResources UP-TO-DATE
> Task :flutter:processDebugManifest UP-TO-DATE
> Task :flutter:generateDebugRFile UP-TO-DATE
> Task :app:generateDebugBuildConfig UP-TO-DATE
> Task :flutter:writeDebugAarMetadata UP-TO-DATE
> Task :app:checkDebugAarMetadata FAILED
> Task :app:mapDebugSourceSetPaths FAILED
> Task :app:createDebugCompatibleScreenManifests UP-TO-DATE
> Task :app:extractDeepLinksDebug UP-TO-DATE
> Task :flutter:extractDeepLinksDebug UP-TO-DATE
> Task :app:processDebugMainManifest FAILED
> Task :flutter:compileDebugLibraryResources UP-TO-DATE
> Task :flutter:generateDebugBuildConfig UP-TO-DATE
> Task :flutter:javaPreCompileDebug UP-TO-DATE
> Task :flutter:compileDebugJavaWithJavac UP-TO-DATE
> Task :flutter:bundleLibCompileToJarDebug UP-TO-DATE
> Task :app:javaPreCompileDebug UP-TO-DATE
> Task :app:mergeDebugShaders UP-TO-DATE
> Task :app:compileDebugShaders NO-SOURCE
> Task :app:generateDebugAssets UP-TO-DATE
> Task :flutter:cleanPackageDebugAssets
> Task :flutter:mergeDebugShaders UP-TO-DATE
> Task :flutter:compileDebugShaders NO-SOURCE
> Task :flutter:generateDebugAssets UP-TO-DATE
> Task :flutter:packageDebugAssets
> Task :flutter:copyFlutterAssetsDebug
> Task :app:mergeDebugAssets FAILED
> Task :app:processDebugJavaRes NO-SOURCE
> Task :flutter:processDebugJavaRes NO-SOURCE
> Task :flutter:bundleLibResDebug NO-SOURCE
> Task :app:checkDebugDuplicateClasses FAILED
> Task :app:desugarDebugFileDependencies FAILED
> Task :flutter:bundleLibRuntimeToJarDebug UP-TO-DATE
> Task :app:mergeDebugJniLibFolders UP-TO-DATE
> Task :flutter:mergeDebugJniLibFolders UP-TO-DATE
> Task :flutter:mergeDebugNativeLibs NO-SOURCE
> Task :flutter:copyDebugJniLibsProjectOnly UP-TO-DATE
> Task :app:mergeDebugNativeLibs FAILED
> Task :app:validateSigningDebug UP-TO-DATE
> Task :app:writeDebugAppMetadata UP-TO-DATE
> Task :app:writeDebugSigningConfigVersions
> Task :app:assembleDebugUnitTest UP-TO-DATE
> Task :app:preDebugAndroidTestBuild SKIPPED
> Task :app:dataBindingMergeDependencyArtifactsDebugAndroidTest FAILED
> Task :app:generateDebugAndroidTestResValues
> Task :app:generateDebugAndroidTestResources
> Task :app:mergeDebugAndroidTestResources
> Task :app:processDebugAndroidTestManifest FAILED
> Task :app:checkDebugAndroidTestAarMetadata FAILED
> Task :app:mapDebugAndroidTestSourceSetPaths
> Task :app:javaPreCompileDebugAndroidTest
> Task :app:mergeDebugAndroidTestShaders
> Task :app:compileDebugAndroidTestShaders NO-SOURCE
> Task :app:generateDebugAndroidTestAssets UP-TO-DATE
> Task :app:mergeDebugAndroidTestAssets FAILED
> Task :app:processDebugAndroidTestJavaRes NO-SOURCE
> Task :app:mergeDebugAndroidTestJniLibFolders
> Task :app:mergeDebugAndroidTestNativeLibs NO-SOURCE
> Task :app:checkDebugAndroidTestDuplicateClasses FAILED
> Task :app:desugarDebugAndroidTestFileDependencies FAILED
> Task :app:validateSigningDebugAndroidTest
> Task :app:writeDebugAndroidTestSigningConfigVersions

FAILURE: Build completed with 15 failures.

1: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':app:dataBindingMergeDependencyArtifactsDebug'.
> Could not resolve all dependencies for configuration ':app:debugCompileClasspath'.
  The project declares repositories, effectively ignoring the repositories you have declared in the settings.
  You can figure out how project repositories are declared by configuring your build to fail on project repositories.
  See https://docs.gradle.org/8.0/userguide/declaring_repositories.html#sub:fail_build_on_project_repositories for details.
   > Could not find com.example.my_flutter:flutter_debug:1.0.
     Required by:
         project :app

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

2: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':app:mergeDebugResources'.
> Could not resolve all dependencies for configuration ':app:debugRuntimeClasspath'.
  The project declares repositories, effectively ignoring the repositories you have declared in the settings.
  You can figure out how project repositories are declared by configuring your build to fail on project repositories.
  See https://docs.gradle.org/8.0/userguide/declaring_repositories.html#sub:fail_build_on_project_repositories for details.
   > Could not find com.example.my_flutter:flutter_debug:1.0.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/com/example/my_flutter/flutter_debug/1.0/flutter_debug-1.0.pom
       - https://repo.maven.apache.org/maven2/com/example/my_flutter/flutter_debug/1.0/flutter_debug-1.0.pom
       - file:/Users/huynq/Documents/NEVERCODE.IO/RepoduceProjects/Flutter-add-to-app-Android-native-sample/my_flutter/build/host/outputs/repo/com/example/my_flutter/flutter_debug/1.0/flutter_debug-1.0.pom
       - https://storage.googleapis.com/download.flutter.io/com/example/my_flutter/flutter_debug/1.0/flutter_debug-1.0.pom
     Required by:
         project :app

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

3: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':app:checkDebugAarMetadata'.
> Could not resolve all dependencies for configuration ':app:debugRuntimeClasspath'.
  The project declares repositories, effectively ignoring the repositories you have declared in the settings.
  You can figure out how project repositories are declared by configuring your build to fail on project repositories.
  See https://docs.gradle.org/8.0/userguide/declaring_repositories.html#sub:fail_build_on_project_repositories for details.
   > Could not find com.example.my_flutter:flutter_debug:1.0.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/com/example/my_flutter/flutter_debug/1.0/flutter_debug-1.0.pom
       - https://repo.maven.apache.org/maven2/com/example/my_flutter/flutter_debug/1.0/flutter_debug-1.0.pom
       - file:/Users/huynq/Documents/NEVERCODE.IO/RepoduceProjects/Flutter-add-to-app-Android-native-sample/my_flutter/build/host/outputs/repo/com/example/my_flutter/flutter_debug/1.0/flutter_debug-1.0.pom
       - https://storage.googleapis.com/download.flutter.io/com/example/my_flutter/flutter_debug/1.0/flutter_debug-1.0.pom
     Required by:
         project :app

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

4: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':app:mapDebugSourceSetPaths'.
> Could not resolve all dependencies for configuration ':app:debugRuntimeClasspath'.
  The project declares repositories, effectively ignoring the repositories you have declared in the settings.
  You can figure out how project repositories are declared by configuring your build to fail on project repositories.
  See https://docs.gradle.org/8.0/userguide/declaring_repositories.html#sub:fail_build_on_project_repositories for details.
   > Could not find com.example.my_flutter:flutter_debug:1.0.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/com/example/my_flutter/flutter_debug/1.0/flutter_debug-1.0.pom
       - https://repo.maven.apache.org/maven2/com/example/my_flutter/flutter_debug/1.0/flutter_debug-1.0.pom
       - file:/Users/huynq/Documents/NEVERCODE.IO/RepoduceProjects/Flutter-add-to-app-Android-native-sample/my_flutter/build/host/outputs/repo/com/example/my_flutter/flutter_debug/1.0/flutter_debug-1.0.pom
       - https://storage.googleapis.com/download.flutter.io/com/example/my_flutter/flutter_debug/1.0/flutter_debug-1.0.pom
     Required by:
         project :app

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

5: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':app:processDebugMainManifest'.
> Could not resolve all dependencies for configuration ':app:debugRuntimeClasspath'.
  The project declares repositories, effectively ignoring the repositories you have declared in the settings.
  You can figure out how project repositories are declared by configuring your build to fail on project repositories.
  See https://docs.gradle.org/8.0/userguide/declaring_repositories.html#sub:fail_build_on_project_repositories for details.
   > Could not find com.example.my_flutter:flutter_debug:1.0.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/com/example/my_flutter/flutter_debug/1.0/flutter_debug-1.0.pom
       - https://repo.maven.apache.org/maven2/com/example/my_flutter/flutter_debug/1.0/flutter_debug-1.0.pom
       - file:/Users/huynq/Documents/NEVERCODE.IO/RepoduceProjects/Flutter-add-to-app-Android-native-sample/my_flutter/build/host/outputs/repo/com/example/my_flutter/flutter_debug/1.0/flutter_debug-1.0.pom
       - https://storage.googleapis.com/download.flutter.io/com/example/my_flutter/flutter_debug/1.0/flutter_debug-1.0.pom
     Required by:
         project :app

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

6: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':app:mergeDebugAssets'.
> Could not resolve all dependencies for configuration ':app:debugRuntimeClasspath'.
  The project declares repositories, effectively ignoring the repositories you have declared in the settings.
  You can figure out how project repositories are declared by configuring your build to fail on project repositories.
  See https://docs.gradle.org/8.0/userguide/declaring_repositories.html#sub:fail_build_on_project_repositories for details.
   > Could not find com.example.my_flutter:flutter_debug:1.0.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/com/example/my_flutter/flutter_debug/1.0/flutter_debug-1.0.pom
       - https://repo.maven.apache.org/maven2/com/example/my_flutter/flutter_debug/1.0/flutter_debug-1.0.pom
       - file:/Users/huynq/Documents/NEVERCODE.IO/RepoduceProjects/Flutter-add-to-app-Android-native-sample/my_flutter/build/host/outputs/repo/com/example/my_flutter/flutter_debug/1.0/flutter_debug-1.0.pom
       - https://storage.googleapis.com/download.flutter.io/com/example/my_flutter/flutter_debug/1.0/flutter_debug-1.0.pom
     Required by:
         project :app

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

7: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':app:checkDebugDuplicateClasses'.
> Could not resolve all dependencies for configuration ':app:debugRuntimeClasspath'.
  The project declares repositories, effectively ignoring the repositories you have declared in the settings.
  You can figure out how project repositories are declared by configuring your build to fail on project repositories.
  See https://docs.gradle.org/8.0/userguide/declaring_repositories.html#sub:fail_build_on_project_repositories for details.
   > Could not find com.example.my_flutter:flutter_debug:1.0.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/com/example/my_flutter/flutter_debug/1.0/flutter_debug-1.0.pom
       - https://repo.maven.apache.org/maven2/com/example/my_flutter/flutter_debug/1.0/flutter_debug-1.0.pom
       - file:/Users/huynq/Documents/NEVERCODE.IO/RepoduceProjects/Flutter-add-to-app-Android-native-sample/my_flutter/build/host/outputs/repo/com/example/my_flutter/flutter_debug/1.0/flutter_debug-1.0.pom
       - https://storage.googleapis.com/download.flutter.io/com/example/my_flutter/flutter_debug/1.0/flutter_debug-1.0.pom
     Required by:
         project :app

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

8: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':app:desugarDebugFileDependencies'.
> Could not resolve all dependencies for configuration ':app:debugRuntimeClasspath'.
  The project declares repositories, effectively ignoring the repositories you have declared in the settings.
  You can figure out how project repositories are declared by configuring your build to fail on project repositories.
  See https://docs.gradle.org/8.0/userguide/declaring_repositories.html#sub:fail_build_on_project_repositories for details.
   > Could not find com.example.my_flutter:flutter_debug:1.0.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/com/example/my_flutter/flutter_debug/1.0/flutter_debug-1.0.pom
       - https://repo.maven.apache.org/maven2/com/example/my_flutter/flutter_debug/1.0/flutter_debug-1.0.pom
       - file:/Users/huynq/Documents/NEVERCODE.IO/RepoduceProjects/Flutter-add-to-app-Android-native-sample/my_flutter/build/host/outputs/repo/com/example/my_flutter/flutter_debug/1.0/flutter_debug-1.0.pom
       - https://storage.googleapis.com/download.flutter.io/com/example/my_flutter/flutter_debug/1.0/flutter_debug-1.0.pom
     Required by:
         project :app

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

9: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':app:mergeDebugNativeLibs'.
> Could not resolve all dependencies for configuration ':app:debugRuntimeClasspath'.
  The project declares repositories, effectively ignoring the repositories you have declared in the settings.
  You can figure out how project repositories are declared by configuring your build to fail on project repositories.
  See https://docs.gradle.org/8.0/userguide/declaring_repositories.html#sub:fail_build_on_project_repositories for details.
   > Could not find com.example.my_flutter:flutter_debug:1.0.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/com/example/my_flutter/flutter_debug/1.0/flutter_debug-1.0.pom
       - https://repo.maven.apache.org/maven2/com/example/my_flutter/flutter_debug/1.0/flutter_debug-1.0.pom
       - file:/Users/huynq/Documents/NEVERCODE.IO/RepoduceProjects/Flutter-add-to-app-Android-native-sample/my_flutter/build/host/outputs/repo/com/example/my_flutter/flutter_debug/1.0/flutter_debug-1.0.pom
       - https://storage.googleapis.com/download.flutter.io/com/example/my_flutter/flutter_debug/1.0/flutter_debug-1.0.pom
     Required by:
         project :app

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

10: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':app:dataBindingMergeDependencyArtifactsDebugAndroidTest'.
> Could not resolve all dependencies for configuration ':app:debugAndroidTestCompileClasspath'.
  The project declares repositories, effectively ignoring the repositories you have declared in the settings.
  You can figure out how project repositories are declared by configuring your build to fail on project repositories.
  See https://docs.gradle.org/8.0/userguide/declaring_repositories.html#sub:fail_build_on_project_repositories for details.
   > Could not find com.example.my_flutter:flutter_debug:1.0.
     Required by:
         project :app

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

11: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':app:processDebugAndroidTestManifest'.
> Could not resolve all dependencies for configuration ':app:debugRuntimeClasspath'.
  The project declares repositories, effectively ignoring the repositories you have declared in the settings.
  You can figure out how project repositories are declared by configuring your build to fail on project repositories.
  See https://docs.gradle.org/8.0/userguide/declaring_repositories.html#sub:fail_build_on_project_repositories for details.
   > Could not find com.example.my_flutter:flutter_debug:1.0.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/com/example/my_flutter/flutter_debug/1.0/flutter_debug-1.0.pom
       - https://repo.maven.apache.org/maven2/com/example/my_flutter/flutter_debug/1.0/flutter_debug-1.0.pom
       - file:/Users/huynq/Documents/NEVERCODE.IO/RepoduceProjects/Flutter-add-to-app-Android-native-sample/my_flutter/build/host/outputs/repo/com/example/my_flutter/flutter_debug/1.0/flutter_debug-1.0.pom
       - https://storage.googleapis.com/download.flutter.io/com/example/my_flutter/flutter_debug/1.0/flutter_debug-1.0.pom
     Required by:
         project :app

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

12: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':app:checkDebugAndroidTestAarMetadata'.
> Could not resolve all dependencies for configuration ':app:debugRuntimeClasspath'.
  The project declares repositories, effectively ignoring the repositories you have declared in the settings.
  You can figure out how project repositories are declared by configuring your build to fail on project repositories.
  See https://docs.gradle.org/8.0/userguide/declaring_repositories.html#sub:fail_build_on_project_repositories for details.
   > Could not find com.example.my_flutter:flutter_debug:1.0.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/com/example/my_flutter/flutter_debug/1.0/flutter_debug-1.0.pom
       - https://repo.maven.apache.org/maven2/com/example/my_flutter/flutter_debug/1.0/flutter_debug-1.0.pom
       - file:/Users/huynq/Documents/NEVERCODE.IO/RepoduceProjects/Flutter-add-to-app-Android-native-sample/my_flutter/build/host/outputs/repo/com/example/my_flutter/flutter_debug/1.0/flutter_debug-1.0.pom
       - https://storage.googleapis.com/download.flutter.io/com/example/my_flutter/flutter_debug/1.0/flutter_debug-1.0.pom
     Required by:
         project :app

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

13: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':app:mergeDebugAndroidTestAssets'.
> Could not resolve all dependencies for configuration ':app:debugRuntimeClasspath'.
  The project declares repositories, effectively ignoring the repositories you have declared in the settings.
  You can figure out how project repositories are declared by configuring your build to fail on project repositories.
  See https://docs.gradle.org/8.0/userguide/declaring_repositories.html#sub:fail_build_on_project_repositories for details.
   > Could not find com.example.my_flutter:flutter_debug:1.0.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/com/example/my_flutter/flutter_debug/1.0/flutter_debug-1.0.pom
       - https://repo.maven.apache.org/maven2/com/example/my_flutter/flutter_debug/1.0/flutter_debug-1.0.pom
       - file:/Users/huynq/Documents/NEVERCODE.IO/RepoduceProjects/Flutter-add-to-app-Android-native-sample/my_flutter/build/host/outputs/repo/com/example/my_flutter/flutter_debug/1.0/flutter_debug-1.0.pom
       - https://storage.googleapis.com/download.flutter.io/com/example/my_flutter/flutter_debug/1.0/flutter_debug-1.0.pom
     Required by:
         project :app

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

14: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':app:checkDebugAndroidTestDuplicateClasses'.
> Could not resolve all dependencies for configuration ':app:debugRuntimeClasspath'.
  The project declares repositories, effectively ignoring the repositories you have declared in the settings.
  You can figure out how project repositories are declared by configuring your build to fail on project repositories.
  See https://docs.gradle.org/8.0/userguide/declaring_repositories.html#sub:fail_build_on_project_repositories for details.
   > Could not find com.example.my_flutter:flutter_debug:1.0.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/com/example/my_flutter/flutter_debug/1.0/flutter_debug-1.0.pom
       - https://repo.maven.apache.org/maven2/com/example/my_flutter/flutter_debug/1.0/flutter_debug-1.0.pom
       - file:/Users/huynq/Documents/NEVERCODE.IO/RepoduceProjects/Flutter-add-to-app-Android-native-sample/my_flutter/build/host/outputs/repo/com/example/my_flutter/flutter_debug/1.0/flutter_debug-1.0.pom
       - https://storage.googleapis.com/download.flutter.io/com/example/my_flutter/flutter_debug/1.0/flutter_debug-1.0.pom
     Required by:
         project :app

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

15: Task failed with an exception.
-----------
* What went wrong:
Execution failed for task ':app:desugarDebugAndroidTestFileDependencies'.
> Could not resolve all dependencies for configuration ':app:debugRuntimeClasspath'.
  The project declares repositories, effectively ignoring the repositories you have declared in the settings.
  You can figure out how project repositories are declared by configuring your build to fail on project repositories.
  See https://docs.gradle.org/8.0/userguide/declaring_repositories.html#sub:fail_build_on_project_repositories for details.
   > Could not find com.example.my_flutter:flutter_debug:1.0.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/com/example/my_flutter/flutter_debug/1.0/flutter_debug-1.0.pom
       - https://repo.maven.apache.org/maven2/com/example/my_flutter/flutter_debug/1.0/flutter_debug-1.0.pom
       - file:/Users/huynq/Documents/NEVERCODE.IO/RepoduceProjects/Flutter-add-to-app-Android-native-sample/my_flutter/build/host/outputs/repo/com/example/my_flutter/flutter_debug/1.0/flutter_debug-1.0.pom
       - https://storage.googleapis.com/download.flutter.io/com/example/my_flutter/flutter_debug/1.0/flutter_debug-1.0.pom
     Required by:
         project :app

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

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

Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.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/8.0/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 7s
57 actionable tasks: 28 executed, 29 up-to-date

Sorry, I forgot to push MyApplication.kt class. Please try pulling again.

I confirm I reproduce the issue

I tried again but still can't reproduce the issue with my sample code (non-Compose). Can you confirm you checked-out branch issue_142227_blackscreen? Can you also share a recorded demo video as well?

untitled.webm

I can reproduce the issue now on non-compose example issue_142227_blackscreen. I forgot to run flutter build aar again :(. I updated my report above. Thanks for helping check this.

From triage: @johnmccutchan would you be willing to take a look at why the flutter launch hangs? I am wondering if this is something that has been broken for a while or if it was related to some of the engine work that recently was broken and fixed.


add readme badges

Prerequisites

[X] I am an Open Source Contributor
[X] I checked to make sure that this issue has not already been filed

Description
I want to add readme badges.Please assign this issue to me
Screenshots

Code of Conduct

[X] I follow Contributing Guidelines of this project.

Assigning you @S-ishita


add transfer benchmarks

transfers/transfer_checked
                        time:   [1.3442 µs 1.3505 µs 1.3569 µs]
                        thrpt:  [736.96 Kelem/s 740.45 Kelem/s 743.92 Kelem/s]
                 change:
                        time:   [-20.833% -20.260% -19.761%] (p = 0.00 < 0.05)
                        thrpt:  [+24.628% +25.407% +26.316%]
                        Performance has improved.
Found 4 outliers among 100 measurements (4.00%)
  4 (4.00%) low mild
transfers/transfer_unchecked
                        time:   [1.3002 µs 1.3097 µs 1.3194 µs]
                        thrpt:  [757.93 Kelem/s 763.51 Kelem/s 769.09 Kelem/s]
                 change:
                        time:   [-21.279% -20.506% -19.807%] (p = 0.00 < 0.05)
                        thrpt:  [+24.698% +25.796% +27.031%]
                        Performance has improved.
Found 4 outliers among 100 measurements (4.00%)
  3 (3.00%) low mild
  1 (1.00%) high severe

Looks like about 20% faster?

Yes. The point is not to compare to ProgramTest.
Sigverify caps out at 30k per second per core, even with fd_ed25519.

🫡


[AMORO-2266] Improve combined data reader performance

Why are the changes needed?
Close #2266 .
Brief change log

Add condition trigger(Eq-Delete record count > Data record count * 2.5) filter eq delete write to structLikeMap

How was this patch tested?

[x] Add some test cases that check the changes thoroughly including negative and positive cases if possible

[ ] Add screenshots for manual tests if appropriate

[x] Run test locally before making a pull request

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

LGTM


LISTENER_ADDRESS not accept port number

Hi! I need something like LISTENER_PORT, found that it is hardcoded :(
https://github.com/vfarcic/docker-flow-proxy/blob/5b80c5c124f1210f0ca1cdb74362e504468ff7bb/server.go#L79

Can you please let me know what's your use-case? Normally, DFP and DFSL are connected through Overlay network and, in that case, the port is irrelevant since Overlay can have as many services on the same port as needed.

 But, for example, i cant move proxy-listener to another port because proxy-proxy know about 8080 port only

Closing due to inactivity. Feel free to reopen the issue.


⚠ Bofrost.de has degraded performance

In 24b8631, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 2314 ms

Resolved: Bofrost.de performance has improved in 31dc944.


#[pymodule] seems to cause link.exe error: 1112 with Python 3.8.1

🐛 Bug Reports
I followed the guide provided by the README file. I am able to build the project with the following piece of code in my lib.rs file
use pyo3::prelude::*;
use pyo3::wrap_pyfunction;
#[pyfunction]
/// Formats the sum of two numbers as string
fn sum_as_string(a: usize, b: usize) -> PyResult<String> {
    Ok((a + b).to_string())
}

However, building the project with the following part added to lib.rs file
/// This module is a python module implemented in Rust.
#[pymodule]
fn string_sum(py: Python, m: &PyModule) -> PyResult<()> {
    m.add_wrapped(wrap_pyfunction!(sum_as_string))?;
    Ok(())
}

will result in an error caused by (cargo build --verbose):
process didn't exit successfully: `rustc --crate-name string_sum --edition=2018 src\lib.rs --error-
format=json --json=diagnostic-rendered-ansi --crate-type cdylib --emit=dep-info,link -C
debuginfo=2 -C metadata=6ac7a18e68c1e33f --out-dir C:\Users\...\Desktop\Projects
\Rust\test\target\debug\deps -C incremental=C:\Users\...\Desktop\Projects
\Rust\test\target\debug\incremental -L dependency=C:\Users\...\Desktop\Projects
\Rust\test\target\debug\deps --extern pyo3=C:\Users\...\Desktop\Projects\Rust\test
\target\debug\deps\libpyo3-9cb39eebe47e1f6a.rlib -L native=C:\Users\...\AppData\Local
\Programs\Python\Python38\libs` (exit code: 1)

In case it is needed, here is my Cargo.toml:
[package]
name = "..."
version = "0.1.0"
authors = ["..."]
edition = "2018"

[lib]
name = "string_sum"
crate-type = ["cdylib"]

[dependencies.pyo3]
git = "https://github.com/PyO3/pyo3"
feature = ["extension-module"]

🌍 Environment

Your operating system and version: Windows 10
Your python version: Python 3.8.1
How did you install python (e.g. apt or pyenv)? Did you use a virtualenv?:  Using the executable file, I am not using a virtual env
Your rust version (rustc --version): rustc 1.42.0-nightly (bc1571cc3 2020-01-05)
Are you using the latest pyo3 version? Have you tried using latest master (replace version = "0.x.y" with git = "https://github.com/PyO3/pyo3")?
I tried with version = "0.8.5" and #git = "https://github.com/PyO3/pyo3"

💥 Reproducing
Here is the complete code I am trying to compile:
use pyo3::prelude::*;
use pyo3::wrap_pyfunction;

#[pyfunction]
/// Formats the sum of two numbers as string
fn sum_as_string(a: usize, b: usize) -> PyResult<String> {
    Ok((a + b).to_string())
}

/// This module is a python module implemented in Rust.
#[pymodule]
fn string_sum(py: Python, m: &PyModule) -> PyResult<()> {
    m.add_wrapped(wrap_pyfunction!(sum_as_string))?;

    Ok(())
}

Hi, thank you for reporting that!
Can you reproduce it with Python 3.7.*?
If not, we should re-check FFI compatibility with Python 3.8, though it works with Linux.
Related: #704

So I did a fresh install of python, and tested it with Python 3.7.6 and still got the same problem.
Caused by:
  process didn't exit successfully: `rustc --crate-name string_sum --edition=2018 src\lib.rs --error-
format=json --json=diagnostic-rendered-ansi --crate-type cdylib --emit=dep-info,link -C
debuginfo=2 -C metadata=6ac7a18e68c1e33f --out-dir C:\Users\...\Desktop\Projects
\Rust\test\target\debug\deps -C incremental=C:\Users\...\Desktop\Projects\Rust\test
\target\debug\incremental -L dependency=C:\Users\...\Desktop\Projects\Rust\test\target
\debug\deps --extern pyo3=C:\Users\...\Desktop\Projects\Rust\test\target\debug
\deps\libpyo3-9cb39eebe47e1f6a.rlib -L native=C:\Users\...\AppData\Local\Programs\Python
\Python37\libs` (exit code: 1)

That error at the end is potentially a clue.
Have you installed a 32- or 64-bit Python install? And similarly is your Rust target 32- or 64- bit?
They'll need to match. I suspect this might be the problem you're encountering.
I wonder if we can detect this in build.rs

@davidhewitt This seems to fix the build issue, I did not know Rust was not installing the 64-bit version by default... Thank you!
However now I get
ImportError: DLL load failed: %1 is not a valid Win32 application.  but I guess it has nothing to do with PyO3

I did not know Rust was not installing the 64-bit version by default

Rustup uses the 64-bit target by default on my machine. Can you check the toolchain with rustup show-active-toolchain ? This is what I get on my windows 10:
~\dev\pyo3 [master]> rustup show active-toolchain
nightly-x86_64-pc-windows-msvc (directory override for '\\?\C:\Users\david\dev\pyo3')

Once you're sure Rust is using a 64-bit target then you'll need to check the python interpreter you're running is also 64-bit. Finally, are you copying the correct output file? (target/debug/string_sum.dll)

At first running the command you told me displayed 'stable-i686-pc-windows-msvc' and in the directory of my PyO3 project it displayed 'nightly-i686-pc-windows-msvc'. Once I downloaded the x86_64 versions of stable and nightly through rustup install stable-x86_64-pc-windows-msvc and rustup install nightly-x86_64-pc-windows-msvc and running rustup override set nightly-x86_64-pc-windows-msvc inside the PyO3 project directory fixed it. Now it is buiding it correctly. So the problen was that the Rust installer seemed to have installed the i686 version instead of the x86_64

@kngwyu Should we rename this ticket to something like "Report error in build.rs when detected python interpreter architecture does not match target architecture" ?
I might put together a PR some time...

Note that I'm doing a 32-bit vs 64-bit and some other architecture checks in maturin, e.g. here, here and also here, so you can just copy from there.

A note for other folks running into this: If you see a flood of "unresolved external symbol" errors, it might be this issue. Previously #175 was the only issue that included those specific words :)


UTF-8 support and POST request

Encode issue summary with utf-8 support
Make request to Google chart API with POST instead of GET

@pbaris thanks so much for your contribution, and sorry for the 3-week delay :)
There's two tiny details I'd need you to fix - see comments.

I just realized that the .gitignore was totally messed up in master. Will merge it and fix all the outstanding issues, then.
Thanks again!.