Synthesis failed for HomeGraph

Hello! Autosynth couldn't regenerate HomeGraph. :broken_heart:
Here's the output from running synth.py:
2020-06-06 06:03:43,408 autosynth [INFO] > logs will be written to: /tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api
2020-06-06 06:03:43,851 autosynth [DEBUG] > Running: git config --global core.excludesfile /home/kbuilder/.autosynth-gitignore
2020-06-06 06:03:43,853 autosynth [DEBUG] > Running: git config user.name yoshi-automation
2020-06-06 06:03:43,856 autosynth [DEBUG] > Running: git config user.email<EMAIL_ADDRESS>2020-06-06 06:03:43,859 autosynth [DEBUG] > Running: git config push.default simple
2020-06-06 06:03:43,861 autosynth [DEBUG] > Running: git branch -f autosynth-homegraph
2020-06-06 06:03:43,865 autosynth [DEBUG] > Running: git checkout autosynth-homegraph
Switched to branch 'autosynth-homegraph'
2020-06-06 06:03:44,088 autosynth [INFO] > Running synthtool
2020-06-06 06:03:44,088 autosynth [INFO] > ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/home_graph/synth.metadata', 'synth.py', '--']
2020-06-06 06:03:44,090 autosynth [DEBUG] > Running: /tmpfs/src/github/synthtool/env/bin/python3 -m synthtool --metadata clients/home_graph/synth.metadata synth.py -- HomeGraph
tee: /tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api: Is a directory
2020-06-06 06:03:44,320 synthtool [DEBUG] > Executing /home/kbuilder/.cache/synthtool/elixir-google-api/synth.py.
On branch autosynth-homegraph
nothing to commit, working tree clean
2020-06-06 06:03:46,225 synthtool [DEBUG] > Running: docker run --rm -v/tmpfs/tmp/tmpbc2wogdc/repo:/workspace -v/var/run/docker.sock:/var/run/docker.sock -e USER_GROUP=1000:1000 -w /workspace gcr.io/cloud-devrel-public-resources/elixir19 scripts/generate_client.sh HomeGraph
DEBUG:synthtool:Running: docker run --rm -v/tmpfs/tmp/tmpbc2wogdc/repo:/workspace -v/var/run/docker.sock:/var/run/docker.sock -e USER_GROUP=1000:1000 -w /workspace gcr.io/cloud-devrel-public-resources/elixir19 scripts/generate_client.sh HomeGraph
/workspace /workspace
The mix.lock file was generated with a newer version of Hex. Update your client by running `mix local.hex` to avoid losing data.
Resolving Hex dependencies...
Dependency resolution completed:
Unchanged:
  certifi 2.5.1
  google_api_discovery 0.7.0
  google_gax 0.3.2
  hackney 1.15.2
  idna 6.0.0
  jason 1.2.1
  metrics 1.0.1
  mime 1.3.1
  mimerl 1.2.0
  oauth2 0.9.4
  parse_trans 3.3.0
  poison 3.1.0
  ssl_verify_fun 1.1.5
  temp 0.4.7
  tesla 1.3.3
  unicode_util_compat 0.4.1
* Getting google_api_discovery (Hex package)
* Getting tesla (Hex package)
* Getting oauth2 (Hex package)
* Getting temp (Hex package)
* Getting jason (Hex package)
* Getting poison (Hex package)
* Getting hackney (Hex package)
* Getting certifi (Hex package)
* Getting idna (Hex package)
* Getting metrics (Hex package)
* Getting mimerl (Hex package)
* Getting ssl_verify_fun (Hex package)
* Getting unicode_util_compat (Hex package)
* Getting parse_trans (Hex package)
* Getting mime (Hex package)
* Getting google_gax (Hex package)
The mix.lock file was generated with a newer version of Hex. Update your client by running `mix local.hex` to avoid losing data.
==> temp
Compiling 3 files (.ex)
Generated temp app
===> Compiling parse_trans
===> Compiling mimerl
===> Compiling metrics
===> Compiling unicode_util_compat
===> Compiling idna
==> jason
Compiling 8 files (.ex)
Generated jason app
warning: String.strip/1 is deprecated. Use String.trim/1 instead
  /workspace/deps/poison/mix.exs:4

==> poison
Compiling 4 files (.ex)
warning: Integer.to_char_list/2 is deprecated. Use Integer.to_charlist/2 instead
  lib/poison/encoder.ex:173

Generated poison app
==> ssl_verify_fun
Compiling 7 files (.erl)
Generated ssl_verify_fun app
===> Compiling certifi
===> Compiling hackney
==> oauth2
Compiling 13 files (.ex)
Generated oauth2 app
==> mime
Compiling 2 files (.ex)
Generated mime app
==> tesla
Compiling 26 files (.ex)
Generated tesla app
==> google_gax
Compiling 5 files (.ex)
Generated google_gax app
==> google_api_discovery
Compiling 21 files (.ex)
Generated google_api_discovery app
==> google_apis
Compiling 27 files (.ex)
warning: System.cwd/0 is deprecated. Use File.cwd/0 instead
  lib/google_apis/publisher.ex:24

Generated google_apis app

13:04:19.002 [info]  FETCHING: https://homegraph.googleapis.com/$discovery/GOOGLE_REST_SIMPLE_URI?version=v1

13:04:19.180 [info]  FOUND: https://homegraph.googleapis.com/$discovery/GOOGLE_REST_SIMPLE_URI?version=v1
Revision check: old=20200504, new=20200529, generating=true
Creating leading directories
Writing AgentDeviceId to clients/home_graph/lib/google_api/home_graph/v1/model/agent_device_id.ex.
Writing AgentOtherDeviceId to clients/home_graph/lib/google_api/home_graph/v1/model/agent_other_device_id.ex.
Writing Device to clients/home_graph/lib/google_api/home_graph/v1/model/device.ex.
Writing DeviceInfo to clients/home_graph/lib/google_api/home_graph/v1/model/device_info.ex.
Writing DeviceNames to clients/home_graph/lib/google_api/home_graph/v1/model/device_names.ex.
Writing Empty to clients/home_graph/lib/google_api/home_graph/v1/model/empty.ex.
Writing QueryRequest to clients/home_graph/lib/google_api/home_graph/v1/model/query_request.ex.
Writing QueryRequestInput to clients/home_graph/lib/google_api/home_graph/v1/model/query_request_input.ex.
Writing QueryRequestPayload to clients/home_graph/lib/google_api/home_graph/v1/model/query_request_payload.ex.
Writing QueryResponse to clients/home_graph/lib/google_api/home_graph/v1/model/query_response.ex.
Writing QueryResponsePayload to clients/home_graph/lib/google_api/home_graph/v1/model/query_response_payload.ex.
Writing ReportStateAndNotificationDevice to clients/home_graph/lib/google_api/home_graph/v1/model/report_state_and_notification_device.ex.
Writing ReportStateAndNotificationRequest to clients/home_graph/lib/google_api/home_graph/v1/model/report_state_and_notification_request.ex.
Writing ReportStateAndNotificationResponse to clients/home_graph/lib/google_api/home_graph/v1/model/report_state_and_notification_response.ex.
Writing RequestSyncDevicesRequest to clients/home_graph/lib/google_api/home_graph/v1/model/request_sync_devices_request.ex.
Writing RequestSyncDevicesResponse to clients/home_graph/lib/google_api/home_graph/v1/model/request_sync_devices_response.ex.
Writing StateAndNotificationPayload to clients/home_graph/lib/google_api/home_graph/v1/model/state_and_notification_payload.ex.
Writing SyncRequest to clients/home_graph/lib/google_api/home_graph/v1/model/sync_request.ex.
Writing SyncResponse to clients/home_graph/lib/google_api/home_graph/v1/model/sync_response.ex.
Writing SyncResponsePayload to clients/home_graph/lib/google_api/home_graph/v1/model/sync_response_payload.ex.
Writing AgentUsers to clients/home_graph/lib/google_api/home_graph/v1/api/agent_users.ex.
Writing Devices to clients/home_graph/lib/google_api/home_graph/v1/api/devices.ex.
Writing connection.ex.
Writing metadata.ex.
Writing mix.exs
Writing README.md
Writing LICENSE
Writing .gitignore
Writing config/config.exs
Writing test/test_helper.exs

13:04:19.573 [info]  Found only discovery_revision and/or formatting changes. Not significant enough for a PR.
fixing file permissions
2020-06-06 06:04:22,881 synthtool [DEBUG] > Wrote metadata to clients/home_graph/synth.metadata.
DEBUG:synthtool:Wrote metadata to clients/home_graph/synth.metadata.
2020-06-06 06:04:22,907 autosynth [DEBUG] > Running: git clean -fdx
Removing __pycache__/
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 615, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 476, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 555, in _inner_main
    ).synthesize(base_synth_log_path)
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 121, in synthesize
    with open(log_file_path, "rt") as fp:
IsADirectoryError: [Errno 21] Is a directory: '/tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api'

Google internal developers can see the full log here.

Autosynth is still having trouble generating HomeGraph. :sob:
Here's the output from running synth.py:
2020-06-07 05:57:15,228 autosynth [INFO] > logs will be written to: /tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api
2020-06-07 05:57:15,728 autosynth [DEBUG] > Running: git config --global core.excludesfile /home/kbuilder/.autosynth-gitignore
2020-06-07 05:57:15,730 autosynth [DEBUG] > Running: git config user.name yoshi-automation
2020-06-07 05:57:15,733 autosynth [DEBUG] > Running: git config user.email<EMAIL_ADDRESS>2020-06-07 05:57:15,736 autosynth [DEBUG] > Running: git config push.default simple
2020-06-07 05:57:15,738 autosynth [DEBUG] > Running: git branch -f autosynth-homegraph
2020-06-07 05:57:15,742 autosynth [DEBUG] > Running: git checkout autosynth-homegraph
Switched to branch 'autosynth-homegraph'
2020-06-07 05:57:15,974 autosynth [INFO] > Running synthtool
2020-06-07 05:57:15,975 autosynth [INFO] > ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/home_graph/synth.metadata', 'synth.py', '--']
2020-06-07 05:57:15,977 autosynth [DEBUG] > Running: /tmpfs/src/github/synthtool/env/bin/python3 -m synthtool --metadata clients/home_graph/synth.metadata synth.py -- HomeGraph
tee: /tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api: Is a directory
2020-06-07 05:57:16,188 synthtool [DEBUG] > Executing /home/kbuilder/.cache/synthtool/elixir-google-api/synth.py.
On branch autosynth-homegraph
nothing to commit, working tree clean
2020-06-07 05:57:18,056 synthtool [DEBUG] > Running: docker run --rm -v/tmpfs/tmp/tmpc_2hhd2q/repo:/workspace -v/var/run/docker.sock:/var/run/docker.sock -e USER_GROUP=1000:1000 -w /workspace gcr.io/cloud-devrel-public-resources/elixir19 scripts/generate_client.sh HomeGraph
DEBUG:synthtool:Running: docker run --rm -v/tmpfs/tmp/tmpc_2hhd2q/repo:/workspace -v/var/run/docker.sock:/var/run/docker.sock -e USER_GROUP=1000:1000 -w /workspace gcr.io/cloud-devrel-public-resources/elixir19 scripts/generate_client.sh HomeGraph
/workspace /workspace
The mix.lock file was generated with a newer version of Hex. Update your client by running `mix local.hex` to avoid losing data.
Resolving Hex dependencies...
Dependency resolution completed:
Unchanged:
  certifi 2.5.1
  google_api_discovery 0.7.0
  google_gax 0.3.2
  hackney 1.15.2
  idna 6.0.0
  jason 1.2.1
  metrics 1.0.1
  mime 1.3.1
  mimerl 1.2.0
  oauth2 0.9.4
  parse_trans 3.3.0
  poison 3.1.0
  ssl_verify_fun 1.1.5
  temp 0.4.7
  tesla 1.3.3
  unicode_util_compat 0.4.1
* Getting google_api_discovery (Hex package)
* Getting tesla (Hex package)
* Getting oauth2 (Hex package)
* Getting temp (Hex package)
* Getting jason (Hex package)
* Getting poison (Hex package)
* Getting hackney (Hex package)
* Getting certifi (Hex package)
* Getting idna (Hex package)
* Getting metrics (Hex package)
* Getting mimerl (Hex package)
* Getting ssl_verify_fun (Hex package)
* Getting unicode_util_compat (Hex package)
* Getting parse_trans (Hex package)
* Getting mime (Hex package)
* Getting google_gax (Hex package)
The mix.lock file was generated with a newer version of Hex. Update your client by running `mix local.hex` to avoid losing data.
==> temp
Compiling 3 files (.ex)
Generated temp app
===> Compiling parse_trans
===> Compiling mimerl
===> Compiling metrics
===> Compiling unicode_util_compat
===> Compiling idna
==> jason
Compiling 8 files (.ex)
Generated jason app
warning: String.strip/1 is deprecated. Use String.trim/1 instead
  /workspace/deps/poison/mix.exs:4

==> poison
Compiling 4 files (.ex)
warning: Integer.to_char_list/2 is deprecated. Use Integer.to_charlist/2 instead
  lib/poison/encoder.ex:173

Generated poison app
==> ssl_verify_fun
Compiling 7 files (.erl)
Generated ssl_verify_fun app
===> Compiling certifi
===> Compiling hackney
==> oauth2
Compiling 13 files (.ex)
Generated oauth2 app
==> mime
Compiling 2 files (.ex)
Generated mime app
==> tesla
Compiling 26 files (.ex)
Generated tesla app
==> google_gax
Compiling 5 files (.ex)
Generated google_gax app
==> google_api_discovery
Compiling 21 files (.ex)
Generated google_api_discovery app
==> google_apis
Compiling 27 files (.ex)
warning: System.cwd/0 is deprecated. Use File.cwd/0 instead
  lib/google_apis/publisher.ex:24

Generated google_apis app

12:57:47.679 [info]  FETCHING: https://homegraph.googleapis.com/$discovery/GOOGLE_REST_SIMPLE_URI?version=v1

12:57:47.854 [info]  FOUND: https://homegraph.googleapis.com/$discovery/GOOGLE_REST_SIMPLE_URI?version=v1
Revision check: old=20200504, new=20200529, generating=true
Creating leading directories
Writing AgentDeviceId to clients/home_graph/lib/google_api/home_graph/v1/model/agent_device_id.ex.
Writing AgentOtherDeviceId to clients/home_graph/lib/google_api/home_graph/v1/model/agent_other_device_id.ex.
Writing Device to clients/home_graph/lib/google_api/home_graph/v1/model/device.ex.
Writing DeviceInfo to clients/home_graph/lib/google_api/home_graph/v1/model/device_info.ex.
Writing DeviceNames to clients/home_graph/lib/google_api/home_graph/v1/model/device_names.ex.
Writing Empty to clients/home_graph/lib/google_api/home_graph/v1/model/empty.ex.
Writing QueryRequest to clients/home_graph/lib/google_api/home_graph/v1/model/query_request.ex.
Writing QueryRequestInput to clients/home_graph/lib/google_api/home_graph/v1/model/query_request_input.ex.
Writing QueryRequestPayload to clients/home_graph/lib/google_api/home_graph/v1/model/query_request_payload.ex.
Writing QueryResponse to clients/home_graph/lib/google_api/home_graph/v1/model/query_response.ex.
Writing QueryResponsePayload to clients/home_graph/lib/google_api/home_graph/v1/model/query_response_payload.ex.
Writing ReportStateAndNotificationDevice to clients/home_graph/lib/google_api/home_graph/v1/model/report_state_and_notification_device.ex.
Writing ReportStateAndNotificationRequest to clients/home_graph/lib/google_api/home_graph/v1/model/report_state_and_notification_request.ex.
Writing ReportStateAndNotificationResponse to clients/home_graph/lib/google_api/home_graph/v1/model/report_state_and_notification_response.ex.
Writing RequestSyncDevicesRequest to clients/home_graph/lib/google_api/home_graph/v1/model/request_sync_devices_request.ex.
Writing RequestSyncDevicesResponse to clients/home_graph/lib/google_api/home_graph/v1/model/request_sync_devices_response.ex.
Writing StateAndNotificationPayload to clients/home_graph/lib/google_api/home_graph/v1/model/state_and_notification_payload.ex.
Writing SyncRequest to clients/home_graph/lib/google_api/home_graph/v1/model/sync_request.ex.
Writing SyncResponse to clients/home_graph/lib/google_api/home_graph/v1/model/sync_response.ex.
Writing SyncResponsePayload to clients/home_graph/lib/google_api/home_graph/v1/model/sync_response_payload.ex.
Writing AgentUsers to clients/home_graph/lib/google_api/home_graph/v1/api/agent_users.ex.
Writing Devices to clients/home_graph/lib/google_api/home_graph/v1/api/devices.ex.
Writing connection.ex.
Writing metadata.ex.
Writing mix.exs
Writing README.md
Writing LICENSE
Writing .gitignore
Writing config/config.exs
Writing test/test_helper.exs

12:57:48.222 [info]  Found only discovery_revision and/or formatting changes. Not significant enough for a PR.
fixing file permissions
2020-06-07 05:57:51,260 synthtool [DEBUG] > Wrote metadata to clients/home_graph/synth.metadata.
DEBUG:synthtool:Wrote metadata to clients/home_graph/synth.metadata.
2020-06-07 05:57:51,284 autosynth [DEBUG] > Running: git clean -fdx
Removing __pycache__/
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 615, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 476, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 555, in _inner_main
    ).synthesize(base_synth_log_path)
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 121, in synthesize
    with open(log_file_path, "rt") as fp:
IsADirectoryError: [Errno 21] Is a directory: '/tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api'

Google internal developers can see the full log here.

Autosynth is still having trouble generating HomeGraph. :sob:
Here's the output from running synth.py:
2020-06-08 05:57:46,762 autosynth [INFO] > logs will be written to: /tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api
2020-06-08 05:57:47,594 autosynth [DEBUG] > Running: git config --global core.excludesfile /home/kbuilder/.autosynth-gitignore
2020-06-08 05:57:47,597 autosynth [DEBUG] > Running: git config user.name yoshi-automation
2020-06-08 05:57:47,600 autosynth [DEBUG] > Running: git config user.email<EMAIL_ADDRESS>2020-06-08 05:57:47,603 autosynth [DEBUG] > Running: git config push.default simple
2020-06-08 05:57:47,606 autosynth [DEBUG] > Running: git branch -f autosynth-homegraph
2020-06-08 05:57:47,609 autosynth [DEBUG] > Running: git checkout autosynth-homegraph
Switched to branch 'autosynth-homegraph'
2020-06-08 05:57:47,987 autosynth [INFO] > Running synthtool
2020-06-08 05:57:47,987 autosynth [INFO] > ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/home_graph/synth.metadata', 'synth.py', '--']
2020-06-08 05:57:47,990 autosynth [DEBUG] > Running: /tmpfs/src/github/synthtool/env/bin/python3 -m synthtool --metadata clients/home_graph/synth.metadata synth.py -- HomeGraph
tee: /tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api: Is a directory
2020-06-08 05:57:48,196 synthtool [DEBUG] > Executing /home/kbuilder/.cache/synthtool/elixir-google-api/synth.py.
On branch autosynth-homegraph
nothing to commit, working tree clean
2020-06-08 05:57:49,645 synthtool [DEBUG] > Running: docker run --rm -v/tmpfs/tmp/tmp2lv3o6wg/repo:/workspace -v/var/run/docker.sock:/var/run/docker.sock -e USER_GROUP=1000:1000 -w /workspace gcr.io/cloud-devrel-public-resources/elixir19 scripts/generate_client.sh HomeGraph
DEBUG:synthtool:Running: docker run --rm -v/tmpfs/tmp/tmp2lv3o6wg/repo:/workspace -v/var/run/docker.sock:/var/run/docker.sock -e USER_GROUP=1000:1000 -w /workspace gcr.io/cloud-devrel-public-resources/elixir19 scripts/generate_client.sh HomeGraph
/workspace /workspace
The mix.lock file was generated with a newer version of Hex. Update your client by running `mix local.hex` to avoid losing data.
Resolving Hex dependencies...
Dependency resolution completed:
Unchanged:
  certifi 2.5.1
  google_api_discovery 0.7.0
  google_gax 0.3.2
  hackney 1.15.2
  idna 6.0.0
  jason 1.2.1
  metrics 1.0.1
  mime 1.3.1
  mimerl 1.2.0
  oauth2 0.9.4
  parse_trans 3.3.0
  poison 3.1.0
  ssl_verify_fun 1.1.5
  temp 0.4.7
  tesla 1.3.3
  unicode_util_compat 0.4.1
* Getting google_api_discovery (Hex package)
* Getting tesla (Hex package)
* Getting oauth2 (Hex package)
* Getting temp (Hex package)
* Getting jason (Hex package)
* Getting poison (Hex package)
* Getting hackney (Hex package)
* Getting certifi (Hex package)
* Getting idna (Hex package)
* Getting metrics (Hex package)
* Getting mimerl (Hex package)
* Getting ssl_verify_fun (Hex package)
* Getting unicode_util_compat (Hex package)
* Getting parse_trans (Hex package)
* Getting mime (Hex package)
* Getting google_gax (Hex package)
The mix.lock file was generated with a newer version of Hex. Update your client by running `mix local.hex` to avoid losing data.
==> temp
Compiling 3 files (.ex)
Generated temp app
===> Compiling parse_trans
===> Compiling mimerl
===> Compiling metrics
===> Compiling unicode_util_compat
===> Compiling idna
==> jason
Compiling 8 files (.ex)
Generated jason app
warning: String.strip/1 is deprecated. Use String.trim/1 instead
  /workspace/deps/poison/mix.exs:4

==> poison
Compiling 4 files (.ex)
warning: Integer.to_char_list/2 is deprecated. Use Integer.to_charlist/2 instead
  lib/poison/encoder.ex:173

Generated poison app
==> ssl_verify_fun
Compiling 7 files (.erl)
Generated ssl_verify_fun app
===> Compiling certifi
===> Compiling hackney
==> oauth2
Compiling 13 files (.ex)
Generated oauth2 app
==> mime
Compiling 2 files (.ex)
Generated mime app
==> tesla
Compiling 26 files (.ex)
Generated tesla app
==> google_gax
Compiling 5 files (.ex)
Generated google_gax app
==> google_api_discovery
Compiling 21 files (.ex)
Generated google_api_discovery app
==> google_apis
Compiling 27 files (.ex)
warning: System.cwd/0 is deprecated. Use File.cwd/0 instead
  lib/google_apis/publisher.ex:24

Generated google_apis app

12:58:20.389 [info]  FETCHING: https://homegraph.googleapis.com/$discovery/GOOGLE_REST_SIMPLE_URI?version=v1

12:58:20.569 [info]  FOUND: https://homegraph.googleapis.com/$discovery/GOOGLE_REST_SIMPLE_URI?version=v1
Revision check: old=20200504, new=20200529, generating=true
Creating leading directories
Writing AgentDeviceId to clients/home_graph/lib/google_api/home_graph/v1/model/agent_device_id.ex.
Writing AgentOtherDeviceId to clients/home_graph/lib/google_api/home_graph/v1/model/agent_other_device_id.ex.
Writing Device to clients/home_graph/lib/google_api/home_graph/v1/model/device.ex.
Writing DeviceInfo to clients/home_graph/lib/google_api/home_graph/v1/model/device_info.ex.
Writing DeviceNames to clients/home_graph/lib/google_api/home_graph/v1/model/device_names.ex.
Writing Empty to clients/home_graph/lib/google_api/home_graph/v1/model/empty.ex.
Writing QueryRequest to clients/home_graph/lib/google_api/home_graph/v1/model/query_request.ex.
Writing QueryRequestInput to clients/home_graph/lib/google_api/home_graph/v1/model/query_request_input.ex.
Writing QueryRequestPayload to clients/home_graph/lib/google_api/home_graph/v1/model/query_request_payload.ex.
Writing QueryResponse to clients/home_graph/lib/google_api/home_graph/v1/model/query_response.ex.
Writing QueryResponsePayload to clients/home_graph/lib/google_api/home_graph/v1/model/query_response_payload.ex.
Writing ReportStateAndNotificationDevice to clients/home_graph/lib/google_api/home_graph/v1/model/report_state_and_notification_device.ex.
Writing ReportStateAndNotificationRequest to clients/home_graph/lib/google_api/home_graph/v1/model/report_state_and_notification_request.ex.
Writing ReportStateAndNotificationResponse to clients/home_graph/lib/google_api/home_graph/v1/model/report_state_and_notification_response.ex.
Writing RequestSyncDevicesRequest to clients/home_graph/lib/google_api/home_graph/v1/model/request_sync_devices_request.ex.
Writing RequestSyncDevicesResponse to clients/home_graph/lib/google_api/home_graph/v1/model/request_sync_devices_response.ex.
Writing StateAndNotificationPayload to clients/home_graph/lib/google_api/home_graph/v1/model/state_and_notification_payload.ex.
Writing SyncRequest to clients/home_graph/lib/google_api/home_graph/v1/model/sync_request.ex.
Writing SyncResponse to clients/home_graph/lib/google_api/home_graph/v1/model/sync_response.ex.
Writing SyncResponsePayload to clients/home_graph/lib/google_api/home_graph/v1/model/sync_response_payload.ex.
Writing AgentUsers to clients/home_graph/lib/google_api/home_graph/v1/api/agent_users.ex.
Writing Devices to clients/home_graph/lib/google_api/home_graph/v1/api/devices.ex.
Writing connection.ex.
Writing metadata.ex.
Writing mix.exs
Writing README.md
Writing LICENSE
Writing .gitignore
Writing config/config.exs
Writing test/test_helper.exs

12:58:20.950 [info]  Found only discovery_revision and/or formatting changes. Not significant enough for a PR.
fixing file permissions
2020-06-08 05:58:23,608 synthtool [DEBUG] > Wrote metadata to clients/home_graph/synth.metadata.
DEBUG:synthtool:Wrote metadata to clients/home_graph/synth.metadata.
2020-06-08 05:58:23,635 autosynth [DEBUG] > Running: git clean -fdx
Removing __pycache__/
Traceback (most recent call last):
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 615, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 476, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 555, in _inner_main
    ).synthesize(base_synth_log_path)
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 121, in synthesize
    with open(log_file_path, "rt") as fp:
IsADirectoryError: [Errno 21] Is a directory: '/tmpfs/src/github/synthtool/logs/googleapis/elixir-google-api'

Google internal developers can see the full log here.

Autosynth passed, closing! :green_heart:


Time consuming of ensureFile()

jedis： 3.1.0， jdk：1.8
When I was doing a stress test, I found that redis.clients.jedis.util.RedisInputStream.ensureFill()
was very serious time consuming and that was under larger concurrency.
so why? and what happened?
please anyone can help me， thanks!
the code ：
private void ensureFill() throws JedisConnectionException {
       if (count >= limit) {
           try {
               long start = System.currentTimeMillis();

               limit = in.read(buf);
               long end = System.currentTimeMillis();

              if ((end - start) > 100) {
                System.out.println("in.read: " + (end - start) + "ms, buf size : " + buf.length +", count:"+count+", limit: "+limit +",  in.available():" + in.available());
            }
            count = 0;
            if (limit == -1) {
                throw new JedisConnectionException("Unexpected end of stream.");
            }
        } catch (IOException e) {
            throw new JedisConnectionException(e);
        }
    }
}

the following is log:
in.read: 219ms, buf size : 4096, count:5, limit: 7,  in.available():0
in.read: 219ms, buf size : 4096, count:7, limit: 7,  in.available():0
in.read: 216ms, buf size : 4096, count:7, limit: 7,  in.available():0
in.read: 216ms, buf size : 4096, count:7, limit: 7,  in.available():0
in.read: 216ms, buf size : 4096, count:7, limit: 4,  in.available():0
in.read: 216ms, buf size : 4096, count:7, limit: 7,  in.available():0
in.read: 216ms, buf size : 4096, count:5, limit: 7,  in.available():0
in.read: 216ms, buf size : 4096, count:7, limit: 7,  in.available():0
in.read: 220ms, buf size : 4096, count:7, limit: 7,  in.available():0
in.read: 220ms, buf size : 4096, count:7, limit: 5,  in.available():0
in.read: 220ms, buf size : 4096, count:7, limit: 5,  in.available():0

@yumazhe Let's see the documentation for in.read(buf):

Reads some number of bytes from the input stream and stores them into the buffer array b. The number of bytes actually read is returned as an integer. This method blocks until input data is available, end of file is detected, or an exception is thrown.
If the length of b is zero, then no bytes are read and 0 is returned; otherwise, there is an attempt to read at least one byte. If no byte is available because the stream is at the end of the file, the value -1 is returned; otherwise, at least one byte is read and stored into b.

Let me remind you, the InputStream (in) is actually received from Socket object. Time consumption supposed to be very normal for an InputStream reading from a Socket.


[3.1.0] PHAR file built with box2 seems broken

Steps to reproduce:
~$ wget https://github.com/Behat/Behat/archive/v3.1.0.tar.gz
~$ tar zxf v3.1.0.tar.gz
~$ cd Behat-3.1.0
~/Behat-3.1.0$ curl -LSs https://box-project.github.io/box2/installer.php | php
~/Behat-3.1.0$ composer install --no-dev -q
~/Behat-3.1.0$ php box.phar build
~/Behat-3.1.0$ php behat.phar
PHP Fatal error:  Cannot redeclare composerRequire3b789041321d3943276dff3aa58095fd() (previously declared in /home/marcel/Behat-3.1.0/vendor/composer/autoload_real.php:63) in phar:///home/marcel/Behat-3.1.0/behat.phar/vendor/composer/autoload_real.php on line 70

Changing v3.1.0.tar.gz for another stable release like 3.0.15 works fine.

the issue is that you are loading the local composer autoloading when running behat, and this is the same file than the one used when building the phar, so the random string added in the function name is the same in the phar and in your local project.
If you run composer dump-autoload again in your local behat project, it will use a different random string, which will not conflict with the phar.
The issue happens only because you use the phar to run behat on the source code used to generate the phar itself.

You are right, stof :+1: Thank you.


omnifunc is not set when LspOptionsSet is called after LspAddServer

The documentation states that setting autoComplete to false will automatically set omniComplete to true, and omnifunc will be set. However, this does not work as expected when LspOptionsSet is called after LspAddServer. The documentation should clarify the required order of calling LspOptionsSet and LspAddServer. Alternatively, the code should ensure omniComplete is set correctly after LspOptionsSet is called, or even better, refactor LspAddServer to accept LSP options as an argument.

This was discussed already a couple of times, say in https://github.com/yegappan/lsp/pull/442/files and https://github.com/yegappan/lsp/commit/e3216cae9583c655bfb1c3cfac399738d0521621, and https://github.com/yegappan/lsp/commit/87189faf0bd4a2f974408df2d8c261dbfc3348dd ;
the doc now states the correct order of calling LspOptionsSet and LspAddServer.
However, I'd agree that it would make users' life simpler if the importance of this order was drawn to attention.


Added latest protobuf

Notice that Pikachu can learn PRESENT_FAST but it is not in the game
master

I think this PR is now fine?


Update README.rst

Documentation is under metacat, not metadatadb, these days.

Thanks Marc. Updated.


fix: 인풋 폼 재전송 함수 디폴트 설정

:tada: This PR is included in version 1.3.7 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Retry v2 checkpoint downloads in the case of "Failure when receiving data from the peer" error message

This is a short term solution to a problem surrounding Transient Fault handling with v2 checkpoints. In the long term, we expect to work with SQLite and hopefully have them provide a way for us to better control what we do in the event of an error when downloading blocks.
Resumable downloads are supported by blockcachevfs, meaning that we will not be repeating the same block downloads when retrying these v2 checkpoint downloads.

Could this change also be backported to 2.19.x? I'm unsure how backporting works. Theres a recent github discussion where a connector is unable to download a v2 checkpoint due to this transient "Failure when receiving data from the peer" error. That user is on 2.19.28 at the moment.

Could this change also be backported to 2.19.x?

Are V2 checkpoints enabled in 2.x?

I think in that case we should backport this to work around the issues users are having with downloading iModels.

@mergifyio backport release/2.19.x


Change history tab to info tab

This tab should contain:

[ ] a high level description of the tool's functionality
[ ] links to both feature and API docs
[ ] direct link to GitHub issues to discuss and report bugs
[ ] social links to get in touch (add the bird icon and stuff)
[ ] the log history should move to a auto-collapsed dropdown below all of this, associated with a hint that this is fo dev/bug report purposes.

the log history should move to a auto-collapsed dropdown below all of this, associated with a hint that this is fo dev/bug report purposes.

For now i added this to the navbar burger element.


Use of Cuda terminology instead of HIP terminology in coordinate built-ins

In the file "include/hip/hip_device_launch_parameters.h", the Cuda terminology is used instead of the native HIP terminology for both thread indexes, block indexes, block dims and grid dims definition:

Thread-index: threadIdx.x should be hipThreadIdx_x
Block-index: blockIdx.x	should be hipBlockIdx_x
Block-dim: blockDim.x	should be hipBlockDim_x
Grid-dim: gridDim.x should be hipGridDim_x

This triggers compilation errors and does definitely compromise the portability of codes written in pure HIP or coming out of the "hipify" tool.
https://github.com/ROCm-Developer-Tools/HIP/blob/main/docs/markdown/hip_kernel_language.md#coordinate-built-ins

Thank you for creating this, however I am afraid that it merely points out that HIP's documentation is out of date. The macros are / should be deprecated and never used in current code, where the natural (CUDA, if you want) indexing syntax is preferred. This is / should be guidance for HIP in general, as the macros are way past their expiry date. They were never "native" HIP terminology, but rather a workaround we tried to love because we didn't (at the time) know how to do the other syntax well (fortunately, we learned). I suggest it might be nice to create an issue against HIP itself asking for the documentation to be updated.

Thank you for creating this, however I am afraid that it merely points out that HIP's documentation is out of date. The macros are / should be deprecated and never used in current code, where the natural (CUDA, if you want) indexing syntax is preferred. This is / should be guidance for HIP in general, as the macros are way past their expiry date. They were never "native" HIP terminology, but rather a workaround we tried to love because we didn't (at the time) know how to do the other syntax well (fortunately, we learned). I suggest it might be nice to create an issue against HIP itself asking for the documentation to be updated.

Thanks for the fast answer. I understand your point, but I don't agree with the wontfix status.
The README file in the current repository says:

The HIP CPU Runtime is a header-only library that allows CPUs to execute unmodified HIP code.

My reading of this statement is HIP-CPU has no role of law enforcement of the HIP code syntax but rather to be as close as possible to HIP-GPU's behaviour.
An existing HIP code using the above mentioned "hipXXX" acronyms currently compiles without any deprecation message and runs on any AMD GPU, even with the most recent version of ROCm, while it does not currently compile with HIP-CPU without being modified.
The corresponding #define statements are still present in the HIP-GPU source code for the same legacy reasons I guess.
https://github.com/ROCm-Developer-Tools/HIP/blob/main/include/hip/hcc_detail/hip_runtime.h.
Wouldn't it be worth adding the following lines at end of include/hip/hip_runtime.h?
#define hipThreadIdx_x threadIdx.x
#define hipThreadIdx_y threadIdx.y
#define hipThreadIdx_z threadIdx.z

#define hipBlockIdx_x blockIdx.x
#define hipBlockIdx_y blockIdx.y
#define hipBlockIdx_z blockIdx.z

#define hipBlockDim_x blockDim.x
#define hipBlockDim_y blockDim.y
#define hipBlockDim_z blockDim.z

#define hipGridDim_x gridDim.x
#define hipGridDim_y gridDim.y
#define hipGridDim_z gridDim.z

It's up to you to decide.

Thanks for the fast answer. I understand your point, but I don't agree with the wontfix status.
The README file in the current repository says:

The HIP CPU Runtime is a header-only library that allows CPUs to execute unmodified HIP code.

My reading of this statement is HIP-CPU has no role of law enforcement of the HIP code syntax but rather to be as close as possible to HIP-GPU's behaviour.
An existing HIP code using the above mentioned "hipXXX" acronyms currently compiles without any deprecation message and runs on any AMD GPU, even with the most recent version of ROCm, while it does not currently compile with HIP-CPU without being modified.
The corresponding #define statements are still present in the HIP-GPU source code for the same legacy reasons I guess.
https://github.com/ROCm-Developer-Tools/HIP/blob/main/include/hip/hcc_detail/hip_runtime.h.
Wouldn't it be worth adding the following lines at end of include/hip/hip_runtime.h?
#define hipThreadIdx_x threadIdx.x
#define hipThreadIdx_y threadIdx.y
#define hipThreadIdx_z threadIdx.z

#define hipBlockIdx_x blockIdx.x
#define hipBlockIdx_y blockIdx.y
#define hipBlockIdx_z blockIdx.z

#define hipBlockDim_x blockDim.x
#define hipBlockDim_y blockDim.y
#define hipBlockDim_z blockDim.z

#define hipGridDim_x gridDim.x
#define hipGridDim_y gridDim.y
#define hipGridDim_z gridDim.z

It's up to you to decide.

Your viewpoint is appreciated and your feedback is acknowledged.  However, whilst the disagreement is noted, in this case we have considered the matter and chose not to encourage anti-patterns, therefore this'll not be added anytime soon. I would be surprised if an actual HIP de jure HIP specification will legislate said macros. If that expectation were to be proven wrong, this is definitely worth re-visiting. Until then, we'll try to adhere to commonly accepted good practices and try not to squat on the global namespace with macros unless we absolutely cannot avoid it, which is not the case here.

Your viewpoint is appreciated and your feedback is acknowledged.  However, whilst the disagreement is noted, in this case we have considered the matter and chose not to encourage anti-patterns, therefore this'll not be added anytime soon. I would be surprised if an actual HIP de jure HIP specification will legislate said macros. If that expectation were to be proven wrong, this is definitely worth re-visiting. Until then, we'll try to adhere to commonly accepted good practices and try not to squat on the global namespace with macros unless we absolutely cannot avoid it, which is not the case here.


feat: add source strings API functionality

Codecov Report
Attention: Patch coverage is 1.08696% with 91 lines in your changes are missing coverage. Please review.

Project coverage is 3.11%. Comparing base (a1c20ff) to head (5eee78e).

Files
Patch %
Lines

crowdin/model/source_strings.go
0.00%
51 Missing :warning:

crowdin/source_strings.go
0.00%
40 Missing :warning:

Additional details and impacted files
@@           Coverage Diff            @@
##            main     #12      +/-   ##
========================================
- Coverage   3.38%   3.11%   -0.27%
========================================
  Files         16      18       +2
  Lines        681     773      +92
========================================
+ Hits          23      24       +1
- Misses       656     747      +91
  Partials       2       2

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

@vorobeyme needs a rebase


How do I group multiple dimensions together?

Lets say I want latitude and longitude.
When I make an array of Google_Service_AnalyticsReporting_Dimension, I get these dimensions as separate lists. Meaning I don't get a list of latitude,longitude=visitors, I get a list of latitudes, and another list of longitudes, and all their values are zero. Which is doubly useless... I've tried a comma delimited list of them together, but I get an "unknown dimension(s)" error (Unknown dimension(s): ga:continent,ga:subContinent,ga:country,ga:region,ga:city,ga:latitude,ga:longitude)

These issues are intended for help with usage and problems with the client library. As we are not experts on all the APIs supported, it's difficult for us to answer usage questions specific to an API. I suggest you review the available support resources here.
Best of luck!

Unfortunately I've read that already. And it suggests using JSON
On Wed, Oct 14, 2020, 10:18 AM John Pedrie<EMAIL_ADDRESS>wrote:

These issues are intended for help with usage and problems with the client
library. As we are not experts on all the APIs supported, it's difficult
for us to answer usage questions specific to an API. I suggest you review
the available support resources here
https://developers.google.com/analytics/devguides/reporting/core/v4/help
.
Best of luck!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/googleapis/google-api-php-client/issues/1965#issuecomment-708434145,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AF26DTGAMIBFTHAQMX2IG6LSKWXKFANCNFSM4SPYIQFA
.

Did you try Stackoverflow?

I figured it out. Google's example code is garbage! I actually had the results I wanted, but Google's example printResults() code was discarding most of the data!
Here is better code:
`function printResults($reports, $source = false) {
$RET = [];
for ( $reportIndex = 0; $reportIndex < count( $reports ); $reportIndex++ ) {
$report = $reports[ $reportIndex ];
$header = $report->getColumnHeader();
$dimensionHeaders = $header->getDimensions();
if(is_null($dimensionHeaders)){
$RET = null;
} else {
$metricHeaders = $header->getMetricHeader()->getMetricHeaderEntries();
$rows = $report->getData()->getRows();
for ( $rowIndex = 0; $rowIndex < count($rows); $rowIndex++) {
$RETROW = [];
				$row = $rows[ $rowIndex ];
				$dimensions = $row->getDimensions();
				$metrics = $row->getMetrics();
				for ($i = 0; $i < count($dimensionHeaders) && $i < count($dimensions); $i++) {
					$dimension = str_replace("ga:", "", $dimensionHeaders[$i]);
					$value = $dimensions[$i];
					$RETROW[$dimension] = $value;
				}

				for ($j = 0; $j < count($metrics); $j++) {
					$values = $metrics[$j]->getValues();
					for ($k = 0; $k < count($values); $k++) {
						$entry = $metricHeaders[$k];
						$metric = str_replace("ga:", "", $entry->getName());
						$RETROW[$metric] = $values[$k];
					}
				}

				$RET[] = $RETROW;
			}
		}
	}
	return $RET;
}`

Glad to hear you were able to get the data you need!


Fix application icon in Linux

The application icon is broken in Linux.

For MacOS and Windows icon file is used.

just in case fyi, installation using deb archive doesn't have such issue

just in case fyi, installation using deb archive doesn't have such issue

What is "deb archive"?

What is "deb archive"?
Debian installation Archives (I builded by 'yarn release -l deb')


Error when run image_quality_prediction.py

I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcublas.so.10
段错误 (核心已转储)
报这样的错，修改栈大小没用，不知道是什么原因

It seems to be a problem with your TF or hardware. What is the resolution of your input image?

I just use the given images at 'samples'. I have solved it. It is because of some package is too old.


No emit option

I recently updated from typedoc v0.22.0 which broke a lot of things for me. That's why I would like to add typedoc tests to my CI pipeline. To create docs I am running typedoc src/index.ts. Is it possible to call typedoc with an option so that it runs but doesn't write (no emit) any file? Similar to the noEmit option of TypeScript?

This sounds like a reasonable thing to add, particularly as more validation options are added to TypeDoc. Unfortunately we already use emit to control whether or not TypeDoc will ask tsc to emit, so we need another name... noOutput?... I'd really like a way to obviously distinguish between TS emit and TypeDoc emit.
I guess the emit option could be changed to a mapped option with the values:
const TypeDocEmit = {
  true: true, // Alias for both, for backwards compatibility until 0.23
  false: false, // Alias for docs, for backwards compatibility until 0.23
  both: "both", // Emit both documentation and JS
  docs: "docs", // Emit documentation, but not JS (default)
  none: "none", // Emit nothing, just convert and run validation
} as const;


Better way to handle multiple test

If you want multiple tests on an input there should be a sensible way of doing that.  Currently the two approaches are:

if test is a function call it, if it's an array of functions call them
rethink how happy.methods works to allow some sort of chaining.

Can you show me an example on how you managed multiple tests. Currently I am doing the old way which is repetitive and bad looking code.
Upon reading your suggestion I first tried  my hands at the Chaining Way cause it is elegant and have a reusable approach, I use it in other modules in my project. But chaining needs to return its own object ( AFAIK ), so I couldn't get it to work on return true or false.
Then I tried calling array of functions .
$(document).ready(function () {
	var hap = {
		test1 : function (val) { console.log("Called function test 1 ")},
		test2 : function (val) { console.log("Called function test 2 ")},
		test3 : function (val) { console.log("Called function test 3 ")},
		test4 : function (val) { console.log("Called function test 4 ")},
		test5 : function (val) { console.log("Called function test 5 ")}
	};
	$("#register form").isHappy({
		debug: true,
		submitButton: "#btn-register",
		fields: {

			"#User-Email" : {
				required: true,
				message : "User Email not correct",
				test : [hap.test1, hap.test2, hap.test3]

			},
		},

		happy : function () {
			console.log("I am Happy");
		},
		unHappy : function () {
			console.log("I am not Happy");
		}
	});
});

It doesn't work. Only unHappy method is called, No test was called.

Do you still want to add support for this? As of v0.9, you could do the following:
$("#register").isHappy({
  fields: {
    "#userEmail" : {
      required: true,
      message: "Please provide a valid email address.",
      test: function(value) {
        if (!test1(value)) {
          return new Error('Test 1 failed.');
        }
        if (!test2(value)) {
          return new Error('Test 2 failed.');
        }
        if (!test3(value)) {
          return new Error('Test 3 failed.');
        }
        return true;
      }
    },
  },
});

If we were to run an array of tests, would they get their own message? If so, they would need to be an array of objects with a test and message for each.

That's still one test.  When this was written it was more about being able to say "these three predefined tests need to run" i.e. "must be longer than x characters" "must meet complexity guidelines" "must not contain carriage returns"  But this may be overthinking things and unless people are clamoring for it I'm just gonna close this.

In many scenarios multiple tests are really needed. For example, I have worked on an scheduling app, which is filled with form components, almost all of them require multiple tests. That was before I worked with Happy, so we had written about 60 functions which could be chained. and used the functions which we needed.
What I am saying that at present, happy is perfect for simple registration form validation type of scenarios, But not suitable for JS Apps, which require a more complex set of test, IF blocks are good but does not provide Code re-usability. or proper modular structure.

In many scenarios multiple tests are really needed. For example, I have worked on an scheduling app, which is filled with form components, almost all of them require multiple tests. That was before I worked with Happy, so we had written about 60 functions which could be chained. and used the functions which we needed.
What I am saying that at present, happy is perfect for simple registration form validation type of scenarios, But not suitable for JS Apps, which require a more complex set of test, IF blocks are good but does not provide Code re-usability. or proper modular structure.

In many scenarios multiple tests are really needed. For example, I have worked on an scheduling app, which is filled with form components, almost all of them require multiple tests. That was before I worked with Happy, so we had written about 60 functions which could be chained. and used the functions which we needed.
What I am saying that at present, happy is perfect for simple registration form validation type of scenarios, But not suitable for JS Apps, which require a more complex set of test, IF blocks are good but does not provide Code re-usability. or proper modular structure.

In many scenarios multiple tests are really needed. For example, I have worked on an scheduling app, which is filled with form components, almost all of them require multiple tests. That was before I worked with Happy, so we had written about 60 functions which could be chained. and used the functions which we needed.
What I am saying that at present, happy is perfect for simple registration form validation type of scenarios, But not suitable for JS Apps, which require a more complex set of test, IF blocks are good but does not provide Code re-usability. or proper modular structure.

Well there you go, I closed this prematurely.  Sorry about that.

I wasn't saying this isn't a good idea, what I was trying to say was, if we don't account for how people will expect this to behave, we could be looking at a lot of issues filed.
If we add this support, inevitably, people are going to want custom error messages with this. Do we add that support out of the gate and force a convention like this:
test: [
  {
    test: tooShort,
    message: 'Please provide a username that is longer than 5 characters.'
  }, {
    test: singleLine,
    message: 'Your username cannot contain new lines.'
  }
]

or do we also provide the option to just pass an array of functions?
test: [ tooShort, singleLine ]

Would it be preferable for all tests to run and collect all the failures, or would it be better to stop after the first failed test?
I'm sure there are more questions that need answers, but these are the first that come to mind.
Sort of related; can either of you show how a test could both return the test results and be chainable? I'm having a hard time wrapping my head around that.

Sort of related; can either of you show how a test could both return the test results and be chainable? I'm having a hard time wrapping my head around that.```

It would take quite a refactor of how the methods currently work, something to the effect where they are being passed and return some common state object, which feels like the wrong approach.  Those two ideas were really just brainstorms.

Now that tests can return an error object with a message, it seems like the 'array of tests' approach would be the one that isn't terribly difficult to implement, and is something that will be pretty easy to use and understand.

Your suggestion makes sense to me @btpoe

I should mention that I do like the simplicity of passing an array of named functions. Should we aim to support all 3 or do you see that adding too much to a library that strives to be lightweight?
Also, I realize I'm going full-circle here, but someone could always return an error message out of each test. My only concern with that is that tests wouldn't be useful outside the realm of happy.js. I'm not sure if we want to worry about that or not.

I think simplicity is best, it should be an array of functions that work like errors currently do (return error if you want to customize message beyond the default for that input).  This leaves them as ordered/deterministic so we should stop after the first failure and error accordingly.

The simple array and stopping after the first failure both sound good to me.

I would also prefer simple array of functions, stopping at first error.

All three methods would give developers nice flexibility options. But I would prefer keeping it a simple and lightweight solution. It can skip a few methods if it increases the size and complexity of happy.js .

Alright, I just pushed 7c1fdc3cdd685556b7e7afebedbee4e2abd19ecd that adds support for multiple tests. Something we didn't talk about was the arg parameter. This is supposed to be passed in as a second argument to the test function. Leaving it a single value breaks down even for something as simple as needing a minLength and maxLength.
Here's how I'm handling the arg parameter:

If the test parameter is a single function, the arg parameter will behave exactly as it used to. i.e:

A function will get evaluated and the returned value is what is passed to the test.
Any other type of value will get passed to the test as is.

If the testparameter is an array of functions, the arg parameter will behave as follows:

A single function will get evaluated and the return value will be passed to all of the tests.
A single non-array value will get passed to all of the tests as is.
An array of values will map out in series to each test. If the particular index is a function, it will get evaluated and the returned value will be passed to that specific test.

Here is an example with some of the new possible scenarios:
$("#register").isHappy({
    fields: {
        '#just-like-before': {
            message: 'Field must be at least 3 characters.',
            test: happy.minLength,
            arg: 3
        },
        '#array-of-args-single-test': {
            message: 'Field must be either "this" or "that".',
            test: inArray,
            // this entire array will be passed to this test. as it would have before this recent feature addition
            arg: ['this', 'that']
        },
        '#arg-as-function-many-tests': {
            message: 'Please fill this field.',
            test: [isBeforeNow, isAfterNow],
            //  will pass the current time to all tests.
            arg: function() { return new Date(); }
        },
        '#array-of-args-array-of-tests': {
            message: 'Field must be a reasonable length.',
            test: [happy.minLength, happy.maxLength],
            // minLength will get a second arg of "3", maxLength will get a second arg of "32"
            arg: [3, 32]
        },
        '#arg-is-array-of-functions': {
            required: true,
            message: 'Please fill this field.',
            test: [matchesPassword, isAfterNow],
            // matchesPassword will get the value of $('#password'), isAfterNow will get the current date
            arg: [
                function() { return $('#password').val(); },
                function() { return new Date(); }
            ]
        }
    }
});

Downloading it now to test it. Will give you feedback in a few days. Thanks for this feature.

If this works, great, but part of me feels the arg approach is overwrought and we shout toss it out in favor of just a function that gets the field and nothing else.  Reusing these functions feels a bit clever and over-engineered, and if you want a 'min length' function just make a generator that accepts the value or something.
But changing that feels like a big change so idk, like I said if this works it works.

Stripping the arg value out wouldn't be that hard. I just wanted to maintain the ability to reuse existing test functions, but like you said, a user could wrap a test in a function to set the second argument.
What are your thoughts about having the arg behave as before (if it's a function, evaluate it, otherwise pass it as is) and simply inject the value to all tests?

That works for me

Updated.


Promoted CA1063 to error

Oh, looks like you missed some that are still erroring

ok, I'll take a look. I committed this last weekend and just pushed. Maybe this is new code? Glad to see that it actually fails

Nope, not new code. I forgot about running tests. I'll fix.

/azp run


Feature Request: dishwasher filter notifications

I have a GE Profile dishwasher, model #PDT785SYNFS. Your integration works great for 99% of what I'm looking for.
I'd love to remove the SmartHQ app from my phone, but there's one thing it provides for me that the integration does not - notification to clean the dishwasher filter.
What would it take to get that capability in the integration?
What logs can I provide for you to help make this happen?

Hmm, the latest version of the integration should have that, it's under the "reminders".  Can you confirm you're using the latest version?

I think it's in the latest version, closing for now, but ping if you are still having issues.


fix creation of the social isolation component variables

Components of the social isolation index are created in the wave_specific_data.do file. These are:

Monthly contact with children
Monthly contact with relatives
Monthly contact with friends

Other components come directly from ELSA questions so don't need to be fixed.
The problem I think is that, because the definitions of these variables are complex (separate variables for different types of contact: text, phone call, face to face etc.) I originally had a series of replace == 1 if ... ; replace == 0 if ...
I think this means that the last replace command for each component decides the entire thing. Because of this I need to refactor this to account for all factors in one statement, i.e. replace == 1 if x & if y & if z & ...
OR
take the previous assigned values into account in the chain. i.e.
replace kcntm = 1 if scchdg > 0 & scchdg < 4 & !missing(scchdg) | kcntm == 1 (from previous).

Drastic changes!!
 Top is original, bottom is new:
. tab kcntm, m

 Monthly or |
       more |
    contact |
       with |
   children |      Freq.     Percent        Cum.
------------+-----------------------------------
          0 |     40,690       40.88       40.88
          1 |     32,833       32.99       73.86
          . |     26,014       26.14      100.00
------------+-----------------------------------
      Total |     99,537      100.00

. tab kcntm2, m

     kcntm2 |      Freq.     Percent        Cum.
------------+-----------------------------------
          0 |     12,884       12.94       12.94
          1 |     60,639       60.92       73.86
          . |     26,014       26.14      100.00
------------+-----------------------------------
      Total |     99,537      100.00

Can't do anything about the missing information unfortunately but definite improvement. Now to see what this does for the transition models.

All var definitions fixed and tested in 2ec0852.


Inform the developer if the update to new version of node/compiler is safe

Run tests on behalf of the user with the selected version of Aeproject and prompt a message to the user whether is safe to migrate

cleaning up old issues. feel free to re-open


Rework done on Get-ExcelAllowListObject

I tried to create a specific branch to work on Get-ExcelAllowListObject in case I couldn't fix the issue

1st pull request, done for myself & understand the pull  request workflow


Fixed rx delay for class A.

Fixed rx delay for class A.
Default RX Window is 1 second.
Reference: https://lora-developers.semtech.com/documentation/tech-papers-and-guides/lorawan-class-a-devices/

I closed the old pull request and created a new pull request.
Please help to review.

@wero1414 @REGIOIGER Please help to review. Thanks a lot.

Sorry been really busy with work here, friday i will take a look! thanks for the patience

I have already checked it, i think we are missing also the RXdelay2, i will merge this cause its a good implementation of RXdelay1, also i found a bug with class C in this case.

Thanks a lot. :D


[Feature Request] provider barrierDismissible

It will be nice if you provide params for barrierDismissible

@nizwar Thank you for your feedback. Could you explain your specific use case, so I can better understand the problem? Thanks!

Make user able to close the dialog or screen once they click on barrier, or background... as i can see you're using showDialog to show it, you'll find barrierDismissable parameter

@nizwar Correct me if I'm wrong, but would this even make a difference since we are taking up the whole screen to show the dialog? Is there even a barrier that could be tapped to dismiss it? Would you be able to put together a PR with a demo?

Well, since you have backroundColor and i can set it to Colors.black.withOpacity, it will look like dialog, but in my case, there is no way to close it by tap... in other hand your plugin only accept ImageProvider and there is no way i can wrap the image with GestureDetector
i'll make PR once i'm free


Suggestion: import and display existing images if they existed previous to install of Kitematic

I would assume that if I had an existing boot2docker VM with images that Kitematic would import and display them. It seems Kitematic has no knowledge of existing images. At the very least, this should be addressed in the documentation.

Still, Kitematic Version 0.5.10 has no knowledge of existing images (that I can usually find via docker images) :( :(
When is gonna be fixed?


Vulnerability roundup 87: ameba-0.13.0: 1 advisory

search, files

[ ] CVE-2014-3902 (nixos-unstable)

Scanned versions: nixos-unstable: b3251e04ee4. May contain false positives.
Cc @kimburgess

Thanks for the heads up - this is a false positive.
The linked CVE is for CyberAgent Ameba. The ameba package is for the Crystal Ameba static analysis tool.


[PIR] Added retained size analysis

Don't look here yet.

Ready for review.
@michaelpj could you fix nix for me? My nix-polluted machine is hard to reach right now.

@michaelpj could you fix nix for me?

Perhaps right before merging the PR or otherwise it might get broken again after addressing comments.

@effectfully are you planning to finish this off? Otherwise I'll pick it up.

@effectfully are you planning to finish this off? Otherwise I'll pick it up.

I'm gonna at least partially address your comments on the weekend or something. There's no rush, I assume?

Not really, just a question of whether I should work on it or not.

I've addressed all easily addressable comments and fixed merge conflicts, handing it over to you @michaelpj.


Superstates the only nation that transforms into the superstate is the one country doing the descisions

Currently, when you complete the transition to a super state only you become that super state for example as the British I did all of the pre-requisites to form the EU except when I formed it just turned me into the EU and nobody else just because the AI were too busy dicking around getting all of the military techs. Only one of the states required to form a superstate should have to do the decisions and the other states should automatically join or get a decision or something like in the German unification ion the vanilla game if I create the common market or common defence or poltical union descisions when I make them the other states that it effects should get a descision and if they reject, then I should be able to get a descision to do something about it

Two things;
1, You expand the Union by "any_neighbor", so the UK is a bit "see-locked" and needs to expand via Gibraltar (Spain). This is probably why you have a problem as the UK.
2. The big superstate is really a "two-way" interaction by-design. Other states will join because they want to not because they are "forced/coerced". So, prepare the prerequisites (sphering) then wait, and put your attention to other parts of the political arena (like preventing other super-states from forming).
Your model is a different one, where you sphere all and then form the union. The pathway here is different. all superstates are growing entities, where members are integrated over time.
If AI only goes for military tech it sounds like a bug. Please provide as screen shot with distorted AI preferences, so we can fix it and balance the preferences a bit making forming super states easier.

I have sphered Spain and I have no idea what to do next how do I get them to join

I have sphered Spain and I have no idea what to do next how do I get them to join, I thought that creating a superstate would work similar to the way it did in the vanilla game i.e if you sphered them and did the decision they went with you into a superstate and if you did after then you would get a decision to annexe them I mean I followed the wiki for the NWO mod on superstates it explains very clearly how to get you to change to the superstate but it doesn't really elaborate on how to get other nations to join I mean Germany is just sitting there on the defence union stage when I have formed the European Union already with just the UK
On Wednesday, 27 April 2016, 19:06, simsulla<EMAIL_ADDRESS>wrote:

Closed #396.—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub

Actually, it does say in the wiki that you need a Democracy for the European Union does that mean it has excluded government of the realm because that is what the UK has and Germany has it's government type listed as a Democracy so maybe it is that
On Wednesday, 27 April 2016, 19:06, simsulla<EMAIL_ADDRESS>wrote:

Closed #396.—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub


Twitter notifier fails to post unless media given

The switch to async in #9261 introduced a bug which prevents the Twitter notifier from posting when no media is given.
Home Assistant release (hass --version):
0.53.1
Python release (python3 --version):
Python 3.4.2
Component/platform:
notify/twitter.py
Description of problem:
Twitter notifier cannot post without media.
Expected:
🤦♂ Twitter notifier should be able to post without media.
Problem-relevant configuration.yaml entries and steps to reproduce:
notify:
  - name: twitter
    platform: twitter
    consumer_key: …
    consumer_secret: …
    access_token: …
    access_token_secret: …

automation twitter:
  alias: Send a test message
  initial_state: True
  hide_entity: False
  trigger:
    platform: homeassistant
    event: start
  action:
    - service: notify.twitter
      data:
        message: "Test at {{ now().strftime('%I:%M:%S %p') }}."
    - service: homeassistant.turn_off
      entity_id: automation.send_a_test_message

@balloob @pvizeli Another quick fix for regression introduced in #9261. 🤦♂


feat: kitex gen tool support for windows

feat: kitex gen tool support for windows， issues: #763
But you can't use power shell, you need to use cmd

支持 windows 的设计可能要配合 thriftgo 一起修改，现在还没开始做，我先 close 下，等这次发版之后再看下吧


Add new company: [Polaroid]

Company Name?
Polaroid
What's the company main business today?
Instant cameras
What did the company do in the early days?
Polarized lenses and optics for the armed forces.
What caused the company to pivot?
Edwin Land effectively invented one of the first commercially viable processes for creating polarized lenses which he sold to the armed forces for making sunglasses for aviators. Spending most of World War 2 prototyping techniques for night vision and improved optics, after the war, Polaroid pivoted into making instant cameras. Failure to pivot into digital cameras resulted in the bankruptcy of the company several years after the founder passed away.
Source?

Added! Thanks a lot for contributing!


Unable to Clone project

In trying to checkout this project I'm getting the following error:
PS C:\Users\sirki\Documents\GitHub> git clone git@github.com:MetaGenAI/MetaGenNeos.git
Cloning into 'MetaGenNeos'...
remote: Enumerating objects: 2532, done.
remote: Counting objects: 100% (156/156), done.
remote: Compressing objects: 100% (62/62), done.
remote: Total 2532 (delta 80), reused 105 (delta 65), pack-reused 2376
Receiving objects: 100% (2532/2532), 82.98 MiB | 10.53 MiB/s, done.
Resolving deltas: 100% (1552/1552), done.
error: invalid path 'C:/Program Files (x86)/Steam/steamapps/common/NeosVR/Libraries/net472/x86_64/BaseX.dll'
fatal: unable to checkout working tree
warning: Clone succeeded, but checkout failed.
You can inspect what was checked out with 'git status'
and retry with 'git restore --source=HEAD :/'

If you've followed the steps for installation, you'll note that there is a net462 dir inside of the zip archive in the releases tab, but there isn't a net472. I'm not sure where this comes from...

Looks like this is part of Harmony? Perhaps a different version


v12?

Just wondering how far away the v12 update is?

Hero System 6e (Unofficial) v2 3.0.74 supports FoundryVTT 12.324.  The next release of Hero System is expected to be released this weekend and will support FoundryVTT 12.327.
Keep in mind that some recommended support modules (Drag Ruler) still do not support FoundryVTT v12.x, which may significantly impact your game.

OK cool thanks for the quick response.

Version 3.0.75 Hero System 6e (Unofficial) v2

We recommend sticking with FoundryVTT v11.  Known v12 issues:

Drag Ruler module breaks several things.
Bar Brawl mostly works. Oddities changing token images.

FoundryVTT 12.327 support.
Reworked Combat Tracker to more closely align to FoundryVTT v12.
Improved chat messages for power toggles to include GM & token owners.
Improved initial toggle states during HDC upload.  For example, items in a multipower default to off.
Improved BASE actor type support. PD and ED are now resistant.  BODY now shows in characteristics tab. Implied DCV=3 or 0 if adjacent.
Barrier proof of concept.
Fix for compound powers within a list, where not all compound items were uploaded.  Also fixed issue where some compound power items were duplicating modifiers. #964
You can now make attack rolls from equipment tab.
Added EXPERIENCE field to the OTHER tab.  Be careful as this gets overwritten when you upload an HDC file.


[WIP] Implement a new transaction type to store raw data

I defined a new transaction type to store raw data.
I added a member to the Transaction.
When deserializing the binary block data, an error occurred in the test code. I fixed this test code.
Relates to #1214

I implemented the transaction type that can store raw data, and added some to the transaction validation.

The TransactionData related PR was moved to #1320. I would appreciate it if you continue to review it there.

I have moved the fee-related PR according to data storage to #1321 .
I would appreciate it if you continue to review it there.


MSVC 2022 compatibility

Check/verify MSVC 2022 compatibility with various language standards and include MSVC 2022 in CI if feasible.

Update MSVC works fine. No warnings. performance good (and similar to previous MSVC).
At the moment, I see no need to add any new CI runs. Maybe down the road.


Errors when updating certs.

This docker fails to update certs since a couple of days. Might be because some changes done to nginx-proxy?
Might be worth mentioning on the page if you do not intend to continue developing this image.
All the best!
letsencrypt.1 | Traceback (most recent call last):
letsencrypt.1 |     working_set = WorkingSet._build_master()
letsencrypt.1 |     ws.require(__requires__)
letsencrypt.1 |     needed = self.resolve(parse_requirements(requirements))
letsencrypt.1 |     requirements.extend(dist.requires(req.extras)[::-1])
letsencrypt.1 |     dm = self._dep_map
letsencrypt.1 |   File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 2597, in _dep_map
letsencrypt.1 |     self.__dep_map = self._compute_dependencies()
letsencrypt.1 |   File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 2614, in _compute_dependencies
letsencrypt.1 |     from _markerlib import compile as compile_marker
letsencrypt.1 | ImportError: No module named _markerlib

I'm not planning on maintaining this image. I'll make that known in the README and let anyone take over the repository if they want to.

Updated README


Add some more stubs files for exercises

Hello world was already added in #122, add to next 4 exercises (to make it 5).
I guess these would be enough.
Fixes #121

LGTM, thanks!

Hey @tejasbubane @yurrriq Thanks for your work on this.
Would it make sense to add the stub files for each exercise, or to make them a requirement when adding a new exercise?
It would make the whole thing more consistent, rather than some exercises having it and others not having it.
I could add them if needed.


Vertical Tabs have incorrect border radius.

If you look at the what's new in 2.0 page, you'll see the vertical tabs have a border radius on the top left and top right, instead of the top left and bottom left. Picking up the wrong style from a parent class.
http://beta.semantic-ui.com/introduction/new.html#vertical-tabs

My kingdom for a css specificity property that acted like z-index.


Documentation missing on TexturedMarker.resolution

Hello,
I've been using mapviz the last couple of days. Yes, documentation is lacking, but the content is awesome. Thanks for that!
I'm trying to work with TexturedMarker to project photos taken from a quadrotor to the ground.
To my understanding, the "resolution" field should affect the final image size, but the image should also scale when the altitude of the UAV changes, which doesn't happen.
That said, is there any hint on resizing the image by using the resolution field? Is there another, recommended method?
Thanks

The pose,  resolution, and frame_id fields determine how the image is projected onto the fixed frame in mapviz:

The resolution field represents the scale of a pixel in the image in meters.
The pose field represents the center of the image with respect to the frame_id in the header.

I think you could use the textured marker plug-in to visualize this data, but you will need to calculate the pixel resolution yourself based on the UAV height from the ground and the camera intrinsics.
You can also use the TexturedMarkerArray message in the same way as a MarkerArray and visualize multiple photos like a map.  One thing to keep in mind is that each image is loaded into texture memory on the GPU, so it's not a scalable solution.
It should be possible in the future to make the plug-in more intelligent about how much to load and whether to automatically downsample based on the viewport, but there are no immediate plans to do so.

My question was more about scaling rather than the displayed image resolution itself.
Thanks for the answer.


Bump Version 2.0.1

Use Javaslang 2.0.1

Current coverage is 100.00%

Merging #47 into master will not affect coverage as of c0ee6dc

@@            master     #47   diff @@
======================================
  Files           24      24
  Stmts          246     246
  Branches        53      53
  Methods          0       0
======================================
  Hit            246     246
  Partial          0       0
  Missed           0       0

Review entire Coverage Diff as of c0ee6dc

Powered by Codecov. Updated on successful CI builds.

@danieldietrich OK i get it now :D

Many thanks for updating the versions, that helps!

@danieldietrich I have credentials only on my home computer, so please could you deploy jackson module to oss repository?

yep, will do!

oh, merged the PR - maybe you would have waited until push to maven central. however, will be there neartime...

it is released, will appear in maven central soon...


Can kbld have workaround with manifests (Harbor)

Due to recent DockerHub 429 issues, i really like kbld to be a solution to reallocating images to private registries.
However due to Harbor not supporting manifests, I am unable to reallocate the simplest alpine image.
% cat manifest.lock
apiVersion: kbld.k14s.io/v1alpha1
kind: Config
minimumRequiredVersion: 0.25.0
overrides:
- image: alpine
  newImage: index.docker.io/library/alpine@sha256:c0e9560cda118f9ec63ddefb4a173a2b2a0347082d7dff7dc14272e7841a5b5a
  preresolved: true

% kbld relocate -f ./manifest.lock --repository <IP_ADDRESS>/machi/concourse --lock-output ./manifest.lock.copied
relocate | exporting 1 images...
relocate | will export index.docker.io/library/alpine@sha256:c0e9560cda118f9ec63ddefb4a173a2b2a0347082d7dff7dc14272e7841a5b5a
relocate | exported 1 images
relocate | importing 1 images...
relocate | importing index.docker.io/library/alpine@sha256:c0e9560cda118f9ec63ddefb4a173a2b2a0347082d7dff7dc14272e7841a5b5a -> <IP_ADDRESS>/machi/concourse@sha256:c0e9560cda118f9ec63ddefb4a173a2b2a0347082d7dff7dc14272e7841a5b5a...
relocate | imported 0 images
kbld: Error: Importing image index.docker.io/library/alpine@sha256:c0e9560cda118f9ec63ddefb4a173a2b2a0347082d7dff7dc14272e7841a5b5a:
  Importing image index as <IP_ADDRESS>/machi/concourse@sha256:c0e9560cda118f9ec63ddefb4a173a2b2a0347082d7dff7dc14272e7841a5b5a:
    Writing image index:
      Retried 5 times:
        PUT https://<IP_ADDRESS>/v2/machi/concourse/manifests/kbld-sha256-c0e9560cda118f9ec63ddefb4a173a2b2a0347082d7dff7dc14272e7841a5b5a:
          UNSUPPORTED_MEDIA_TYPE:
            Manifest.list is not supported.; Manifest.list is not supported.

Can we have some solution to overcome this manifests issue ?

hmm, i was pretty sure harbor support manifest lists. is it an older version of harbor?
your alternative would be to look at manifest list, identify specific image (the one that makes sense for your platform) and then reference that instead of referencing to the manifest list.

Sorry you were correct, the latest harbor does support manifest... I was using an old version.
Thank you!


Better name for "Verbose display mode"

Is there reason? Because all "Verbose display mode" is doing is using words and not numbers.
@artyommironov Btw sorry if I'm spamming you

"verbose" means "wordy" and "verbal" means "spoken". Both numbers and words can be spoken so "verbal" doesn't fit here, isn't it? Technically if we don't count numbers as words then it means we show more words, so "verbose" make sense. But I think it's not a perfect case for usual meaning of "verbose". In old version this mode was called like "Show words" but I thought it might be unlear to users. Maybe there are other options? BTW I can be wrong, because English is not my native language.

Yea english isnt my native language either, so its hard to come up with replacement, but "verbose" means "by the use of many or too many words"  and that i think just doesnt explain it very well.
Yea you right, "verbal" isnt great option for replacement, but it also means "consisting of words" and "communication with words" and that was my line of thinking.
I would let this issue open for while if someone doesnt get better idea, but in last case scenario I would just replace it with "Time with numbers/words" or something like that imo.

@artyommironov What about "Replace numbers with words" its easy, clear etc.

Thank you @inson1 ^^ I decided to translate the string like this by reading this issue!
However, I wondered how to translate "toggle verbose display mode" given that "toggle replace numbers by words" does not sound good. In my translation I have finally chosen "toggle words display mode" but I’m not sure the link between the two options is clear. I thought about it and now I think "switch between numbers and words" would be clearer. What do you think?

@Vsnmrn Well I'm happy that this issue helped, even If I didnt come up with something better. You should have said something, if you read this and got an idea. At least I and Google translate did find it. 😃
Yes that is also better. Btw I think that "toggle between numbers and words" is maybe even better imho. What do you think?
And if you would prefer translate in weblate/crowdin, please like this issue #26.

Yes, clearly I wonder why I didn't do it.
@inson1 I trust you, in the context in which it is used, switch and between have the same translation into French anyway. But it is true that "toggle" may be better than "switch".
I have already made the change in my translation. If @artyommironov thinks it's not suitable, I can change it later of course.
Indeed, Weblate would probably be easier to use and could allow more people to contribute.

Replace numbers with words

Word "replace" was used in the past, but it was changed because it's not just "replace numbers with words" but rather a different mode. Not only numbers will be replaced and extra words might be added. For example "00:00" is "Zero hundred" (English military form). : is not a number, and hundred came out of nothing. And the might be more cases as new supported languages are added.
So I'm thininking of something like "Words instead of numbers". No need extra verb like "Use" or "replace" because switch UI control is alreaydy implying "use/activate/enable". What do you think?

toggle between numbers and words

How about shorter "Toggle words/numbers"?

Oh, okay, I wasn't aware of this subtlety. So we should avoid "replace"…
On second thoughts, I'm not convinced by "words display mode" because as I mentioned earlier I think that "words display mode" does not really describe what the option do.
However, if we assume that a verb is not necessary, I think "words instead of numbers" is a good proposal. @inson1 what do you think?
Toggle words/numbers
As is often the case, the shorter the better! However, if we decide to use this wording it will not change my translation (which would not sound good if I translated "toggle words/numbers" literally). But this is ultimately only a detail, the important thing is to find the best wording in English to have a good basis for future translations, and I think @artyommironov found something good.


Indicator 1.5.3 (and others) - needs status change

This indicator still displays example data - it should be set to "not started" or "in progress".

This also applies to 2.5.1.

This also applies to 6.5.1.

This also applies to 6.6.1.

This also applies to 13.1.2.

This also applies to 14.b.1.

This also applies to 16.8.1.

This also applies to 16.a.1.

This also applies to 16.10.2.

This also applies to 17.14.1.

This also applies to 17.17.1.

This also applies to 17.18.1.

This also applies to 17.18.3.

This also applies to 17.19.1.


Enable react/function-component-definition

… with:
{
  "namedComponents": "function-declaration"
}

This provides auto fixing for a pattern we're already enforcing with func-style.

Duplicate of #75


Typo in RegGetValueA

Go to https://docs.microsoft.com/en-us/windows/win32/api/winreg/nf-winreg-reggetvaluea
Scroll down to dwFlags
The description of RRF_RT_QWORD reads: Restrict type to 64-bit RRF_RT_REG_BINARY | RRF_RT_REG_DWORD.
I’m sure the end should read QWORD, not DWORD.

Attempting to fix here: https://github.com/MicrosoftDocs/sdk-api/pull/452

We fixed the doc. Thanks for the eagle eyes. ~Jason

#please-close


view logging error changing menu item colours

[x] when the colours are changed in the menu item this repeating high freq error is in logs

requestLayout() improperly called by androidx.appcompat.view.menu.ActionMenuItemView{4f057c9 VFED..C.. ........ 127,10-254,136 #7f0a01d6 app:id/menu_paste_add} during second layout pass: posting in next frame

was reactivating all the time when should collapsed


fix: explicitly make pageInfo non nullable

PageInfo is nullable when defaultFieldNullability is true, but the relay spec indicates, that PageInfo must not be nullable

Thanks for the PR!
Since this has the potential to change the resulting schema for anyone affected by this bug, I don't feel comfortable making it a patch version change.
Since it is a bug, and the change it introduced is non-breaking from a client perspective, I think we can avoid a major, and just do a minor version bump.
Can you update the changeset to be a minor version, and mention how this can be reverted by setting nullable in pageInfoFieldOptions in the builders relay options


Change expected value in 'should clear socket timeout for keep-alive sockets'

In WSL nothing works
in a clean manjaro installation, all tests works except the one in the title.
fixed reading docs

it fails only on node v8.
i can't figure out what is the problem.

Closing in favor of https://github.com/sindresorhus/timed-out/pull/24


'Add to favorites' does not work

Describe this problem
Select a log monitoring, and then click 'Add to favorites'.
There is a success message, but also an error message.

To Reproduce
Select a log monitoring , click 'Add to favorites'.
Expected behavior
Collect successfully, and no error
Additional Information

I test this scene today. It now works. Maybe it is fixed by some commit.


Update composure.sh

Description
The composure.sh vendor library has been updated upstream, but I am still not getting my head right on how to make git vendor work.
Possible Solution
Someone with a working git vendor update composure.sh?
Context
I offered some PRs upstream and they were accepted, so I'm hoping we can update to get the improvements.

Maybe @NoahGorny can help?


[#1273] Different behaviour of valid and transaction time semantic

fixes dbs-leipzig#1273

Done. Please Re-review


Fix bump dependencies

:tada: This PR is included in version 6.0.0-alpha.7 :tada:
The release is available on:

v6.0.0-alpha.7
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 6.0.0-beta.1 :tada:
The release is available on:

v6.0.0-beta.1
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 6.0.0 :tada:
The release is available on:

v6.0.0
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 6.0.0-rc.1 :tada:
The release is available on:

v6.0.0-rc.1
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 6.0.0 :tada:
The release is available on:

v6.0.0
GitHub release

Your semantic-release bot :package::rocket:


Supermium Canary and Superfox Nightly (Beta/Alpha)

Win32SS Are there plans to create preliminary (Nightly, Canary, Dev, etc.) builds of the Supermium and Superfox browser in the future? Thank You

There aren't enough resources to have more than one Supermium build stream at this time. The best I can do is increase the release frequency on stable tags, possibly to about two weeks.

There aren't enough resources to have more than one Supermium build stream at this time. The best I can do is increase the release frequency on stable tags, possibly to about two weeks.

Thanks for the answer. It is possible that sometime in the future (when you have more time and resources, many people will join in helping develop the Supermium and Superfox browsers


allow workaround for counter-intuitive contexts behavior keeping backward compatibility

Description
changeSet with context specified applies even when update executed with no --contexts specified at runtime
I assume decision about this behavior was made pretty long time ago, so you want to keep backward compatibility. However, googling all around, many people found this behavior as counter-intuitive.
Actual problem is the need to introduce behavior like:

if there is no --contexts specified at runtime, only changesets without any context specified will be applied
if there is(are) some --contexts specified at runtime, all changesets without any context specified will be applied and all changesets with matching context expression specified will be updated.

Would it be possible to add some pseudo-context like nocontexts (or similar) to be available for checks when no --contexts specified at runtime?
So we'll be able to add a check to changeset's/changelog's context expression.
something like context="!nocontexts AND specificcontext"
Maybe in case of "the opposite approach"  pseudo-context's name could be notblank (or similar) and condition then
context="notblank AND specificcontext"
Another possibility would be to add another attribute to changeSet/changeLog, something like strictContext=true/false, with default value "false"

Yes, the current behavior does trip people up at times.
The rationale behind it is this: when first running liquibase you have no contexts defined and just run liquibase update and everything runs. As you start to use contexts and add contextFilter to changesets what should the behavior be for times when you just run liquibase update like before? Still run all changesets? Or only run ones with no contextFilter added? We kept with the "still" in "still run" for consistency.
But in the end, some people want it to be "still run all" and some people want "only run ones without contextFilter" and if we change that default behavior it's going to be breaking for people.
But, we can certainly add new settings to make that behavior modifiable.
We could make a global config setting like filter-unspecfied-context=true|false  (I'm sure there is a better name) which can toggle the match logic for when context is not set so a simple liquibase update will not run any changeSets with contextFilter="whatever".
Alternately, there is the suggestion of having a nocontexts or something default value for --contexts like you suggest. That is interesting in that it allows you to have contextFilters that explicitly handle the case of not specifying a context. I wonder if that will be more complex to implement though? We have the CONTEXTS_ARG settings which don't have a default value, and we probably can't currently have a default value that is itself a configuration value. But, we could maybe still add that support into the filter matching logic? In this case, the new global setting could be something different than filter-unspecfied-context like default-context=nocontext or whatever the user wants?
That could also maybe just be a feature of  filter-unspecfied-context=true where we enable the filtering and have a hard-coded nocontext context that is made available? I'd maybe think this is the best solution, but will probably take some playing with the code and with examples to see.
If anyone wants to take a stab at implementing it and sending a PR, we're always open to that.


Gather facts in the 99-logs.yml playbook

Since this specific playbook may be called from another run, we want to
ensure facts are actually gathered.
This should prevent weird cases when the "run" stage in zuul fails to
do anything (or the pre-run is failing), hitting directly the "post-run"
stage.
As a pull request owner and reviewers, I checked that:

[X] Appropriate testing is done and actually running

recheck

Forcing the merge: the error raised in zuul isn't related to the patch, and should actually be fixed by #301. Since we may need the logs in failing jobs, we'd rather ensure we're actually able to get them.


Default background/vspacing/hspacing for Operation.arrayjoin in docs is incorrect

The help docs for the options :background, :vspacing and :hspacing  are not aligned to the online docs and also not aligned to the actual behaviour.
iex> h Vix.Vips.Operation.arrayjoin
....
## Optional

  • vspacing - Vertical spacing between images. Default: 1
  • hspacing - Horizontal spacing between images. Default: 1
  • background - Colour for new pixels. Default: nil
  ...

However the online docs for libvips say:
Each input image is placed with a box of size hspacing by vspacing pixels and cropped. These default to the largest width and largest height of the input images.

Space between images is filled with background . This defaults to 0 (black).

The online docs and the actual behaviour appear to align as expected.  Unfortunately there isn't really a default value for :hspacing and :vspacing. They need to be omitted for them to be correctly calculated.

Hi @kipcole9, unfortunately those are the default values libvips specify. And libvips online document is different from the one it provides in the operation introspection.
I guess it is like so because currently there is no way to specify null value as default value for an integer type.
Let me bring this up in libvips repo and see.

Akash, thanks, I figured that was probably the case.  I think there are a few other cases in libvips like this. Perhaps standardising on -1 meaning "default behaviour" would be something for John/Klaus to consider for the future.


Fixing JUnitJupiterCategoriesOrTagsCoverageIntegrationTest

Fixing JUnitJupiterCategoriesOrTagsCoverageIntegrationTest#'can combine tags with custom extension' for non-english environments

Fixes #25947
Context
addressing langue failure in non-english environment for JUnitJupiterCategoriesOrTagsCoverageIntegrationTest
Contributor Checklist

[x] Review Contribution Guidelines
[x] Make sure that all commits are signed off to indicate that you agree to the terms of Developer Certificate of Origin.
[x] Make sure all contributed code can be distributed under the terms of the Apache License 2.0, e.g. the code was written by yourself or the original code is licensed under a license compatible to Apache License 2.0.
[x] Check "Allow edit from maintainers" option in pull request so that additional changes can be pushed by Gradle team
[ ] Provide integration tests (under <subproject>/src/integTest) to verify changes from a user perspective

not applicable, it's fixing a Test

[ ] Provide unit tests (under <subproject>/src/test) to verify logic

not applicable: no changes in src/main

[ ] Update User Guide, DSL Reference, and Javadoc for public-facing changes

not applicable: no changes

[x] Ensure that tests pass sanity check: ./gradlew sanityCheck
[x] Ensure that tests pass locally: ./gradlew <changed-subproject>:quickTest

Reviewing cheatsheet
Before merging the PR, comments starting with

❌ ❓must be fixed
🤔 💅 should be fixed
💭 may be fixed
🎉 celebrate happy things

@bot-gradle test and merge

Your PR is queued. See the queue page for details.

I've triggered a build for you. Click here to see all failures if there's any.