Synthesis failed for AbusiveExperienceReport

Hello! Autosynth couldn't regenerate AbusiveExperienceReport. :broken_heart:
Here's the output from running synth.py:
2020-12-18 05:02:44,978 autosynth [INFO] > logs will be written to: /tmpfs/src/logs/elixir-google-api
2020-12-18 05:02:45,883 autosynth [DEBUG] > Running: git config --global core.excludesfile /home/kbuilder/.autosynth-gitignore
2020-12-18 05:02:45,886 autosynth [DEBUG] > Running: git config user.name yoshi-automation
2020-12-18 05:02:45,889 autosynth [DEBUG] > Running: git config user.email<EMAIL_ADDRESS>2020-12-18 05:02:45,892 autosynth [DEBUG] > Running: git config push.default simple
2020-12-18 05:02:45,895 autosynth [DEBUG] > Running: git branch -f autosynth-abusiveexperiencereport
2020-12-18 05:02:45,898 autosynth [DEBUG] > Running: git checkout autosynth-abusiveexperiencereport
Switched to branch 'autosynth-abusiveexperiencereport'
2020-12-18 05:02:46,173 autosynth [INFO] > Running synthtool
2020-12-18 05:02:46,173 autosynth [INFO] > ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/abusive_experience_report/synth.metadata', 'synth.py', '--']
2020-12-18 05:02:46,173 autosynth [DEBUG] > log_file_path: /tmpfs/src/logs/elixir-google-api/AbusiveExperienceReport/sponge_log.log
2020-12-18 05:02:46,175 autosynth [DEBUG] > Running: /tmpfs/src/github/synthtool/env/bin/python3 -m synthtool --metadata clients/abusive_experience_report/synth.metadata synth.py -- AbusiveExperienceReport
2020-12-18 05:02:46,390 synthtool [DEBUG] > Executing /home/kbuilder/.cache/synthtool/elixir-google-api/synth.py.
On branch autosynth-abusiveexperiencereport
nothing to commit, working tree clean
2020-12-18 05:02:48,285 synthtool [DEBUG] > Running: docker run --rm -v/tmpfs/tmp/tmpchian2lm/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 AbusiveExperienceReport
DEBUG:synthtool:Running: docker run --rm -v/tmpfs/tmp/tmpchian2lm/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 AbusiveExperienceReport
/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

13:03:19.268 [info]  FETCHING: https://abusiveexperiencereport.googleapis.com/$discovery/GOOGLE_REST_SIMPLE_URI?version=v1

13:03:19.587 [info]  FOUND: https://abusiveexperiencereport.googleapis.com/$discovery/GOOGLE_REST_SIMPLE_URI?version=v1
Revision check: old=20200803, new=20201213, generating=true
Creating leading directories
Writing SiteSummaryResponse to clients/abusive_experience_report/lib/google_api/abusive_experience_report/v1/model/site_summary_response.ex.
Writing ViolatingSitesResponse to clients/abusive_experience_report/lib/google_api/abusive_experience_report/v1/model/violating_sites_response.ex.
Writing Sites to clients/abusive_experience_report/lib/google_api/abusive_experience_report/v1/api/sites.ex.
Writing ViolatingSites to clients/abusive_experience_report/lib/google_api/abusive_experience_report/v1/api/violating_sites.ex.
Writing connection.ex.
Writing metadata.ex.
Writing mix.exs
Writing README.md
Writing LICENSE
Writing .gitignore
Writing config/config.exs
Writing test/test_helper.exs

13:03:19.996 [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 05:03:23,102 autosynth [ERROR] > Synthesis failed
2020-12-18 05:03:23,103 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/abusive_experience_report/synth.metadata', 'synth.py', '--', 'AbusiveExperienceReport']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth is still having trouble generating AbusiveExperienceReport. :sob:
Here's the output from running synth.py:
2020-12-19 05:02:50,256 autosynth [INFO] > logs will be written to: /tmpfs/src/logs/elixir-google-api
2020-12-19 05:02:51,141 autosynth [DEBUG] > Running: git config --global core.excludesfile /home/kbuilder/.autosynth-gitignore
2020-12-19 05:02:51,144 autosynth [DEBUG] > Running: git config user.name yoshi-automation
2020-12-19 05:02:51,147 autosynth [DEBUG] > Running: git config user.email<EMAIL_ADDRESS>2020-12-19 05:02:51,150 autosynth [DEBUG] > Running: git config push.default simple
2020-12-19 05:02:51,153 autosynth [DEBUG] > Running: git branch -f autosynth-abusiveexperiencereport
2020-12-19 05:02:51,157 autosynth [DEBUG] > Running: git checkout autosynth-abusiveexperiencereport
Switched to branch 'autosynth-abusiveexperiencereport'
2020-12-19 05:02:51,415 autosynth [INFO] > Running synthtool
2020-12-19 05:02:51,415 autosynth [INFO] > ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/abusive_experience_report/synth.metadata', 'synth.py', '--']
2020-12-19 05:02:51,415 autosynth [DEBUG] > log_file_path: /tmpfs/src/logs/elixir-google-api/AbusiveExperienceReport/sponge_log.log
2020-12-19 05:02:51,417 autosynth [DEBUG] > Running: /tmpfs/src/github/synthtool/env/bin/python3 -m synthtool --metadata clients/abusive_experience_report/synth.metadata synth.py -- AbusiveExperienceReport
2020-12-19 05:02:51,642 synthtool [DEBUG] > Executing /home/kbuilder/.cache/synthtool/elixir-google-api/synth.py.
On branch autosynth-abusiveexperiencereport
nothing to commit, working tree clean
2020-12-19 05:02:53,443 synthtool [DEBUG] > Running: docker run --rm -v/tmpfs/tmp/tmpvsxygt_t/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 AbusiveExperienceReport
DEBUG:synthtool:Running: docker run --rm -v/tmpfs/tmp/tmpvsxygt_t/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 AbusiveExperienceReport
/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

13:03:26.310 [info]  FETCHING: https://abusiveexperiencereport.googleapis.com/$discovery/GOOGLE_REST_SIMPLE_URI?version=v1

13:03:26.633 [info]  FOUND: https://abusiveexperiencereport.googleapis.com/$discovery/GOOGLE_REST_SIMPLE_URI?version=v1
Revision check: old=20200803, new=20201213, generating=true
Creating leading directories
Writing SiteSummaryResponse to clients/abusive_experience_report/lib/google_api/abusive_experience_report/v1/model/site_summary_response.ex.
Writing ViolatingSitesResponse to clients/abusive_experience_report/lib/google_api/abusive_experience_report/v1/model/violating_sites_response.ex.
Writing Sites to clients/abusive_experience_report/lib/google_api/abusive_experience_report/v1/api/sites.ex.
Writing ViolatingSites to clients/abusive_experience_report/lib/google_api/abusive_experience_report/v1/api/violating_sites.ex.
Writing connection.ex.
Writing metadata.ex.
Writing mix.exs
Writing README.md
Writing LICENSE
Writing .gitignore
Writing config/config.exs
Writing test/test_helper.exs

13:03:27.050 [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 05:03:30,278 autosynth [ERROR] > Synthesis failed
2020-12-19 05:03:30,278 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/abusive_experience_report/synth.metadata', 'synth.py', '--', 'AbusiveExperienceReport']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth is still having trouble generating AbusiveExperienceReport. :sob:
Here's the output from running synth.py:
2020-12-20 05:02:50,749 autosynth [INFO] > logs will be written to: /tmpfs/src/logs/elixir-google-api
2020-12-20 05:02:51,636 autosynth [DEBUG] > Running: git config --global core.excludesfile /home/kbuilder/.autosynth-gitignore
2020-12-20 05:02:51,640 autosynth [DEBUG] > Running: git config user.name yoshi-automation
2020-12-20 05:02:51,643 autosynth [DEBUG] > Running: git config user.email<EMAIL_ADDRESS>2020-12-20 05:02:51,645 autosynth [DEBUG] > Running: git config push.default simple
2020-12-20 05:02:51,648 autosynth [DEBUG] > Running: git branch -f autosynth-abusiveexperiencereport
2020-12-20 05:02:51,652 autosynth [DEBUG] > Running: git checkout autosynth-abusiveexperiencereport
Switched to branch 'autosynth-abusiveexperiencereport'
2020-12-20 05:02:51,912 autosynth [INFO] > Running synthtool
2020-12-20 05:02:51,912 autosynth [INFO] > ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/abusive_experience_report/synth.metadata', 'synth.py', '--']
2020-12-20 05:02:51,912 autosynth [DEBUG] > log_file_path: /tmpfs/src/logs/elixir-google-api/AbusiveExperienceReport/sponge_log.log
2020-12-20 05:02:51,915 autosynth [DEBUG] > Running: /tmpfs/src/github/synthtool/env/bin/python3 -m synthtool --metadata clients/abusive_experience_report/synth.metadata synth.py -- AbusiveExperienceReport
2020-12-20 05:02:52,138 synthtool [DEBUG] > Executing /home/kbuilder/.cache/synthtool/elixir-google-api/synth.py.
On branch autosynth-abusiveexperiencereport
nothing to commit, working tree clean
2020-12-20 05:02:53,946 synthtool [DEBUG] > Running: docker run --rm -v/tmpfs/tmp/tmp677w_xyw/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 AbusiveExperienceReport
DEBUG:synthtool:Running: docker run --rm -v/tmpfs/tmp/tmp677w_xyw/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 AbusiveExperienceReport
/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

13:03:27.197 [info]  FETCHING: https://abusiveexperiencereport.googleapis.com/$discovery/GOOGLE_REST_SIMPLE_URI?version=v1

13:03:27.521 [info]  FOUND: https://abusiveexperiencereport.googleapis.com/$discovery/GOOGLE_REST_SIMPLE_URI?version=v1
Revision check: old=20200803, new=20201213, generating=true
Creating leading directories
Writing SiteSummaryResponse to clients/abusive_experience_report/lib/google_api/abusive_experience_report/v1/model/site_summary_response.ex.
Writing ViolatingSitesResponse to clients/abusive_experience_report/lib/google_api/abusive_experience_report/v1/model/violating_sites_response.ex.
Writing Sites to clients/abusive_experience_report/lib/google_api/abusive_experience_report/v1/api/sites.ex.
Writing ViolatingSites to clients/abusive_experience_report/lib/google_api/abusive_experience_report/v1/api/violating_sites.ex.
Writing connection.ex.
Writing metadata.ex.
Writing mix.exs
Writing README.md
Writing LICENSE
Writing .gitignore
Writing config/config.exs
Writing test/test_helper.exs

13:03:27.951 [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 05:03:31,163 autosynth [ERROR] > Synthesis failed
2020-12-20 05:03:31,164 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/abusive_experience_report/synth.metadata', 'synth.py', '--', 'AbusiveExperienceReport']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth is still having trouble generating AbusiveExperienceReport. :sob:
Here's the output from running synth.py:
2020-12-21 05:02:45,479 autosynth [INFO] > logs will be written to: /tmpfs/src/logs/elixir-google-api
2020-12-21 05:02:46,367 autosynth [DEBUG] > Running: git config --global core.excludesfile /home/kbuilder/.autosynth-gitignore
2020-12-21 05:02:46,371 autosynth [DEBUG] > Running: git config user.name yoshi-automation
2020-12-21 05:02:46,374 autosynth [DEBUG] > Running: git config user.email<EMAIL_ADDRESS>2020-12-21 05:02:46,378 autosynth [DEBUG] > Running: git config push.default simple
2020-12-21 05:02:46,381 autosynth [DEBUG] > Running: git branch -f autosynth-abusiveexperiencereport
2020-12-21 05:02:46,386 autosynth [DEBUG] > Running: git checkout autosynth-abusiveexperiencereport
Switched to branch 'autosynth-abusiveexperiencereport'
2020-12-21 05:02:46,675 autosynth [INFO] > Running synthtool
2020-12-21 05:02:46,675 autosynth [INFO] > ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/abusive_experience_report/synth.metadata', 'synth.py', '--']
2020-12-21 05:02:46,675 autosynth [DEBUG] > log_file_path: /tmpfs/src/logs/elixir-google-api/AbusiveExperienceReport/sponge_log.log
2020-12-21 05:02:46,678 autosynth [DEBUG] > Running: /tmpfs/src/github/synthtool/env/bin/python3 -m synthtool --metadata clients/abusive_experience_report/synth.metadata synth.py -- AbusiveExperienceReport
2020-12-21 05:02:46,918 synthtool [DEBUG] > Executing /home/kbuilder/.cache/synthtool/elixir-google-api/synth.py.
On branch autosynth-abusiveexperiencereport
nothing to commit, working tree clean
2020-12-21 05:02:48,694 synthtool [DEBUG] > Running: docker run --rm -v/tmpfs/tmp/tmprajj5564/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 AbusiveExperienceReport
DEBUG:synthtool:Running: docker run --rm -v/tmpfs/tmp/tmprajj5564/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 AbusiveExperienceReport
/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

13:03:23.193 [info]  FETCHING: https://abusiveexperiencereport.googleapis.com/$discovery/GOOGLE_REST_SIMPLE_URI?version=v1

13:03:23.535 [info]  FOUND: https://abusiveexperiencereport.googleapis.com/$discovery/GOOGLE_REST_SIMPLE_URI?version=v1
Revision check: old=20200803, new=20201213, generating=true
Creating leading directories
Writing SiteSummaryResponse to clients/abusive_experience_report/lib/google_api/abusive_experience_report/v1/model/site_summary_response.ex.
Writing ViolatingSitesResponse to clients/abusive_experience_report/lib/google_api/abusive_experience_report/v1/model/violating_sites_response.ex.
Writing Sites to clients/abusive_experience_report/lib/google_api/abusive_experience_report/v1/api/sites.ex.
Writing ViolatingSites to clients/abusive_experience_report/lib/google_api/abusive_experience_report/v1/api/violating_sites.ex.
Writing connection.ex.
Writing metadata.ex.
Writing mix.exs
Writing README.md
Writing LICENSE
Writing .gitignore
Writing config/config.exs
Writing test/test_helper.exs

13:03:23.948 [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 05:03:26,960 autosynth [ERROR] > Synthesis failed
2020-12-21 05:03:26,961 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/abusive_experience_report/synth.metadata', 'synth.py', '--', 'AbusiveExperienceReport']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth is still having trouble generating AbusiveExperienceReport. :sob:
Here's the output from running synth.py:
2020-12-22 05:02:37,115 autosynth [INFO] > logs will be written to: /tmpfs/src/logs/elixir-google-api
2020-12-22 05:02:37,978 autosynth [DEBUG] > Running: git config --global core.excludesfile /home/kbuilder/.autosynth-gitignore
2020-12-22 05:02:37,981 autosynth [DEBUG] > Running: git config user.name yoshi-automation
2020-12-22 05:02:37,984 autosynth [DEBUG] > Running: git config user.email<EMAIL_ADDRESS>2020-12-22 05:02:37,986 autosynth [DEBUG] > Running: git config push.default simple
2020-12-22 05:02:37,989 autosynth [DEBUG] > Running: git branch -f autosynth-abusiveexperiencereport
2020-12-22 05:02:37,992 autosynth [DEBUG] > Running: git checkout autosynth-abusiveexperiencereport
Switched to branch 'autosynth-abusiveexperiencereport'
2020-12-22 05:02:38,247 autosynth [INFO] > Running synthtool
2020-12-22 05:02:38,247 autosynth [INFO] > ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'clients/abusive_experience_report/synth.metadata', 'synth.py', '--']
2020-12-22 05:02:38,247 autosynth [DEBUG] > log_file_path: /tmpfs/src/logs/elixir-google-api/AbusiveExperienceReport/sponge_log.log
2020-12-22 05:02:38,249 autosynth [DEBUG] > Running: /tmpfs/src/github/synthtool/env/bin/python3 -m synthtool --metadata clients/abusive_experience_report/synth.metadata synth.py -- AbusiveExperienceReport
2020-12-22 05:02:38,464 synthtool [DEBUG] > Executing /home/kbuilder/.cache/synthtool/elixir-google-api/synth.py.
On branch autosynth-abusiveexperiencereport
nothing to commit, working tree clean
2020-12-22 05:02:40,204 synthtool [DEBUG] > Running: docker run --rm -v/tmpfs/tmp/tmpr95exww8/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 AbusiveExperienceReport
DEBUG:synthtool:Running: docker run --rm -v/tmpfs/tmp/tmpr95exww8/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 AbusiveExperienceReport
/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

13:03:10.307 [info]  FETCHING: https://abusiveexperiencereport.googleapis.com/$discovery/GOOGLE_REST_SIMPLE_URI?version=v1

13:03:10.653 [info]  FOUND: https://abusiveexperiencereport.googleapis.com/$discovery/GOOGLE_REST_SIMPLE_URI?version=v1
Revision check: old=20200803, new=20201213, generating=true
Creating leading directories
Writing SiteSummaryResponse to clients/abusive_experience_report/lib/google_api/abusive_experience_report/v1/model/site_summary_response.ex.
Writing ViolatingSitesResponse to clients/abusive_experience_report/lib/google_api/abusive_experience_report/v1/model/violating_sites_response.ex.
Writing Sites to clients/abusive_experience_report/lib/google_api/abusive_experience_report/v1/api/sites.ex.
Writing ViolatingSites to clients/abusive_experience_report/lib/google_api/abusive_experience_report/v1/api/violating_sites.ex.
Writing connection.ex.
Writing metadata.ex.
Writing mix.exs
Writing README.md
Writing LICENSE
Writing .gitignore
Writing config/config.exs
Writing test/test_helper.exs

13:03:11.060 [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 05:03:14,077 autosynth [ERROR] > Synthesis failed
2020-12-22 05:03:14,077 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/abusive_experience_report/synth.metadata', 'synth.py', '--', 'AbusiveExperienceReport']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth passed, closing! :green_heart:


Add info-json JSON schema

Before submitting a pull request make sure you have:

[ ] At least skimmed through adding new extractor tutorial and youtube-dl coding conventions sections
[x] Searched the bugtracker for similar pull requests
[ ] Checked the code with flake8

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[ ] Bug fix
[ ] Improvement
[ ] New extractor
[x] New feature

Description of your pull request and other information
This adds a JSON schema for the JSON file generated when the --write-info-json argument is used. I have run this schema (using jsonschema) on 20,000+ JSON files I have and it passes. This covers all fields and data types I encountered.
This could allow the --load-info-json functionality to validate the passed in JSON file, and allows other tools to confidently interact with the data.

Current implementation does not guarantee actual JSON to match this schema.
Schema should mention only documented fields.

@dstftw If you want me to make changes, I'll need to re-make this PR. I asked GitHub and they cannot fix branch references.
Also I can base off #21822 too.


Media Keys

Hey,
Your app si almost perfect, all it lacks is media keys support, is this something you are thinking of implementing?
Thank you very much for sharing this app!

Hi! I didn't expect anyone to use the program, I made it for myself.
I am glad that the program turned out to be useful for you.
I will add support for multimedia keys

Wow, such a fast response, thank you!
Maybe add a donate button to the project? Would like to buy you a beer!

Many thanks! I added the button.

I made a new release with support for multimedia keys.

Wow, works great! Thank you!


issue#695

I cannot seem to be able to get a key to redeem can someone help

Thank you for reporting.
Currently we have another problem on installation.
Please check https://github.com/polygraphene/ALVR/issues/695#issuecomment-757471079
Originally posted by @polygraphene in https://github.com/polygraphene/ALVR/issues/697#issuecomment-757480106

Thank you for reporting.
Currently we have another problem on installation.
Please check https://github.com/polygraphene/ALVR/issues/695#issuecomment-757471079
Originally posted by @polygraphene in https://github.com/polygraphene/ALVR/issues/697#issuecomment-757480106


java.lang.IllegalArgumentException when trying to get CamelContext as EJB @Resource

Having:

WildFly 10.1 running with standalone.xml

Installed wildfly-camel-plugin over existing WildFly standalone.xml configuration ( by: bin/fuseconfig.sh --configs=camel --enable )

Camel context started with Sample-camel-context.xml as described here: https://wildflyext.gitbooks.io/wildfly-camel/content/features/context-deployments.html

EJB @Singleton with @Resource(name = "java:jboss/camel/context/mycontext")   CamelContext camelContext;

Then:
EJB @Singleton bean in EAR EJB module raises java.lang.IllegalArgumentException when trying to initialize camelContext
The same EJB @Singleton in EAR WAR module file works fine
Attached is stack trace
trace.txt

I have not been able to reproduce this. We have some integration tests for EJB EAR deployments. I created a simple singleton bean, into which two Spring Camel contexts are injected.
When the test runs and the hello method is invoked, I see the sysout messages appear in the console log.
Do you perhaps have a unit test or some example code that replicates the problem?

Hi James,
I will try to prepare an arrangement to the end of the month. I thing about EAR with small 1 WAR and 1 EJB module but without any testing environments like junit or arquillian. Do you think it will be ok ?
best regardsPaweł
On Wednesday, December 14, 2016 3:19 PM, James Netherton<EMAIL_ADDRESS>wrote:

I have not been able to reproduce this. We have some integration tests for EJB EAR deployments. I created a simple singleton bean, into which two Spring Camel contexts are injected.When the test runs and the hello method is invoked, I see the sysout messages appear in the console log.Do you perhaps have a unit test or some example code that replicates the problem?—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Yes, that's fine. Thanks!

Now the same EJB moved from WAR module to EJB module works fine. I am not able to reproduce the error :)

Thanks for retesting!


Feature request: ability to control the brightness value at which a color is considerd dark or light

Currently the isDark and isLight is determined by checking the brightness against a static 128 value, however it would be nice to be able to adjust this value(I've found, for example, that 170 fits my needs better). Potentially add an option in the constructor, maybe as part of TinyColorOptions: {brightnessThreshold: number}.
I'm aware that you can get around it by doing const isDark = tinyColor.getBrightness() < 170;, but this proposal would allow the user to create a wrapper around TinyColor, and have a default brightness threshold across the entire app, and not have to manually specify it every time.

sounds very reasonable


Add a 16-bit 'tank' or 'volume' object ID

It would be convenient to have a tank level (or volume, though that term can be misconstrued) object ID measuring in Gallons (or Liters for the metrically inclined).  I have water and heating-oil tanks that I monitor. Today, I can use percent, distance, or count fields, but it would be nice to have a specified object-id with appropriate volume units.

I will add that. I prefer to use "Volume", to make it useable in general for all kind of things (e.g. water consumption).
What kind of precision do you want. With 16 bit, you can have:

[ ] 65535 gallons/liters --> 0 decimals
[ ] 6553.5 gallons/liters --> 1 decimals
[ ] 655.35 gallons/liters --> 2 decimals

A standard heating oil tank in the US is 270gal (1022liters) (a double is 540gal).  I want to measure a 1500gal(5700 liter) water tank, but there is no standard for that and tanks could be much bigger or smaller.  55gal (208l) drums are also standard, as are 5-gal tanks.  On more consideration, I think you should probably stick with metric-only units.  Currently I see only 1 sensor that is imperial (0x07 - lb), and gallons are worse because there are multiple standards (the imperial gallon is 1.2 US gal).
I'm not sure a single decimal will cover all cases.  For my uses 0 or 1 decimal would be fine, but for a larger tank, you'd require 0 decimals, and for a 5gal tank, you'd want at least 1 decimal.  Another option would be 1 decimal with a 24bit value, which probably has sufficient range for most applications.  Anything smaller than that would probably be measured in ml.
If you want my recommendation, maybe 2 sensors
Volume(liters) - 24bit - 1 decimal
Volume(milileters) 16bit - 0 decimal
Also, while I don't currently have much use for it, flow-rate is another sensor to consider (my guess is that liters/sec 16 bit, 1 decimal would cover most needs).  But as I said, I don't have a use for such a sensor at this time.

I have started with adding these to the sensor-state-data pypi package, which we use.
https://github.com/Bluetooth-Devices/sensor-state-data/pull/45
For "volume flow rate", there was already a unit "m3 per hour" apparently, I will use that if that is ok with you?
I guess 1 digit will be ok.

Thanks.
I will reiterate that I don't currently have a direct need for flow-rate, so I am mostly speculating as to what it is useful for.  I'm thinking of things like household water usage, well pumps,  or monitoring fish tank pumps.  These would all do well with liters/min as a unit, and you will likely need more decimal points to use m^3/hr as a metric.
For instance, a low-flow shower head uses ~1.2gal/min which would be ~.273 m^3/hour
Also, having recently run out of space in the advertising payload, I guess 24bit values are not idea, and it is better to stick with 16bit values as much as possible.

Fixed in 2.4.0.
Will be added in HA with this PR https://github.com/home-assistant/core/pull/84189


There is a way to clear any selection made?

I have a native <select>, when I pick an option I store the value and reset its selectedIndex, just because the first element is just a placeholder with no value.
I tried to achieve the same with Choices, but I didn't found yet any method to clear the selection, everything else is fine. 👍
Edit: even a method for selecting the placeholder would be enough too. Or an option for disabling Choices from changing anything (but keep the events for capture choice, etc.)

Hi @pateketrueke,
Could you comment with your Choices setup so I can get a better understanding of what you mean please :)

Well, I did this:
const $select = document.querySelector('select');
$select.addEventListener('change', e => {
  console.log(e.target.value); // do domething with the value
  e.target.selectedIndex = 0; // the first <option> is just a aplceholder
});

I tried to replicate the same with Choices but I have no luck.

So are you just trying to reselect the placeholder choice (first element in dropdown) after each selection?

That's exactly what I'm looking for...

You could use setValueByChoice if you know the value of the placeholder.
I would be happy to review a pull request where this method could also take an index!


Update scala-library to 2.13.11

About this PR
📦 Updates org.scala-lang:scala-library from 2.13.4 to 2.13.11
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-lang", artifactId = "scala-library" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scala-lang", artifactId = "scala-library" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:n:2

Superseded by #87.


Visual Studio Code not opening in full screen on version 1.95.3 for projects closed in full screen. Also, for some time now, Search has been opening in expanded form upon launch. I am running Ubuntu 22.04.1 LTS.

Does this issue occur when all extensions are disabled?: Yes/No
Yes

VS Code Version: 1.95.3
OS Version: Ubuntu 22.04.1 LTS

Steps to Reproduce:

Open a project and press F11 to enter full screen mode.
Press Alt+F4 to close the project.
Open the project again—it'll not open in full screen.

Visual Studio Code Not Opening in Full Screen
If Visual Studio Code isn't opening in full screen mode when you previously closed it in that state, you can try the following steps:

Toggle Full Screen: When you open VS Code, try pressing F11 to toggle full screen mode manually.
Check Settings: Sometimes, settings can affect how applications remember their window state. You can check if there are any settings related to window management in VS Code:
Open VS Code.
Go to File > Preferences > Settings (or press Ctrl + ,).
Search for "window" and look for any settings related to window size or full screen.
Update VS Code: Ensure you’re using the latest version of VS Code, as updates often fix bugs. You can check for updates by going to Help > Check for Updates.
Reset Window State: Sometimes, resetting the window state can help:
Close VS Code.
Open a terminal and run the following command to reset the window state:
bash
rm -rf ~/.config/Code/User
Restart VS Code.
2. Search Opening in Expanded Form
If the Search panel is opening in expanded form by default, you can try these steps:
Toggle Search Panel: You can manually close the Search panel by clicking on the "X" or pressing Ctrl + Shift + F to toggle it.
Check for Extensions: Sometimes, extensions can modify the default behavior of the editor. Try disabling extensions to see if one of them is causing the issue.
Settings Reset: Similar to the previous issue, you can reset your settings to default:
Open the command palette with Ctrl + Shift + P.
Type Preferences: Open Settings (JSON).
Backup your current settings and then clear the contents to reset to default.
Additional Steps
If the above solutions don’t work, consider the following:
Reinstall VS Code: Uninstall and then reinstall Visual Studio Code to see if that resolves the issues. You can do this with the following commands:
bash
sudo apt remove code
sudo apt install code
Check for System Updates: Ensure your system is up to date. Run:
bash
sudo apt update
sudo apt upgrade
If these steps don’t resolve your issues, please let me know, and we can explore further troubleshooting options!

It is now working after toggling the extensions on and off. I appreciate the support.


Make the boxes on the MS dashboard links

I keep trying to click on the 'Flagging' box to go to https://metasmoke.erwaysoftware.com/flagging, and the 'feedback' box to go to https://metasmoke.erwaysoftware.com/admin/user_feedback?user_id=59. I also think that the 'Posts today' box should link to https://metasmoke.erwaysoftware.com/posts. This would be more useful than them just sitting there.

Done in 2fdf7c1c5727a1ef7078e6d88ce983ead61bb83c; lint fixed in ac85be2d51e13abd8343f9d62ca2c9ba80bfbe80


fix: don't use mixin for menus

fixes #93
while it helped reduce a little bit of code duplication, i was never particularly happy with the _MenuMixin anyway.  So this just removes it

@Czaki, this is now working on PySide6 everywhere but linux, where we're now seeing:
tests/test_qt/test_demos.py qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
[117](https://github.com/pyapp-kit/app-model/actions/runs/4613142601/jobs/8154827820?pr=95#step:6:120)
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.
[118](https://github.com/pyapp-kit/app-model/actions/runs/4613142601/jobs/8154827820?pr=95#step:6:121)

[119](https://github.com/pyapp-kit/app-model/actions/runs/4613142601/jobs/8154827820?pr=95#step:6:122)
Available platform plugins are: xcb, eglfs, offscreen, vnc, wayland, minimalegl, linuxfb, vkkhrdisplay, minimal, wayland-egl.
[120](https://github.com/pyapp-kit/app-model/actions/runs/4613142601/jobs/8154827820?pr=95#step:6:123)

[121](https://github.com/pyapp-kit/app-model/actions/runs/4613142601/jobs/8154827820?pr=95#step:6:124)
Fatal Python error: Aborted
[122](https://github.com/pyapp-kit/app-model/actions/runs/4613142601/jobs/8154827820?pr=95#step:6:125)

do you know if PySide 6.5.0 added library dependencies that need to be added to setup-qt-libs?

do you know if PySide 6.5.0 added library dependencies that need to be added to setup-qt-libs?

I think it is a general Qt problem, and it now requires libxcb-cursor0. (The PyQt6 last release is 6.4.2).  I have created PR to setup-qt-libs


Multi Selection: using multiple views in simple item.

Hi,
Please give me a code snippet showing.

How to apply ClickListener for views within an item?
How to Toggle the view colors on selected item, in onSelectionChanged() method?

Currently I can get the selected item and selection state, when clicked on outside of a card view.
But when I click on the card view the item is not selected.
The card view has a TextView within it, the user can either click on the card view or the text view to select an item but not outside the card view.
When clicked I want to toggle the color of the card view and text color of TextView.
I have gone through the sample code and the blog post, but unable to figure out how to implement the above two actions.
Thank you,
Mani

Hi,
For your first question take a look at the sample in the readme.
https://github.com/mikepenz/FastAdapter#4-click-listeners-for-views-inside-your-item
You can add as many event hooks as you need to.
To toggle the view color when an item gets selected, just use the isSelected() to check if the item is selected or not inside onBind. When you have click listeners in your item, make sure there don´t stop intercepting the click event to the itemView.

Hi,
Thank you for the quick reply.
Here is the code snippet, i tried as per your answer:
`mFastAdapter.withEventHook(new ClickEventHook() {
private CardView cardView;
private TextView textView;
        @Nullable
        @Override
        public View onBind(@NonNull RecyclerView.ViewHolder viewHolder) {
            //return the views on which you want to bind this event
            if (viewHolder instanceof VccMaterialItem.ViewHolder) {
                cardView = ((VccMaterialItem.ViewHolder) viewHolder).mCardView;
                textView = ((VccMaterialItem.ViewHolder) viewHolder).mTextView;

                if (cardView.isSelected()) {
                    cardView.setCardBackgroundColor(getActivity().getResources().getColor(R.color.app_green_dark));
                    textView.setTextColor(getActivity().getResources().getColor(R.color.app_white));
                } else {
                    cardView.setCardBackgroundColor(getActivity().getResources().getColor(R.color.app_light_blue_50));
                    textView.setTextColor(getActivity().getResources().getColor(R.color.primary_text));
                }
                return cardView;
            } else {
                return null;
            }
        }

        @Override
        public void onClick(View v, int position, FastAdapter<VccMaterialItem> fastAdapter, VccMaterialItem item) {
            //react on the click event
            Logger.i("Clicked [%s]", item.getText());
        }
    });`

I m getting the logger output when clicked on the cardview, but i m not able to toggle the color inside the onBind() method.

The onBind of the event hook is only there to return the view the click listener should bind to and nothing more.

I am sorry, I do not understand how it is implemented in code.
Kindly show me a code snippet to toggle the view color on select/unselect.

Now I have moved the view color toggling to onClick() method,
@Override
            public void onClick(View v, int position, FastAdapter<VccMaterialItem> fastAdapter, VccMaterialItem item) {
                //react on the click event
                Logger.i("Clicked [%s]", item.getText());
                if (cardView.isSelected()) {
                    cardView.setCardBackgroundColor(getActivity().getResources().getColor(R.color.app_green_dark));
                    textView.setTextColor(getActivity().getResources().getColor(R.color.app_white));
                } else {
                    cardView.setCardBackgroundColor(getActivity().getResources().getColor(R.color.app_light_blue_50));
                    textView.setTextColor(getActivity().getResources().getColor(R.color.primary_text));
                }
            }

Still no luck. Please help, I need to make a great app.
Thank you,
Mani

like i said use for your normal viewbindings the bind of the item and for click handling the onClick.

Accessing any view inside onClick affects another view in the list since the views are recycled. I found out that this line is responsible for setting the background to RED color in the FastAdapter sample.
//set the background for the item
UIUtils.setBackground(viewHolder.view, FastAdapterUIUtils.getSelectableBackground(ctx, Color.RED, true));

Similarly I tried in my app,
UIUtils.setBackground(viewHolder.mCardView, FastAdapterUIUtils.getSelectableBackground(ctx, Color.GREEN, true));

It will set the background for the card view to GREEN in selected state with the ripple effect which is the desired result, in unselected state the view is invisible.
It would be very grateful if you can explain why it is invisible in unselected state? Is it something do with the LinearLayout within which the card view is placed?
Thank you,

@manid2 seems to be related to the CardView or so. It is not really related to this library.
There might be some weird behaviour of a CardView in a RecyclerView...
Please see here: https://github.com/mikepenz/FastAdapter/issues/495

@mikepenz Thank you for pointing me to post #495. I will try this method to see if it works in my app.
Thank you for the good support. :relaxed:

Hi @mikepenz , I tried the method in #495, it works in my app. I used FrameLayout and set its foreground as it is implemented in the sample app.
viewHolder.view.setForeground(FastAdapterUIUtils.getSelectablePressedBackground(ctx, FastAdapterUIUtils.adjustAlpha(color, 100), 50, true));

Thank you for the answers, I am happy 😃.


Add tests for getting Istio Proxy image path and refactor code

Post PR to:

https://github.com/kyma-incubator/reconciler/pull/1080

Issue:

https://github.com/kyma-incubator/reconciler/issues/1079

/retest

/retest

/retest

/retest

/retest


Admin footer menu

I think it would be a good design choice to have all front-end admin actions in a special admin menu in the footer (see the mock designs).
This means:

At the home page:

The start / join shift buttons

At the shift overview page

A button to join baking the shift

At the shift admin

A button to switch the allow/disallow order status
A button to extend the shift end date with 10 minutes
A button to increase the shift capacity (if almost reached)
A button to place an order yourself
Maybe more....?

Should we really do start/join shift buttons on the home page? The way they are right now are more nice I think.


[Sword World 2.5] New features

Submission Checklist
Required

[x] The pull request title clearly contains the name of the sheet I am editing.
[x] The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).
[x] The pull request makes changes to files in only one sub-folder.
[x] The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)

New Sheet Details

The name of this game is: <   >  (i.e. Dungeons & Dragons 5th Edition, The Dresden Files RPG)

The publisher of this game is: <   > (i.e. Wizards of the Coast, Evil Hat)

The name of this game system/family is: <   > (i.e. Dungeons & Dragons, FATE)

[x] I have followed the Character Sheets Standards when building this sheet.

[ ] This sheet has been made on behalf of, or by, the game's publisher.
[ ] This game is not a traditionally published game, but a copy of the game rules can be purchased/downloaded/found at: <   >
[ ] This sheet is for an unofficial fan game, modification to an existing game, or a homebrew system.

Changes / Description

Fellow sheet w/ expanded and rolls
Fellow sheet autocalc switch
Enhancements for stats (MP/HP/Abilities/etc.) that can be added on top of calc
Work skills (toggle on in settings)
Improved monster section name style
Bug: declared action icon on monster sheet
Roll button for token actions with context sensitivity
Bug: alchemist cards show on 0

Character Sheet Info Roll20 Internal Use only.


Define scenario and assumptions on product level requirements

Scenario:
Starting on the surface of the moon and using only human power and stored energy from human power input, accelerate a human and bicycle into orbit around the moon at a low altitude. Except for the road/track infrastructure, the e-bike and human system shall be self contained. The system shall be an e-bike.
See top level requirements notebook:


Improvements for ndloc and sampling

A while ago we added ndloc as a means to provide array like integer indexing for gridded Datasets. This has worked out well overall and this PR simply builds on top of that. In particular this PR adds an out-of-bounds IndexError when sampling outside the Image bounds. Secondly it adds an xarray ndloc implementation, which should be more efficient than the generic implementation that we currently have, ensure that the datatype doesn't change when sampling and selecting and also ensure that any xarray variables that are not referenced by HoloViews aren't dropped after a slicing operation. Also added a number of additional unit tests ensuring that the implementations behave identically.

Ready to merge.


Revert QC level to full force when PCO import is fixed

Revert this commit:
https://github.com/FlyBase/drosophila-phenotype-ontology/pull/62/commits/7326d115a4333dac38c9c04a1db1a6f80d3d3e51
When PCO gets rid of of the axioms:
        <rdfs:isDefinedBy rdf:resource="http://www.geneontology.org/formats/oboinowl.owl"/>

Wait for:
https://github.com/PopulationAndCommunityOntology/pco/issues/78


GH-1986 use line separator

GitHub issue resolved: #1986
Briefly describe the changes proposed in this PR:

(backport) use line separator when comparing output

@barthanssens can I ask what merge strategy you used to merge this PR?
The reason I ask is that it shows up rather oddly in the git log on master, as both a normal commit as well as a merge commit:
d527d6d23 Merge pull request #2002 from Fedict/GH-1986-arrangedwritertest-crlf-backport
f937b905b GH-1986 use line separator Signed-off-by:Bart Hanssens<EMAIL_ADDRESS>
Yours is not the only one PR with this behavior btw - I'm just trying to figure out what causes it.


Update version to 1.0.77-0 on staging

Update version to 1.0.77-0

🚀 Deployed to production         in version: 1.0.77-5🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Support account alias

Pretty please!

solved in https://github.com/OlafConijn/AwsOrganizationFormation/commit/40a79022a6a6b8d6045147b2717dec043d1ec13a


Enhancement: Check if a condition is met before the polling interval has elapsed.

What happened:
An instant first tick is preferred over long running operations, which may have a particular condition satisfied already.
https://github.com/ppc64le-cloud/pvsadm/blob/d2d3bd1406b9b8ce6a647c8d00db6b7bf58ffd67/pkg/utils/utils.go#L59-L71

What you expected to happen:
The condition to be checked once when the function is invoked, to cut down on waiting for a condition that may already be achieved.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
https://stackoverflow.com/questions/32705582/how-to-get-time-tick-to-tick-immediately
Environment:

pvsadm version (use pvsadm --version):
Environment - On-Prem or IBM PowerVS:
OS (e.g: cat /etc/os-release):
Kernel (e.g. uname -a):
Others:

/good-first-issue

/assign

/remove-kind bug
/kind feature

Fixed with #680.
/close


Call parent tearDown method to allow additional extension

Users may want to adjust the setUp and tearDown steps of their test suite. In the current arrangement, calling parent::setUp is required as it needs to make it's way up into Laravel but it allows allows users to customise the set up in their TestCase. Adding a parent call for tearDown allows users to customise the tear down procedure as well.
I have a possible use case for this - my current test suite often causes a MySQL "too many connections" error when run. If I call DB::disconnect() in my tearDown I'm able to prevent this from happening. While I don't think it's worth hard-coding this into DbTestCase it's important to provide users the option.

Thanks!


Merge to stable

Codecov Report

:exclamation: No coverage uploaded for pull request base (stable@151175e). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             stable      #37   +/-   ##
=========================================
  Coverage          ?   47.81%
=========================================
  Files             ?       10
  Lines             ?      274
  Branches          ?        0
=========================================
  Hits              ?      131
  Misses            ?      143
  Partials          ?        0

Continue to review full report at Codecov.

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


Create Posts “20230104-a-visual-guide-to-react-rendering-cheat-sheet”

Automatically generated by Netlify CMS

👷 Deploy Preview for thehashtable processing.

Name
Link

🔨 Latest commit
a027feb7514609181e4fdbfbcb653f974ecb3992

🔍 Latest deploy log
https://app.netlify.com/sites/thehashtable/deploys/63b602f828d8540008c80bbe


Clipboard does not copy ascii text from atom to firefox

When attempting to copy text from atom to a different program such as a google search in firefox, the copy attempt fails and does not post any text at all.

@GuerrillaWarfare Which version of Atom are you using and which OS? Can you reproduce the problem in safe mode?

I'm running atom 0.189.0 on Ubuntu 14.04 LTS.

Ubuntu 14.10 I have the same issue. I can not copy and paste to another app, but pasting in atom works. I also tried with --safe and it has the same behavior. Downgrading to 0.188.0 makes things work again.

Arch Linux here, everything up to date and having the same problem. In sublime text or chrome the context menu won't even show up if I have something in the clipboard from an atom buffer.

Copying stuff from a markdown preview works. Also trying to copy something from a buffer into chrome will crash the tab and copying into sublime will...well, the cursor stays put when I type: the characters appear but the cursor will just stay in its current position and will keep blinking.
Using the selection clipboard (selecting text and pasting it with middle mouse click) works  though... :confused:

Same here on ubuntu vivid, downgrading to 0.188.0 works.
To sum up:

pasting in atom works with Ctrl+V
copying from atom (to another atom instance or any other app) doesn't work with Ctrl+C (it's not in X window paste area)
Subcribing.

Same problem here (Arch Linux).
Downgrading...

I'm going to close this as a duplicate of #6221.


Revert #130, downgrade cargo-deny-action to 1.2.6

This reverts commit 4162060d4df9108ed5830da0ef6aba2256884491.
Cargo-deny 0.11.0 no longer applies exceptions to workspace-local crates, causing CI failures everywhere.

The actual cause here seems to be https://github.com/EmbarkStudios/cargo-deny/issues/371.


Add alternative sorting for form submission data

Adds an additional optional sorting for submission data
via a new config entry.
Add documentation for the full data view and the new config
entry.

Deals with #3761

I fully agree with you that form submissions need a sorting option. I vote for implementing "newest first" as default, even though this needs a small upgrade consideration because it's backwards-incompatible.

@timorieber I agree that newest first as default makes the most sense, but I bet you there is someone out there who has gotten used to oldest first, and liked it. For that person, I'd rather just add a setting so we can make newest first an option. Because right now, it's hardcoded as oldest first only.
That said, I need to add some tests because the code coverage tests are complaining!
Oh and, it's probably worth keeping the discussion in the issue instead since this pull request may not be the best option: #3761

Thanks @Adrian-Turjak!
I'm not keen on making this a config setting, for a couple of reasons: firstly, it's overlooking the multi-user nature of Wagtail. The person who's dealing with form submissions from day to day isn't necessarily the person with the keys to the codebase who can tweak settings according to their personal preference - and it's quite unlikely that it will occur to the user to go to their developer / agency and ask "can you change this setting please?", even if it is annoying them.
Secondly, micro-managing UX design choices is a poor use of config settings. If newest-first is indeed the more natural way of viewing the list - and I think there are good arguments that it is - then we should be bold and fix that for everyone, not just people who are persistent enough to read through the settings docs thinking "how do I want this set up?". (To me, 99% of good UX design is UX that you don't have to think about - it should just be there.)
To cater for people who do want the listing to be oldest-first, I think it would be worth making the "Submission date" heading clickable, as we do on other listings. (To be even nicer, we could make this a persistent property on the user profile, but that's probably overkill.) Also, we should keep in mind that this view is also used for CSV output - in this case I think oldest-first is more appropriate (since it essentially acts as a log file) so we should switch the behaviour accordingly.

@gasman I totally agree. I'd much prefer we do this right, and I'd also much prefer to make newest first the default.
We can continue the discussion around this in the issue I opened (#3761).


Updated RavenDB dependencies to 3.5.1 and targeted .Net 4.5.1

Updated RavenDB dependencies to 3.5.1
Now targetting .Net 4.5.1
Updated Json.Net to 9.0.1
Minor tweeks like string interpolation usage and formatting stuff
Removed old Copyright from SharedAssemblyInfo
Removed NLog
Bumped assembly version to 2.0

Cheers or the PR @RagingKore 👍


1.11.4 changes

Checklist before submitting

[ ] Did you read the contributor guide?
[ ] Did you update any affected documentation?
[ ] Did you write any tests to validate this change?

Description
Fixes # (issue).
Review process to land

All tests and other checks must succeed.
At least one maintainer must review and approve.
If any  maintainer requests changes, they must be addressed.

This PR adds all changes that were added in trial PR - https://github.com/open-ce/open-ce/pull/1261/


The time/date a station was made shown on the overview

Display the a timestamp when the spot was created and modified

Added a Spot metadata page with commit 808e6a49406689565fd38cac000bebc56d6b9e41
Access by pressing the icon for the Spot in the notebook


Austin data has disappeared?

Last week https://github.com/dabreegster/abstreet/blob/master/docs/dev.md#getting-started said that opting into everything is:
runtime: seattle,huge_seattle,austin
input: seattle,huge_seattle,austin

Now it says:
runtime: seattle,huge_seattle,krakow
input: seattle,huge_seattle,krakow

Did Austin disappear?

Yes. I originally included Austin just to make sure all of the importing pipeline worked for a second city. There was no active use of Austin by anyone. Now that @matkoniecz is iterating on Kraków, Austin is just a bit of a maintenance burden. At some point, there'll be many cities maintained, but until that point, it's slowing me down a bit for no good reason. Is it OK to exclude it from the FreeBSD release?
I would also not recommend including huge_seattle either; I don't regularly test it yet, and even just loading it may oomph your system's RAM a bit much.

Ok, thanks, I'll exclude huge_seattle then.


Installation Problem

Hello
Describe the bug
I have trouble to install VRX. I am following the 2023 installation guide (https://github.com/osrf/vrx/wiki/2023-installation).
Gazebo Garden and ROS 2 Humble are operating normally. I installed VRX from source according to the guide. Completed steps 1 and 2 and the bugs started at step 3. I cannot build the environment.
cd ~/vrx_ws
GZ_VERSION=garden colcon build --merge-install

Expected behavior
Create the Environment.
To Reproduce
I reproduced the problem in a test workspace. Screenshots below.

In order to solve the error depicted in Screenshot 1 I git cloned rcl_intefaces that contains built in interfaces (https://github.com/ros2/rcl_interfaces.git)
In the next run I got the error depicted in Screenshot 2. I solved it in the same way. That happens for multiple dependencies.
After a point I got the error depicted in Screenshot 3 and 4.

System Configuration:

OS: Ubuntu 22.04.02
ROS Version: ROS 2, Humble
Gazebo Version: Gazebo Sim 7.4, Garden
Graphics Card: Nvidia GTX 1660 Ti
VRX

Screenshots
(Screenshot 1)

(Screenshot 2)

(Screenshot 3)

(Screenshot 4)

Thanks very much for this helpful report. It seems like some dependencies are not getting installed during the installation of ROS 2 and Gazebo. You should not have to build anything from source (unless you want to). A few things to check:

When you installed ROS 2, did you use sudo apt install ros-humble-desktop or sudo apt install ros-humble-ros-base?
Did you install the ros-dev-tools package?
Have you sourced your installation? (e.g. run source /opt/ros/humble/setup.bash in the terminal before building)

I did the desktop installation because it was the recommended.
I installed the ros-dev-tools package.
No, I didn't source it, I forgot it. That solved most of the problems now.

The following screenshot shows my current output.

Is there any problem with the stderr output?
I know it's obvious, but I think you should add the source /opt/ros/humble/setup.bash in the installation guide.

Is there any problem with the stderr output?
No, this is fine. If you build a second time you won't see the warning.

I know it's obvious, but I think you should add the source /opt/ros/humble/setup.bash in the installation guide.
I agree. Added.

I did what you said and it finally worked. Thank you very much.
Can you also give me some information on how to spawn The Sydney Regatta environment. It is not clear enough for me through the tutorial.

Great. I added a reminder about sourcing the environment. Closing this as resolved.


ARTEMIS-2094 Only deploy reloadable config if reloaded.

@clebertsuconic this does the reversion you did, and then adds to deploy reloadable config, where it only deploys reloaded config, if it reloaded, thus avoiding the issues. @jbertram hopefully this runs fine, if you could do the cross check that would be great.

@michaelandrepearce I'm also running tests on this.. I will let you know...
Thank you so much.

@clebertsuconic is this good to merge?

@michaelandrepearce  the testsuite was still frozen when I ran it. I'm not sure it's related to this yet...
I just wanted to keep it open until I figure it out. give me until the day of the day?

@clebertsuconic sure no worries, i have some feature work (currently on DO NOT MERGE pr atm) , thats behind this currently, and have some further feature work behind that (e.g. builds on some refactor bits in first feature work), I just have bit of a serialised queue forming :).

@michaelandrepearce I will merge this.. I'm not sure if there's still something broken yet... I will ping you here if I see anything else wrong, ok?

@michaelandrepearce really really thanks! It's all good now!


Why do some games never update on Steam OS Products that are confirmed to work page?

For example these games are all listed as last updated 2 years ago:

Many of these games have updated in the last month:
https://steamdb.info/app/326160/history/
https://steamdb.info/app/268870/history/
https://steamdb.info/app/331470/history/
https://steamdb.info/app/286690/history/
https://steamdb.info/app/257510/history/

Hello @robertc, I'm pretty sure the date listed is when the game was confirmed, and is not "Last Updated."

Ah OK, that makes sense.  Is there any way to see a list in order of last updated for the confirmed products?


How to create a suitable zst file?

The README.md says:

IndexedZstdFile will only speed up seeking when there are more than one block, which sadly requires a bit of care in zstd.

Could you elaborate on the specific "bit of care" that's needed? At the zstd command-line, I see options like:
--target-compressed-block-size=# : generate compressed block of approximately targeted size
 -B#    : cut file into independent blocks of size # (default: no block)

...will one of these options produce the desired result? If so, what would you say is a reasonable blocksize? My only reference is bgzf which uses 65536 bytes.

That's really a confusing line I wrote, sorry. I don't recall the exact reason I wrote it that way but all I can think of is that I meant to say that in zstd it's not the default behaviour. I will update the readme.
The block size really depends on the data you are working with and the speed you want to achieve while seeking.
Keep in mind that in zstd each block is independently compressed. It means that no informations is shared between blocks and thus small blocks equals worse compression ratio.
As far as I know the options you pointed out will not create multiple blocks, you can inspect the generated zstd file with zstd -l <archive.zstd>
You may want to use t2sz to generate the archives.
65536 bytes is very small and will not give you much in term of compression. Start with a few megabytes.


Fixes step selection issue in lazy blended pairwise CG

note: couldn't run test on my machine as julia-1.9.2 crashes due to a malloc issue:
ulia(59061,0x1ff4de080) malloc: *** error for object 0xe00000000000000: pointer being freed was not allocated
julia(59061,0x1ff4de080) malloc: *** set a breakpoint in malloc_error_break to debug

[59061] signal (6): Abort trap: 6
in expression starting at /Users/x_bas/Documents/Mathematik/projects/2022_branchWolfe/FrankWolfe.jl/test/lmo.jl:386
__pthread_kill at /usr/lib/system/libsystem_kernel.dylib (unknown line)
Allocations: 55868956 (Pool: 55827465; Big: 41491); GC: 81
ERROR: Package FrankWolfe errored during testing (received signal: 6)

(maybe something to report separately)

@matbesancon please check whether the project.toml update is necessary. otherwise change.


Reduced counts of collisions for cache srf filenames

Resolves #1230 issue

Hello @pavel-trafimuk ,
thank you very much for your contribution 🤝


Mac & Windows support

Hi there, is there any hope for supporting Mac & Windows? Some building hints or preferably binaries?

I'm also wondering if there would be a porting to windows ?
So we could integrate the web-driver in our C# based selenium testing ?

@taigh @boutsen https://github.com/rkavalap/crosswalk-web-driver/releases
try this out.


Get rid of core::gl::camera

Description
Remove core camera and replace it with engine camera in renderer.
Checklist

[x] Self-review changes.

LGTM :) btw you can mark my comments as resolved when you push their suggestions, makes it easier to know what has been done