Synthesis failed for Fitness

Hello! Autosynth couldn't regenerate Fitness. :broken_heart:
Here's the output from running synth.py:
-m', 'synthtool', '--metadata', 'clients/fitness/synth.metadata', 'synth.py', '--']
2020-12-18 06:06:17,715 autosynth [DEBUG] > log_file_path: /tmpfs/src/logs/elixir-google-api/Fitness/sponge_log.log
2020-12-18 06:06:17,717 autosynth [DEBUG] > Running: /tmpfs/src/github/synthtool/env/bin/python3 -m synthtool --metadata clients/fitness/synth.metadata synth.py -- Fitness
2020-12-18 06:06:17,955 synthtool [DEBUG] > Executing /home/kbuilder/.cache/synthtool/elixir-google-api/synth.py.
On branch autosynth-fitness
nothing to commit, working tree clean
2020-12-18 06:06:19,700 synthtool [DEBUG] > Running: docker run --rm -v/tmpfs/tmp/tmpyqlgl9ho/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 Fitness
DEBUG:synthtool:Running: docker run --rm -v/tmpfs/tmp/tmpyqlgl9ho/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 Fitness
/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 28 files (.ex)
Generated google_apis app

14:06:50.252 [info]  FETCHING: https://fitness.googleapis.com/$discovery/GOOGLE_REST_SIMPLE_URI?version=v1

14:06:50.367 [info]  FETCHING: https://fitness.googleapis.com/$discovery/rest?version=v1

14:06:50.418 [info]  FOUND: https://fitness.googleapis.com/$discovery/rest?version=v1
Revision check: old=20201012, new=20201208, generating=true
Creating leading directories
Writing AggregateBucket to clients/fitness/lib/google_api/fitness/v1/model/aggregate_bucket.ex.
Writing AggregateBy to clients/fitness/lib/google_api/fitness/v1/model/aggregate_by.ex.
Writing AggregateRequest to clients/fitness/lib/google_api/fitness/v1/model/aggregate_request.ex.
Writing AggregateResponse to clients/fitness/lib/google_api/fitness/v1/model/aggregate_response.ex.
Writing Application to clients/fitness/lib/google_api/fitness/v1/model/application.ex.
Writing BucketByActivity to clients/fitness/lib/google_api/fitness/v1/model/bucket_by_activity.ex.
Writing BucketBySession to clients/fitness/lib/google_api/fitness/v1/model/bucket_by_session.ex.
Writing BucketByTime to clients/fitness/lib/google_api/fitness/v1/model/bucket_by_time.ex.
Writing BucketByTimePeriod to clients/fitness/lib/google_api/fitness/v1/model/bucket_by_time_period.ex.
Writing DataPoint to clients/fitness/lib/google_api/fitness/v1/model/data_point.ex.
Writing DataSource to clients/fitness/lib/google_api/fitness/v1/model/data_source.ex.
Writing DataType to clients/fitness/lib/google_api/fitness/v1/model/data_type.ex.
Writing DataTypeField to clients/fitness/lib/google_api/fitness/v1/model/data_type_field.ex.
Writing Dataset to clients/fitness/lib/google_api/fitness/v1/model/dataset.ex.
Writing Device to clients/fitness/lib/google_api/fitness/v1/model/device.ex.
Writing ListDataPointChangesResponse to clients/fitness/lib/google_api/fitness/v1/model/list_data_point_changes_response.ex.
Writing ListDataSourcesResponse to clients/fitness/lib/google_api/fitness/v1/model/list_data_sources_response.ex.
Writing ListSessionsResponse to clients/fitness/lib/google_api/fitness/v1/model/list_sessions_response.ex.
Writing MapValue to clients/fitness/lib/google_api/fitness/v1/model/map_value.ex.
Writing Session to clients/fitness/lib/google_api/fitness/v1/model/session.ex.
Writing Value to clients/fitness/lib/google_api/fitness/v1/model/value.ex.
Writing ValueMapValEntry to clients/fitness/lib/google_api/fitness/v1/model/value_map_val_entry.ex.
Writing Users to clients/fitness/lib/google_api/fitness/v1/api/users.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

14:06:50.880 [info]  Found only discovery_revision and/or formatting changes. Not significant enough for a PR.
fixing file permissions
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/synthtool/__main__.py", line 102, in <module>
    main()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 94, in main
    spec.loader.exec_module(synth_module)  # type: ignore
  File "/tmpfs/src/github/synthtool/synthtool/metadata.py", line 252, in __exit__
    self.observer.stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/utils/__init__.py", line 81, in stop
    self.on_thread_stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/api.py", line 361, in on_thread_stop
    self.unschedule_all()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/api.py", line 357, in unschedule_all
    self._clear_emitters()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/api.py", line 231, in _clear_emitters
    emitter.stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/utils/__init__.py", line 81, in stop
    self.on_thread_stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/inotify.py", line 121, in on_thread_stop
    self._inotify.close()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/inotify_buffer.py", line 50, in close
    self.stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/utils/__init__.py", line 81, in stop
    self.on_thread_stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/inotify_buffer.py", line 46, in on_thread_stop
    self._inotify.close()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/inotify_c.py", line 277, in close
    os.close(self._inotify_fd)
OSError: [Errno 9] Bad file descriptor
2020-12-18 06:06:53,895 autosynth [ERROR] > Synthesis failed
2020-12-18 06:06:53,896 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 354, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 189, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 291, in _inner_main
    ).synthesize(synth_log_path / "sponge_log.log")
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 120, in synthesize
    synth_proc.check_returncode()  # Raise an exception.
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 389, in check_returncode
    self.stderr)
subprocess.CalledProcessError: Command '['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/fitness/synth.metadata', 'synth.py', '--', 'Fitness']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth is still having trouble generating Fitness. :sob:
Here's the output from running synth.py:
-m', 'synthtool', '--metadata', 'clients/fitness/synth.metadata', 'synth.py', '--']
2020-12-19 06:04:24,345 autosynth [DEBUG] > log_file_path: /tmpfs/src/logs/elixir-google-api/Fitness/sponge_log.log
2020-12-19 06:04:24,348 autosynth [DEBUG] > Running: /tmpfs/src/github/synthtool/env/bin/python3 -m synthtool --metadata clients/fitness/synth.metadata synth.py -- Fitness
2020-12-19 06:04:24,570 synthtool [DEBUG] > Executing /home/kbuilder/.cache/synthtool/elixir-google-api/synth.py.
On branch autosynth-fitness
nothing to commit, working tree clean
2020-12-19 06:04:26,369 synthtool [DEBUG] > Running: docker run --rm -v/tmpfs/tmp/tmpzc4vl3wx/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 Fitness
DEBUG:synthtool:Running: docker run --rm -v/tmpfs/tmp/tmpzc4vl3wx/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 Fitness
/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 28 files (.ex)
Generated google_apis app

14:04:57.096 [info]  FETCHING: https://fitness.googleapis.com/$discovery/GOOGLE_REST_SIMPLE_URI?version=v1

14:04:57.208 [info]  FETCHING: https://fitness.googleapis.com/$discovery/rest?version=v1

14:04:57.260 [info]  FOUND: https://fitness.googleapis.com/$discovery/rest?version=v1
Revision check: old=20201012, new=20201208, generating=true
Creating leading directories
Writing AggregateBucket to clients/fitness/lib/google_api/fitness/v1/model/aggregate_bucket.ex.
Writing AggregateBy to clients/fitness/lib/google_api/fitness/v1/model/aggregate_by.ex.
Writing AggregateRequest to clients/fitness/lib/google_api/fitness/v1/model/aggregate_request.ex.
Writing AggregateResponse to clients/fitness/lib/google_api/fitness/v1/model/aggregate_response.ex.
Writing Application to clients/fitness/lib/google_api/fitness/v1/model/application.ex.
Writing BucketByActivity to clients/fitness/lib/google_api/fitness/v1/model/bucket_by_activity.ex.
Writing BucketBySession to clients/fitness/lib/google_api/fitness/v1/model/bucket_by_session.ex.
Writing BucketByTime to clients/fitness/lib/google_api/fitness/v1/model/bucket_by_time.ex.
Writing BucketByTimePeriod to clients/fitness/lib/google_api/fitness/v1/model/bucket_by_time_period.ex.
Writing DataPoint to clients/fitness/lib/google_api/fitness/v1/model/data_point.ex.
Writing DataSource to clients/fitness/lib/google_api/fitness/v1/model/data_source.ex.
Writing DataType to clients/fitness/lib/google_api/fitness/v1/model/data_type.ex.
Writing DataTypeField to clients/fitness/lib/google_api/fitness/v1/model/data_type_field.ex.
Writing Dataset to clients/fitness/lib/google_api/fitness/v1/model/dataset.ex.
Writing Device to clients/fitness/lib/google_api/fitness/v1/model/device.ex.
Writing ListDataPointChangesResponse to clients/fitness/lib/google_api/fitness/v1/model/list_data_point_changes_response.ex.
Writing ListDataSourcesResponse to clients/fitness/lib/google_api/fitness/v1/model/list_data_sources_response.ex.
Writing ListSessionsResponse to clients/fitness/lib/google_api/fitness/v1/model/list_sessions_response.ex.
Writing MapValue to clients/fitness/lib/google_api/fitness/v1/model/map_value.ex.
Writing Session to clients/fitness/lib/google_api/fitness/v1/model/session.ex.
Writing Value to clients/fitness/lib/google_api/fitness/v1/model/value.ex.
Writing ValueMapValEntry to clients/fitness/lib/google_api/fitness/v1/model/value_map_val_entry.ex.
Writing Users to clients/fitness/lib/google_api/fitness/v1/api/users.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

14:04:57.719 [info]  Found only discovery_revision and/or formatting changes. Not significant enough for a PR.
fixing file permissions
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/synthtool/__main__.py", line 102, in <module>
    main()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 94, in main
    spec.loader.exec_module(synth_module)  # type: ignore
  File "/tmpfs/src/github/synthtool/synthtool/metadata.py", line 252, in __exit__
    self.observer.stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/utils/__init__.py", line 81, in stop
    self.on_thread_stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/api.py", line 361, in on_thread_stop
    self.unschedule_all()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/api.py", line 357, in unschedule_all
    self._clear_emitters()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/api.py", line 231, in _clear_emitters
    emitter.stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/utils/__init__.py", line 81, in stop
    self.on_thread_stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/inotify.py", line 121, in on_thread_stop
    self._inotify.close()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/inotify_buffer.py", line 50, in close
    self.stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/utils/__init__.py", line 81, in stop
    self.on_thread_stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/inotify_buffer.py", line 46, in on_thread_stop
    self._inotify.close()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/inotify_c.py", line 277, in close
    os.close(self._inotify_fd)
OSError: [Errno 9] Bad file descriptor
2020-12-19 06:05:00,795 autosynth [ERROR] > Synthesis failed
2020-12-19 06:05:00,796 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 354, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 189, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 291, in _inner_main
    ).synthesize(synth_log_path / "sponge_log.log")
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 120, in synthesize
    synth_proc.check_returncode()  # Raise an exception.
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 389, in check_returncode
    self.stderr)
subprocess.CalledProcessError: Command '['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/fitness/synth.metadata', 'synth.py', '--', 'Fitness']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth is still having trouble generating Fitness. :sob:
Here's the output from running synth.py:
-m', 'synthtool', '--metadata', 'clients/fitness/synth.metadata', 'synth.py', '--']
2020-12-20 06:09:10,996 autosynth [DEBUG] > log_file_path: /tmpfs/src/logs/elixir-google-api/Fitness/sponge_log.log
2020-12-20 06:09:10,999 autosynth [DEBUG] > Running: /tmpfs/src/github/synthtool/env/bin/python3 -m synthtool --metadata clients/fitness/synth.metadata synth.py -- Fitness
2020-12-20 06:09:11,223 synthtool [DEBUG] > Executing /home/kbuilder/.cache/synthtool/elixir-google-api/synth.py.
On branch autosynth-fitness
nothing to commit, working tree clean
2020-12-20 06:09:13,119 synthtool [DEBUG] > Running: docker run --rm -v/tmpfs/tmp/tmptlvty55y/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 Fitness
DEBUG:synthtool:Running: docker run --rm -v/tmpfs/tmp/tmptlvty55y/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 Fitness
/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 28 files (.ex)
Generated google_apis app

14:09:46.903 [info]  FETCHING: https://fitness.googleapis.com/$discovery/GOOGLE_REST_SIMPLE_URI?version=v1

14:09:47.020 [info]  FETCHING: https://fitness.googleapis.com/$discovery/rest?version=v1

14:09:47.075 [info]  FOUND: https://fitness.googleapis.com/$discovery/rest?version=v1
Revision check: old=20201012, new=20201208, generating=true
Creating leading directories
Writing AggregateBucket to clients/fitness/lib/google_api/fitness/v1/model/aggregate_bucket.ex.
Writing AggregateBy to clients/fitness/lib/google_api/fitness/v1/model/aggregate_by.ex.
Writing AggregateRequest to clients/fitness/lib/google_api/fitness/v1/model/aggregate_request.ex.
Writing AggregateResponse to clients/fitness/lib/google_api/fitness/v1/model/aggregate_response.ex.
Writing Application to clients/fitness/lib/google_api/fitness/v1/model/application.ex.
Writing BucketByActivity to clients/fitness/lib/google_api/fitness/v1/model/bucket_by_activity.ex.
Writing BucketBySession to clients/fitness/lib/google_api/fitness/v1/model/bucket_by_session.ex.
Writing BucketByTime to clients/fitness/lib/google_api/fitness/v1/model/bucket_by_time.ex.
Writing BucketByTimePeriod to clients/fitness/lib/google_api/fitness/v1/model/bucket_by_time_period.ex.
Writing DataPoint to clients/fitness/lib/google_api/fitness/v1/model/data_point.ex.
Writing DataSource to clients/fitness/lib/google_api/fitness/v1/model/data_source.ex.
Writing DataType to clients/fitness/lib/google_api/fitness/v1/model/data_type.ex.
Writing DataTypeField to clients/fitness/lib/google_api/fitness/v1/model/data_type_field.ex.
Writing Dataset to clients/fitness/lib/google_api/fitness/v1/model/dataset.ex.
Writing Device to clients/fitness/lib/google_api/fitness/v1/model/device.ex.
Writing ListDataPointChangesResponse to clients/fitness/lib/google_api/fitness/v1/model/list_data_point_changes_response.ex.
Writing ListDataSourcesResponse to clients/fitness/lib/google_api/fitness/v1/model/list_data_sources_response.ex.
Writing ListSessionsResponse to clients/fitness/lib/google_api/fitness/v1/model/list_sessions_response.ex.
Writing MapValue to clients/fitness/lib/google_api/fitness/v1/model/map_value.ex.
Writing Session to clients/fitness/lib/google_api/fitness/v1/model/session.ex.
Writing Value to clients/fitness/lib/google_api/fitness/v1/model/value.ex.
Writing ValueMapValEntry to clients/fitness/lib/google_api/fitness/v1/model/value_map_val_entry.ex.
Writing Users to clients/fitness/lib/google_api/fitness/v1/api/users.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

14:09:47.558 [info]  Found only discovery_revision and/or formatting changes. Not significant enough for a PR.
fixing file permissions
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/synthtool/__main__.py", line 102, in <module>
    main()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 94, in main
    spec.loader.exec_module(synth_module)  # type: ignore
  File "/tmpfs/src/github/synthtool/synthtool/metadata.py", line 252, in __exit__
    self.observer.stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/utils/__init__.py", line 81, in stop
    self.on_thread_stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/api.py", line 361, in on_thread_stop
    self.unschedule_all()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/api.py", line 357, in unschedule_all
    self._clear_emitters()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/api.py", line 231, in _clear_emitters
    emitter.stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/utils/__init__.py", line 81, in stop
    self.on_thread_stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/inotify.py", line 121, in on_thread_stop
    self._inotify.close()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/inotify_buffer.py", line 50, in close
    self.stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/utils/__init__.py", line 81, in stop
    self.on_thread_stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/inotify_buffer.py", line 46, in on_thread_stop
    self._inotify.close()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/inotify_c.py", line 277, in close
    os.close(self._inotify_fd)
OSError: [Errno 9] Bad file descriptor
2020-12-20 06:09:50,930 autosynth [ERROR] > Synthesis failed
2020-12-20 06:09:50,930 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 354, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 189, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 291, in _inner_main
    ).synthesize(synth_log_path / "sponge_log.log")
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 120, in synthesize
    synth_proc.check_returncode()  # Raise an exception.
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 389, in check_returncode
    self.stderr)
subprocess.CalledProcessError: Command '['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/fitness/synth.metadata', 'synth.py', '--', 'Fitness']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth is still having trouble generating Fitness. :sob:
Here's the output from running synth.py:
-m', 'synthtool', '--metadata', 'clients/fitness/synth.metadata', 'synth.py', '--']
2020-12-21 06:03:13,263 autosynth [DEBUG] > log_file_path: /tmpfs/src/logs/elixir-google-api/Fitness/sponge_log.log
2020-12-21 06:03:13,265 autosynth [DEBUG] > Running: /tmpfs/src/github/synthtool/env/bin/python3 -m synthtool --metadata clients/fitness/synth.metadata synth.py -- Fitness
2020-12-21 06:03:13,473 synthtool [DEBUG] > Executing /home/kbuilder/.cache/synthtool/elixir-google-api/synth.py.
On branch autosynth-fitness
nothing to commit, working tree clean
2020-12-21 06:03:15,179 synthtool [DEBUG] > Running: docker run --rm -v/tmpfs/tmp/tmpm57_tf68/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 Fitness
DEBUG:synthtool:Running: docker run --rm -v/tmpfs/tmp/tmpm57_tf68/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 Fitness
/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 28 files (.ex)
Generated google_apis app

14:03:43.804 [info]  FETCHING: https://fitness.googleapis.com/$discovery/GOOGLE_REST_SIMPLE_URI?version=v1

14:03:43.906 [info]  FETCHING: https://fitness.googleapis.com/$discovery/rest?version=v1

14:03:43.962 [info]  FOUND: https://fitness.googleapis.com/$discovery/rest?version=v1
Revision check: old=20201012, new=20201208, generating=true
Creating leading directories
Writing AggregateBucket to clients/fitness/lib/google_api/fitness/v1/model/aggregate_bucket.ex.
Writing AggregateBy to clients/fitness/lib/google_api/fitness/v1/model/aggregate_by.ex.
Writing AggregateRequest to clients/fitness/lib/google_api/fitness/v1/model/aggregate_request.ex.
Writing AggregateResponse to clients/fitness/lib/google_api/fitness/v1/model/aggregate_response.ex.
Writing Application to clients/fitness/lib/google_api/fitness/v1/model/application.ex.
Writing BucketByActivity to clients/fitness/lib/google_api/fitness/v1/model/bucket_by_activity.ex.
Writing BucketBySession to clients/fitness/lib/google_api/fitness/v1/model/bucket_by_session.ex.
Writing BucketByTime to clients/fitness/lib/google_api/fitness/v1/model/bucket_by_time.ex.
Writing BucketByTimePeriod to clients/fitness/lib/google_api/fitness/v1/model/bucket_by_time_period.ex.
Writing DataPoint to clients/fitness/lib/google_api/fitness/v1/model/data_point.ex.
Writing DataSource to clients/fitness/lib/google_api/fitness/v1/model/data_source.ex.
Writing DataType to clients/fitness/lib/google_api/fitness/v1/model/data_type.ex.
Writing DataTypeField to clients/fitness/lib/google_api/fitness/v1/model/data_type_field.ex.
Writing Dataset to clients/fitness/lib/google_api/fitness/v1/model/dataset.ex.
Writing Device to clients/fitness/lib/google_api/fitness/v1/model/device.ex.
Writing ListDataPointChangesResponse to clients/fitness/lib/google_api/fitness/v1/model/list_data_point_changes_response.ex.
Writing ListDataSourcesResponse to clients/fitness/lib/google_api/fitness/v1/model/list_data_sources_response.ex.
Writing ListSessionsResponse to clients/fitness/lib/google_api/fitness/v1/model/list_sessions_response.ex.
Writing MapValue to clients/fitness/lib/google_api/fitness/v1/model/map_value.ex.
Writing Session to clients/fitness/lib/google_api/fitness/v1/model/session.ex.
Writing Value to clients/fitness/lib/google_api/fitness/v1/model/value.ex.
Writing ValueMapValEntry to clients/fitness/lib/google_api/fitness/v1/model/value_map_val_entry.ex.
Writing Users to clients/fitness/lib/google_api/fitness/v1/api/users.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

14:03:44.392 [info]  Found only discovery_revision and/or formatting changes. Not significant enough for a PR.
fixing file permissions
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/synthtool/__main__.py", line 102, in <module>
    main()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 94, in main
    spec.loader.exec_module(synth_module)  # type: ignore
  File "/tmpfs/src/github/synthtool/synthtool/metadata.py", line 252, in __exit__
    self.observer.stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/utils/__init__.py", line 81, in stop
    self.on_thread_stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/api.py", line 361, in on_thread_stop
    self.unschedule_all()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/api.py", line 357, in unschedule_all
    self._clear_emitters()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/api.py", line 231, in _clear_emitters
    emitter.stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/utils/__init__.py", line 81, in stop
    self.on_thread_stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/inotify.py", line 121, in on_thread_stop
    self._inotify.close()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/inotify_buffer.py", line 50, in close
    self.stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/utils/__init__.py", line 81, in stop
    self.on_thread_stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/inotify_buffer.py", line 46, in on_thread_stop
    self._inotify.close()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/inotify_c.py", line 277, in close
    os.close(self._inotify_fd)
OSError: [Errno 9] Bad file descriptor
2020-12-21 06:03:47,290 autosynth [ERROR] > Synthesis failed
2020-12-21 06:03:47,290 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 354, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 189, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 291, in _inner_main
    ).synthesize(synth_log_path / "sponge_log.log")
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 120, in synthesize
    synth_proc.check_returncode()  # Raise an exception.
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 389, in check_returncode
    self.stderr)
subprocess.CalledProcessError: Command '['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/fitness/synth.metadata', 'synth.py', '--', 'Fitness']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth is still having trouble generating Fitness. :sob:
Here's the output from running synth.py:
-m', 'synthtool', '--metadata', 'clients/fitness/synth.metadata', 'synth.py', '--']
2020-12-22 06:03:28,681 autosynth [DEBUG] > log_file_path: /tmpfs/src/logs/elixir-google-api/Fitness/sponge_log.log
2020-12-22 06:03:28,683 autosynth [DEBUG] > Running: /tmpfs/src/github/synthtool/env/bin/python3 -m synthtool --metadata clients/fitness/synth.metadata synth.py -- Fitness
2020-12-22 06:03:28,905 synthtool [DEBUG] > Executing /home/kbuilder/.cache/synthtool/elixir-google-api/synth.py.
On branch autosynth-fitness
nothing to commit, working tree clean
2020-12-22 06:03:30,733 synthtool [DEBUG] > Running: docker run --rm -v/tmpfs/tmp/tmpjr6ybw7f/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 Fitness
DEBUG:synthtool:Running: docker run --rm -v/tmpfs/tmp/tmpjr6ybw7f/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 Fitness
/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 28 files (.ex)
Generated google_apis app

14:04:01.005 [info]  FETCHING: https://fitness.googleapis.com/$discovery/GOOGLE_REST_SIMPLE_URI?version=v1

14:04:01.120 [info]  FETCHING: https://fitness.googleapis.com/$discovery/rest?version=v1

14:04:01.174 [info]  FOUND: https://fitness.googleapis.com/$discovery/rest?version=v1
Revision check: old=20201012, new=20201208, generating=true
Creating leading directories
Writing AggregateBucket to clients/fitness/lib/google_api/fitness/v1/model/aggregate_bucket.ex.
Writing AggregateBy to clients/fitness/lib/google_api/fitness/v1/model/aggregate_by.ex.
Writing AggregateRequest to clients/fitness/lib/google_api/fitness/v1/model/aggregate_request.ex.
Writing AggregateResponse to clients/fitness/lib/google_api/fitness/v1/model/aggregate_response.ex.
Writing Application to clients/fitness/lib/google_api/fitness/v1/model/application.ex.
Writing BucketByActivity to clients/fitness/lib/google_api/fitness/v1/model/bucket_by_activity.ex.
Writing BucketBySession to clients/fitness/lib/google_api/fitness/v1/model/bucket_by_session.ex.
Writing BucketByTime to clients/fitness/lib/google_api/fitness/v1/model/bucket_by_time.ex.
Writing BucketByTimePeriod to clients/fitness/lib/google_api/fitness/v1/model/bucket_by_time_period.ex.
Writing DataPoint to clients/fitness/lib/google_api/fitness/v1/model/data_point.ex.
Writing DataSource to clients/fitness/lib/google_api/fitness/v1/model/data_source.ex.
Writing DataType to clients/fitness/lib/google_api/fitness/v1/model/data_type.ex.
Writing DataTypeField to clients/fitness/lib/google_api/fitness/v1/model/data_type_field.ex.
Writing Dataset to clients/fitness/lib/google_api/fitness/v1/model/dataset.ex.
Writing Device to clients/fitness/lib/google_api/fitness/v1/model/device.ex.
Writing ListDataPointChangesResponse to clients/fitness/lib/google_api/fitness/v1/model/list_data_point_changes_response.ex.
Writing ListDataSourcesResponse to clients/fitness/lib/google_api/fitness/v1/model/list_data_sources_response.ex.
Writing ListSessionsResponse to clients/fitness/lib/google_api/fitness/v1/model/list_sessions_response.ex.
Writing MapValue to clients/fitness/lib/google_api/fitness/v1/model/map_value.ex.
Writing Session to clients/fitness/lib/google_api/fitness/v1/model/session.ex.
Writing Value to clients/fitness/lib/google_api/fitness/v1/model/value.ex.
Writing ValueMapValEntry to clients/fitness/lib/google_api/fitness/v1/model/value_map_val_entry.ex.
Writing Users to clients/fitness/lib/google_api/fitness/v1/api/users.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

14:04:01.640 [info]  Found only discovery_revision and/or formatting changes. Not significant enough for a PR.
fixing file permissions
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/synthtool/__main__.py", line 102, in <module>
    main()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/__main__.py", line 94, in main
    spec.loader.exec_module(synth_module)  # type: ignore
  File "/tmpfs/src/github/synthtool/synthtool/metadata.py", line 252, in __exit__
    self.observer.stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/utils/__init__.py", line 81, in stop
    self.on_thread_stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/api.py", line 361, in on_thread_stop
    self.unschedule_all()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/api.py", line 357, in unschedule_all
    self._clear_emitters()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/api.py", line 231, in _clear_emitters
    emitter.stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/utils/__init__.py", line 81, in stop
    self.on_thread_stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/inotify.py", line 121, in on_thread_stop
    self._inotify.close()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/inotify_buffer.py", line 50, in close
    self.stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/utils/__init__.py", line 81, in stop
    self.on_thread_stop()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/inotify_buffer.py", line 46, in on_thread_stop
    self._inotify.close()
  File "/tmpfs/src/github/synthtool/env/lib/python3.6/site-packages/watchdog/observers/inotify_c.py", line 277, in close
    os.close(self._inotify_fd)
OSError: [Errno 9] Bad file descriptor
2020-12-22 06:04:04,709 autosynth [ERROR] > Synthesis failed
2020-12-22 06:04:04,710 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 354, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 189, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 291, in _inner_main
    ).synthesize(synth_log_path / "sponge_log.log")
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 120, in synthesize
    synth_proc.check_returncode()  # Raise an exception.
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 389, in check_returncode
    self.stderr)
subprocess.CalledProcessError: Command '['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/fitness/synth.metadata', 'synth.py', '--', 'Fitness']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth passed, closing! :green_heart:


Error update flutter 0.1.5 -> 0.3.1

I/flutter (11940): Color(0xffffde00), borderRadius: BorderRadius.circular(25.0)), constraints:
I/flutter (11940): BoxConstraints(0.0<=w<=Infinity, h=50.0), margin: EdgeInsets(10.0, 0.0, 10.0, 10.0)):
I/flutter (11940): The getter 'value' was called on null.
I/flutter (11940): Receiver: null
I/flutter (11940): Tried calling: value
I/flutter (11940): When the exception was thrown, this was the stack:
I/flutter (11940): #0      Object.noSuchMethod (dart:core-patch/dart:core/object_patch.dart:46)
I/flutter (11940): #1      _TabBarState._indicator (package:flutter/src/material/tabs.dart:694:51)
I/flutter (11940): #2      _TabBarState._initIndicatorPainter (package:flutter/src/material/tabs.dart:738:18)

Please add the output of flutter doctor -v

[✓] Flutter (Channel beta, v0.3.1, on Linux, locale pt_BR.UTF-8)
• Flutter version 0.3.1 at /home/giovanni/flutter
• Framework revision 12bbaba9ae (6 days ago), 2018-04-19 23:36:15 -0700
• Engine revision 09d05a3891
• Dart version 2.0.0-dev.48.0.flutter-fe606f890b
[✓] Android toolchain - develop for Android devices (Android SDK 27.0.3)
• Android SDK at /home/giovanni/Android/Sdk
• Android NDK location not configured (optional; useful for native profiling support)
• Platform android-27, build-tools 27.0.3
• Java binary at: /usr/local/android-studio/jre/bin/java
• Java version OpenJDK Runtime Environment (build 1.8.0_152-release-915-b01)
• All Android licenses accepted.
[✓] Android Studio (version 3.0)
• Android Studio at /usr/local/android-studio
• Flutter plugin version 22.2.1
• Dart plugin version 171.4424
• Java version OpenJDK Runtime Environment (build 1.8.0_152-release-915-b01)
[✓] VS Code (version 1.22.2)
• VS Code at /usr/share/code
• Dart Code extension version 2.11.2
[✓] Connected devices (1 available)
• A18 •<PHONE_NUMBER>ABCDEF • android-arm • Android 4.4.2 (API 19)

I run as flutter run --no-preview-dart-2

I got


Fix for issue #23

i've no env to test it (yet) so if you could deploy it somewhere and provide api i would be happ.
br/piotr

Reopening

@dzebrys, we're not going to merge this specific PR because it is not a fix but rather changes the equipment is handled. Making equipment not deviceclass but more device specific.
If your project is in need for per device equipment - let's chat and include such feature in future devicehive release. We are thinking on large change for 2.1 which may even remove equipment as is now and replace it with more versatile custom data per device and/or per deviceclass. If you have some feedback on that, you can comment on issue #23.


On chat screen emojis are cutted at the top

As we can see, the emoji is cutted on top, I think it's because emojis change the line height

I just removed the add of lineHeights on RkText in bootstrap.js and I removed lineHeights from style files (theme.js and darkTheme.js) and it works.
I didn't test all components, but chat works with emojis now!


ConnectCaller Method connection timeout

I always get connection timeout when calling connectCaller Method, here is error output

Error: Connection timeout
at Timeout.setTimeout [as _onTimeout] (C:\TFS2\Viases-Cloud Project\Viases_Cloud.IVREngine\node_modules\drachtio-fsmrf\lib\mediaserver.js:283:22)
at ontimeout (timers.js:427:11)
at tryOnTimeout (timers.js:289:5)
at listOnTimeout (timers.js:252:5)
at Timer.processTimers (timers.js:212:10)

My drachtio-server and freeswitch docker image runs on different servers.
Update: I also tried to run freeswitch docker image on the same server with drachtio-server, still I get timeout.

I think connection::ready event does not get triggered. Freeswitch either cannot create connection or cannot let drachtio-fsmrf channel is created. _onNewCall method is never called.
mediaserver.js
this._server.on('connection::ready', this._onNewCall.bind(this)) ;


[WIP] change: add buildspec-release file

Issue #, if available:
Description of changes:

fix tox file
use tox instead of pytest in buildspec
add cpu_py3 and gpu_py2 tests in buildspec
add buildspec-release file

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

AWS CodeBuild CI Report

Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


Quality of Life improvements (round 1)

This issue lists a number of quality of life improvements that can and should be added to the tool to increase developer productivity:

[x] The tool should have a "Reset" or "Clean" action which cleans out the environment, in preparation for starting over.

Can start by adding as a Tool the ability to clean out the storage account. We have access to the storage connection string from web.config, so can just clean out using that.
Storage account wise, this is covered by #69.

[ ] It should be possible to run individual steps or a subset of steps during scale unit configuration (for example: to avoid having to run DbSync while only wanting to invoke the configure endpoint in the AOS). Could use Sharprompt for this.
[ ] We should reset the tool after each action instead of quitting completely.
[x] We should provide documentation on how to set up the Azure storage account(s) as there are multiple options in the process and we have no indication on what combinations we support.

https://github.com/microsoft/SCMScaleUnitDevTools/wiki/How-to-create-a-compatible-storage-account

Resetting the tool is covered by #72

Creating issue for the remaining item and closing this.


Issue #148 - Add up direction to dropdown rendering.

This addresses issue #148, which relates to how the dropdown displays in the event there isn't enough space to render it fully.  An up direction has been added.
I verified the change against demo.html, demo-multi-select.html and the three theme html files.

big :+1: for getting this in

Thanks @JeromeLam, I'll try to take a look soon.

Thanks @JeromeLam for this PR :sparkles:
Hope it will be merge soon! :+1:

Thanks @JeromeLam

:+1: Great !

how to disable up direction?

+1
how to disable up direction? On some circumstances its doing something wrong.

This seems to be breaking for me. Perhaps it is for you all too?
The searchInput element is not focused, so opening the dropdown, and beginning to type doesn't work.
The $timeout function seems to be missing a call to now focus() the search input once it has been given the new display property.
$select.searchInput[0].focus();

@JeromeLam would love to get some help from you on this feature.  There are a number of bugs that seem to have come out of this feature #977, #990, #989, #976, #973.

+1; [PR for 989] (https://github.com/angular-ui/ui-select/pull/989) fixes my issue.

Experiencing the same problem. Even when bottom space available is more then top, it still takes a top position.

Restating what I wrote in https://github.com/angular-ui/ui-select/issues/977#issuecomment-119199767.
From usability perspective, its really annoying not to control the direction where things appear.
With the buggy implementation, the version, as it, makes the latest version of ui-select unusable.
The PR #989 fixes the issue of inconsistent behaviour (at least in my design). Although I personally would like to have it configurable.
If this does not get fixed, its better to revert this feature.

@igorlino  Totally agree

Agree with @igorlino.  I updated to the latest version to get the benefit of some other bug fixes I was facing.  While those other bugs indeed have been fixed (nice!), this has made the select unusable for my project.  It seems that when it's automatically showing the options above and you are using the multiselect search, the options don't really drop into place above the input nicely.  See this screenshot, the blue highlighted items should be just above the input, not floating way up there like that:

Would be great if the "opens-up" thing was an option that could be configured off.

+1

Yeah, this kinda hurts... also updated for other bug fixes, but now this.  I agree that if there isn't an option to disable it, it should probably be reverted.

+1 @evillemez

I'm experiencing the same issue as @ramdog and it has made this unusable for me.

ui-select is dead in a broken, inusable state... great, really

it's not anymore usable, please fix  :+1:

Yes... please fix it :smile_cat:

@ramdog can you setup a plunker to reproduce this and try solving asap?

Hey @dimirc - the issue that @igorlino references has an existing one showing the issue:
https://github.com/angular-ui/ui-select/issues/977#issue-83383891
Here it is:
http://plnkr.co/edit/oZCudVaPNc42B7hLYB7j?p=preview
Steps to reproduce

Scroll down to the red field
Start typing admin2

Note that the selection remains "floated" above.

@ramdog take a look https://github.com/angular-ui/ui-select/pull/1212
Thanks for the demo!


fix: set transpile option before extending config

@zhanafe did you see my comment? without knowing if that makes a big difference can you check if it it needs to be updated?


Simplify workflow

Are subworkflows for this workflow necessary?
A subworkflow for every process is overkill making it harder to figure out what the workflow is supposed to do from reading the code. It makes more sense to put at least 2 processes into a subworkflow. To be honest, I don't really see the need for subworkflows for this workflow since there aren't that many steps in this workflow.

Work in progress (https://github.com/nhhaidee/scovtree/pull/11)

This enhancement was addressed by https://github.com/nhhaidee/scovtree/pull/17/commits/d9295d05a0f64d08af35d292dac7e50e2ad4ef92


Fix some datetime functions examples, formatting

@Mytherin I fixed some example outputs of the datetime functions and added some formatting:
GitHub's word-diff is not great so here's a list of the main changes:

age now returns a timestamp and not a date (!)
mons is now months.
TIMESTAMP '1992-03-27' - TIMESTAMP '1992-03-22': previously was INTERVAL 5 DAY, changed to 5 days
dayofyear(TIMESTAMP '1992-03-22'): previously was 81, changed to 82
monthname(TIMESTAMP '1992-09-20'): previously was March, changed to September

There were some missing/extra apostrophes and generate_series was mixed up with range.

Thanks!


Added tests for AverageModelCheckpoint() callback

Fixes #1502 .
@gabrieldemarmiesse, @shun-lin and @Squadrick , Please review.

@shun-lin , @Squadrick - The build is cancelled. I don't understand. Please help

That behavior from github actions is very unexpected. Either the tensorflow org has run out of build minutes, either there is a problem with github itself. I'll try to restart the CI.

@gabrieldemarmiesse , @AakashKumarNain , @shun-lin - Resolved all the reviews except one and modified the code accordingly. The review which is puzzling is to test the functionality of the model. Please give some ideas. I will also try to experiment.

@gabrieldemarmiesse , Changed tmpdir to tmp_path. Also, added last function to test functionality of model by asserting model weights. Please review now.

@googlebot I consent.


Error running plugin google ReferencError: search is not defined.

I seem to be having problems with a lot of the plugins not working.
Error running plugin google ReferenceError: search is not defined
    at Object.googlePlugin [as fn] (file:///usr/lib/cerebro/resources/app.asar/dist/main.bundle.js:29247:14)
    at Object.keys.forEach.error (file:///usr/lib/cerebro/resources/app.asar/dist/main.bundle.js:114849:32)
    at Array.forEach (native)
    at eachPlugin (file:///usr/lib/cerebro/resources/app.asar/dist/main.bundle.js:114847:35)
    at dispatch (file:///usr/lib/cerebro/resources/app.asar/dist/main.bundle.js:114905:6)
    at file:///usr/lib/cerebro/resources/app.asar/dist/main.bundle.js:123521:19
    at Object.onChange (file:///usr/lib/cerebro/resources/app.asar/dist/main.bundle.js:123608:13)
    at onChange (file:///usr/lib/cerebro/resources/app.asar/dist/main.bundle.js:115880:34)
    at Object.executeOnChange (file:///usr/lib/cerebro/resources/app.asar/dist/main.bundle.js:11257:35)
    at ReactDOMComponent._handleChange (file:///usr/lib/cerebro/resources/app.asar/dist/main.bundle.js:101930:39)

In addition, I have tried installing some plugins but they do not seem to be registered.

@mijoharas what version do you use?

Your are using latest version of Cerebro (0.2.6).
(installed from arch cerebro-git aur package).

I didn't notice it earlier, but I reproduce this as well. I think it was caused by https://github.com/KELiON/cerebro/pull/157
Can't start apps anymore, and google plugin is not there.

@maximbaz looks like it is something related to babel or other building stuff because I can reproduce it only in production build. In dev. environment everything works well. So, I'm investigating what is the reason

Yes, I just reached the same conclusion, it is not reproducing with yarn run dev. Interesting...

@maximbaz hm, ok. If I change const here to var it works in production build too. Current status:

Going to use it as a hotfix now. I have no idea what causes this issue, but I'm almost sure that the reason in #148, because I've changed a bit building process there.

@maximbaz I just pushed the fix, but should it be updated somehow for cerebro-git, or it just uses  latest version from master branch?
@mijoharas I think you can try to reinstall it

It just uses the latest code from master branch, no extra change required. Just tested, the search is working again. What a weird issue!

Hi, reinstalling fixes the search issue.
I am still having troubles with the plugins though. The only other error message I can find is:
main.bundle.js:95675 The provided value 'moz-chunked-arraybuffer' is not a valid enum value of type XMLHttpRequestResponseType.

what kind of troubles do you have?

Hi, @maximbaz all of the plugins I have tried installing do not work. devdocs lipsum and linux so far are ones I've tested. (tried typing in devdocs, lipsum and shutdown to test the respective plugins, but nothing but google search and translate seems to come up).
The plugins appear to have installed themselves, and when I install a new plugin nothing seems untoward in either of the consoles.

Could you please open a different issue for that? I can repro it as well, I'll add some details in there.

Thanks @maximbaz new issue is https://github.com/KELiON/cerebro/issues/169


Introduce subscription support in the Wallet crate.

Description
The last bit missing to wrap up #442
The main goal is to add a subscription to CDK Mint updates into the wallet. This feature will be particularly useful for improving the code whenever loops hit the mint server to check status changes.
The goal is to add an easy-to-use interface that will hide the fact that we're connecting to WebSocket and subscribing to events. This will also hide the fact that the CDK-mint server may not support WebSocket updates.
To be fully backward compatible, the HttpClientMethods traits have a new method, subscribe, which will return an object that implements ActiveSubscription.
In the primary implementation, there is a SubscriptionClient that will attempt to connect through WebSocket and will fall to the HTTP-status pull and sleep approach (the current approach), but upper stream code will receive updates as if they come from a stream of updates through WebSocket. This SubscriptionClient struct will also manage reconnections to WebSockets (with automatic resubscriptions) and all the low-level stuff, providing an easy-to-use interface and leaving the upper-level code with a nice interface that is hard to misuse. When ActiveSubscription is dropped, it will automatically unsubscribe.

Notes to the reviewers

Suggested CHANGELOG Updates
Added Websocket subscription to the Wallet.
CHANGED
ADDED
REMOVED
FIXED

Checklist

[x] I followed the code style guidelines
[x] I ran just final-check before committing

[ ] https://github.com/cashubtc/cdk/issues/493


Union crashes on specific polygons when exporting results to polytree under C++

Hi! I encountered a crash with EXC_BAD_ACCESS in BuildTreeD(). Here is sample code that leads to the crash:
void Crashing() {
    // This crashes after up to a few thousand iterations in the loop (can also crash just after a few iterations)
    // Failing in `BuildTreeD` accessing the `OutRec* outrec` in the for loop
    PathD polygon0 = {{135, 190}, {27, 19}, {81, 68}, {287, 245}, {200, 6}};
    PathD polygon1 = {{134, 105}, {142, 209}, {24, 134}, {107, 276}, {104, 295}};

    for (int i{0}; i<1000000; ++i) {
        Clipper2Lib::ClipperD cD;
        Clipper2Lib::PolyTreeD polytree;
        cD.AddSubject({polygon0, polygon1});
        cD.Execute(Clipper2Lib::ClipType::Union, Clipper2Lib::FillRule::NonZero, polytree);
    }
}

void NotCrashing() {
    // This never crashes => Clearing the `ClipperD` instance instead of re-creating
    PathD polygon0 = {{135, 190}, {27, 19}, {81, 68}, {287, 245}, {200, 6}};
    PathD polygon1 = {{134, 105}, {142, 209}, {24, 134}, {107, 276}, {104, 295}};

    Clipper2Lib::ClipperD cD;
    for (int i{0}; i<1000000; ++i) {
        Clipper2Lib::PolyTreeD polytree;
        cD.AddSubject({polygon0, polygon1});
        cD.Execute(Clipper2Lib::ClipType::Union, Clipper2Lib::FillRule::NonZero, polytree);

        cD.Clear();
    }
}

Code provided under MIT license.

Strange, if I change line 3033 in clipper.engine.cpp to
    //for (OutRec* outrec : outrec_list_)
    {
    for (size_t i = 0; i < outrec_list_.size(); ++i)
      OutRec* outrec = outrec_list_[i];

the code runs without a hitch. Which makes me suspect there's an invalid pointer somewhere 😱.

This comment looks relevant, same here in BuildTreeD?

This comment looks relevant, same here in BuildTreeD?

Yes, you're right. Good catch.
Nevertheless I'm concerned that there may be more going on here.

Hopefully fixed now.

That fixed the issue, thanks!


how to install this?

how to install this?

You should be able to install with "pip install downhill" (to install from pypi) or "pip install<EMAIL_ADDRESS>(to install from github).


feat: mirror2mirror capable UX

Closes #62 and #52
Note
This is part one of a two part change to the UX. This PR maintains the current RootOptions which need to be refactored as a follow-on PR.

/lgtm


Newer than expected EFI firmware and build of 10.12.6.

I ran the current build of EFIgy, failed the first two tests, but found that I had newer than expected firmware and OS build. That's how I'm interpreting the results. I participated in Apple's AppleSeed beta-testing program for 10.12.6, which may be why.
Below are the full test results, followed by my interpretation notes.

EFIgyLite API Information:
API Version: 0.2
Updated On: Oct 3 2017, 16:44
Enumerated system informaton (This data will be sent to the API in order to determine your correct EFI version):
Hashed SysUUID   : 6c300eb55df872a187804496eea3e07762c6a4c0bafb3b4b5a4dff0ad0a014ec
Hardware Version : MacBookPro11,3
Boot ROM Version : MBP112.0142.B00
SMC Version      : 2.19f12
Board-ID         : Mac-2BD1B31983FE1663
OS Version       : 10.12.6
Build Number     : 16G1023
[?] Do you want to continue and submit this request? [Y/N]  y
EFI firmware version check:
[-] ATTENTION - You are running an unexpected firmware version given the model of your system (MacBookPro11,3) and OS build you have installed (16G1023). Your firmware MBP112.0142.B00, expected firmware MBP112.0138.B25.
Update your firmware!!
Highest build number check:
[-] ATTENTION - You are NOT running the latest build number of your OS version (10.12.6). Your build number is 16G1023, the latest build number is 16G29
Up-to-date OS check:
[+] SUCCESS - You are running the latest major/minor/micro version of the OS you have installed (10.12.6)

My results show that my MacBookPro11,3 FAILed the EFI firmware test because it has NEWER firmware than was expected. Meanwhile, EFIgy tells me to ‘update’ my firmware. Wrong.

The “Highest build number check” of 10.12.6 FAILed. This one is very odd. I’d been AppleSeed testing 10.12.6. Therefore, it would not be strange for me to have a different build of it on my MBP. However, I’d installed the FULL public installation of 10.12.6 anyway. That means I’m supposed to have the full, final, finished version of 10.12.6 on the MPB. So why do the test results say:

[-] ATTENTION - You are NOT running the latest build number of your OS version (10.12.6). Your build number is 16G1023, the latest build number is 16G29

And how do I interpret this FAIL? If I have build 16G1023, isn’t that well beyond the ‘latest’ 16G29? I think so!

@DerekCurrie I have exactly the same results. Since you're on a beta channel, did you perchance install the Security Update Public Beta 2017-001?

Below are results after re-installing 10.12.6 via the Repair volume on my MacBookPro11,3. Note that this is a different installer than I had previous used, which was the Combo update for 10.12.6. I'll discuss the possible repercussions below. As a result, the test for 10.12.6 build versions passed.

EFI firmware version check:
[-] ATTENTION - You are running an unexpected firmware version given the model of your system (MacBookPro11,3) and OS build you have installed (16G29). Your firmware MBP112.0142.B00, expected firmware MBP112.0138.B40.
Update your firmware!!

Note that I still have the same firmware version. Note that it is still a higher version than what was expected. But also note that the test's 'expected' firmware versions have changed! Why? It points to the test being faulty. Originally expected was ...B25. Now expected ...B40. Huh?!
What I think is going on:
• Duo Labs didn’t take into account the build number difference for the Combo update of 10.12.6. That would explain the higher build number I had in the first test.
• Duo Labs does NOT have a complete list of EFI Firmware versions. I clearly have a MORE RECENT version of the firmware than they expect.
• Duo Labs still has work to do on its flaky software. Having a mismatch between test results regarding expected firmware versions is itself a FAIL.
Conclusion: This version of EFIgy and its corresponding web database are a source of confusion and not much else. Highly disappointing. I cannot recommend anyone bother with it at this point. Sorry.

@zigg:

did you perchance install the Security Update Public Beta 2017-001?

That's unlikely. I am only aware of having installed successive beta versions of specifically 10.12.x. I stayed entirely out of 10.13.x beta testing.

@DerekCurrie It was a security update to 10.12.6. Looks like it was followed by a released patch to 10.12.6? https://support.apple.com/en-us/HT207835

On Oct 4, 2017, at 2:44 PM, Matt Behrens<EMAIL_ADDRESS>wrote:
@DerekCurrie https://github.com/derekcurrie It was a security update to 10.12.6. Looks like it was followed by a released patch to 10.12.6? https://support.apple.com/en-us/HT207835 https://support.apple.com/en-us/HT207835
https://user-images.githubusercontent.com/56017/31193468-2d9e1e1c-a912-11e7-857e-0f152ee50bb0.png
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/duo-labs/EFIgy/issues/6#issuecomment-334252180, or mute the thread https://github.com/notifications/unsubscribe-auth/AIiYcm2Skzbx0Lom1SDbtVa0DNG54BxJks5so9H7gaJpZM4Pt0kL.

I don’t recall. If it was a public security patch AFTER 10.12.6 was publicly released, I would have installed it. But that’s not what you’re asking, from what I can tell. I don’t know anything about a ‘beta’ 10.12.6 security patch that would have come out after 10.12.6 was publicly released.
Note that at this time I have reinstalled 10.12.6 twice after the initial 10.12.6 update. The first time was via the Combo installer. The second time, today, was via what’s fed to the Repair volume on my MacBookPro11,3. The firmware version remained the same between these reinstallations. I would assume that because I have a higher number, the installers would not attempt to install the lower numbers.
Also note that the EFIgy tests didn’t provide consistent ‘expected’ versions of firmware. I elaborated in my added notes at GitHub. That’s bad, resulting in confusion.
:-Derek Currie
————————————
Derek G Currie
<EMAIL_ADDRESS><EMAIL_ADDRESS>————————————

I believe I have a similar issue.  The output of the checker, in part, is:
	[-] ATTENTION - You are running an unexpected firmware version given the model of your system (MacBookPro11,3) and OS build you have installed (15G1611). Your firmware MBP112.0138.B40, expected firmware MBP112.0138.B25.
Update your firmware!!

It seems likely to me that (though I absolutely do not no for sure) that .B40 is more recent that .B25.

Yes, Security Update 2017-001 for Sierra came out on or about Sep 27th for testers. I expect it to be released along with macOS 10.13.1.
-Al-
On Wed, Oct 04, 2017 at 11:55 AM, Derek Currie wrote:

On Oct 4, 2017, at 2:44 PM, Matt Behrens<EMAIL_ADDRESS><EMAIL_ADDRESS>wrote:
@DerekCurrie <https://github.com/derekcurrie https://github.com/derekcurrie> It was a security update to 10.12.6. Looks like it was followed by a released patch to 10.12.6? https://support.apple.com/en-us/HT207835 https://support.apple.com/en-us/HT207835 <https://support.apple.com/en-us/HT207835 https://support.apple.com/en-us/HT207835>
<https://user-images.githubusercontent.com/56017/31193468-2d9e1e1c-a912-11e7-857e-0f152ee50bb0.png https://user-images.githubusercontent.com/56017/31193468-2d9e1e1c-a912-11e7-857e-0f152ee50bb0.png>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <https://github.com/duo-labs/EFIgy/issues/6#issuecomment-334252180 https://github.com/duo-labs/EFIgy/issues/6#issuecomment-334252180>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AIiYcm2Skzbx0Lom1SDbtVa0DNG54BxJks5so9H7gaJpZM4Pt0kL https://github.com/notifications/unsubscribe-auth/AIiYcm2Skzbx0Lom1SDbtVa0DNG54BxJks5so9H7gaJpZM4Pt0kL>.

I don’t recall. If it was a public security patch AFTER 10.12.6 was publicly released, I would have installed it. But that’s not what you’re asking, from what I can tell. I don’t know anything about a ‘beta’ 10.12.6 security patch that would have come out after 10.12.6 was publicly released.
Note that at this time I have reinstalled 10.12.6 twice after the initial 10.12.6 update. The first time was via the Combo installer. The second time, today, was via what’s fed to the Repair volume on my MacBookPro11,3. The firmware version remained the same between these reinstallations. I would assume that because I have a higher number, the installers would not attempt to install the lower numbers.
Also note that the EFIgy tests didn’t provide consistent ‘expected’ versions of firmware. I elaborated in my added notes at GitHub. That’s bad, resulting in confusion.
:-Derek Currie
————————————
Derek G Currie
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>————————————
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/duo-labs/EFIgy/issues/6#issuecomment-334255563, or mute the thread https://github.com/notifications/unsubscribe-auth/AEtvWFlIBhwa6gQklpkN53wLYlK7zCx7ks5so9SxgaJpZM4Pt0kL.

-Al-
Al Varnell
Mountain View, CA

Ah! I figured out the situation. On my end the update is entitled “Security Update Developer Beta 2017-001” with “Developer” being the variant word. I assume this update is exactly what you’re asking about.
IOW: YES, I did!
Therefore, let’s consider that the likely source of the newer EFI firmware.
Sorry for the confusion at my end.
:-Derek

On Oct 4, 2017, at 2:44 PM, Matt Behrens<EMAIL_ADDRESS>wrote:
@DerekCurrie https://github.com/derekcurrie It was a security update to 10.12.6. Looks like it was followed by a released patch to 10.12.6? https://support.apple.com/en-us/HT207835 https://support.apple.com/en-us/HT207835

————————————
Derek G Currie
<EMAIL_ADDRESS><EMAIL_ADDRESS>————————————

I am less clear on why I have a more recent EFI than is expected.  I’m running 10:11:6.  I see the following two updates, that may be relevant:
            <string>Security Update 2017-003</string>
            <string>10.11.6</string>

… and:
macOS
12.6.03
Hope that helps…

blake

I've a similar issue. Why is it asking me to update if I have a newer version?
Thanks!
EFI firmware version check:
	[-] ATTENTION - You are running an unexpected firmware version given the model of your system (MacBookPro11,3) and OS build you have installed (14F2511).
Update your firmware!!

Similar. EFIgy is happy with the Sierra version, but not my 2012 15" non-Retina MacBook Pro’s firmware:
EFI firmware version check:
[-] ATTENTION - You are running an unexpected firmware version given the model of your system (MacBookPro9,1) and OS build you have installed (16G29).
Update your firmware!!
Now unless i’m counting wrong, 00D7.B00 is higher than 00D3.B22.
Maybe it’s a matter of wording. The first part says “unexpected” which may well be true. It’s the last sentence “Update your firmware!!” which appears false.
Note to developers: i ran EFIgy with --debug and saved the entire results. Let me know if you want it, and how to get it to you.
Note 2: I usually only use general release software and trail a year behind Apple (e.g. i just recently upgraded to Sierra). However this year i did participate in the High Sierra Public Beta with this Mac, lastly with the GM candidate. That was on an external test drive, then i reverted to stock Sierra for regular production work on this Mac.

@SonicPurity, As indicated, the tool has not been updated for macOS High Sierra yet, so it knows nothing about the fact that you updated your firmware by running HS. It's also clear that the tool isn't for use by anybody that has participated in a public (or otherwise) beta test since those updates haven't been included and my guess is they won't in the future. It's mostly for Enterprise administrators who need to check machines that are on a regular update track.

As of commit https://github.com/duo-labs/EFIgy/commit/798116c0b5bd827b04febbfd156f4b44ff673985 there is now initial 10.13.x support in the dataset and firmware that appears newer than expected is better messaged to the user.

https://check.efigy.io/ still says that "macOS 10.13 is NOT currently supported". Is that true?

Note that ‘this issue is marked closed, so you may not get a response and need to open a new issue wupith details on your platform, etc.


Throw fingerprint write errors

Per review feedback, reverting part of the changes introduced in https://github.com/apple/swift-package-manager/pull/3928.

@swift-ci please smoke test

@swift-ci please smoke test


Request for "UltraWide Video 21:9" extension

Webextension name: UltraWide Video 21:9
Browser version: 61.0b9
Operating system: Windows 10
Link to the webextension in the AMO store:
https://addons.mozilla.org/en-US/firefox/addon/ultrawide-video-21-9/
What needs to be themed:
https://i.imgur.com/R5l7PFK.png

Hi @SlimF, unfortunately this add-on doesn't appear to be available for macOS, which is something I actually haven't run into before (when I go to the AMO page, I get a message saying "This add-on is not available on your platform.").
Because of this, I won't be able to add a theme for it, but I would gladly accept a pull request if someone else is able to do so.

Well, that's actually an easy one.
@-moz-document url-prefix("moz-extension://{f07fb9b1-1eaf-4d80-85b4-95b32557ba24}/html/popup.html") {
	html {
		background: var(--in-content-box-background) !important;
		color: var(--in-content-page-color) !important;
		border: 3px solid var(--in-content-box-border-color) !important;
}

@overdodactyl I'm not sure if anything else besides creating a new .css file has to be modified to make it work with the updater? I already inserted the extension ID, not the internal UUID.

Thanks @stonecrusher, and sorry for taking so long to get back to you.
The extension ID is all you need for the updater - I usually add ones like this in their one file within the css/userContent-files/webextension-tweaks/ directory and add an @import statement in userContent_imports.css.
Do you want to submit a pull or should I add in that code?

Ok thanks for the info.
It's fine when you add the code :-)

Thanks! Just didn't want to take your code without asking incase you wanted the commit history to reflect it :)


util/read_files_in_dir: return map by value

It's efficient to return std::map as value with NRVO  in C++17.

Great. The original code was probably a premature optimization anyway, the maps are pretty small and the function is only used on process init.


MudHighlighter - unexpected behavior with markup and quotes or other html markups

Things to check

[X] I have searched the existing issues for this bug
[X] To rule out a caching problem I made sure the bug also happens in an incognito tab

Bug type
Component
Component name
MudHighlighter
What happened?
When I try to search for quotation marks or e.g. 'span' with Markup enabled, the component presents an html markup fragment and breaks proper html displaying.
Expected behavior
Display proper highligheted text with markup.
Reproduction link
https://try.mudblazor.com/snippet/mYGebllJSfwoiaPz
Reproduction steps

Checkout snippet
Change highlighted text to span

...
Relevant log output
No response
Version (bug)
7.15.0
Version (working)
No response
What browsers are you seeing the problem on?
Firefox, Chrome, Edge, Safari, Other
On which operating systems are you experiencing the issue?
Windows, macOS, Linux, iOS, Android, Other
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

[X] I agree to follow this project's Code of Conduct

@Anu6is @vernou any interest to check this?
There is another issue as well https://github.com/MudBlazor/MudBlazor/issues/8196

I can take a look, actually skimmed it last week but it needed a deeper dive. Think I can resolve this one... will check out the other one as well.

I am not sure to understand.
@JakubRejman, can you detail your need or the problem?

I quickly looked the example. The tag attribute values are encapsulated between ' instead of ". See this fixed example.

@vernou take a look at @Anu6is answer.
Your example is not a solution.
Now, trying to search for text containing double quotes ("), we get the same result like serching for span. Component returns the result from the underlying HTML and the markup rendering breaks.

@JakubRejman
Sorry, I went too fast. ' is valid to encapsulate attribute value.
Indeed, when the seach founds a part in markup element, it breaks the rendering.

@Anu6is
Indeed, this requires deeper dive.
I'm already struggling with other issues, so I will not give a try before many days.


enable selector as cli overriding option - feature request

I think one of the strong use cases for this program is selecting an option for opening files.
we naturally set a default application for the file types. for some file types, there will be more than one program.
It provides more flexibility to  call selector option (which can be overriding the option set in configuration file, i.e: enable_selector=false).
I request you to provide this option, to selectively call (with this overriding option) this application from other programs.

I would really appreciate this feature. Would make handlr a great launcher for stuff like terminal file browsers where most of the time i want to open with the default application and have a separate binding for letting me select out of the available applications when I need to


UnusedShowInterpolator rule that detects use of the show interpolator without any interpolated variables

Fixes #17

Hmm have you seen this one before @armanbilge?
[error] java.lang.RuntimeException: not a directory or jar file: /home/runner/work/typelevel-scalafix/typelevel-scalafix/target/rules-aggregate/target/scala-2.13/classes
[error] 	at scala.sys.package$.error(package.scala:30)
[error] 	at com.typesafe.tools.mima.lib.MiMaLib.$anonfun$createPackage$1(MiMaLib.scala:13)
[error] 	at scala.Option.getOrElse(Option.scala:189)
[error] 	at com.typesafe.tools.mima.lib.MiMaLib.createPackage(MiMaLib.scala:13)

when trying to run typelevel-scalafix-rules / mimaReportBinaryIssues, so it's specifically the binary compatibility check for the aggregate module.
It seems to be complaining that the class files are missing, but this is an aggregate module so I don't think there will ever be any.

Ooh, ouch. I wonder if it's technically a MiMa bug (i.e. it should handle this situation more gracefully). I guess we can set mimaPreviousArtifacts := Set.empty for that aggregate module. I generally try to avoid this (esp. for temporary fixes) but seems appropriate in this situation.

Looks good! Question: can we implement this rule as a rewrite? Apologies if that's what you've done here 😅 in which case, doesn't it need an output/ test?

Hmm I feel a bit weird about implementing this as a rewrite - if the user didn't mean to add an interpolation then a rewrite works well, but if they did, it silently changes their code in a way that removes the warning that could have alerted them that they've forgotten something. What do you think, is that a bit too hypothetical of a concern?

Ahh, absolutely. Been there done that :) 👍


Bicep REPL

Is your feature request related to a problem? Please describe.
Constructing complicated expressions using one or more built-in functions in Bicep can be tricky, and there is a need to test the expressions. In my experience this is most often string manipulation functions, but it could also be something else. To test these types of expressions today you need to create an actual deployment at a scope in Azure. This is unnecessarily time consuming.
Describe the solution you'd like
A REPL/console experience similar to what Terraform has (terraform console) that has most functions available for testing. Only functions that make sense need to be included, i.e. resourceGroup() would not make sense in a REPL unless you can scope the REPL to a given scope in Azure (e.g. a resource group).
Example:
$ az bicep console
> take('one two three', 3)
'one'
>
> var arrayString = [
  'one'
  'two'
  'three'
]
> join(arrayString, ',')
'one,two,three'

Addendum:
Perhaps the REPL can be started in a given scope by adding a flag to the command, then even scope-like functions like resourceGroup() would be available, e.g.:
$ az bicep console --scope /subscriptions/<id>/resourceGroups/rg-sample
> resourceGroup().location
'swedencentral'
>
> resourceGroup().name
'rg-sample'


Static localization support

Allow static localization of some hardcoded texts

German localization

closed pull request to add some changes


Azure.Security.KeyVault.Certificates Readme issues

Section link

Reason:
1."CONTRIBUTING.md" should be a hyperlink.
Suggestion:
1.Update to [CONTRIBUTING.md][contributing].
And Add:
[contributing]: https://github.com/Azure/azure-sdk-for-net/blob/master/sdk/keyvault/CONTRIBUTING.md
2.Add hyperlink for Conduct FAQ  https://opensource.microsoft.com/codeofconduct/faq/
@jongio for notification

@tzhanl could you submit a PR for this?

PR merged.


Graphs for v2

just the preview how the new design should be of v2

THIS PR Put everyting in v2 so the prototype can be merged to be more added, the reviewer is only for infos about the changes


Multipage Tables get compressed to one Page inside figure

Description
I have a table spanning over multiple pages (abolutely amazing that that just works btw). when i wanted to add a label to the table to reference it, the compiler threw an error and told me to put the table inside a figure. I did that like this
#let results = csv("long.csv")

#figure(
    table(
        columns: 5,
        ..results.flatten()
    ),
    caption: [Indizes tabelle]
)<indices>

Now i can reference the table, but instead of generating multiple pages of table, everything after the first page, gets crampt at the bottom.

Is there a way to expand figures over multiple pages, or do I have to split up the table?
Reproduction URL
No response
Operating system
Windows
Typst version

[X] I am using the latest version of Typst

Maybe related to how figure creates a block(breakable: false) - perhaps we could add a breakable option to figure as well?
https://github.com/typst/typst/blob/main/library/src/meta/figure.rs#L252-L254

I also need a breakable figure. Is there a temporary solution for this?

I also need a breakable figure. Is there a temporary solution for this?

For now you would have to implement figure "manually" (a block with your content and a caption to the end, using some sort of label to be able to reference it, and locate with a counter to automatically generate numbers).
However, I opened a PR to allow breakable figures with show rules, so keep an eye on that.

@PgBiel is there an example on how to create the solution you mentioned? Thank you!

@ldliao my solution is outdated since https://github.com/typst/typst/pull/1121 was merged into Typst v0.4.0; now you just need to write #show figure: set block(breakable: true) somewhere before your figure!

@ldliao my solution is outdated since #1121 was merged into Typst v0.4.0; now you just need to write #show figure: set block(breakable: true) somewhere before your figure!

Thanks for providing this solution. As far as I understand, this will apply the breakable rule globally. Is there a way to apply it only to a specific figure? I tried wrapping the figure into #block(breakable: true)[#figure(...)] but that didn't work.

@jreniel Try something like this:
#{
  show figure: set block(breakable: true)
  figure(..)
}

@jreniel Try something like this:
#{
  show figure: set block(breakable: true)
  figure(..)
}

This way the show-set rule is scoped to just the contents of the block, i.e. the one figure.

Love it, Thanks!

@jreniel Try something like this:
#{
  show figure: set block(breakable: true)
  figure(..)
}

This way the show-set rule is scoped to just the contents of the block, i.e. the one figure.

But doesn't this recursively affect all blocks inside the figure? Now all blocks inside the figure have to be made explicitly non–breakable, if desired. Is this correct?

@jreniel Try something like this:
#{
  show figure: set block(breakable: true)
  figure(..)
}

This way the show-set rule is scoped to just the contents of the block, i.e. the one figure.

But doesn't this recursively affect all blocks inside the figure? Now all blocks inside the figure have to be made explicitly non–breakable, if desired. Is this correct?
@marc-thieme
It's lots of trial and error bro. I'm not a Typst expert, though I still love it.
Last time I had some serious Typst issues that I couldn't resolve even with AI, I ended up going into the Discord with a full description of my problem, and I had a solid answer within a few minutes. Good luck!

@jreniel Try something like this:

#{

show figure: set block(breakable: true)

figure(..)

}

This way the show-set rule is scoped to just the contents of the block, i.e. the one figure.

But doesn't this recursively affect all blocks inside the figure? Now all blocks inside the figure have to be made explicitly non–breakable, if desired. Is this correct?

It's the only way at the moment, because figure implicitly adds #show figure: set block(breakable: false) to its show rule, so you're just reversing that. There aren't non-recursive set rules as of today, but that may be possible in the future.
Though this generally isn't a problem here, and if you'd like to reverse the behavior, you can use #set block(breakable: false) inside the figure, but note that this would contradict your desire as you'd make the table itself unbreakable instead of the figure, potentially leading to the same problem.

I've fiddled with a bit now and I don't mind the current API.
Something which bothers me though is that it's not possible to use show figure: set block(false) to inverse it later in the document. The only way is to scope it with an extra block.

I've fiddled with a bit now and I don't mind the current API. Something which bothers me though is that it's not possible to use show figure: set block(false) to inverse it later in the document. The only way is to scope it with an extra block.

Scoping it is indeed the correct way, however I can't reproduce that behavior. Seems like you meant to write "set block(breakable: false)" instead of just set block(false)?
This works fine for me (the second figure doesn't break):
#show figure: set block(breakable: true)

#figure(
  table(..([a],) * 80),
)

#show figure: set block(breakable: false)

#figure(
  table(..([b],) * 80),
)

With that said, if you don't like using the block, you can always make a function which creates the block for you in a shorter way.
#let breakable-figure(..args) = {
  show figure: set block(breakable: true)
  figure(..args)
}

#breakable-figure(
  table(..([a],) * 80),
)

#figure(
  table(..([b],) * 80),
)

I've fiddled with a bit now and I don't mind the current API. Something which bothers me though is that it's not possible to use show figure: set block(false) to inverse it later in the document. The only way is to scope it with an extra block.

Scoping it is indeed the correct and expected way to only apply a particular style at only one place in general, however I can't reproduce that behavior. Seems like you meant to write "set block(breakable: false)" instead of just set block(false)?
This works fine for me (the second figure doesn't break):
#show figure: set block(breakable: true)

#figure(
  table(..([a],) * 80),
)

#show figure: set block(breakable: false)

#figure(
  table(..([b],) * 80),
)

Oh in that case I need to check on my project again because this if this is possible it changes how I should write my API. I'm going to try it tomorrow.

With that said, if you don't like using the block, you can always make a function which creates the block for you in a shorter way.
#let breakable-figure(..args) = {
  show figure: set block(breakable: true)
  figure(..args)
}

#breakable-figure(
  table(..([a],) * 80),
)

#figure(
  table(..([b],) * 80),
)

There's only one case where this was an issue for me because the figure in the first version is label lable, the block in the second version not.
For instance, I wrote a library where a function needs to return a figure so the user can stick a label onto the figure:
#theorem[Infinite Primes] <theorem>

If the theorem returns a block which includes a show rule, the label does not work unfortunately.


Sign In: Invalid email when using browser suggestion

Describe the bug
In the Sign In form, when using the browser suggestions to fill the email input, the form can't be submitted because the form is invalid.
To Reproduce
Steps to reproduce the behavior:

Go to https://staging.opencollective.com/signin
Use browser suggestion to fill the email input

Screenshots

Environment:

OS: Mac OS
Browser: Firefox 65

More details
When debugging with the following code:
<StyledInput
  error={!!state.error}
  fontSize="Paragraph"
  id="email"
  name="email"
  onChange={({ target }) => {
    console.log('StyledInput', 'onChange', target.value, target.validationMessage);
    onEmailChange(target.value);
    setState({ error: target.validationMessage, showError: false });
  }}

What I get as output on:

Chrome (Mac OS): StyledInput onChange<EMAIL_ADDRESS>Firefox (Mac OS): StyledInput onChange<EMAIL_ADDRESS>Please enter an email address.

So, target.validationMessage is not being reset. Is that an edge case because we're not using it properly or an obvious bug on Firefox side?

@znarf My Firefox was updated to 65.0 and now I'm affected by this too (OS is still Ubuntu 18.04). Do you have a link to the bugzilla's issue so I can report this information?