Synthesis failed for WebSecurityScanner

Hello! Autosynth couldn't regenerate WebSecurityScanner. :broken_heart:
Here's the output from running synth.py:
_finding_type_stats_response.ex.
Writing ListFindingsResponse to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/list_findings_response.ex.
Writing ListScanConfigsResponse to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/list_scan_configs_response.ex.
Writing ListScanRunsResponse to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/list_scan_runs_response.ex.
Writing OutdatedLibrary to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/outdated_library.ex.
Writing ScanConfig to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/scan_config.ex.
Writing ScanConfigError to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/scan_config_error.ex.
Writing ScanRun to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/scan_run.ex.
Writing ScanRunErrorTrace to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/scan_run_error_trace.ex.
Writing ScanRunWarningTrace to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/scan_run_warning_trace.ex.
Writing Schedule to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/schedule.ex.
Writing StartScanRunRequest to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/start_scan_run_request.ex.
Writing StopScanRunRequest to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/stop_scan_run_request.ex.
Writing ViolatingResource to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/violating_resource.ex.
Writing VulnerableHeaders to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/vulnerable_headers.ex.
Writing VulnerableParameters to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/vulnerable_parameters.ex.
Writing Xss to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/xss.ex.
Writing Projects to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/api/projects.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

15:07:36.073 [info]  FETCHING: https://websecurityscanner.googleapis.com/$discovery/GOOGLE_REST_SIMPLE_URI?version=v1alpha

15:07:36.086 [info]  FETCHING: https://websecurityscanner.googleapis.com/$discovery/rest?version=v1alpha

15:07:36.099 [info]  FOUND: https://websecurityscanner.googleapis.com/$discovery/rest?version=v1alpha
Revision check: old=20200801, new=20201213, generating=true
Creating leading directories
Writing Authentication to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/authentication.ex.
Writing CrawledUrl to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/crawled_url.ex.
Writing CustomAccount to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/custom_account.ex.
Writing Empty to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/empty.ex.
Writing Finding to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/finding.ex.
Writing FindingTypeStats to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/finding_type_stats.ex.
Writing GoogleAccount to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/google_account.ex.
Writing Header to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/header.ex.
Writing ListCrawledUrlsResponse to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/list_crawled_urls_response.ex.
Writing ListFindingTypeStatsResponse to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/list_finding_type_stats_response.ex.
Writing ListFindingsResponse to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/list_findings_response.ex.
Writing ListScanConfigsResponse to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/list_scan_configs_response.ex.
Writing ListScanRunsResponse to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/list_scan_runs_response.ex.
Writing OutdatedLibrary to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/outdated_library.ex.
Writing ScanConfig to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/scan_config.ex.
Writing ScanRun to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/scan_run.ex.
Writing Schedule to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/schedule.ex.
Writing StartScanRunRequest to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/start_scan_run_request.ex.
Writing StopScanRunRequest to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/stop_scan_run_request.ex.
Writing ViolatingResource to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/violating_resource.ex.
Writing VulnerableHeaders to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/vulnerable_headers.ex.
Writing VulnerableParameters to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/vulnerable_parameters.ex.
Writing Xss to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/xss.ex.
Writing Projects to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/api/projects.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

15:07:36.659 [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 07:07:39,870 autosynth [ERROR] > Synthesis failed
2020-12-18 07:07:39,870 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/web_security_scanner/synth.metadata', 'synth.py', '--', 'WebSecurityScanner']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth is still having trouble generating WebSecurityScanner. :sob:
Here's the output from running synth.py:
_finding_type_stats_response.ex.
Writing ListFindingsResponse to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/list_findings_response.ex.
Writing ListScanConfigsResponse to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/list_scan_configs_response.ex.
Writing ListScanRunsResponse to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/list_scan_runs_response.ex.
Writing OutdatedLibrary to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/outdated_library.ex.
Writing ScanConfig to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/scan_config.ex.
Writing ScanConfigError to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/scan_config_error.ex.
Writing ScanRun to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/scan_run.ex.
Writing ScanRunErrorTrace to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/scan_run_error_trace.ex.
Writing ScanRunWarningTrace to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/scan_run_warning_trace.ex.
Writing Schedule to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/schedule.ex.
Writing StartScanRunRequest to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/start_scan_run_request.ex.
Writing StopScanRunRequest to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/stop_scan_run_request.ex.
Writing ViolatingResource to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/violating_resource.ex.
Writing VulnerableHeaders to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/vulnerable_headers.ex.
Writing VulnerableParameters to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/vulnerable_parameters.ex.
Writing Xss to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/xss.ex.
Writing Projects to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/api/projects.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

15:03:22.235 [info]  FETCHING: https://websecurityscanner.googleapis.com/$discovery/GOOGLE_REST_SIMPLE_URI?version=v1alpha

15:03:22.245 [info]  FETCHING: https://websecurityscanner.googleapis.com/$discovery/rest?version=v1alpha

15:03:22.260 [info]  FOUND: https://websecurityscanner.googleapis.com/$discovery/rest?version=v1alpha
Revision check: old=20200801, new=20201213, generating=true
Creating leading directories
Writing Authentication to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/authentication.ex.
Writing CrawledUrl to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/crawled_url.ex.
Writing CustomAccount to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/custom_account.ex.
Writing Empty to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/empty.ex.
Writing Finding to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/finding.ex.
Writing FindingTypeStats to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/finding_type_stats.ex.
Writing GoogleAccount to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/google_account.ex.
Writing Header to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/header.ex.
Writing ListCrawledUrlsResponse to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/list_crawled_urls_response.ex.
Writing ListFindingTypeStatsResponse to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/list_finding_type_stats_response.ex.
Writing ListFindingsResponse to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/list_findings_response.ex.
Writing ListScanConfigsResponse to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/list_scan_configs_response.ex.
Writing ListScanRunsResponse to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/list_scan_runs_response.ex.
Writing OutdatedLibrary to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/outdated_library.ex.
Writing ScanConfig to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/scan_config.ex.
Writing ScanRun to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/scan_run.ex.
Writing Schedule to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/schedule.ex.
Writing StartScanRunRequest to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/start_scan_run_request.ex.
Writing StopScanRunRequest to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/stop_scan_run_request.ex.
Writing ViolatingResource to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/violating_resource.ex.
Writing VulnerableHeaders to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/vulnerable_headers.ex.
Writing VulnerableParameters to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/vulnerable_parameters.ex.
Writing Xss to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/xss.ex.
Writing Projects to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/api/projects.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

15:03:22.813 [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 07:03:25,891 autosynth [ERROR] > Synthesis failed
2020-12-19 07:03:25,891 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/web_security_scanner/synth.metadata', 'synth.py', '--', 'WebSecurityScanner']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth is still having trouble generating WebSecurityScanner. :sob:
Here's the output from running synth.py:
_finding_type_stats_response.ex.
Writing ListFindingsResponse to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/list_findings_response.ex.
Writing ListScanConfigsResponse to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/list_scan_configs_response.ex.
Writing ListScanRunsResponse to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/list_scan_runs_response.ex.
Writing OutdatedLibrary to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/outdated_library.ex.
Writing ScanConfig to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/scan_config.ex.
Writing ScanConfigError to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/scan_config_error.ex.
Writing ScanRun to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/scan_run.ex.
Writing ScanRunErrorTrace to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/scan_run_error_trace.ex.
Writing ScanRunWarningTrace to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/scan_run_warning_trace.ex.
Writing Schedule to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/schedule.ex.
Writing StartScanRunRequest to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/start_scan_run_request.ex.
Writing StopScanRunRequest to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/stop_scan_run_request.ex.
Writing ViolatingResource to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/violating_resource.ex.
Writing VulnerableHeaders to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/vulnerable_headers.ex.
Writing VulnerableParameters to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/vulnerable_parameters.ex.
Writing Xss to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/xss.ex.
Writing Projects to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/api/projects.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

15:12:58.463 [info]  FETCHING: https://websecurityscanner.googleapis.com/$discovery/GOOGLE_REST_SIMPLE_URI?version=v1alpha

15:12:58.473 [info]  FETCHING: https://websecurityscanner.googleapis.com/$discovery/rest?version=v1alpha

15:12:58.491 [info]  FOUND: https://websecurityscanner.googleapis.com/$discovery/rest?version=v1alpha
Revision check: old=20200801, new=20201213, generating=true
Creating leading directories
Writing Authentication to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/authentication.ex.
Writing CrawledUrl to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/crawled_url.ex.
Writing CustomAccount to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/custom_account.ex.
Writing Empty to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/empty.ex.
Writing Finding to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/finding.ex.
Writing FindingTypeStats to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/finding_type_stats.ex.
Writing GoogleAccount to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/google_account.ex.
Writing Header to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/header.ex.
Writing ListCrawledUrlsResponse to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/list_crawled_urls_response.ex.
Writing ListFindingTypeStatsResponse to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/list_finding_type_stats_response.ex.
Writing ListFindingsResponse to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/list_findings_response.ex.
Writing ListScanConfigsResponse to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/list_scan_configs_response.ex.
Writing ListScanRunsResponse to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/list_scan_runs_response.ex.
Writing OutdatedLibrary to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/outdated_library.ex.
Writing ScanConfig to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/scan_config.ex.
Writing ScanRun to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/scan_run.ex.
Writing Schedule to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/schedule.ex.
Writing StartScanRunRequest to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/start_scan_run_request.ex.
Writing StopScanRunRequest to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/stop_scan_run_request.ex.
Writing ViolatingResource to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/violating_resource.ex.
Writing VulnerableHeaders to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/vulnerable_headers.ex.
Writing VulnerableParameters to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/vulnerable_parameters.ex.
Writing Xss to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/xss.ex.
Writing Projects to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/api/projects.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

15:12:59.066 [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 07:13:02,342 autosynth [ERROR] > Synthesis failed
2020-12-20 07:13:02,342 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/web_security_scanner/synth.metadata', 'synth.py', '--', 'WebSecurityScanner']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth is still having trouble generating WebSecurityScanner. :sob:
Here's the output from running synth.py:
_finding_type_stats_response.ex.
Writing ListFindingsResponse to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/list_findings_response.ex.
Writing ListScanConfigsResponse to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/list_scan_configs_response.ex.
Writing ListScanRunsResponse to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/list_scan_runs_response.ex.
Writing OutdatedLibrary to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/outdated_library.ex.
Writing ScanConfig to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/scan_config.ex.
Writing ScanConfigError to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/scan_config_error.ex.
Writing ScanRun to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/scan_run.ex.
Writing ScanRunErrorTrace to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/scan_run_error_trace.ex.
Writing ScanRunWarningTrace to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/scan_run_warning_trace.ex.
Writing Schedule to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/schedule.ex.
Writing StartScanRunRequest to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/start_scan_run_request.ex.
Writing StopScanRunRequest to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/stop_scan_run_request.ex.
Writing ViolatingResource to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/violating_resource.ex.
Writing VulnerableHeaders to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/vulnerable_headers.ex.
Writing VulnerableParameters to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/vulnerable_parameters.ex.
Writing Xss to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/xss.ex.
Writing Projects to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/api/projects.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

15:00:02.134 [info]  FETCHING: https://websecurityscanner.googleapis.com/$discovery/GOOGLE_REST_SIMPLE_URI?version=v1alpha

15:00:02.147 [info]  FETCHING: https://websecurityscanner.googleapis.com/$discovery/rest?version=v1alpha

15:00:02.165 [info]  FOUND: https://websecurityscanner.googleapis.com/$discovery/rest?version=v1alpha
Revision check: old=20200801, new=20201213, generating=true
Creating leading directories
Writing Authentication to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/authentication.ex.
Writing CrawledUrl to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/crawled_url.ex.
Writing CustomAccount to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/custom_account.ex.
Writing Empty to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/empty.ex.
Writing Finding to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/finding.ex.
Writing FindingTypeStats to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/finding_type_stats.ex.
Writing GoogleAccount to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/google_account.ex.
Writing Header to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/header.ex.
Writing ListCrawledUrlsResponse to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/list_crawled_urls_response.ex.
Writing ListFindingTypeStatsResponse to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/list_finding_type_stats_response.ex.
Writing ListFindingsResponse to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/list_findings_response.ex.
Writing ListScanConfigsResponse to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/list_scan_configs_response.ex.
Writing ListScanRunsResponse to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/list_scan_runs_response.ex.
Writing OutdatedLibrary to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/outdated_library.ex.
Writing ScanConfig to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/scan_config.ex.
Writing ScanRun to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/scan_run.ex.
Writing Schedule to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/schedule.ex.
Writing StartScanRunRequest to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/start_scan_run_request.ex.
Writing StopScanRunRequest to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/stop_scan_run_request.ex.
Writing ViolatingResource to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/violating_resource.ex.
Writing VulnerableHeaders to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/vulnerable_headers.ex.
Writing VulnerableParameters to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/vulnerable_parameters.ex.
Writing Xss to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/xss.ex.
Writing Projects to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/api/projects.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

15:00:02.747 [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 07:00:05,791 autosynth [ERROR] > Synthesis failed
2020-12-21 07:00:05,792 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/web_security_scanner/synth.metadata', 'synth.py', '--', 'WebSecurityScanner']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth is still having trouble generating WebSecurityScanner. :sob:
Here's the output from running synth.py:
_finding_type_stats_response.ex.
Writing ListFindingsResponse to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/list_findings_response.ex.
Writing ListScanConfigsResponse to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/list_scan_configs_response.ex.
Writing ListScanRunsResponse to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/list_scan_runs_response.ex.
Writing OutdatedLibrary to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/outdated_library.ex.
Writing ScanConfig to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/scan_config.ex.
Writing ScanConfigError to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/scan_config_error.ex.
Writing ScanRun to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/scan_run.ex.
Writing ScanRunErrorTrace to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/scan_run_error_trace.ex.
Writing ScanRunWarningTrace to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/scan_run_warning_trace.ex.
Writing Schedule to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/schedule.ex.
Writing StartScanRunRequest to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/start_scan_run_request.ex.
Writing StopScanRunRequest to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/stop_scan_run_request.ex.
Writing ViolatingResource to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/violating_resource.ex.
Writing VulnerableHeaders to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/vulnerable_headers.ex.
Writing VulnerableParameters to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/vulnerable_parameters.ex.
Writing Xss to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/model/xss.ex.
Writing Projects to clients/web_security_scanner/lib/google_api/web_security_scanner/v1/api/projects.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

15:02:44.469 [info]  FETCHING: https://websecurityscanner.googleapis.com/$discovery/GOOGLE_REST_SIMPLE_URI?version=v1alpha

15:02:44.480 [info]  FETCHING: https://websecurityscanner.googleapis.com/$discovery/rest?version=v1alpha

15:02:44.496 [info]  FOUND: https://websecurityscanner.googleapis.com/$discovery/rest?version=v1alpha
Revision check: old=20200801, new=20201213, generating=true
Creating leading directories
Writing Authentication to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/authentication.ex.
Writing CrawledUrl to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/crawled_url.ex.
Writing CustomAccount to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/custom_account.ex.
Writing Empty to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/empty.ex.
Writing Finding to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/finding.ex.
Writing FindingTypeStats to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/finding_type_stats.ex.
Writing GoogleAccount to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/google_account.ex.
Writing Header to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/header.ex.
Writing ListCrawledUrlsResponse to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/list_crawled_urls_response.ex.
Writing ListFindingTypeStatsResponse to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/list_finding_type_stats_response.ex.
Writing ListFindingsResponse to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/list_findings_response.ex.
Writing ListScanConfigsResponse to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/list_scan_configs_response.ex.
Writing ListScanRunsResponse to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/list_scan_runs_response.ex.
Writing OutdatedLibrary to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/outdated_library.ex.
Writing ScanConfig to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/scan_config.ex.
Writing ScanRun to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/scan_run.ex.
Writing Schedule to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/schedule.ex.
Writing StartScanRunRequest to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/start_scan_run_request.ex.
Writing StopScanRunRequest to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/stop_scan_run_request.ex.
Writing ViolatingResource to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/violating_resource.ex.
Writing VulnerableHeaders to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/vulnerable_headers.ex.
Writing VulnerableParameters to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/vulnerable_parameters.ex.
Writing Xss to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/model/xss.ex.
Writing Projects to clients/web_security_scanner/lib/google_api/web_security_scanner/v1alpha/api/projects.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

15:02:45.058 [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 07:02:48,138 autosynth [ERROR] > Synthesis failed
2020-12-22 07:02:48,138 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/web_security_scanner/synth.metadata', 'synth.py', '--', 'WebSecurityScanner']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth passed, closing! :green_heart:


Get comments method and like comment method  added in project

Methods were added to query comments from a medium and thereby obtain the commentId to be used in the addLikeComment method as requested in issue /112.

Thank you for PR.
Looks like we have simular endpoints
.getMediaLikes({ shortcode, first, after })
.getMediaComments({ shortcode, first, after })


From template=vite-typescript, run package error

Pre-flight checklist

[X] I have read the contribution documentation for this project.
[X] I agree to follow the code of conduct that this project uses.
[X] I have searched the issue tracker for a bug that matches the one I want to file, without success.

Electron Forge version
7.4.0
Electron version
32.0.2
Operating system
macOS 14.6.1
Last known working Electron Forge version
No response
Expected behavior
run package success
Actual behavior
run package error

Steps to reproduce

npm init electron-app@latest my-app -- --template=vite-typescript

run yarn package
Additional information
No response

Got the fix here @bdlr2
https://github.com/electron/asar/pull/325

This can be resolved by upgrading electron/asar in the dependency tree 🙇


[JOSS Review] Dependency on astropy

pyGWB depends specifically on astropy==5.2. Fixing the dependency version can cause major headaches to package maintainers downstream. Is astropy really needed? As far as I can see, it is used for a couple of physical constants, and for the function io_registry. Maybe you can remove astropy as dependency all together (which would be nice because astropy is not a small package`).

astropy is indeed a fundamental dependency of our package (more or less unfortunately); we have been advised to fix the version as indeed the interaction between astropy and other packages (e.g., gwpy) requires a careful version balancing act. It is a bit of a pain but I am willingly in charge of maintaining this dependency and assuring that we always use the most up to date packages, where compatible.

Could you clarify how is astropy needed as direct dependency?
The main place where I see it used is for i/o in omega_spectra.py, but maybe you could consider using a different format?
Also, the readme says that the package depends on astropy>=5.2, but it should say that requires astropy == 5.2.
The reason I would like to see this pin gone is because it makes developing packages that depend on pyGWB much harder. As you say, there's already a balancing act between other dependencies, and if your package fixes astropy to a particular version, it completely removes any wiggle room.

Sure - both bilby and gwpy depend on astropy, so the package needs to be installed for those dependencies to work properly. omega_spectra objects subclass gwpy objects that use astropy i/o, and I can't change that. Plus, in the community we constantly refer to astropy-defined cosmologies which streamlines implementing assumptions consistently across different codes (see the constants module as well).
Thanks for spotting the mistake in the readme - indeed it used to be a weaker dependency but when astropy was upgraded to >5.2 a gwpy functionality broke down, perhaps this has actually been fixed in the meantime so I will also double check this - and make sure the readme is up to date.
I understand your point about making dev. harder, but unfortunately I can't really see how to drop astropy without significantly reducing our functionalities as well as our compatibility with the other packages used. This is a shared burden across the GW coding community, not a unique pygwb problem.

My point is not with having astropy in the dependency tree, but with pygwb directly depending on a very specific version of astropy for something that seems to be one isolated function.
It shouldn't be your task to find what version of gwpy and astropy work well together. That's up to to the gwpy developers. If the stated version constraints of gwpy do not result in a working package, you should report an issue to their package.
If you can remove direct references to astropy in your package, you'll leave the problem of finding the version that works across all the dependencies to the constraint solver in the package manager, which is the piece of code that is purposefully designed to solve this problem. When you fix the constraint yourself, you are taking all the burden of finding the correct version (which is a rather difficult task when you start to think about multiple versions of packages/Python), and updating that in perpetuity (if you want to have a working package). You are also adding constraints that are not relevant to your package.
As a developer, I had to hold back releases of my packages because upstream dependencies were not carefully with their constraints. My impression is that your package is in a good position to not depend directly on astropy. And if you do that, you can remove one source of potential problems to potential downstream developers.

omega_spectra objects subclass gwpy objects that use astropy i/o, and I can't change that.

If you are subclassing, can't you use the methods of the parent class for that?

It shouldn't be your task to find what version of gwpy and astropy work well together. That's up to to the gwpy developers. If the stated version constraints of gwpy do not result in a working package, you should report an issue to their package.

It shouldn't, but, unfortunately, it has caused issues in the past and the gwpy developers themselves suggested fixing this particular dependency for now to ensure smooth sailing. I was confused as to why this wasn't fixed as a gwpy dependency in the first place (resolving this issue as you point out), I can't speak to why that is.

If you are subclassing, can't you use the methods of the parent class for that?

I had tried this originally, but the reading/writing of the objects was not performing correctly, in particular attributes were not registered properly. I could find no other way than to register the new classes directly.

My impression is that your package is in a good position to not depend directly on astropy.

While dependencies are few, they are still requirements of the package. Other than the registry mentioned above, we also rely on astropy constants and cosmologies. While these may seem like trivial dependencies at first glance, they are in fact instrumental to the package, and the dependency on these is quite possibly set to grow as the pe module grows. Given that astropy is in the dependency tree anyway, I see no reason not to use it, and use it well.
I have verified that our tests still break when admitting astropy>5.2 - this has to do with how gwpy objects are compared to each other in the test suite. this is possibly not something that users would notice, but it is an issue for developers. As our user base is currently developer-dominated, I think fixing this version for now is our safest way forward, as we work with gwpy dev.s to update our test suite. I have not changed it myself as I was under the impression that gwpy devs were considering making changes in their objects which would in fact fix the errors caused by the new astropy version. As I cannot find an issue recording all the work done on this (perhaps issues were also mistakenly closed...), I can open an issue to address the incompatibility with astropy>5.2, either by changing our tests or by monitoring the fixes in gwpy.

My personal take is that reducing dependencies is always a good thing, especially when they are prone to incompatibilities (such as astropy). All the instances I currently see of astropy seem relatively minor and easily replaceable. Of course, if you expect your reliance to astropy to grow, feel free it keep it as dependency.
In any case, I think you should fix your tests. Pinning the version of astropy to 5.2 feels like a workaround, not something that a production-ready package should do. For example, one of the side effect is every user that installs pygwb in another environment will see their version of astropy downgraded to 5.2 (and astropy 6 is about to be released). Also, while your package doesn't restrict compatibility with Python 3.12, astropy 5.2 won't support it. So, every developer that wants to use your library in a package will have to use astropy 5.2, and won't be able to use Python 3.12.
I believe that this is important to be addressed, but I also recognize my bias on the subject (given all the time I had to invest to work around problems in constraints in upstream dependencies). So maybe the first step might be to least clearly document the problem and identify the way forward?
(The same discussion about unnecessary dependencies goes with seaborn, that is used only to get a color palette (but at least doesn't impose version constraints).)

Pinning the version of astropy to 5.2 feels like a workaround, not something that a production-ready package should do.

That's because it was :) it was never meant to be a permanent fix, it was in place to ensure the package worked as its dependencies were updated to be compatible. I admit there is poor documentation about the issue but devs were well aware and I work closely with gwpy and bilby folk to make sure our packages all work together.
I decided to dig a little deeper to see whether the issue had evolved since the version was first pinned, and I was quite pleased to find out that using a fresh verson of gwpy and astropy>5.2 I was able to single out a few minor fixes I could make in pygwb.tests to ensure compatibility. I am now unpinning the astropy version! This is is a new MR where I'll fold in the other edits discussed on the other issues.

Yay! Thank you very much for all your time and effort spent on this!


Navigation Timeout Error

Describe the bug
Everytime I run the script I encounter an error that seems to be coming from screenshots.py in the video directory.
This is the error pyppeteer.errors.TimeoutError: Navigation Timeout Exceeded: 30000 ms exceeded.
To Reproduce
Steps to reproduce the behavior:

Run the program

Expected behavior
To not timeout during the screenshot phase

👋🏻, the cause is most likely internet connection.
But it's not the behavior anyone wants to see.
I'm working on major update and I'll close the issue there.


Missing PropTypes errors

Describe the bug
After pulling the latest code, there seem to be a bunch of errors. The initial error was as follows:
./src/components/project/label/index.js
  Line 111:17:  Missing "key" prop for element in iterator  react/jsx-key

After solving this, the next error was:
./src/components/profile/index.js
  Line 141:27:  Missing "key" prop for element in iterator  react/jsx-key

After solving the previous error, the PropTypes error is shown:

Even after adding the proptypes for this component, the same error is shown for more components.
To Reproduce
Steps to reproduce the behavior:

Pull the latest code
Run LabelLab by running npm run dev in labellab-server
Fix the first error shown by adding key={index} to line 112 of label/index.js
Fix the second error by adding key={project._id} to line 142 of profile/index.js
See the errors

Expected behavior
Code should compile without any missing PropTypes errors even if prop types are not present
Screenshots
Attached above
Desktop (please complete the following information):

OS: Windows
Browser: Chrome
Version: 80

Additional context
I think these errors are due to the changes in PR #303 but I'm not sure. I tried to add "react/prop-types": [0] to .eslintrc.js but it did not solve the issue.

I rolled back my code to 702c84e and the code seems to work properly. I think this error is occurring due to the react app being ejected.

I rolled back my code to 702c84e and the code seems to work properly. I think this error is occurring due to the react app being ejected.

@laksh22 react-eject script only ejects the configuration files of the CRA it does not change the code structure as such. What I think is the issue here is that the props-types are required and are not provided. It is a solely prop-type related issue.

@carpecodeum This error shows up when prop-types are not even defined for a component. Additionally, there were errors not related to prop-types which were shown in the beginning, such as the Missing "key" prop for element in iterator error which I have mentioned above. These errors did not show up before, even though there has been no change in these components.

@laksh22 Did you try deleting 'node_modules' and reinstalling? #303 is supposed to fix this issue. There were some dependency updates so clean your cache and do a npm install.

Hello ,
I am facing the same error where it describes that options' is missing in props validation I have retried after deleting the node modules folder and installing it again but the error still persist
Can anybody help
Thank You

I'm closing this issue since it has been fixed by #312


Tensorflow broken by new Bazel versions

Simplest way to reproduce the issue, run:
$ bazel build --config=opt --incompatible_load_argument_is_label --nobuild //tensorflow/tools/pip_package:build_pip_package
Suggested fix to tensorflow/third_party/sycl/sycl/BUILD.tpl:
-load("platform", "sycl_library_path")
+load(":platform.bzl", "sycl_library_path")

-load("platform", "readlink_command")
+load(":platform.bzl", "readlink_command")

This should address the immediate need.
There are other issues to fix (although not as pressing). You can see them by building using --all_incompatible_changes.
Let me know if you need any help.
Thanks!

/CC @gunan, can you resolve this?

Thanks for the report @laurentlb Could you file a bug internally for us to quickly triage this?

I've prepared a change that will fix this internally.

The fix has been applied to our internal branch. The next repository sync should bring the fix over to Github.

Thanks!


Include Gameplay preview

include screen recordings of this on put it on github as gameplay preview or something . Let users understand how much fun they could have

Done, Thanks for your suggestion.


where to add fields dynamically to formly

Hello, where to add fields dynamically to formly?
I just add an element to the array this.form.fields but it's not enough. This the code:
`<form [formGroup]="form.formGroup" (ngSubmit)="submit(userModel)">
<formly-form [form]="form.formGroup" [model]="form.model" [fields]="form.fields" [options]="form.options">

Submit
`

@davidoween you should pass a new ref to the field to take account of your changes

@aitboudad what do you mean with that?

@IustiNN I mean:
form.fields = [ ...form.fields, { key: 'title', type: 'input' }];
// instead of
form.fields.push({ key: 'title', type: 'input' });

@aitboudad Thank you very much!

Hi sir I'm also looking for a way to add input dynamically to my form so what i have here for testing is this  import {FormArray, FormGroup} from '@angular/forms'; import {FormlyFormOptions, FormlyFieldConfig} from '@ngx-formly/core'; import { FieldType, FormlyFormBuilder } from '@ngx-formly/core';   form = new FormGroup({});   fields: FormlyFieldConfig[];   formControl: FormArray;   model: any = {}; setTimeout(function() {       let template = {         key: 'myInput',         type: 'horizontalInput',         templateOptions: {           type: 'text',           label: 'My input',           placeholder: 'My input',           required: true,         }       };       this.fields.push(template);       this.builder.buildForm(this.form, this.fields[0], this.model[0], this.options);       this.formControl.push(this.form);     }.bind(this), 5000);
as a result my new input got created but without a label nor validation and not recognized by model what i want is the possibility to inject the new input in the position i pass on a parametre
is there a way i can do that

not sure what do you want to achieve if you're looking for an easy way to manage repeating fields please check the following example: https://formly-js.github.io/ngx-formly/examples/advanced/repeating-section


glfwGetCursorPos() xpos and ypos are swapped

As the title says, I am getting the semantics of xpos and ypos swapped when using glfwGetCursorPos().
OS: Arch Linux. Window manager: i3.
It works fine using the callback set with glfwSetCursorPosCallback().

Never mind, I must had been doing something wrong because it is working now...


Set projects under tools/ as IsPackable=false

It throws off Universe's groove because these projects under tools/ appear to produce the same package ID.

cc @seancpeters


Encourage explicit namespacing for using'd bindings in packages

In other words, a rule like:
"Where feasible, avoid relying on upstream packages' export statements in downstream package using statements, and explicitly"
So instead of writing:
using Them # exports `their_function`

my_function(x) = their_function(x) + 1

We encourage users to write:
using Them: their_function # explicitly bring `their_function` into my namespace

my_function(x) = their_function(x) + 1

Benefits:

easier to approach new codebases + refactor old code (no more "which package did this binding come from?")
easier to upgrade dependencies ("which bindings am I using from this package, were any of them deprecated in the latest release?")
avoids inappropriate inversion of extra responsibility to dependencies. IMO a package should be responsible for the bindings in its own namespace, not push that responsibility upwards to dependencies by relying on their export list. this is kind of a hot take, since you could argue the export list is part of each package's API, so they're taking responsibility for it regardless

Downsides:

using statements could become verbose for packages which use a lot of exported bindings from their dependencies. I actually don't think this is that bad in most cases, and even when it is, it feels like simple tooling for generating the bindings could make it obsolete regardless.
There's an ambiguous situation we'd have to define a convention around: Let's package A defines f. Package B overloads A.f, and package C overloads A.f. Package D depends on B and C (but not A directly) and uses f. How should D "declare" f? I feel like we could establish a convention here that resolves this, but maybe it'd be crufty

Regardless, I think we probably should introduce this a "preference" as opposed to a hard requirement, unless it ends up being really nice in practice.
cc @omus @ararslan

* There's an ambiguous situation we'd have to define a convention around: Let's package `A` defines `f`. Package `B` overloads `A.f`, and package `C` overloads `A.f`. Package `D` depends on `B` and `C` (but not `A` directly) and uses `f`. How should `D` "declare" `f`? I feel like we could establish a convention here that resolves this, but maybe it'd be crufty

I typically would import this from the package that defines the function and doesn't just extend it. That doesn't clearly document of the explicit requirement that C and D is needed. What we can do is import from both modules as these are the same function and Julia seems to be fine with this:
julia> module A
       function f end
       end
Main.A

julia> module C
       using Main.A: A, f
       A.f(::Integer) = "C"
       end
Main.C

julia> module D
       using Main.A: A, f
       A.f(::Float64) = "D"
       end
Main.D

julia> module B
       using Main.C: f
       using Main.D: f
       end
Main.B

julia> B.f
f (generic function with 2 methods)

The only real caveat I see is that the modules you depend on need to import f into their namespace.

easier to approach new codebases + refactor old code (no more "which package did this binding come from?")
easier to upgrade dependencies ("which bindings am I using from this package, were any of them deprecated in the latest release?")

Even if you know where a name came from, you don't necessarily know how it's being used based on the loaded packages, or whether particular methods have been deprecated.
Say you have something like S3Path from AWSS3.jl and you bring it into scope explicitly. Whenever you see S3Path you know where you got it from. Okay, cool. But then you call joinpath on it, a function from Base. The method that gets called isn't from AWSS3 or Base, it's from FilePathsBase. Do you need to write using FilePathsBase: joinpath or using Base: joinpath to tell readers of the code that you're relying on particular methods? What if AWSS3 adds its own method to fix some incorrect fallback behavior from the FilePathsBase method, do you need to signal that with using AWSS3: joinpath?
Similarly, consider the following:
using AWSS3: AWSS3
using FilePathsBase: @p_str  # an unfortunate implementation detail to need to expose for p""

Now calling p"s3://cool/beans" will give you an S3Path, which you never brought into scope, that has all of the methods defined for it as previously mentioned. So you're implicitly using a part of AWSS3.jl that you never explicitly expressed.
These kinds of cross-package interactions are not uncommon (and are actually a strength of Julia/multiple dispatch). The point I'm trying to make here is that listing the things you think you want in your namespace doesn't actually buy you that much in terms of understanding what's going on in the code.

since you could argue the export list is part of each package's API

And indeed I would. :smile: IMO, by declaring a dependency on a package, you're opting into taking whatever it's giving you. If you don't want to use a particular binding, you don't have to. And maybe you won't even end up using more than one thing from a package, which is fine; bindings aren't resolved until they're used (when you use using rather than import, but the guide already disallows import so we're good there).
Somewhat tangentially, there's always FUD about "polluting" namespaces, but you can have like six million names in your namespace that will have no effect unless you call them, and you can define your own binding with the same name as something exported from a dependency without consequence.

using statements could become verbose for packages which use a lot of exported bindings from their dependencies.

Yes. IMO this is also placing a large undue burden on the people writing code, since you might end up needing a different binding than you thought you did but oh no! it wasn't loaded explicitly earlier, now your development workflow is messed up because you have to go back and load the other one, and you have an unused, outdated one hanging around in the meantime. This could happen when using a package like DataFrames, where you could be using a leftjoin but then realize you actually needed an innerjoin.

it feels like simple tooling for generating the bindings could make it obsolete

Sure, but said tooling would need to exist first. :smile:

since you could argue the export list is part of each package's API

A thousand times this. In fact, removing something from the export list would be a breaking change and require a major version  bump, so that seems API-like to me. In the packages I maintain and develop, we export exactly those functions that we expect the average user to use.
There are also cases where the "root" declaration of the function stub gets moved around. IIRC, we've had a few methods in the JuliaStats ecosystem that started off in a particular package (say GLM or MixedModels), but the function was recognized as something more general, so the "root" stub was moved to StatsBase. In fact, this is encouraged practice: wrinkle out a few kinks in the API of a new function in a package with fewer downstream dependencies than StatsBase, then migrate it to StatsBase. (As a concrete example, I have a PR open against StatsBase that's been punted off to GLM and MixedModels for a trial period before joining a package higher up the dependency tree.) As longer as everybody keeps (re-)exporting, it's fine and the downstream user never knows better. And all of this is fine because of the magic of multiple dispatch. Depending on which path is chosen above for selecting where to grab the binding, this could be annoying and churn-y instead of nearly invisible to the user.


Theseus fails with SIGABRT

superposer 3pk2 3pk2

outputs:
 ┌─┐┬ ┬┌─┐┌─┐┬─┐┌─┐┌─┐┌─┐┌─┐┬─┐
 └─┐│ │├─┘├┤ ├┬┘├─┘│ │└─┐├┤ ├┬┘
 └─┘└─┘┴  └─┘┴└─┴  └─┘└─┘└─┘┴└─
 Brought to you by @volkamerlab

gsl: svd.c:712: ERROR: Jacobi iterations did not reach desired tolerance
Default GSL error handler invoked.
Traceback (most recent call last):
  File "/home/jaime/.conda/envs/structuralalignment/bin/superposer", line 11, in <module>
    load_entry_point('superposer', 'console_scripts', 'superposer')()
  File "/home/jaime/devel/py/volkamerlab/superposer/superposer/cli.py", line 88, in main
    result, *_empty = align(
  File "/home/jaime/devel/py/volkamerlab/superposer/superposer/api.py", line 34, in align
    result = aligner.calculate([reference, mobile])
  File "/home/jaime/devel/py/volkamerlab/superposer/superposer/superposition/base.py", line 32, in calculate
    return self._calculate(structures, **kwargs)
  File "/home/jaime/devel/py/volkamerlab/superposer/superposer/superposition/theseus.py", line 182, in _calculate
    superposition_output = self._run_theseus_different(pdbs_filename)
  File "/home/jaime/devel/py/volkamerlab/superposer/superposer/superposition/theseus.py", line 262, in _run_theseus_different
    output = subprocess.check_output(
  File "/home/jaime/.conda/envs/structuralalignment/lib/python3.8/subprocess.py", line 411, in check_output
    return run(*popenargs, stdout=PIPE, timeout=timeout, check=True,
  File "/home/jaime/.conda/envs/structuralalignment/lib/python3.8/subprocess.py", line 512, in run
    raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['theseus', '-f', '-M', 'theseus.filemap', '-A', 'theseus.aln', '0.pdb', '1.pdb']' died with <Signals.SIGABRT: 6>.

This might be due to the presence of metals, and we should take care of that, but we should catch that error in a better way.

Turns out it's not the metal in 3pk2 but using exactly the same structure that messes the convergence  checks.


docs: Adjust phrasing of "From your desktop, click on the gear...".

https://chat.zulip.org/#narrow/stream/19-documentation/topic/.22From.20your.20.20desktop.2C.20click.20on.20the.20gear.22.20phrasing
We actually mean the main Zulip UI here, so "from your desktop" sounds
potentially misleading. It seems better to just remove the phrase, as it
isn't enlightening on where the gear is (main Zulip UI) and only risks
confusion that it's the users main desktop screen.

Do we want this sentence to end with "of the web or desktop app" for clarity?

Yeah, that sort of migration is probably a good idea, but I'd kinda only want to do that transition alongside adding mobile app tabs for workflows that one can absolutely do in the mobile app.  Maybe we should just do a pass of adding that content.

Merged after doing the tweak I suggested above; the tabs concept is a good idea but definitely more of a Project.


Basic version of Hyperbolic Matern kernel

Details can be found here.
Original source code is here (see Millson kernels).

While working on the kernel example for the sphere, I realized that we still have a general issue with the distances that we take from geomstats for the Hyperbolic and sphere manifold.
Namely, the distance d(x1,x2) seems to break if both x1 and x2 contains several data. For example, the second distance computed in the following code snippet breaks:
import numpy as np
from geometric_kernels.spaces.hyperbolic import Hyperbolic

hyperboloid = Hyperbolic(dim=2)
base = np.r_[7.14142843e+00, -5.00000000e+00, -5.00000000e+00]
point = np.r_[14.17744688, 10., 10.]
geodesic = hyperboloid.metric.geodesic(initial_point=base, end_point=point)
x1 = geodesic(np.linspace(0., 1., 100))
x2 = x1[-1, None]
x3 = np.vstack((x2, x2))
distances12 = hyperboloid.distance(x1, x2)
distances13 = hyperboloid.distance(x1, x3)

As the distance function is used for heat kernels and in the MaternIntegratedKernel, we may need to have a look at this (before merging?).

@NoemieJaquier thanks for the notice! I have commited a fix for this, please have a look!

@stoprightthere It seems to have fixed it, thank you!


check performance issues useHtmlMinifier/clientManifest

Current behavior

config useHtmlMinifier can multiply response time
with useHtmlMinifier:

without useHtmlMinifier:

We need to check memory consumption after
const clientManifest = require(resolve('dist/vue-ssr-client-manifest.json')) in core/scripts/server.ts
Memory dump before and after this :point_up: line in v1.8.0:

Same on the v1.11.0 :

Expected behavior

much smaller response time increase
Steps to reproduce the issue

Can you handle fixing this bug by yourself?

[ ] YES
[x] NO

Environment details

Browser:
OS:
Code Version:

Additional information

check on demo instance
check alternatives or what different flow we can apply

The first one - you can safely disable the htmlMinifier  - that's not an issue. It can significantly increase the response time depending on the HTML Document length; however, this feature was intended to work with some form of output cache enabled - to overcome this issue

The later one - from 1.9x on we're generating the clientManifest because it's required for the lazy-loading. I'm not sure if lazy-loading is doing well without this clientManifest imported. Do you have any observations regarding this? Reference: https://ssr.vuejs.org/guide/build-config.html#generating-clientmanifest


Can't get access application after install with docker

Hello,
Thanks a lot for this initiative !
I am having trouble installing the dockerized application.
The containers are launched well
CONTAINER ID   IMAGE                                         COMMAND                  CREATED          STATUS          PORTS																			NAMES a6a919f415c0   developeregrem/fewohbee-acme:latest           "crond -f"               13 minutes ago   Up 12 minutes																					fewohbee-acme-1 af1952916393   mariadb:10.9                                  "docker-entrypoint.s…"   13 minutes ago   Up 13 minutes   3306/tcp																			fewohbee-db-1 1cf571cb5286   developeregrem/fewohbee-phpfpm:latest         "/entrypoint.sh php-…"   13 minutes ago   Up 13 minutes   9000/tcp																			fewohbee-php-1 77c6f7e89019   nginx:mainline-alpine                         "/docker-entrypoint.…"   13 minutes ago   Up 12 minutes   <IP_ADDRESS>:8484->80/tcp, :::8484->80/tcp, <IP_ADDRESS>:4444->443/tcp, :::4444->443/tcp   fewohbee-web-1 a563ff4f7aae   redis:alpine                                  "docker-entrypoint.s…"   13 minutes ago   Up 12 minutes   6379/tcp																			fewohbee-redis-1
As can be seen, I have edited the docker-compose file to map the container's 80 and 443 ports respoctively to ports 8484 and 4444 of the docker host. I have an apache server which receive the requests and forward to the container.
The logs of the web container shows the queries are being rejected with a 301 response code
sudo docker logs -f fewohbee-web-1 <IP_ADDRESS> - - [02/Nov/2022:10:22:58 +0000] "GET / HTTP/1.1" 301 162 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36"
Last thing, since the certificates are handled by the docker host, I have manually edited the .env file to disable the certificate handling
LETSENCRYPT=false SELF_SIGNED=false
Don't know what to chek again. Please any direction ?
Looking forward to try the tool.
Dn

Hi @dnyamy thanks for you interest in the application :)
By default, the setup redirects all traffic from http to https. That is the 301 code. If your SSL/TLS termination is done by your own reverse proxy you need to disable this redirect.
First make sure that fewohbee can be handled using http:
cp conf/nginx/site-enabled-https/01_fewohbee.snippet conf/nginx/site-enabled-http

Second disable the redirect in the file conf/nginx/site.conf on line 18 (add comment character)
#    return         301 https://$server_name$request_uri;

And restart the web container
docker-compose restart web

Afterwards you should be able to see something ;)
Alex

Great !
It is better now
I can see the login page
But, please, can't find the temp credentials for first login
Dn

Good to hear!
For the login data please take a look here https://github.com/developeregrem/fewohbee/issues/61#issuecomment-1259776186

In deed, there is a problem with database setup
Some errors I can see
Creating db backup user ... ERROR 2002 (HY000): Can't connect to local server through socket '/run/mysqld/mysqld.sock' (2)
`
In ExceptionConverter.php line 101:
An exception occurred in the driver: SQLSTATE[HY000] [2002] Connection refused
In Exception.php line 28:
SQLSTATE[HY000] [2002] Connection refused
In Driver.php line 28:
SQLSTATE[HY000] [2002] Connection refused
`

I see ...
Can you give me some more information about your environment? Which operating system and what version are you using.
Can you provide me the full output of docker-compose logs php and docker-compose logs db please?

System info
Linux 5.4.0-124-generic x86_64 GNU/Linux
PHP logs
fewohbee-php-1  | HEAD is now at 535b1fd Merge pull request #60 from developeregrem/3.3.0-dev
fewohbee-php-1  | Installing dependencies from lock file
fewohbee-php-1  | Verifying lock file contents can be installed on current platform.
fewohbee-php-1  | Nothing to install, update or remove
fewohbee-php-1  | Generating optimized autoload files
fewohbee-php-1  | Class App\Entity\SpecialDays located in ./src/Entity/SpecialDay.php does not comply with psr-4 autoloading standard. Skipping.
fewohbee-php-1  | 78 packages you are using are looking for funding.
fewohbee-php-1  | Use the `composer fund` command to find out more!
fewohbee-php-1  |
fewohbee-php-1  | Run composer recipes at any time to see the status of your Symfony recipes.
fewohbee-php-1  |
fewohbee-php-1  | Executing script cache:clear [OK]
fewohbee-php-1  |
fewohbee-php-1  | Executing script assets:install public [OK]
fewohbee-php-1  | {"message":"Notified event \"console.command\" to listener \"Symfony\\Component\\HttpKernel\\EventListener\\DebugHandlersListener::configure\".","context":{"event":"console.command","listener":"Symfony\\Component\\HttpKernel\\EventListener\\DebugHandlersListener::configure"},"level":100,"level_name":"DEBUG","channel":"event","datetime":"2022-11-03T10:44:15.748586+01:00","extra":{}}
fewohbee-php-1  | {"message":"Notified event \"console.command\" to listener \"Symfony\\Bridge\\Monolog\\Handler\\ConsoleHandler::onCommand\".","context":{"event":"console.command","listener":"Symfony\\Bridge\\Monolog\\Handler\\ConsoleHandler::onCommand"},"level":100,"level_name":"DEBUG","channel":"event","datetime":"2022-11-03T10:44:15.748615+01:00","extra":{}}
fewohbee-php-1  | {"message":"Connecting with parameters array{\"driver\":\"pdo_mysql\",\"charset\":\"utf8mb4\",\"url\":\"<redacted>\",\"host\":\"db\",\"port\":3306,\"user\":\"fewohbee\",\"password\":\"<redacted>\",\"driverOptions\":[],\"serverVersion\":\"mariadb-10.8.3\",\"defaultTableOptions\":{\"charset\":\"utf8mb4\",\"collate\":\"utf8mb4_unicode_ci\"},\"dbname\":\"fewohbee\"}","context":{"params":{"driver":"pdo_mysql","charset":"utf8mb4","url":"<redacted>","host":"db","port":3306,"user":"fewohbee","password":"<redacted>","driverOptions":[],"serverVersion":"mariadb-10.8.3","defaultTableOptions":{"charset":"utf8mb4","collate":"utf8mb4_unicode_ci"},"dbname":"fewohbee"}},"level":200,"level_name":"INFO","channel":"doctrine","datetime":"2022-11-03T10:44:15.832508+01:00","extra":{}}
fewohbee-php-1  | {"message":"Error thrown while running command \"--no-interaction 'doctrine:migration:migrate'\".  Message:
"An exception occurred in the driver: SQLSTATE[HY000] [2002] Connection refused" ["exception" => Doctrine\DBAL\Exception\ConnectionException { …},"command" => "--no-interaction 'doctrine:migration:migrate'","message" => "An exception occurred in the driver: SQLSTATE[HY000] [2002] Connection refused"]
fewohbee-php-1  | {"message":"Notified event \"console.error\" to listener \"Symfony\\Bundle\\FrameworkBundle\\EventListener\\SuggestMissingPackageSubscriber::onConsoleError\".","context":{"event":"console.error","listener":"Symfony\\Bundle\\FrameworkBundle\\EventListener\\SuggestMissingPackageSubscriber::onConsoleError"},"level":100,"level_name":"DEBUG","channel":"event","datetime":"2022-11-03T10:44:15.869588+01:00","extra":{}}
fewohbee-php-1  | {"message":"Notified event \"console.error\" to listener \"Symfony\\Component\\Console\\EventListener\\ErrorListener::onConsoleError\".","context":{"event":"console.error","listener":"Symfony\\Component\\Console\\EventListener\\ErrorListener::onConsoleError"},"level":100,"level_name":"DEBUG","channel":"event","datetime":"2022-11-03T10:44:15.869669+01:00","extra":{}}
fewohbee-php-1  | {"message":"Command \"--no-interaction 'doctrine:migration:migrate'\" exited with code \"2002\"","context":{"command":"--no-interaction 'doctrine:migration:migrate'","code":2002},"level":100,"level_name":"DEBUG","channel":"console","datetime":"2022-11-03T10:44:15.870109+01:00","extra":{}}
fewohbee-php-1  | {"message":"Notified event \"console.terminate\" to listener \"Symfony\\Component\\Console\\EventListener\\ErrorListener::onConsoleTerminate\".","context":{"event":"console.terminate","listener":"Symfony\\Component\\Console\\EventListener\\ErrorListener::onConsoleTerminate"},"level":100,"level_name":"DEBUG","channel":"event","datetime":"2022-11-03T10:44:15.870197+01:00","extra":{}}
fewohbee-php-1  | {"message":"Notified event \"console.terminate\" to listener \"Symfony\\Bridge\\Monolog\\Handler\\ConsoleHandler::onTerminate\".","context":{"event":"console.terminate","listener":"Symfony\\Bridge\\Monolog\\Handler\\ConsoleHandler::onTerminate"},"level":100,"level_name":"DEBUG","channel":"event","datetime":"2022-11-03T10:44:15.870342+01:00","extra":{}}
fewohbee-php-1  |
fewohbee-php-1  | In ExceptionConverter.php line 101:
fewohbee-php-1  |
fewohbee-php-1  |   An exception occurred in the driver: SQLSTATE[HY000] [2002] Connection refu
fewohbee-php-1  |   sed
fewohbee-php-1  |
fewohbee-php-1  |
fewohbee-php-1  | In Exception.php line 28:
fewohbee-php-1  |
fewohbee-php-1  |   SQLSTATE[HY000] [2002] Connection refused
fewohbee-php-1  |
fewohbee-php-1  |
fewohbee-php-1  | In Driver.php line 28:
fewohbee-php-1  |
fewohbee-php-1  |   SQLSTATE[HY000] [2002] Connection refused
fewohbee-php-1  |
fewohbee-php-1  |
fewohbee-php-1  | doctrine:migrations:migrate [--write-sql [WRITE-SQL]] [--dry-run] [--query-time] [--allow-no-migration] [--all-or-nothing
[ALL-OR-NOTHING]] [--configuration CONFIGURATION] [--em EM] [--conn CONN] [--] [<version>]
fewohbee-php-1  |
fewohbee-php-1  |
fewohbee-php-1  |  // Clearing cache pool: doctrine.result_cache_pool
fewohbee-php-1  |
fewohbee-php-1  |  // Clearing cache pool: doctrine.system_cache_pool
fewohbee-php-1  |
fewohbee-php-1  |  [OK] Cache was successfully cleared.
fewohbee-php-1  |
fewohbee-php-1  | [03-Nov-2022 10:44:16] NOTICE: fpm is running, pid 1
fewohbee-php-1  | [03-Nov-2022 10:44:16] NOTICE: ready to handle connections

DB logs

Hi,
currently I'm not able to reproduce the issue. I've tested different setups :(
Are you using debian/ubuntu or something else?
Please try to reset everthing again and also delete the fewohbee folder inside /opt/data
The only thing I can see based on the logs is that the db server might be up an running too late and the connection is required earlier. So what you can also try to do is add another short delay here:
https://github.com/developeregrem/fewohbee-dockerized/blob/53eec58bdde5d9be3d58516e4975d202b0132696/install.sh#L194
sleep 5

Did as you said
No error appear. But still I can't see the temp password
$docker-compose logs php
fewohbee-php-1  | HEAD is now at 535b1fd Merge pull request #60 from developeregrem/3.3.0-dev
fewohbee-php-1  | Installing dependencies from lock file
fewohbee-php-1  | Verifying lock file contents can be installed on current platform.
fewohbee-php-1  | Nothing to install, update or remove
fewohbee-php-1  | Generating optimized autoload files
fewohbee-php-1  | Class App\Entity\SpecialDays located in ./src/Entity/SpecialDay.php does not comply with psr-4 autoloading standard. Skipping.
fewohbee-php-1  | 78 packages you are using are looking for funding.
fewohbee-php-1  | Use the `composer fund` command to find out more!
fewohbee-php-1  |
fewohbee-php-1  | Run composer recipes at any time to see the status of your Symfony recipes.
fewohbee-php-1  |
fewohbee-php-1  | Executing script cache:clear [OK]
fewohbee-php-1  | Executing script assets:install public [OK]
fewohbee-php-1  |
fewohbee-php-1  | [notice] Migrating up to DoctrineMigrations\Version20220820130837
fewohbee-php-1  | [warning] Migration DoctrineMigrations\Version20190906160425 was executed but did not result in any SQL statements.
fewohbee-php-1  | [warning] Migration DoctrineMigrations\Version20190915110513 was executed but did not result in any SQL statements.
fewohbee-php-1  | [notice] finished in 32850.4ms, used 10M memory, 14 migrations executed, 101 sql queries
fewohbee-php-1  |
fewohbee-php-1  |
fewohbee-php-1  |  // Clearing cache pool: doctrine.result_cache_pool
fewohbee-php-1  |
fewohbee-php-1  |  // Clearing cache pool: doctrine.system_cache_pool
fewohbee-php-1  |
fewohbee-php-1  |  [OK] Cache was successfully cleared.
fewohbee-php-1  |
fewohbee-php-1  | [07-Nov-2022 11:04:53] NOTICE: fpm is running, pid 1
fewohbee-php-1  | [07-Nov-2022 11:04:53] NOTICE: ready to handle connections
fewohbee-php-1  | <IP_ADDRESS> -  07/Nov/2022:11:05:33 +0100 "GET /index.php" 302
fewohbee-php-1  | <IP_ADDRESS> -  07/Nov/2022:11:05:35 +0100 "GET /index.php" 200
fewohbee-php-1  | <IP_ADDRESS> -  07/Nov/2022:11:06:31 +0100 "GET /index.php" 200

docker-compose logs db
fewohbee-db-1  | 2022-11-07 10:04:04+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.9.3+maria~ubu2204 started.
fewohbee-db-1  | 2022-11-07 10:04:05+00:00 [Note] [Entrypoint]: Switching to dedicated user 'mysql'
fewohbee-db-1  | 2022-11-07 10:04:05+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.9.3+maria~ubu2204 started.
fewohbee-db-1  | 2022-11-07 10:04:07+00:00 [Note] [Entrypoint]: MariaDB upgrade not required
fewohbee-db-1  | 2022-11-07 10:04:07 0 [Note] mariadbd (server 10.9.3-MariaDB-1:10.9.3+maria~ubu2204) starting as process 1 ...
fewohbee-db-1  | 2022-11-07 10:04:07 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
fewohbee-db-1  | 2022-11-07 10:04:07 0 [Note] InnoDB: Number of transaction pools: 1
fewohbee-db-1  | 2022-11-07 10:04:07 0 [Note] InnoDB: Using crc32 + pclmulqdq instructions
fewohbee-db-1  | 2022-11-07 10:04:07 0 [Note] mariadbd: O_TMPFILE is not supported on /tmp (disabling future attempts)
fewohbee-db-1  | 2022-11-07 10:04:07 0 [Warning] mariadbd: io_uring_queue_init() failed with ENOMEM: try larger memory locked limit, ulimit -l, or https://mariadb.com/kb/en/systemd/#configuring-limitmemlock under systemd (262144 bytes required)
fewohbee-db-1  | 2022-11-07 10:04:07 0 [Warning] InnoDB: liburing disabled: falling back to innodb_use_native_aio=OFF
fewohbee-db-1  | 2022-11-07 10:04:07 0 [Note] InnoDB: Initializing buffer pool, total size = 128.000MiB, chunk size = 2.000MiB
fewohbee-db-1  | 2022-11-07 10:04:07 0 [Note] InnoDB: Completed initialization of buffer pool
fewohbee-db-1  | 2022-11-07 10:04:07 0 [Note] InnoDB: File system buffers for log disabled (block size=512 bytes)
fewohbee-db-1  | 2022-11-07 10:04:07 0 [Note] InnoDB: 128 rollback segments are active.
fewohbee-db-1  | 2022-11-07 10:04:07 0 [Note] InnoDB: Setting file './ibtmp1' size to 12.000MiB. Physically writing the file full; Please wait ...
fewohbee-db-1  | 2022-11-07 10:04:07 0 [Note] InnoDB: File './ibtmp1' size is now 12.000MiB.
fewohbee-db-1  | 2022-11-07 10:04:07 0 [Note] InnoDB: log sequence number 46488; transaction id 14
fewohbee-db-1  | 2022-11-07 10:04:07 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
fewohbee-db-1  | 2022-11-07 10:04:07 0 [Note] Plugin 'FEEDBACK' is disabled.
fewohbee-db-1  | 2022-11-07 10:04:07 0 [Warning] You need to use --log-bin to make --expire-logs-days or --binlog-expire-logs-seconds work.
fewohbee-db-1  | 2022-11-07 10:04:07 0 [Note] InnoDB: Buffer pool(s) load completed at 221107 10:04:07
fewohbee-db-1  | 2022-11-07 10:04:07 0 [Note] Server socket created on IP: '<IP_ADDRESS>'.
fewohbee-db-1  | 2022-11-07 10:04:07 0 [Note] Server socket created on IP: '::'.
fewohbee-db-1  | 2022-11-07 10:04:07 0 [Note] mariadbd: ready for connections.
fewohbee-db-1  | Version: '10.9.3-MariaDB-1:10.9.3+maria~ubu2204'  socket: '/run/mysqld/mysqld.sock'  port: 3306  mariadb.org binary distribution

Thanks

Did you run ./install.sh after reset or just docker-compose up -d?
You should be asked to define your own credentials ...
But you can perform this action manually too:
docker-compose exec --user www-data php /bin/sh -c "php fewohbee/bin/console app:first-run"

and afterwards
docker-compose exec --user www-data php /bin/sh -c "php fewohbee/bin/console doctrine:fixtures:load --append

Hello,
I have tried many times
The error message does give a bit more details
But still, no password
I have even tried to define manually with your command
Getting the same error

fewohbee-php-1  | In ExceptionConverter.php line 101:
fewohbee-php-1  |
fewohbee-php-1  |   An exception occurred in the driver: SQLSTATE[HY000] [1045] Access denied f
fewohbee-php-1  |   or user<EMAIL_ADDRESS>(using password: YES)
fewohbee-php-1  |
fewohbee-php-1  |
fewohbee-php-1  | In Exception.php line 28:
fewohbee-php-1  |
fewohbee-php-1  |   SQLSTATE[HY000] [1045] Access denied for user<EMAIL_ADDRESS>(us
fewohbee-php-1  |   ing password: YES)
fewohbee-php-1  |
fewohbee-php-1  |
fewohbee-php-1  | In Driver.php line 28:
fewohbee-php-1  |
fewohbee-php-1  |   SQLSTATE[HY000] [1045] Access denied for user<EMAIL_ADDRESS>(us
fewohbee-php-1  |   ing password: YES)

This is very strange :(
The only thing I would do is to do a complete reset of the installation again (and keep your sleep in the install.sh file)
cd /opt/fewohbee-dockerized
./cleanup.sh
rm .env
rm -r ../data/fewohbee
./install.sh

After install you should also check whether you can login to the db manually
docker-compose exec db /bin/bash
mysql -p$MYSQL_PASSWORD -u$MYSQL_USER $MYSQL_DATABASE

If the login is working than the user should work as expected
(2x Strg+D at the end to exit the db and the container)

Another new error,
After cleanup, rm .env ...
In ExceptionConverter.php line 49:

  An exception occurred while executing a query: SQLSTATE[42S02]: Base table or view not found: 1146 Table 'fewohbee.reservation_origins' doesn't exist

In Exception.php line 28:

  SQLSTATE[42S02]: Base table or view not found: 1146 Table 'fewohbee.reservation_origins' doesn't exist

In Statement.php line 134:

  SQLSTATE[42S02]: Base table or view not found: 1146 Table 'fewohbee.reservation_origins' doesn't exist

Hi, sorry for the late response. I'm not able to reproduce the issue either when using ubutnu.
Maybe you can try the version without docker/docker-compose. See LAMP-Stack:-Apache,-MySQL,-PHP-(Ubuntu-22)

Thanks for this reply,
I have tried and am experiencing issues also with that method.
https://github.com/developeregrem/fewohbee/issues/75
I looks forward to trying the application.

Hello,
I try to switch back to dockerized version
I have started all over
docker-compose exec db /bin/bash
mysql -p$MYSQL_PASSWORD -u$MYSQL_USER $MYSQL_DATABASE

I am able to login to db manually now
But DB is empty.
MariaDB [fewohbee]> show tables;
Empty set (0.001 sec)

MariaDB [fewohbee]>

Is that normal ?

Something in your setup/installation seems to be broken :( But I have no idea what went wrong. The database must be filled if no errors occurred during setup process.
I guess you will find some messages in docker-compose logs php?
I can provide you a demo access to a running version of fewohbee if you want to play a bit with the application. Please email me to info @ fewohbee.de if you are interested and I provide you credentials.


Mvnrepository pom dependency provided or optional

Why pom dependecy in maven central is marked with scope=provided. If the library is only used for compilaion time it wouldn't be better use it as 'true' instead provided?

Can you supply actual pom files to explain what you mean?

yes sorry, my question is not a bug properly and maybe this is not the location to get information about it, so i close the issue.
Thanks