Segfault in libjvm.dylib during CreatePanelOfNormalsIntegrationTest

I got a segfault while running CreatePanelOfNormalsIntegrationTest.  Subsequent runs were unable to reproduce it.
   18:03:07.573 WARN  TaskSetManager:70 - Stage 181 contains a task of very large size (119 KB). The maximum recommended task size is 100 KB.
Test: Test method testAllTargetsHDF5PoNCreationSpark[0](null, src/test/resources/org/broadinstitute/hellbender/tools/exome/create-pon-control-full.pcov)(org.broadinstitute.hellbender.tools.exome.CreatePanelOfNormalsIntegrationTest) produced standard out/err: 18:03:07.612 WARN  TaskSetManager:70 - Stage 182 contains a task of very large size (119 KB). The maximum recommended task size is 100 KB.

    18:03:07.612 WARN  TaskSetManager:70 - Stage 182 contains a task of very large size (119 KB). The maximum recommended task size is 100 KB.
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x000000010a5a9401, pid=2425, tid=8963
#
# JRE version: Java(TM) SE Runtime Environment (8.0_91-b14) (build 1.8.0_91-b14)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (25.91-b14 mixed mode bsd-amd64 compressed oops)
# Problematic frame:
# V  [libjvm.dylib+0x1a9401]
#
# Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# An error report file with more information is saved as:
# /Users/louisb/Workspace/gatk-protected/hs_err_pid2425.log
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
#

hs_err_pid2425.log.txt
@yfarjoun Is this similar to the crash you saw a while back?

no. this is different.
On Wed, Aug 31, 2016 at 3:27 PM, Louis Bergelson<EMAIL_ADDRESS>wrote:

I got a segfault while running CreatePanelOfNormalsIntegrationTest.
Subsequent runs were unable to reproduce it.
18:03:07.573 WARN  TaskSetManager:70 - Stage 181 contains a task of very large size (119 KB). The maximum recommended task size is 100 KB.
Test: Test method testAllTargetsHDF5PoNCreationSpark[0](null, src/test/resources/org/broadinstitute/hellbender/tools/exome/create-pon-control-full.pcov)(org.broadinstitute.hellbender.tools.exome.CreatePanelOfNormalsIntegrationTest) produced standard out/err: 18:03:07.612 WARN  TaskSetManager:70 - Stage 182 contains a task of very large size (119 KB). The maximum recommended task size is 100 KB.
18:03:07.612 WARN  TaskSetManager:70 - Stage 182 contains a task of very large size (119 KB). The maximum recommended task size is 100 KB.

A fatal error has been detected by the Java Runtime Environment:

SIGSEGV (0xb) at pc=0x000000010a5a9401, pid=2425, tid=8963

JRE version: Java(TM) SE Runtime Environment (8.0_91-b14) (build 1.8.0_91-b14)
Java VM: Java HotSpot(TM) 64-Bit Server VM (25.91-b14 mixed mode bsd-amd64 compressed oops)
Problematic frame:
V  [libjvm.dylib+0x1a9401]

Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again

An error report file with more information is saved as:
/Users/louisb/Workspace/gatk-protected/hs_err_pid2425.log

If you would like to submit a bug report, please visit:
http://bugreport.java.com/bugreport/crash.jsp

hs_err_pid2425.log.txt
https://github.com/broadinstitute/gatk-protected/files/448383/hs_err_pid2425.log.txt
@yfarjoun https://github.com/yfarjoun Is this similar to the crash you
saw a while back?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/broadinstitute/gatk-protected/issues/659, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ACnk0h0xGA8ntZ_9wd53IUeIqTIfWye0ks5qlf_YgaJpZM4JyIZS
.

Issue moved to broadinstitute/gatk #2883 via ZenHub


Allow modification of Route Methods

This is a placeholder for a PR that allows me (or end users) to solve this issue without Laravel maintaining anything.
Original tweet: https://twitter.com/snellingio/status/1688643282408964097
Pitch I made in the internals discord:
It would be cool to add a method to compile an anonymous class or function to handle post requests.
Currently: Laravel Volt allows us to very easily hook up forms with Folio page routing.
Imagine a contact-us form.
pages
└── contact-us.blade.php

The Volt component would look something like:
<?php

use function Livewire\Volt\{rules, state};

state(['issue_type' => '', 'message' => '', 'email' => '',);
rules([ 'issue_type' => ['bail', 'required'], 'message' => ['required'], 'email' => [ 'required', 'email', ],]);

$save = function () {
    // do the work
};
?>

…
<form wire:submit="save">

This is amazing. However, there are a lot of times / projects that I’m not using Livewire.
I’d love if we had some sort of post or store helper inside folio directly.
<?php

use function Laravel\Folio\{post};

post(function(Request $request) {
    // do the work
});
?>

…
<form action="/contact-us" method="POST">

I think it would work the exact same, it just compiles to an anon function. The actual route would stay the same, and we could route based on the request type.

Thank you. It seems you already made a PR so let's see how it goes.


[QUESTION] Multiple Search Terms / Boolean Searches

Issue Template
Please use this template!
Initial Check

If the issue is a request please specify that it is a request in the title (Example: [REQUEST] more features). If this is a question regarding 'twint' please specify that it's a question in the title (Example: [QUESTION] What is x?). Please only submit issues related to 'twint'. Thanks.

Make sure you've checked the following:

[x] Python version is 3.6;
[x] Updated Twint with pip3 install --user --upgrade -e git+https://github.com/twintproject/twint.git@origin/master#egg=twint;
[x] I have searched the issues and there are no duplicates of this issue/question/request.

Command Ran

Please provide the exact command ran including the username/search/code so I may reproduce the issue.
Multiple/See description.

Description of Issue

Please use as much detail as possible.
I'm wondering if a multiple search terms/boolean search terms feature has been added and how to structure that command.

For example, I can run python twint -s "cat"+"dog"``` or ```python twint -s "cat","dog" and twint will grab tweets that contain both the words "cat" and "dog" in the same tweet. I would like to be able to do some boolean filtering with the search terms such as python twint -s "pets" AND ("cat" OR "dog") currently I am working around this by just executing multiple commands i.e. python twint -s "pets"+"cat" and python twint -s "pets"+"dog" and combining the files. However, this example is not practical when you have a 50+ keywords.
I've tried just running the search tag multiple times in a single command hoping it would magically work such as python twint -s "pets"+"cat" -s "pets"+"dog" but it will skip every -s flag except the last one and produce the output of -s "pets"+"dogs".
Any assistance would be great!
Environment Details

Using Windows, Linux? What OS version? Running this in Anaconda? Jupyter Notebook? Terminal?
I'm running Garuda Linux Dragonized and after a few tweaks, Twint works flawlessly.

Please look at this link it
You should have your search words encapsulated in one quotes not two
twint -s "cat OR dog"
https://stackoverflow.com/questions/62198077/search-multiple-words-in-twint-python-library


Include this package's Project.toml file when parsing Project.toml files

Fixes #22

bors r+

bors r-

bors r+


Ubuntu 20.04 - php-gettext

I think the scrip is not compatible with 20.04 at the moment since php-gettext is not released yet in Focal servers.
https://launchpad.net/ubuntu/focal/+source/php-gettext
Running the script fails with:

Edit: Forgot to add; I just wanted to let you know that as it is, it doesn't run on 20.04. I don't think you 'officially' support it but saw you tweet about it a few weeks ago.

Allegedly, php-gettext is now provided by php-common. Can you do me a
favor? on line 127:
declare -a packages=( mariadb-server mariadb-client nginx php php-fpm
php-pear php-cgi php-common php-zip php-mbstring php-net-socket php-gd
php-xml-util php-mysql php-gettext php-bcmath rng-tools );
install_packages ${packages[@]}
remove the package php-gettext to where the line reads:
declare -a packages=( mariadb-server mariadb-client nginx php php-fpm
php-pear php-cgi php-common php-zip php-mbstring php-net-socket php-gd
php-xml-util php-mysql php-bcmath rng-tools );
install_packages ${packages[@]}
or, if you're not feeling particularly confident and don't want to hunt
line numbers:
sed -i 's/php-gettext//g' ciderpress.sh
then run the script again. Tell me if you run into anymore problems.
Thanks!
On Sun, Sep 6, 2020 at 1:15 AM d-salinas<EMAIL_ADDRESS>wrote:

I think the scrip is not compatible with 20.04 at the moment since
php-gettext is not released yet in Focal servers.
https://launchpad.net/ubuntu/focal/+source/php-gettext
Running the script fails with:
[image: image]
https://user-images.githubusercontent.com/47836038/92318702-f8d4f580-efd5-11ea-8330-016424b62796.png
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/da667/Ciderpress/issues/1, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAQW67ZDIOEU7IN6FEPJTBTSEMLGXANCNFSM4Q34OOZQ
.

--
when does reality end? when does fantasy begin?

Just got around having time to test again, and removing the 'php-gettext' on line 127 worked like a charm!
Seems like that was the only issue running this on 20.04 - thank you for the help!


widget rectangle works draws area too small

I've got the config
displays:
  window:
    width: 1280
    height: 720
window:
  width: 1280
  height: 720
  title: Mission Pinball Framework
  resizable: false
  fullscreen: false
  borderless: false
  exit_on_escape: true
  source_display: window

With the following widget, there appears just an rectangle quarter of the window. Other widgets use the whole window.
    - type: rectangle
      x: 0
      y: 0
      width: 1280
      height: 720
      color: pink

This appears to be bad documentation here. Widgets claim they anchor from the bottom left corner. Thus it should fill the whole thing. However, rectangles actually are anchoring from the middle. So when you say X: 0 and y: 0, you are putting the middle in the bottom corner. The whole thing is there, just only the top right quadrant is shown.
Changing this would be breaking for others, so updating docs is the best approach.
If you remove x and y, it with default center. Additionally if you add anchor_x: left and anchor_y: bottom then it will appear as expected.
From cmd use mpf imc to see an interactive MC. This allows you to play with positioning, then copy it into your config.

I'll amend that slightly.
https://missionpinball.org/mc/widgets/common_settings/
The default anchor position is middle. This is inconsistent with what shows elsewhere. So this page matches how the code works. Other pages are inconsistent though. I'll try to run through and fix them and the examples.


Better error message.

What are those two „Merge branch 'master' into crypto_fix“? Is this merging of the master into the branch, instead of rebasing the branch? If so, what's the advantage?


YouTube player occasionally does not preload properly

I'm still trying to get to the bottom of this one, but I have a theory for why it might not work properly 100% of the time:

Player starts with a valid SoundCloud URL
SoundCloud player is rendered before the YouTube iframe is rendered and ready
YouTube iframe does not have whatever focus token Chrome gives it
This tab/window loses focus
YouTube videos will not autoplay until window attains focus

Hey @Fauntleroy, do you have steps to reproduce this? I can see the problem but only when changing to another tab before the blank YT preload video has started playing (that is, quite quickly after initial load), which makes sense, and is something that can't really be fixed.

Anything further on this @Fauntleroy?

Closing this due to age. Feel free to re-open with steps to reproduce the issue.


Regular Expression Denial of Service vulnerability detected

Below vulnerability is detected via npm version 6.4.1
Regular Expression Denial of Service (as low severity)
Manual Review
Some vulnerabilities require your attention to resolve
Visit https://go.npm.me/audit-guide for additional guidance
Low             Regular Expression Denial of Service
Package         braces
Patched in      >=2.3.1

This was fixed a long time ago.


update boot flow documentation

https://github.com/threefoldtech/zosv2/blob/master/zinit/readme.md

fixed by #164


[FEAT] Implement API Endpoint to Assign Role and Permissions to a User within an Organization

Description
Develop and integrate a complete Role-Based Access Control (RBAC) system into the application to manage user permissions and access levels. This includes endpoints for creating permissions, roles, assigning roles to users, and checking permissions.
Acceptance Criteria:

Create Permission Endpoint:

Endpoint: The endpoint /api/v1/permissions should be accessible via a POST request.
Request Body: The request body should include the permission name and description.
Successful Creation: When a valid permission name and description are provided, the endpoint returns a 201 Created status with a success message and the details of the created permission.
Permission Already Exists: If a permission with the same name already exists, the endpoint returns a 409 Conflict status with an appropriate error message.

Create Role Endpoint:

Endpoint: The endpoint /api/v1/roles should be accessible via a POST request.
Request Body: The request body should include the role name and an array of permission_ids.
Successful Creation: When a valid role name and permissions are provided, the endpoint returns a 201 Created status with a success message and the details of the created role.
Role Already Exists: If a role with the same name already exists, the endpoint returns a 409 Conflict status with an appropriate error message.
Invalid Permission: If any provided permission_id does not exist, the endpoint returns a 404 Not Found status with an appropriate error message.

Assign Role to User Endpoint:

Endpoint: The endpoint /api/v1/organizations/{organization-id}/users/{user-id}/roles should be accessible via a POST request.
Request Body: The request body should include the role_id to be assigned to the user.
Successful Assignment: When valid organization-id, user-id, and role_id are provided, the endpoint returns a 200 OK status with a success message.
Invalid Format: When an invalid organization-id or user-id format is provided, the endpoint returns a 400 Bad Request status with an appropriate error message.
Role Not Found: When a role_id that does not exist is provided, the endpoint returns a 404 Not Found status with an appropriate error message.
User or Organization Not Found: When an organization-id or user-id that does not exist is provided, the endpoint returns a 404 Not Found status with an appropriate error message.
Server Error: If an unexpected server error occurs, the endpoint returns a 500 Internal Server Error status with an appropriate error message.

Check Permissions Endpoint:

Endpoint: The endpoint /api/v1/users/{user-id}/permissions should be accessible via a GET request.
Response: The endpoint returns a 200 OK status with the list of permissions assigned to the user.
User Not Found: If the user-id does not exist, the endpoint returns a 404 Not Found status with an appropriate error message.

Create Permission Endpoint
Endpoint URL:
bash

POST /api/v1/permissions

Request Body:
json

{
  "name": "update_profile",
  "description": "Allows the user to update their profile information"
}

Responses:
Success Response:
Code: 201 Created
Content:
json

{
  "message": "Permission created successfully",
  "status_code": 201,
  "data": {
    "id": "permission-id",
    "name": "update_profile",
    "description": "Allows the user to update their profile information",
    "created_at": "DateTime"
  }
}

Error Responses:
Code: 400 BAD REQUEST
Content:
json

{
  "status_code": 400,
  "message": "Invalid permission name or description format"
}

Code: 409 CONFLICT
Content:
json

{
  "status_code": 409,
  "message": "Permission already exists"
}

Code: 500 INTERNAL SERVER ERROR
Content:
json
{
  "status_code": 500,
  "message": "An unexpected error occurred"
}

Create Role Endpoint
Endpoint URL:
bash

POST /api/v1/roles

Request Body:
json

{
  "name": "admin",
  "permission_ids": ["1", "3", "5"]
}

Responses:
Success Response:
Code: 201 Created
Content:
json

{
  "message": "Role created successfully",
  "status_code": 201,
  "data": {
    "id": "role-id",
    "name": "admin",
    "permissions": [
      {"id": "1", "name": "create_user"},
      {"id": "3", "name": "delete_user"},
      {"id": "5", "name": "update_user"}
    ],
    "created_at": "DateTime"
  }
}

Error Responses:
Code: 400 BAD REQUEST
Content:
json

{
  "status_code": 400,
  "message": "Invalid role name or permission_ids format"
}

Code: 404 NOT FOUND
Content:
json

{
  "status_code": 404,
  "message": "One or more permissions not found"
}

Code: 409 CONFLICT
Content:
json

{
  "status_code": 409,
  "message": "Role already exists"
}

Code: 500 INTERNAL SERVER ERROR
Content:
json

{
  "status_code": 500,
  "message": "An unexpected error occurred"
}

Assign Role to User Endpoint
Endpoint URL:
bash
POST /api/v1/organizations/{organization-id}/users/{user-id}/roles

Request Body:
json
{
  "role_id": "role-id"
}

Responses:
Success Response:
Code: 200 OK
Content:
json

{
  "message": "Role assigned successfully",
  "status_code": 200,
  "data": {
    "id": "user-id",
    "organization_id": "organization-id",
    "role": "admin",
    "permissions": [
      {"id": "1", "name": "create_user"},
      {"id": "3", "name": "delete_user"},
      {"id": "5", "name": "update_user"}
    ],
    "created_at": "DateTime"
  }
}

Error Responses:
Code: 400 BAD REQUEST
Content:
json

{
  "status_code": 400,
  "message": "Invalid organization ID or user ID format"
}

Code: 404 NOT FOUND
Content:
json

{
  "status_code": 404,
  "message": "Organization, user, or role not found"
}

Code: 422 UNPROCESSABLE CONTENT / VALIDATION ERROR
Content:
json

{
  "status_code": 422,
  "message": "Validation error",
  "errors": {
    "field": "<field>",
    "message": "<message>"
  }
}

Code: 500 INTERNAL SERVER ERROR
Content:
json

{
  "status_code": 500,
  "message": "An unexpected error occurred"
}

Check Permissions Endpoint
Endpoint URL:
bash

GET /api/v1/users/{user-id}/permissions

Responses:
Success Response:
Code: 200 OK
Content:
json

{
  "status_code": 200,
  "message": "Permissions fetched successfully",
  "data": {
    "id": "user-id",
    "permissions": [
      {"id": "1", "name": "create_user"},
      {"id": "3", "name": "delete_user"},
      {"id": "5", "name": "update_user"}
    ],
    "created_at": "DateTime"
  }
}

Error Responses:
Code: 404 NOT FOUND
Content:
json

{
  "status_code": 404,
  "message": "User not found"
}

Code: 500 INTERNAL SERVER ERROR
Content:
json

{
  "status_code": 500,
  "message": "An unexpected error occurred"
}

Database Schema:
sql

Table users {
  id int [pk, increment]
  name varchar(255) [not null]
  email varchar(255) [not null, unique]
  created_at timestamp [default: `current_timestamp`]
  updated_at timestamp [default: `current_timestamp`]
}

Table organizations {
  id int [pk, increment]
  name varchar(255) [not null]
  created_at timestamp [default: `current_timestamp`]
  updated_at timestamp [default: `current_timestamp`]
}

Table permissions {
  id int [pk, increment]
  name varchar(255) [not null, unique]
  description text [not null]
  created_at timestamp [default: `current_timestamp`]
  updated_at timestamp [default: `current_timestamp`]
}

Table roles {
  id int [pk, increment]
  name varchar(255) [not null, unique]
  created_at timestamp [default: `current_timestamp`]
  updated_at timestamp [default: `current_timestamp`]
}

Table role_permissions {
  id int [pk, increment]
  role_id int [ref: > roles.id]
  permission_id int [ref: > permissions.id]
  created_at timestamp [default: `current_timestamp`]
  updated_at timestamp [default: `current_timestamp`]
}

Table user_roles {
  id int [pk, increment]
  user_id int [ref: > users.id]
  organization_id int [ref: > organizations.id]
  role_id int [ref: > roles.id]
  created_at timestamp [default: `current_timestamp`]
  updated_at timestamp [default: `current_timestamp`]
}

Purpose:

The Create Permission endpoint allows for the creation of new permissions.
The Create Role endpoint allows for creating roles and assigning existing permissions to these roles.
The Assign Role to User endpoint allows for assigning existing roles to users within an organization.
The Check Permissions endpoint allows for retrieving the permissions of a user.

Requirements:

Implement the Create Permission endpoint to create new permissions.
Implement the Create Role endpoint to create new roles with assigned permissions.
Implement the Assign Role to User endpoint to assign existing roles to users.
Implement the Check Permissions endpoint to retrieve a user's permissions.
Return detailed information on the created or assigned roles and permissions.
Handle situations where permissions, roles, users, or organizations do not exist.

Expected Outcome:

Four API endpoints that manage permission creation, role creation with permissions, role assignment to users, and permission retrieval, ensuring clear and effective role and permission management within the system.

Tasks:
1.Define Create Permission Endpoint:

[ ] Create an endpoint /api/v1/permissions to create permissions.

Define Create Role Endpoint:

[ ] Create an endpoint /api/v1/roles to create roles with permissions.

Define Assign Role to User Endpoint:

[ ] Create an endpoint /api/v1/organizations/{organization-id}/users/{user-id}/roles to assign roles and permissions.

Define Check Permissions Endpoint:

[ ] Create an endpoint /api/v1/users/{user-id}/permissions to retrieve user permissions.

Implement Logic:

[ ] Implement server-side logic to handle successful and failed permission creation, role creation, role assignment, and permission retrieval requests.

Input Validation:

[ ] Ensure input validation to verify the correctness of permission names, role names, permission IDs, organization-id, and user-id.

Database Query:

[ ] Write the necessary database queries to create permissions, create roles with assigned permissions, update user roles and permissions, and retrieve user permissions.

Error Handling:

[ ] Implement error handling for invalid inputs, non-existing permissions, roles, users, or organizations, and server errors.

Logging:

[ ] Implement logging for errors and role assignment or creation attempts.

Testing:

[ ] Write unit tests for the permission creation, role creation, role assignment, and permission retrieval endpoints.
[ ] Write integration tests for the permission creation, role creation, role assignment, and permission retrieval logic.

Security:

[ ] Perform security testing to ensure data protection and compliance.
[ ] Ensure all sensitive data is encrypted and secure.

Request Body or Params?
How is the role or user identified or add in the URL?
@Takinnuoye5

@highb33kay boss I have made necessary amendments please assist confirm if requirement was met

I still have questions about this. One is are the roles being created or assigned?

@highb33kay so the role must already exist within the system. But then I don’t know if I should create the role and assign together

@highb33kay approve if satisfied with his changes

Not satisfied because I think this is how it should be.
Permissions exists
Create this
Update
Read
Execute
Update credit card
Update role
Delete role
Etc.
Then roles should be created with an endpoint that assigns these permissions to the roles
Role : permission [1, 3,8]
So when we are running auth checks we check for permissions not roles
This is just a summary of how I think it should go.
This would allow us generate dynamic roles and not static roles

@phurhard Let me know what you think

@Takinnuoye5 See also #153

So IMO we need a create role that takes in permission and also to assign role

okay i will factor this into it immediately boss

Did you see my comment on the other issue? About permissions and roles being dynamic?

hello boss , @highb33kay  please check the new structure

This looks good, I just think it is too many endpoints for one ticket.

can i create three tickets then , to cater for it

@Takinnuoye5 you still here?

Yes i am asking if i can create 3 tickets so to ensure I cover everything on user roles and permissions

@highb33kay i have agreed to go with the Create Permission Endpoint: while the rest Endpoints have been shared accordingly

Alright, niceee.


Add k8s annotations to the Envoy Proxy Service

Description:
Extend the Envoy Proxy API to allow a user to add more k8s annotations to the Envoy Proxy service.
Relates to https://github.com/envoyproxy/gateway/issues/368#issuecomment-1243432619
[optional Relevant Links:]

Any extra documentation required to understand the issue.

assign, quite busy recently, will work on this tomorrow.

@Xunzhuo thanks for offering to help with this issue. Since this is a "Backlog" milestone issue, I suggest working on RC-2 issues since they're more pressing.

Relates to https://github.com/envoyproxy/gateway/issues/368#issuecomment-1243432619

IMHO this issue is very different from #368. #368 was required because EG needs a mechanism to correlate the Gateway ns/name that was used to create the managed resources, e.g. Service. If the managed resources were in the same ns as the Gateway, an ownerReference could be used and the owning ns/name label would be unneeded.
I'm not sure if passing annotations to the Service is the best approach for solving this problem. I think it can be error-prone as opposed to creating an API. For example, what if LoadBalancer annotations are specified for an internal (ClusterIP) Service or GCP-specific LoadBalancer annotations are specified when EG runs in AWS?
Thoughts @LukeShu @skriss @youngnick @AliceProxy @Xunzhuo?

I have a slightly different use case. I would like to have the Gateway annotate its LoadBalancer service in order to register with external-dns when the gateway is created. Right now I can manually annotate the service after it is created, but then any time a change is made to the Gateway the annotation is removed from the Service.
So there is two ways that this can be approached. Either A) The gateway manages the annotations that are put onto the Service object or B) the Gateway leaves any existing annotations in place when making changes to the Gateway.
"kubectl annotate service envoy-default-eg-64656661 -n envoy-gateway-system "external-dns.alpha.kubernetes.io/hostname=myhostname.com" will annotate the service and external-dns will see this and register the DNS name with the provider.

@ericgoode External DNS supports Gateway API, so I would expect it to work natively with EG. Have you tested the integration yet?
xref: https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/gateway-api.md

Thank you for pointing this out. I have tested it and it works. My use case listed above for this issue is void.

We currently have infrastructure defined in the GatewayClass level tied to the EnvoyProxy CRD using paramsRef https://gateway.envoyproxy.io/v0.3.0/api/config_types.html#kubernetesdeploymentspec
So an annotations knob within a services field makes sense to me.
cross linking with https://github.com/kubernetes-sigs/gateway-api/pull/1653#issuecomment-1451025249 where @youngnick highlighted that a notion of infrastructure could be added to the Gateway resource.
Prefer if we started off adding to the EnvoyProxy CRD and later incorporated the upstream proposal


New package: ChemTableSoftware.SoftOrganizer version 9.32

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.4 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/112684&drop=dogfoodAlpha

@microsoft-github-policy-service agree


Release 1.2.5

Description
Release 1.2.5 since some changes didn't go out in 1.2.4

Codecov Report

Merging #693 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #693   +/-   ##
=========================================
  Coverage     55.94%   55.94%
  Complexity      757      757
=========================================
  Files           181      181
  Lines          3207     3207
  Branches        237      237
=========================================
  Hits           1794     1794
  Misses         1277     1277
  Partials        136      136

Continue to review full report at Codecov.

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


LeetCodeTest only opens a new window with #Test Input

After running LeetCodeTest on some the first two-sim problem, I expect to have a 'run code' / 'test' submission. But right now I am only able to use this to see the Test Input.
# Test Input
[2,7,11,15]
9

for the two-sums problem
When running LeetCodeSubmit, I get a window with expected output.

I'm seeing the same running in NVIM v0.4.4 against a solution written in go. LeetCodeTest opens a new split with test input, but not one with test results.

Try  :wq on the new window that opens with the test input.


Split out API into its out service

The API should be reusable without having to use UI.

Forgot to tag.  Major changes here: 6fea63e17278271b661c1f3b2b05b07178c5cba7


SpriteBatch#draw draws nothing and gives no error if very high rotation value is passed

Issue details
When very high values are passed as rotation in SpriteBatch#draw (for example, 100,000,000f), nothing is drawn and no errors appear in log.
Reproduction steps/code
package com.mygdx.game;

import com.badlogic.gdx.ApplicationAdapter;
import com.badlogic.gdx.Gdx;
import com.badlogic.gdx.graphics.GL20;
import com.badlogic.gdx.graphics.Texture;
import com.badlogic.gdx.graphics.g2d.SpriteBatch;
import com.badlogic.gdx.graphics.g2d.TextureRegion;

public class MyGdxGame extends ApplicationAdapter {
	SpriteBatch batch;
	Texture img;
	TextureRegion tr;

	@Override
	public void create () {
		batch = new SpriteBatch();
		img = new Texture("badlogic.jpg");
		tr = new TextureRegion(img, 128, 128);
	}

	@Override
	public void render () {
		Gdx.gl.glClearColor(1, 0, 0, 1);
		Gdx.gl.glClear(GL20.GL_COLOR_BUFFER_BIT);
		batch.begin();
		batch.draw(tr, 0, 0, 64, 64, 128, 128, 1, 1, 100000000f);
		batch.end();
	}
}

Version of LibGDX and/or relevant dependencies
1.9.2
Please select the affected platforms

[x] Android
[ ] iOS
[ ] HTML/GWT
[x] Windows
[ ] Linux
[ ] MacOS

This is because MathUtils.sin/cos lose precision significantly for high input values. I doubt it will be fixed, because it would incur performance penalty. It could be documented somewhere though.

I agree with @Darkyenus . Someone could fix that by using a modulo operation on the rotation inside that method. But modulo is based on division which is really slow on some devices (mostly mobile). Therefore you would introduce a huge performance impact on most users.
A better way would be to check your rotation variable every frame or two and subtract 360 if the value is greater than 360. Because sin/cos are periodic this is possible. Same goes with negative values.

I think it's best if users just avoid passing such high values.


Support license-file option in Cargo.toml

Thanks for the issue! Can you test if master branch solves your problem?
In commit 49ced88ae7702a83ee97e5248b956ba7fda06e93 I added support for taking the license file path from license_file and include it to list of licenses to be printed out fully.


Adding passing unit test for unknown schema.net types.

Unknown types are deserialized as Thing.
Unknown properties are ignored.

Addresses #7

Please fix:

ThingTest.cs(16,33): warning SA1214: Readonly fields should appear before non-readonly fields [C:\projects\schema-net\Tests\Schema.NET.Test\Schema.NET.Test.csproj

You should probably make both fields readonly.

Cool. Thanks for your efforts. Adding you as a contributor to front page as a thank you.

No problem at all. Just paying back.


Translate  docs/tasks/extend-kubernetes/setup-konnectivity.md into Chinese

This is a Feature Request
What would you like to be added
Translate docs/tasks/extend-kubernetes/setup-konnectivity.md into Chinese
Why is this needed
Cannot find docs/tasks/extend-kubernetes/setup-konnectivity.md in Chinese
Comments
The page to update:
https://kubernetes.io/docs/tasks/extend-kubernetes/setup-konnectivity/

/language zh
/assign

Done. (31aa397284e4c777ade95c94ff7c3b89d0a280bd)
/close


Visual aid to determine the current keymap with Vi keybindings

First of all, excellent job with the prompt 👏  I discovered today that Zim had a "new" default prompt after reinstalling my machine, and it is so simple and functional that I want to use it instead of Pure.
Is your feature request related to a problem? Please describe.
When Vi keybindings are enabled (bindkey -v) there is no visual aid to determine whether zle's current keymap is viins (insert mode, default) or vicmd (command mode, when pressing ESC).
I think making such visual aid part of the prompt would be sensible because:

Vi keybindings are built into Zsh
The keymap configuration is part of Zim's default configuration

Describe the solution you'd like

Option 1 (preferred)
Change the prompt symbol to another character of the ASCII table while the vicmd keymap is active. There aren't that many but, as an example, the extended ASCII table contains § (char 167), which should be available in any font and is quite subtle.
It looks like below (viins / vicmd):

Option 2
Change the color of the prompt symbol to something other than green or red while the vicmd keymap is active. I suggest cyan because it is somewhat close to green, yet distinguishable.
Potential issue: the red color coding — which indicates that the previous command failed — is lost while in vicmd mode, unless translated to yet another color like magenta. I'm not yet sure how I'd feel about that.
It looks like below (viins / vicmd):

Describe alternatives you've considered
Spaceship includes a text indicator ([I] / [N]) on the first line, which I find bloated.
Starship allows configuring the shape and color of the prompt symbol in different states, which I find interesting and well designed. But considering the minimal nature of asciiship, I think a sane default that people can customize by forking the prompt's code would be enough.
Changing the terminal's cursor shape while changing mode e.g. from beam to block and back — like in Vim itself — would be controversial and error prone.
Additional context
-

Hi @antoineco. So good to know you like our lightweight prompt theme!  :- D
Not sure which indicator to pick for the vicmd keymap. We're already using # when root, % otherwise. Also, it's already green or red depending on the exit status of the last command. I agree changing the terminal cursor shape is controversial and error prone.
If you want to experiment with it yourself, we have two themes that have vicmd keymap indicators implemented:

sorin
s1ck94

It's quite a good amount of additional code.

This is what I've come up with: changing the prompt indicator to standout when in vicmd.
diff --git a/asciiship.zsh-theme b/asciiship.zsh-theme
index def650b..7641305 100644
--- a/asciiship.zsh-theme
+++ b/asciiship.zsh-theme
@@ -1,5 +1,23 @@
 # vim:et sts=2 sw=2 ft=zsh

+_prompt_asciiship_vimode() {
+  case ${KEYMAP} in
+    vicmd) print -n '%S%#%s' ;;
+    *) print -n '%#' ;;
+  esac
+}
+
+_prompt_asciiship_keymap_select() {
+  zle reset-prompt
+  zle -R
+}
+if autoload -Uz is-at-least && is-at-least 5.3; then
+  autoload -Uz add-zle-hook-widget && \
+      add-zle-hook-widget -Uz keymap-select _prompt_asciiship_keymap_select
+else
+  zle -N zle-keymap-select _prompt_asciiship_keymap_select
+fi
+
 typeset -g VIRTUAL_ENV_DISABLE_PROMPT=1

 setopt nopromptbang prompt{cr,percent,sp,subst}
@@ -31,5 +49,5 @@ fi

 PS1='
 %(2L.%B%F{yellow}(%L)%f%b .)%(!.%B%F{red}%n%f%b in .${SSH_TTY:+"%B%F{yellow}%n%f%b in "})${SSH_TTY:+"%B%F{green}%m%f%b in "}%B%F{cyan}%~%f%b${(e)git_info[prompt]}${VIRTUAL_ENV:+" via %B%F{yellow}${VIRTUAL_ENV:t}%b%f"}${duration_info}
-%B%(1j.%F{blue}*%f .)%(?.%F{green}.%F{red}%? )%#%f%b '
+%B%(1j.%F{blue}*%f .)%(?.%F{green}.%F{red}%? )$(_prompt_asciiship_vimode)%f%b '
 unset RPS1

I hadn't though about standout, that could be a good approach I think! Underline comes to mind too.
I know that the screen-* / tmux-* terminfos that ship with macOS don't include italics and standout, but

those are much less common than xterm-*
a lot of macOS users who rely on these capabilities either enable them manually or recompile their terminfo from a more recent ncurses to enable them

Contrary to what I remembered, standout does work perfectly fine in tmux on macOS, with the default tmux config (TERM=screen-256color) and the OS' default terminfo.
It also works in various terminal emulators I've tried on macOS, with various xterm terminfo variants.
tmux 3.3, screen-256color

Terminal.app, xterm-256color

Kitty, xterm-kitty


ENH: Revise and add tests for the PEPOLAR correction

I still need to double-check the simplified workflow is equivalent to the original one, but I'm adding Matt since the review can be started.

Hey @mattcieslak, can you give this a quick look?
I'll be addressing the suggestions you gave under #18 in a different PR (the reason is that there are some more hard-wired elements specific to BOLD, so such generalization will require more surgery on these workflows)
Results are here:
https://181-189236569-gh.circle-artifacts.com/0/tmp/tests/sdcflows/sub-1/fmap/sub-1_dir-AP_desc-pepolar_epi.svg
https://181-189236569-gh.circle-artifacts.com/0/tmp/tests/sdcflows/sub-HCP101006/fmap/sub-HCP101006_dir-LR_desc-pepolar_epi.svg
BTW, what do you think about the new way of plotting field maps (bilateral with linear intensity gradient scheme)?

The color scheme does not have into account the polarity of the phase encoding, so unfortunately not yet.
It is meant to be useful in the representation of fieldmaps in Hz (e.g. https://181-189236569-gh.circle-artifacts.com/0/tmp/tests/sdcflows/sub-1/fmap/sub-1_acq-v4_phasediff.svg and https://181-189236569-gh.circle-artifacts.com/0/tmp/tests/sdcflows/sub-HCP101006/fmap/sub-HCP101006_phasediff.svg).


Finalized Changelog edits for 1.36.0 (2.0)

Updated with edits to cover the latest editions to the Changelog and a small revision to last week's bug fix.

Waiting for CLA signature by @K8med
@K8med - We require a Contributor License Agreement (CLA) for people who contribute to Puppet, but we have an easy click-through license with instructions, which is available at https://cla.puppet.com/
Note: if your contribution is trivial and you think it may be exempt from the CLA, please post a short reply to this comment with details. http://docs.puppet.com/community/trivial_patch_exemption.html

CLA signed by all contributors.


updated afterKillShow - added faux plural to kill message

var killedText = "You have killed " + lookupCount + " " + killedThing + (lookupCount!=1?"s":"") + "!";

better implementation in main exists


THUMOS14 fetch_tag_proposal.sh doesn't work

Checklist

[x]  I have searched related issues but cannot get the expected help.
[x]  The bug has not been fixed in the latest version.

Describe the bug
fetch_tag_proposal.sh in THUMOS14 dataset doesn't work because these links are forbidden as follow.
https://open-mmlab.s3.ap-northeast-2.amazonaws.com/mmaction/filelist/thumos14_tag_val_normalized_proposal_list.txt
https://open-mmlab.s3.ap-northeast-2.amazonaws.com/mmaction/filelist/thumos14_tag_test_normalized_proposal_list.txt

Reproduction

What command or script did you run?

cd $MMACTION2/tools/data/thumos14/
bash fetch_tag_proposals.sh

Did you make any modifications on the code or config? Did you understand what you have modified?
Links of thumos14_tag_val_normalized_proposal_list.txt and thumos14_tag_test_normalized_proposal_list.txt are invalid.

What dataset did you use?
THUMOS14

Environment

Please run PYTHONPATH=${PWD}:$PYTHONPATH python mmaction/utils/collect_env.py to collect necessary environment information and paste it here.

sys.platform: linux
Python: 3.8.5 (default, Sep  4 2020, 07:30:14) [GCC 7.3.0]
CUDA available: True
GPU 0,1,2,3: NVIDIA Quadro RTX 8000
CUDA_HOME: /usr/local/cuda
NVCC: Build cuda_11.0_bu.TC445_37.28845127_0
GCC: gcc (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0
PyTorch: 1.7.1
PyTorch compiling details: PyTorch built with:
  - GCC 7.3
  - C++ Version: 201402
  - Intel(R) Math Kernel Library Version 2020.0.2 Product Build 20200624 for Intel(R) 64 architecture applications
  - Intel(R) MKL-DNN v1.6.0 (Git Hash 5ef631a030a6f73131c77892041042805a06064f)
  - OpenMP 201511 (a.k.a. OpenMP 4.5)
  - NNPACK is enabled
  - CPU capability usage: AVX2
  - CUDA Runtime 11.0
  - NVCC architecture flags: -gencode;arch=compute_37,code=sm_37;-gencode;arch=compute_50,code=sm_50;-gencode;arch=compute_60,code=sm_60;-gencode;arch=compute_61,code=sm_61;-gencode;arch=compute_70,code=sm_70;-gencode;arch=compute_75,code=sm_75;-gencode;arch=compute_80,code=sm_80;-gencode;arch=compute_37,code=compute_37
  - CuDNN 8.0.5
  - Magma 2.5.2
  - Build settings: BLAS=MKL, BUILD_TYPE=Release, CXX_FLAGS= -Wno-deprecated -fvisibility-inlines-hidden -DUSE_PTHREADPOOL -fopenmp -DNDEBUG -DUSE_FBGEMM -DUSE_QNNPACK -DUSE_PYTORCH_QNNPACK -DUSE_XNNPACK -DUSE_VULKAN_WRAPPER -O2 -fPIC -Wno-narrowing -Wall -Wextra -Werror=return-type -Wno-missing-field-initializers -Wno-type-limits -Wno-array-bounds -Wno-unknown-pragmas -Wno-sign-compare -Wno-unused-parameter -Wno-unused-variable -Wno-unused-function -Wno-unused-result -Wno-unused-local-typedefs -Wno-strict-overflow -Wno-strict-aliasing -Wno-error=deprecated-declarations -Wno-stringop-overflow -Wno-psabi -Wno-error=pedantic -Wno-error=redundant-decls -Wno-error=old-style-cast -fdiagnostics-color=always -faligned-new -Wno-unused-but-set-variable -Wno-maybe-uninitialized -fno-math-errno -fno-trapping-math -Werror=format -Wno-stringop-overflow, PERF_WITH_AVX=1, PERF_WITH_AVX2=1, PERF_WITH_AVX512=1, USE_CUDA=ON, USE_EXCEPTION_PTR=1, USE_GFLAGS=OFF, USE_GLOG=OFF, USE_MKL=ON, USE_MKLDNN=ON, USE_MPI=OFF, USE_NCCL=ON, USE_NNPACK=ON, USE_OPENMP=ON,

TorchVision: 0.8.2
OpenCV: 4.5.3
MMCV: 1.3.6
MMCV Compiler: GCC 7.5
MMCV CUDA Compiler: 11.0
MMAction2: 0.17.0+acce52d

Error traceback
If applicable, paste the error traceback here.
root@###########:/mmaction2/tools/data/thumos14# bash fetch_tag_proposals.sh
../../../data/thumos14/proposals does not exist. Creating
--2021-09-10 00:25:51--  https://open-mmlab.s3.ap-northeast-2.amazonaws.com/mmaction/filelist/thumos14_tag_val_normalized_proposal_list.txt
Resolving open-mmlab.s3.ap-northeast-2.amazonaws.com (open-mmlab.s3.ap-northeast-2.amazonaws.com)... <IP_ADDRESS>
Connecting to open-mmlab.s3.ap-northeast-2.amazonaws.com (open-mmlab.s3.ap-northeast-2.amazonaws.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 403 Forbidden
2021-09-10 00:25:51 ERROR 403: Forbidden.

--2021-09-10 00:25:51--  https://open-mmlab.s3.ap-northeast-2.amazonaws.com/mmaction/filelist/thumos14_tag_test_normalized_proposal_list.txt
Resolving open-mmlab.s3.ap-northeast-2.amazonaws.com (open-mmlab.s3.ap-northeast-2.amazonaws.com)... <IP_ADDRESS>
Connecting to open-mmlab.s3.ap-northeast-2.amazonaws.com (open-mmlab.s3.ap-northeast-2.amazonaws.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 403 Forbidden
2021-09-10 00:25:51 ERROR 403: Forbidden.

Thank you.

We haven't tried THUMOS14 dataset, you can refer to https://github.com/open-mmlab/mmaction2 for help


Broken crate on crates.io

fails to compile with stable 1.3, while directly from git works just fine

Yeah, I'm aware, the API is still not stable or complete enough to publish a new crate, so for the time being you'll have to use master.


Encapsulate away linear and sRGB conversions from Drawable and Container.

Not 100% sure if this makes things simpler or more complicated for the end user.

i think i prefer this.


Customizable Autoscaler

Motivation
When PAI is deployed on cloud, admins may want to stop some free nodes to save money. When a new job is submitted, the closed nodes can be started again to let the job fit in.
This feature is usually called "autoscaler", and was implemented in #4735 before.  However, #4735 only works on AKS. We can design an extensible autoscaler framework, which works in different cloud environment: e.g. Azure Virtual Machine Scale Set, or other cloud provider.

There are a few points in which this proposal and other low-level auto-scaling services differ

more customizable. Users could customize easily to let OpenPAI, an AI workload platform, to make decision when and which worker nodes to be scaled. Admins could write custom codes to enable trigger conditions such as observation of waiting jobs, virtual cluster utilization, and other high-level and end-to-end metrics.
a snip of codes that could easily support multiple types and hybrids cloud infrastructures.


Switch from "python" to "python3" exec

Switch python executions that are used to replace them with python3 instead, to follow PEP 394 recommendation.
Also, need to consider a more reliable way for Windows OS and test with macOS.

 🐞 [1.0.0-beta.4] Switch from "python" to "python3" exec

We make use of Pipenv and set the virtual env with pipenv --three, so there is no need to switch anything here as Leon runs already inside a virtual env when talking Python.


fix: don't allow bypassing ALLOW_REGISTRATION_WITHOUT_INVITE behaviour

Changes
This PR adds a new invite_hash field to the payload on the register endpoint to ensure that it's not possible to bypass the ALLOW_REGISTRATION_WITHOUT_INVITE setting.
Note: this will need to be added on the frontend. It's likely that the E2E tests will fail until that is done.
How did you test this code?
Added new tests and updated an existing test.

FE component has been merged and tested here


Fixed Timeout duration

duration.seconds was returning 0 if the time was a multiple of 60.
For example a timeout with a duration of 600 Seconds would result in a time of 0 seconds.

Oops, you're right, thanks!


Implement Completions Environment Heirarchy

Per conversation in spyder-ide/ux-improvements#10:

Implement a completions environment preference at both the document and project level.
The LSP server will use the first available environment in priority order: document, project, Spyder preferences.

Hi @mrclary,
I'm moving this issue to the ux-improvements repo so we can discuss it with all the team.
Thanks for reporting!


[#1881] Improvement: ConfigConstants.java updated as class and is not an interface

What changes were proposed in this pull request?
ConfigConstants updated as class and is not an interface
Why are the changes needed?
Fix: https://github.com/datastrato/gravitino/issues/1881
Does this PR introduce any user-facing change?
NO
How was this patch tested?
./gradlew build

Can you format your PR description? it appears that the markdown subtitle has been removed. The following is an example.

We use Spotless to make our code consistently formatted. Can you run ./gradlew :common:spotlessApply to fix this.

justinmclean

i did run it  ,but i believe @yuqi1129 comment was over PR description .

LGTM. thanks @ajayl83 for your work.


[2d] Support to run API test-cases created using RESTFiddle as part of Jenkins builds.

First dependency on defining test-cases issue #141 and then on issue #20


Updating rules to use File Traversal APIs.

disallowPaddingNewLinesBeforeKeywords: Now using File Traversal APIs
disallowPaddingNewLinesInObjects: Now using File Traversal APIs
disallowSpacesInsideParentheses: Now using File Traversal APIs
requireCamelcaseOrUppercaseIdentifiers: Now using File Traversal APIs
requirePaddingNewLinesBeforeKeywords: Now using File Traversal APIs
Finishes step 1 in auto format steps outlined in #516

Coverage increased (+0.0%) to 98.71% when pulling 22c8b38c73e5b952eb10a5428e0b87e732005c61 on TheSavior:fix/file-traversal into 38459ea13a12a235d8e16e321d5f4a6677fc504e on jscs-dev:master.

Thanks for contributing!

Closed? Or Merged and Closed? -_^ haha


Fix for missing interpolation argument :msg

I saw missing interpolation argument error when an import job failed.
Error:
Processing stopped at row 4 [Some system error has occurred [missing interpolation argument :msg in "Processing stopped at row %{row} [%{msg}]" ({row=>4} given].]
Solution:
Added a second parameter :msg => se.message to I18n.t() method call.

Thanks for the fix!  I got it in just before announcing my new! improved! plugin :-)

Thanks! Looking forward to the new plugin. This plugin has saved us
countless hours!  We also made a few changes to Agent and Subject fields.
Ended up modifying logic in ResourcesUpdatesController::process_subjects
and ResourcesUpdatesController::process_agents methods.
Chintan
On Thu, Mar 8, 2018 at 1:53 PM, Bobbi Fox at Harvard LTS <
<EMAIL_ADDRESS>wrote:

Thanks for the fix! I got it in just before announcing my new! improved!
plugin :-)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/harvard-library/aspace-import-excel/pull/23#issuecomment-371586285,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AMmDKvbGlSjvDWx5f-_7g4zXLrevnj5xks5tcX44gaJpZM4ShZmh
.

I'd be interested in seeing your changes (and the rationale for them) to the Agents & Subjects.  I think we're a little behind in the A&S stuff -- most of our EADs only have them associated at the Resource level.
Cheers,
Bobbi


On iOS, enterText() is unable to enter text, making test failed

Steps to reproduce

Minimal, reproducible example
void main() {
  patrolTest(
    'counter state is the same after going to home and switching apps',
    nativeAutomation: true,
    ($) async {
      await $.pumpWidgetAndSettle(
        MaterialApp(
          home: Scaffold(
            appBar: AppBar(title: const Text('app')),
            backgroundColor: Colors.blue,
            body: const SizedBox(
              height: 200,
              child: TextField(),
            ),
          ),
        ),
      );

      if (await native.isPermissionDialogVisible(
        timeout: const Duration(seconds: 2),
      )) {
        await native.grantPermissionWhenInUse();
      }

      await $(TextField).tap();
      await $(TextField).enterText('this is a test test');
      await Future.delayed(const Duration(seconds: 4));
      expect($(TextField).visible, findsOneWidget);
    },
  );
}

Actual results
No text was entered by the test. The test froze for a few seconds and failed.
Logs

Logs
patrol test -t integration_test --release -v
You're using Patrol CLI 2.0, which has breaking changes.
Read the migration guide at https://patrol.leancode.co/v2.
Disable this warning by setting the PATROL_MIGRATED environment variable.

Verbose mode enabled. More logs will be printed.
Received 1 test target(s)
Received test target: /Users/dangtuandat/Desktop/dev/zlp/mobile/integration_test/log_in_ui_test.dart
Generated entrypoint /Users/dangtuandat/Desktop/dev/zlp/mobile/integration_test/test_bundle.dart with 1 bundled test(s)
Received Android flavor: dev
Received iOS flavor: dev
$ flutter --no-version-check devices --machine
No device specified, using the first one (ダット)
Received 1 device(s) to run on
Received device: ダット
Received 7 --dart-define(s) (0 custom, 7 internal)
Received internal --dart-define: PATROL_WAIT=0
Received internal --dart-define: PATROL_APP_PACKAGE_NAME=com.my-bundle-id.dev
Received internal --dart-define: PATROL_APP_BUNDLE_ID=com.my-bundle-id.dev
Received internal --dart-define: PATROL_ANDROID_APP_NAME=P2P Dev
Received internal --dart-define: PATROL_IOS_APP_NAME=P2P Dev
Received internal --dart-define: INTEGRATION_TEST_SHOULD_REPORT_RESULTS_TO_NATIVE=false
Received internal --dart-define: PATROL_TEST_LABEL_ENABLED=true
• Building app with entrypoint test_bundle.dart for iOS device (release)...
$ flutter build ios --no-version-check --config-only --no-codesign --release --flavor dev --target /Users/dangtuandat/Desktop/dev/zlp/mobile/integration_test/test_bundle.dart --dart-define PATROL_WAIT=0 --dart-define PATROL_APP_PACKAGE_NAME=com.my-bundle-id.dev --dart-define PATROL_APP_BUNDLE_ID=com.my-bundle-id.dev --dart-define PATROL_ANDROID_APP_NAME=P2P Dev --dart-define PATROL_IOS_APP_NAME=P2P Dev --dart-define INTEGRATION_TEST_SHOULD_REPORT_RESULTS_TO_NATIVE=false --dart-define PATROL_TEST_LABEL_ENABLED=true
	Warning: Building for device with codesigning disabled. You will have to manually codesign before deploying to device.
	Building com.my-bundle-id.dev for device (ios-release)...
$ xcodebuild build-for-testing -workspace Runner.xcworkspace -scheme dev -configuration Release-dev -only-testing RunnerUITests -sdk iphoneos -destination generic/platform=iOS -quiet -derivedDataPath ../build/ios_integ OTHER_SWIFT_FLAGS=$(inherited) -D PATROL_ENABLED
	2023-07-10 14:10:15.187 xcodebuild[85141:828784] DVTCoreDeviceEnabledState: DVTCoreDeviceEnabledState_Disabled set via user default (DVTEnableCoreDevice=disabled)
	2023-07-10 14:10:15.344 xcodebuild[85141:828784] warning:  The file reference for "CleverTapSDK/ProductExperiences/CTVar.h" is a member of multiple groups ("CleverTap-iOS-SDK" and "CleverTap-iOS-SDK"); this indicates a malformed project.  Only the membership in one of the groups will be preserved (but membership in targets will be unaffected).  If you want a reference to the same file in more than one group, please add another reference to the same path.
	warning: The CFBundleVersion of an app extension ('1') must match that of its containing parent app ('43').
	error: the following command failed with exit code 0 but produced no further output
	ValidateEmbeddedBinary /Users/dangtuandat/Desktop/dev/zlp/mobile/build/ios_integ/Build/Products/Release-dev-iphoneos/Runner.app/PlugIns/content\ extension.appex (in target 'Runner' from project 'Runner')
	note: Building targets in dependency order
	warning: Skipping duplicate build file in Copy Headers build phase: /Users/dangtuandat/Desktop/dev/zlp/mobile/ios/Pods/CleverTap-iOS-SDK/CleverTapSDK/ProductExperiences/CTVar.h (in target 'CleverTap-iOS-SDK' from project 'Pods')
	warning: Run script build phase 'xcode_backend build' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'Runner' from project 'Runner')
	warning: Run script build phase 'Config env' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'Runner' from project 'Runner')
	note: Run script build phase 'Thin Binary' will be run during every build because the option to run the script phase "Based on dependency analysis" is unchecked. (in target 'Runner' from project 'Runner')
	warning: Run script build phase '[firebase_crashlytics] Crashlytics Upload Symbols' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'Runner' from project 'Runner')
	warning: Run script build phase 'xcode_backend build' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'RunnerUITests' from project 'Runner')
	warning: Run script build phase 'xcode_backend embed_and_thin' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'RunnerUITests' from project 'Runner')
✓ Completed building app with entrypoint test_bundle.dart for iOS device (85.3s)
• Running app with entrypoint test_bundle.dart for iOS device on device ダット...
$ xcodebuild -showsdks -json
Assuming SDK version 16.4 for iphonesimulator
Looking for .xctestrun matching dev_iphoneos16.4*.xctestrun at /Users/dangtuandat/Desktop/dev/zlp/mobile/build/ios_integ/Build/Products
Found 2 match(es), the first one will be used
Found /Users/dangtuandat/Desktop/dev/zlp/mobile/build/ios_integ/Build/Products/dev_iphoneos16.4-arm64.xctestrun
Found /Users/dangtuandat/Desktop/dev/zlp/mobile/build/ios_integ/Build/Products/dev_iphoneos16.4.xctestrun
$ xcodebuild test-without-building -xctestrun /Users/dangtuandat/Desktop/dev/zlp/mobile/build/ios_integ/Build/Products/dev_iphoneos16.4-arm64.xctestrun -only-testing RunnerUITests -destination platform=iOS,name=ダット
	2023-07-10 14:11:27.554 xcodebuild[88884:838761] DVTCoreDeviceEnabledState: DVTCoreDeviceEnabledState_Disabled set via user default (DVTEnableCoreDevice=disabled)
	Command line invocation:
	    /Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild test-without-building -xctestrun /Users/dangtuandat/Desktop/dev/zlp/mobile/build/ios_integ/Build/Products/dev_iphoneos16.4-arm64.xctestrun -only-testing RunnerUITests -destination platform=iOS,name=ダット

	User defaults from command line:
	    IDEPackageSupportUseBuiltinSCM = YES

	2023-07-10 14:11:36.490045+0700 RunnerUITests-Runner[45738:4530713] Running tests...
	2023-07-10 14:11:37.417968+0700 RunnerUITests-Runner[45738:4530713] PatrolServer: INFO: PATROL_PORT is null, falling back to default (8081)
	2023-07-10 14:11:37.418108+0700 RunnerUITests-Runner[45738:4530713] PatrolServer: INFO: PatrolServer constructor called
	2023-07-10 14:11:37.418153+0700 RunnerUITests-Runner[45738:4530713] PatrolServer: INFO: PATROL_ENABLED flag is defined
	2023-07-10 14:11:37.418245+0700 RunnerUITests-Runner[45738:4530713] PatrolAppServiceClient: created, port: 8082
	2023-07-10 14:11:37.426774+0700 RunnerUITests-Runner[45738:4530944] [si_destination_compare] send failed: Invalid argument
	2023-07-10 14:11:37.427033+0700 RunnerUITests-Runner[45738:4530944] [si_destination_compare] send failed: Undefined error: 0
	2023-07-10 14:11:37.466012+0700 RunnerUITests-Runner[45738:4530987] PatrolServer: INFO: Server started on http://localhost:8081
	    t =      nans Checking existence of `"Allow" Button`
	    t =      nans Ignoring failure to get hierarchy for remote element in process 19001 (Error getting main window kAXErrorServerNotFound)
	    t =      nans Open com.my-bundle-id.dev
	    t =      nans     Launch com.my-bundle-id.dev
	2023-07-10 14:11:37.904988+0700 RunnerUITests-Runner[45738:4530713] [TraitCollection] Class CKBrowserSwitcherViewController overrides the -traitCollection getter, which is not supported. If you're trying to override traits, you must use the appropriate API.
	    t =      nans         Setting up automation session
	    t =      nans         Wait for com.my-bundle-id.dev to idle
	2023-07-10 14:11:48.261664+0700 RunnerUITests-Runner[45738:4530986] PatrolServer: INFO: App reported that it is ready
	2023-07-10 14:11:49.230130+0700 RunnerUITests-Runner[45738:4530986] PatrolAppServiceClient.listDartTests()
	2023-07-10 14:11:50.236256+0700 RunnerUITests-Runner[45738:4530713] Got 1 Dart tests: (
	    "log_in_ui_test"
	)
	2023-07-10 14:11:50.238582+0700 RunnerUITests-Runner[45738:4530713] RunnerUITests.testInvocations(): selectorName = logInUiTest, signature: <NSMethodSignature: 0x950f403f69d6ad07>
	Test Suite 'All tests' started at 2023-07-10 14:11:50.243
	Test Suite 'RunnerUITests.xctest' started at 2023-07-10 14:11:50.247
	Test Suite 'RunnerUITests' started at 2023-07-10 14:11:50.248
	Test Case '-[RunnerUITests logInUiTest]' started.
	    t =     0.00s Start Test at 2023-07-10 14:11:50.251
	    t =     0.12s Set Up
	    t =     0.12s Open com.my-bundle-id.dev
	    t =     0.22s     Launch com.my-bundle-id.dev
	    t =     0.22s         Terminate com.my-bundle-id.dev:45740
	    t =     1.84s         Setting up automation session
	    t =     1.89s         Wait for com.my-bundle-id.dev to idle
	2023-07-10 14:11:52.146804+0700 RunnerUITests-Runner[45738:4530945] PatrolServer: INFO: App reported that it is ready
	2023-07-10 14:11:53.255968+0700 RunnerUITests-Runner[45738:4530986] PatrolAppServiceClient.runDartTest(log_in_ui_test)
	2023-07-10 14:11:53.439497+0700 RunnerUITests-Runner[45738:4530713] PatrolServer: INFO: checking if permission dialog is visible...
	    t =     3.19s Checking existence of `"OK" Button`
	    t =     3.28s Ignoring failure to get hierarchy for remote element in process 19001 (Error getting main window kAXErrorServerNotFound)
	    t =     3.29s Checking existence of `"Allow" Button`
	    t =     3.34s Ignoring failure to get hierarchy for remote element in process 19001 (Error getting main window kAXErrorServerNotFound)
	2023-07-10 14:11:53.601462+0700 RunnerUITests-Runner[45738:4530713] PatrolServer: INFO: done checking if permission dialog is visible
	2023-07-10 14:11:53.602149+0700 RunnerUITests-Runner[45738:4530713] PatrolServer: INFO: result: true
	2023-07-10 14:11:53.605253+0700 RunnerUITests-Runner[45738:4530713] PatrolServer: INFO: allowing while using app...
	    t =     3.36s Checking existence of `"OK" Button`
	    t =     3.39s Ignoring failure to get hierarchy for remote element in process 19001 (Error getting main window kAXErrorServerNotFound)
	    t =     3.40s Checking existence of `"Allow" Button`
	    t =     3.44s Ignoring failure to get hierarchy for remote element in process 19001 (Error getting main window kAXErrorServerNotFound)
	    t =     3.45s Tap "Allow" Button
	    t =     3.45s     Wait for com.apple.springboard to idle
	    t =     3.56s     Find the "Allow" Button
	    t =     3.61s Ignoring failure to get hierarchy for remote element in process 19001 (Error getting main window kAXErrorServerNotFound)
	    t =     3.61s     Check for interrupting elements affecting "Allow" Button
	    t =     3.65s Ignoring failure to get hierarchy for remote element in process 19001 (Error getting main window kAXErrorServerNotFound)
	    t =     3.66s     Synthesize event
	    t =     4.06s     Wait for com.apple.springboard to idle
	2023-07-10 14:11:54.528888+0700 RunnerUITests-Runner[45738:4530713] PatrolServer: INFO: done allowing while using app
	2023-07-10 14:11:54.532101+0700 RunnerUITests-Runner[45738:4530713] PatrolServer: INFO: result: ()
	/Users/dangtuandat/Desktop/dev/zlp/mobile/ios/RunnerUITests/RunnerUITests.m:5: error: -[RunnerUITests logInUiTest] : ((response.passed) is true) failed
	    t =    11.50s Tear Down
	Test Case '-[RunnerUITests logInUiTest]' failed (11.707 seconds).
	Test Suite 'RunnerUITests' failed at 2023-07-10 14:12:01.958.
		 Executed 1 test, with 1 failure (0 unexpected) in 11.707 (11.710) seconds
	Test Suite 'RunnerUITests.xctest' failed at 2023-07-10 14:12:01.961.
		 Executed 1 test, with 1 failure (0 unexpected) in 11.707 (11.714) seconds
	Test Suite 'All tests' failed at 2023-07-10 14:12:01.963.
		 Executed 1 test, with 1 failure (0 unexpected) in 11.707 (11.720) seconds
	2023-07-10 14:12:02.045 xcodebuild[88884:838761] [MT] IDETestOperationsObserverDebug: 33.134 elapsed -- Testing started completed.
	2023-07-10 14:12:02.045 xcodebuild[88884:838761] [MT] IDETestOperationsObserverDebug: 0.000 sec, +0.000 sec -- start
	2023-07-10 14:12:02.046 xcodebuild[88884:838761] [MT] IDETestOperationsObserverDebug: 33.134 sec, +33.134 sec -- end
	2023-07-10 14:12:02.127 xcodebuild[88884:838761] [MT] IDEResultKit: Warning: While writing a result bundle to /Users/dangtuandat/Library/Developer/Xcode/DerivedData/Runner-ewrcfahvjsfftmdtsllwovfajnzy/Logs/Test/Test-dev-2023.07.10_14-11-28-+0700.xcresult, not all contents have been imported, as the Staging directory still contains the following files/directories: ["1_Test"]

	Test session results, code coverage, and logs:
		/Users/dangtuandat/Library/Developer/Xcode/DerivedData/Runner-ewrcfahvjsfftmdtsllwovfajnzy/Logs/Test/Test-dev-2023.07.10_14-11-28-+0700.xcresult

	Failing tests:
		-[RunnerUITests logInUiTest]

	** TEST EXECUTE FAILED **

	Testing started
✗ Failed to execute tests of app with entrypoint test_bundle.dart for iOS device on device ダット (xcodebuild exited with code 65) (35.5s)
Error: xcodebuild exited with code 65
#0      throwToolExit (package:patrol_cli/src/base/exceptions.dart:7:3)
#1      IOSTestBackend.execute.<anonymous closure> (package:patrol_cli/src/ios/ios_test_backend.dart:177:9)
<asynchronous suspension>
#2      DisposeScope.run (package:dispose_scope/src/dispose_scope.dart:46:7)
<asynchronous suspension>
#3      IOSTestBackend.execute (package:patrol_cli/src/ios/ios_test_backend.dart:143:5)
<asynchronous suspension>
#4      TestCommand._execute (package:patrol_cli/src/commands/test.dart:232:7)
<asynchronous suspension>
#5      TestCommand.run (package:patrol_cli/src/commands/test.dart:168:23)
<asynchronous suspension>
#6      CommandRunner.runCommand (package:args/command_runner.dart:212:13)
<asynchronous suspension>
#7      PatrolCommandRunner.runCommand (package:patrol_cli/src/runner/patrol_command_runner.dart:310:18)
<asynchronous suspension>
#8      PatrolCommandRunner.run (package:patrol_cli/src/runner/patrol_command_runner.dart:254:18)
<asynchronous suspension>
#9      patrolCommandRunner (package:patrol_cli/src/runner/patrol_command_runner.dart:72:20)
<asynchronous suspension>
#10     main (file:///Users/dangtuandat/.pub-cache/hosted/pub.dev/patrol_cli-2.0.1/bin/main.dart:6:20)
<asynchronous suspension>

See the logs above to learn what happened. Also consider running with --verbose. If the logs still aren't useful, then it's a bug - please report it.
$ ideviceinstaller --udid 00008030-000210A43E09802E --uninstall com.my-bundle-id.dev
$ ideviceinstaller --udid 00008030-000210A43E09802E --uninstall com.my-bundle-id.dev.RunnerUITests.xctrunner

Patrol version
patrol: ^2.0.0
Patrol Doctor output

Patrol Doctor output
You're using Patrol CLI 2.0, which has breaking changes.
Read the migration guide at https://patrol.leancode.co/v2.
Disable this warning by setting the PATROL_MIGRATED environment variable.

Patrol CLI version: 2.0.1
Program adb found in /opt/homebrew/bin/adb
Env var $ANDROID_HOME set to /Users/dangtuandat/Library/Android/sdk
Program xcodebuild found in /usr/bin/xcodebuild
Program ideviceinstaller found in /opt/homebrew/bin/ideviceinstaller

Flutter Doctor output

Flutter Doctor output
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.10.5, on macOS 13.4.1 22F82 darwin-arm64, locale en-VN)
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 14.3.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2022.1)
[✓] VS Code (version 1.80.0)
[✓] Connected device (3 available)
[✓] Network resources

• No issues found!

Hi @datdang1995,
The problem lies in this line:
expect($(TextField).visible, findsOneWidget);

$(TextField).visible returns a bool, but findsOneWidget expects a Finder.
Here's a fixed version of your test that passes:
void main() {
  patrolTest(
    'counter state is the same after going to home and switching apps',
    nativeAutomation: true,
    ($) async {
      await $.pumpWidgetAndSettle(
        MaterialApp(
          home: Scaffold(
            appBar: AppBar(title: const Text('app')),
            backgroundColor: Colors.blue,
            body: const SizedBox(
              height: 200,
              child: TextField(),
            ),
          ),
        ),
      );

      if (await $.native.isPermissionDialogVisible(
        timeout: const Duration(seconds: 2),
      )) {
        await $.native.grantPermissionWhenInUse();
      }

      await $(TextField).tap();
      await $(TextField).enterText('this is a test test');
      await Future.delayed(const Duration(seconds: 4));
      expect($(TextField).visible, true);
    },
  );
}

Could you please share the video? Also, it'd help if the TextField was more visible, instead of blue everywhere :D

Oh now it works :D sorry for the trouble. It's kinda related to this issue so I'll ask it here. If you find the question unrelated and should be included in a new issue then feel free to close this. While the test passed, the text still wasn't visible in the TextField. Is it expected behavior from my example code snippet or potentially a bug?

While the test passed, the text still wasn't visible in the TextField.

That's very strange. Again, a video would help a lot.
This might be a bug.

Right this is the screen record of that test. I modified the UI a bit compare to the original, but it should still reflect the same result.

Modified test code:
void main() {
  patrolTest(
    'counter state is the same after going to home and switching apps',
    nativeAutomation: true,
    ($) async {
      await $.pumpWidgetAndSettle(
        MaterialApp(
          home: Scaffold(
            appBar: AppBar(title: const Text('app')),
            backgroundColor: Colors.blueAccent,
            body: const Center(
              child: SizedBox(
                height: 200,
                child: TextField(
                  decoration: InputDecoration(
                    fillColor: Colors.white,
                    filled: true,
                  ),
                ),
              ),
            ),
          ),
        ),
      );

      if (await $.native.isPermissionDialogVisible(
        timeout: const Duration(seconds: 2),
      )) {
        await $.native.grantPermissionWhenInUse();
      }

      await $(TextField).tap();
      await $(TextField).enterText('this is a test test');
      await Future.delayed(const Duration(seconds: 4));
      expect($(TextField).visible, true);
    },
  );
}

Well, that's strange indeed.
We have a test that tests entering input in our example app - I recommend you to clone it and run locally, and then compare our implementation with yours.

Sure let me try out the example in patrol's repo

@bartekpacia the test inside example_test.dart worked fine as is. However, as soon as I added dart await $(#textField).tap(); on line 13, the text wasn't get inputted into the TextField, AND that test failed.

The logs that failed
patrol test --release -t integration_test/example_test.dart -v
You're using Patrol CLI 2.0, which has breaking changes.
Read the migration guide at https://patrol.leancode.co/v2.
Disable this warning by setting the PATROL_MIGRATED environment variable.

Verbose mode enabled. More logs will be printed.
Received 1 test target(s)
Received test target: /Users/dangtuandat/Desktop/dev/patrol/packages/patrol/example/integration_test/example_test.dart
Generated entrypoint /Users/dangtuandat/Desktop/dev/patrol/packages/patrol/example/integration_test/test_bundle.dart with 1 bundled test(s)
$ flutter --no-version-check devices --machine
No device specified, using the first one (ダット)
Received 1 device(s) to run on
Received device: ダット
Received 7 --dart-define(s) (0 custom, 7 internal)
Received internal --dart-define: PATROL_WAIT=0
Received internal --dart-define: PATROL_APP_PACKAGE_NAME=pl.leancode.patrol.example
Received internal --dart-define: PATROL_APP_BUNDLE_ID=myBundleId
Received internal --dart-define: PATROL_ANDROID_APP_NAME=Patrol example
Received internal --dart-define: PATROL_IOS_APP_NAME=Patrol example
Received internal --dart-define: INTEGRATION_TEST_SHOULD_REPORT_RESULTS_TO_NATIVE=false
Received internal --dart-define: PATROL_TEST_LABEL_ENABLED=true
• Building app with entrypoint test_bundle.dart for iOS device (release)...
$ flutter build ios --no-version-check --config-only --no-codesign --release --target /Users/dangtuandat/Desktop/dev/patrol/packages/patrol/example/integration_test/test_bundle.dart --dart-define PATROL_WAIT=0 --dart-define PATROL_APP_PACKAGE_NAME=pl.leancode.patrol.example --dart-define PATROL_APP_BUNDLE_ID=myBundleId--dart-define PATROL_ANDROID_APP_NAME=Patrol example --dart-define PATROL_IOS_APP_NAME=Patrol example --dart-define INTEGRATION_TEST_SHOULD_REPORT_RESULTS_TO_NATIVE=false --dart-define PATROL_TEST_LABEL_ENABLED=true
	Warning: Building for device with codesigning disabled. You will have to manually codesign before deploying to device.
	Building myBundleId for device (ios-release)...
$ xcodebuild build-for-testing -workspace Runner.xcworkspace -scheme Runner -configuration Release -only-testing RunnerUITests -sdk iphoneos -destination generic/platform=iOS -quiet -derivedDataPath ../build/ios_integ OTHER_SWIFT_FLAGS=$(inherited) -D PATROL_ENABLED
	2023-07-10 20:23:40.431 xcodebuild[36106:1476114] DVTCoreDeviceEnabledState: DVTCoreDeviceEnabledState_Disabled set via user default (DVTEnableCoreDevice=disabled)
	note: Building targets in dependency order
	warning: Run script build phase 'xcode_backend build' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'Runner' from project 'Runner')
	warning: Run script build phase 'xcode_backend embed_and_thin' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'Runner' from project 'Runner')
	warning: Run script build phase 'xcode_backend build' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'RunnerUITests' from project 'Runner')
	warning: Run script build phase 'xcode_backend embed_and_thin' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'RunnerUITests' from project 'Runner')
✓ Completed building app with entrypoint test_bundle.dart for iOS device (73.3s)
• Running app with entrypoint test_bundle.dart for iOS device on device ダット...
$ xcodebuild -showsdks -json
Assuming SDK version 16.4 for iphonesimulator
Looking for .xctestrun matching Runner_iphoneos16.4*.xctestrun at /Users/dangtuandat/Desktop/dev/patrol/packages/patrol/example/build/ios_integ/Build/Products
Found 1 match(es), the first one will be used
Found /Users/dangtuandat/Desktop/dev/patrol/packages/patrol/example/build/ios_integ/Build/Products/Runner_iphoneos16.4-arm64.xctestrun
$ xcodebuild test-without-building -xctestrun /Users/dangtuandat/Desktop/dev/patrol/packages/patrol/example/build/ios_integ/Build/Products/Runner_iphoneos16.4-arm64.xctestrun -only-testing RunnerUITests -destination platform=iOS,name=ダット
	2023-07-10 20:24:44.940 xcodebuild[37883:1481721] DVTCoreDeviceEnabledState: DVTCoreDeviceEnabledState_Disabled set via user default (DVTEnableCoreDevice=disabled)
	Command line invocation:
	    /Applications/Xcode.app/Contents/Developer/usr/bin/xcodebuild test-without-building -xctestrun /Users/dangtuandat/Desktop/dev/patrol/packages/patrol/example/build/ios_integ/Build/Products/Runner_iphoneos16.4-arm64.xctestrun -only-testing RunnerUITests -destination platform=iOS,name=ダット

	User defaults from command line:
	    IDEPackageSupportUseBuiltinSCM = YES

	2023-07-10 20:24:51.646646+0700 RunnerUITests-Runner[48357:4716244] Running tests...
	2023-07-10 20:24:52.015922+0700 RunnerUITests-Runner[48357:4716244] PatrolServer: INFO: PATROL_PORT is null, falling back to default (8081)
	2023-07-10 20:24:52.016032+0700 RunnerUITests-Runner[48357:4716244] PatrolServer: INFO: PatrolServer constructor called
	2023-07-10 20:24:52.016061+0700 RunnerUITests-Runner[48357:4716244] PatrolServer: INFO: PATROL_ENABLED flag is defined
	2023-07-10 20:24:52.016137+0700 RunnerUITests-Runner[48357:4716244] PatrolAppServiceClient: created, port: 8082
	2023-07-10 20:24:52.027100+0700 RunnerUITests-Runner[48357:4716490] [si_destination_compare] send failed: Invalid argument
	2023-07-10 20:24:52.027136+0700 RunnerUITests-Runner[48357:4716490] [si_destination_compare] send failed: Undefined error: 0
	2023-07-10 20:24:52.031616+0700 RunnerUITests-Runner[48357:4716487] PatrolServer: INFO: Server started on http://localhost:8081
	    t =      nans Checking existence of `"Allow" Button`
	    t =      nans Ignoring failure to get hierarchy for remote element in process 19001 (Error getting main window kAXErrorServerNotFound)
	    t =      nans Open myBundleId
	    t =      nans     Launch myBundleId
	    t =      nans         Setting up automation session
	    t =      nans         Wait for myBundleId to idle
	2023-07-10 20:24:58.063463+0700 RunnerUITests-Runner[48357:4716491] PatrolServer: INFO: App reported that it is ready
	2023-07-10 20:24:59.058477+0700 RunnerUITests-Runner[48357:4716491] PatrolAppServiceClient.listDartTests()
	2023-07-10 20:25:00.062426+0700 RunnerUITests-Runner[48357:4716244] Got 1 Dart tests: (
	    "example_test"
	)
	2023-07-10 20:25:00.064587+0700 RunnerUITests-Runner[48357:4716244] RunnerUITests.testInvocations(): selectorName = exampleTest, signature: <NSMethodSignature: 0x87901f1d4738a47f>
	Test Suite 'All tests' started at 2023-07-10 20:25:00.070
	Test Suite 'RunnerUITests.xctest' started at 2023-07-10 20:25:00.072
	Test Suite 'RunnerUITests' started at 2023-07-10 20:25:00.075
	Test Case '-[RunnerUITests exampleTest]' started.
	    t =     0.00s Start Test at 2023-07-10 20:25:00.077
	    t =     0.12s Set Up
	    t =     0.12s Open myBundleId
	    t =     0.21s     Launch myBundleId
	    t =     0.21s         Terminate myBundleId:48358
	2023-07-10 20:25:01.860943+0700 RunnerUITests-Runner[48357:4716491] PatrolServer: INFO: App reported that it is ready
	    t =     1.79s         Setting up automation session
	    t =     1.80s         Wait for myBundleId to idle
	2023-07-10 20:25:03.018334+0700 RunnerUITests-Runner[48357:4716488] PatrolAppServiceClient.runDartTest(example_test)
	/Users/dangtuandat/Desktop/dev/patrol/packages/patrol/example/ios/RunnerUITests/RunnerUITests.m:5: error: -[RunnerUITests exampleTest] : ((response.passed) is true) failed
	    t =     6.13s Tear Down
	Test Case '-[RunnerUITests exampleTest]' failed (6.337 seconds).
	Test Suite 'RunnerUITests' failed at 2023-07-10 20:25:06.414.
		 Executed 1 test, with 1 failure (0 unexpected) in 6.337 (6.339) seconds
	Test Suite 'RunnerUITests.xctest' failed at 2023-07-10 20:25:06.416.
		 Executed 1 test, with 1 failure (0 unexpected) in 6.337 (6.343) seconds
	Test Suite 'All tests' failed at 2023-07-10 20:25:06.419.
		 Executed 1 test, with 1 failure (0 unexpected) in 6.337 (6.349) seconds
	2023-07-10 20:25:06.432 xcodebuild[37883:1481721] [MT] IDETestOperationsObserverDebug: 20.147 elapsed -- Testing started completed.
	2023-07-10 20:25:06.432 xcodebuild[37883:1481721] [MT] IDETestOperationsObserverDebug: 0.000 sec, +0.000 sec -- start
	2023-07-10 20:25:06.433 xcodebuild[37883:1481721] [MT] IDETestOperationsObserverDebug: 20.147 sec, +20.147 sec -- end
	2023-07-10 20:25:06.505 xcodebuild[37883:1481721] [MT] IDEResultKit: Warning: While writing a result bundle to /Users/dangtuandat/Library/Developer/Xcode/DerivedData/Runner-cdljmaezpnkshlguhbhnzhcvfjoi/Logs/Test/Test-Runner-2023.07.10_20-24-46-+0700.xcresult, not all contents have been imported, as the Staging directory still contains the following files/directories: ["1_Test"]

	Test session results, code coverage, and logs:
		/Users/dangtuandat/Library/Developer/Xcode/DerivedData/Runner-cdljmaezpnkshlguhbhnzhcvfjoi/Logs/Test/Test-Runner-2023.07.10_20-24-46-+0700.xcresult

	Failing tests:
		-[RunnerUITests exampleTest]

	** TEST EXECUTE FAILED **

	Testing started
✗ Failed to execute tests of app with entrypoint test_bundle.dart for iOS device on device ダット (xcodebuild exited with code 65) (22.5s)
Error: xcodebuild exited with code 65
#0      throwToolExit (package:patrol_cli/src/base/exceptions.dart:7:3)
#1      IOSTestBackend.execute.<anonymous closure> (package:patrol_cli/src/ios/ios_test_backend.dart:181:9)
<asynchronous suspension>
#2      DisposeScope.run (package:dispose_scope/src/dispose_scope.dart:46:7)
<asynchronous suspension>
#3      IOSTestBackend.execute (package:patrol_cli/src/ios/ios_test_backend.dart:147:5)
<asynchronous suspension>
#4      TestCommand._execute (package:patrol_cli/src/commands/test.dart:232:7)
<asynchronous suspension>
#5      TestCommand.run (package:patrol_cli/src/commands/test.dart:168:23)
<asynchronous suspension>
#6      CommandRunner.runCommand (package:args/command_runner.dart:212:13)
<asynchronous suspension>
#7      PatrolCommandRunner.runCommand (package:patrol_cli/src/runner/patrol_command_runner.dart:310:18)
<asynchronous suspension>
#8      PatrolCommandRunner.run (package:patrol_cli/src/runner/patrol_command_runner.dart:254:18)
<asynchronous suspension>
#9      patrolCommandRunner (package:patrol_cli/src/runner/patrol_command_runner.dart:72:20)
<asynchronous suspension>
#10     main (file:///Users/dangtuandat/.pub-cache/hosted/pub.dev/patrol_cli-2.0.2/bin/main.dart:6:20)
<asynchronous suspension>

See the logs above to learn what happened. Also consider running with --verbose. If the logs still aren't useful, then it's a bug - please report it.
$ ideviceinstaller --udid 00008030-000210A43E09802E --uninstall myBundleId
$ ideviceinstaller --udid 00008030-000210A43E09802E --uninstall myBundleId.RunnerUITests.xctrunner

Why is it needed at all?

Because our UI & integration testing involve the appearance of the system keyboard, as user cannot type anything until the keyboard comes up, and several buttons are also hidden under the keyboard. I will do a quick test with pure flutter_integration to see if it already occurs on Flutter side.

Reading this now again, it looks like the original issue was solved.
To continue a discussion about that other problem, please create a new issue with all the required information provided, including a minimal, reproducible sample.


Roll all logs by default

Issue
#1372
TODO

[ ] rip out nested block parsing
[x] add new subdirectives + share between logging middleware
[x] set defaults to rotate logs
[ ] update docs

work in progress!

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

Ok, looks like this implements the desired behavior for default rolling logs config.
# old
log ... {
    rotate {
        size maxsize
        age maxage
        keep maxkeep
    }
}

# new
log ... {
    rotate_size maxsize
    rotate_age maxage
    rotate_keep maxkeep
}

# old
errors {
    log error.log {
      rotate_size maxsize
      rotate_age maxage
      rotate_keep maxkeep
    }
}

# new
errors {
    log error.log {
      rotate_size maxsize
      rotate_age maxage
      rotate_keep maxkeep
    }
}

Does this PR do enough to rip out the original nested block parsing for log?
The log directive was flattened by removing the rotate subdirective, but c.IncrNest() seems like it's still the best option for parsing both the log and errors directives.
See here: https://github.com/mholt/caddy/pull/1379/files#diff-b44dbfe18c42f72684e2df145fae3da9L92

Thanks for starting on this!
Let's flatten this:
errors {
    log ... {
      rotate_size maxsize
      rotate_age maxage
      rotate_keep maxkeep
    }
}

down to this:
errors {
      rotate_size maxsize
      rotate_age maxage
      rotate_keep maxkeep
}

We can get rid of the whole IncrNest() function I think, since nesting isn't really a thing without this; it won't be needed.

Got it, flattened + removed IncrNest()

Nice work :+1: Thanks. I'm away for a week but will get back to this ASAP!

Hm, anything I should do to fix the AppVeyor build?

That's weird. GitHub bug? It definitely passed: https://ci.appveyor.com/project/mholt/caddy/build/2195
I'll merge it in soon. :) I'm at school for a bit.

@julianvmodesto Can you resolve the merge conflicts?
And before I merge, have you verified that there is/are test cases to ensure logs are rolled by default and the default configuration is properly overwritten when specified?

Conflicts resolved!
Yes – examples of test cases for the default + overrides are here:

Error log default

directive: errors errors.txt
test case

Error log with rotation specified

directive: errors errors.txt { rotate_size 2 rotate_age 10 rotate_keep 3 }
test case

Log default

directive: log
test case

Log with rotation specified

directive: log access.log { rotate_size 2 rotate_age 10 rotate_keep 3 }
test case

Great work! Thanks @julianvmodesto. I'll merge this now and invite you to be a collaborator to the project so you can help by reviewing PRs, merging accepted ones, and contributing fixes on branches instead of forks. Really appreciate your contribution!

IncrNest was removed from Controller which breaks caddy filter building :(