Assigned
Status Update
Comments
va...@google.com <va...@google.com>
du...@google.com <du...@google.com> #2
I don't think this is related to Gradle itself. This is how Android handles resources.
Adam, do you have an idea of what's going on here?
Adam, do you have an idea of what's going on here?
ro...@cluemaster.io <ro...@cluemaster.io> #3
It seems the way Android handles the resources of type <item type=string> is flawed.
If gradle resValue generated the String resources using <string> tag instead of <item type=string> this would not be happening.
BTW, i don't see much advantage on using generic <item> tag in this case.
If gradle resValue generated the String resources using <string> tag instead of <item type=string> this would not be happening.
BTW, i don't see much advantage on using generic <item> tag in this case.
du...@google.com <du...@google.com> #4
ah it's interesting that <string> would be different from <item type=string>!
I'll talk to Adam to see what's up.
I'll talk to Adam to see what's up.
Description
YAML option "target_concurrent_requests:"
(Beta) Target number of concurrent connections per instance.
What you expected to happen:
The var name is confusing as the instructions say concurrent connections. Which is it???