text:
Synthesis failed for java-securitycenter

Hello! Autosynth couldn't regenerate java-securitycenter. :broken_heart:
Here's the output from running synth.py:
Cloning into 'working_repo'...
Switched to a new branch 'autosynth'
Cloning into '/tmpfs/tmp/tmpcc83u0mo/googleapis'...
Cloning into '/tmpfs/tmp/tmpcc83u0mo/synthtool'...
Switched to branch 'autosynth-self'
Note: checking out '760ebf4cf4bd26b10451113bd7141f8303cf238f'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at 760ebf4 deps: update dependency com.google.api.grpc:proto-google-common-protos to v1.18.0 (#135)
Note: checking out 'f8a9933e5e98202b04ef427f28d1d79221190fa4'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at f8a9933 chore(java): allow overriding the versioning section of the Java README (#495)
Note: checking out '862cd840dbb0101a0630913217bf8b6d4101c84c'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at 862cd840 chore: Update gapic-generator version The updated version is required to migrate Python clients generation from artman to bazel.
Switched to a new branch 'autosynth-self-2'
2020-05-05 21:33:35 [INFO] Running synthtool
2020-05-05 21:33:35 [INFO] ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
2020-05-05 21:33:35,915 synthtool > Executing /tmpfs/src/github/synthtool/working_repo/synth.py.
On branch autosynth-self-2
nothing to commit, working tree clean
2020-05-05 21:33:36,050 synthtool > Ensuring dependencies.
2020-05-05 21:33:36,060 synthtool > Cloning googleapis.
2020-05-05 21:33:36,061 synthtool > Using precloned repo /tmpfs/tmp/tmpcc83u0mo/googleapis
2020-05-05 21:33:36,066 synthtool > Generating code for: //google/cloud/securitycenter/v1p1beta1:google-cloud-securitycenter-v1p1beta1-java.
2020-05-05 21:33:36,177 synthtool > Failed executing bazel build //google/cloud/securitycenter/v1p1beta1:google-cloud-securitycenter-v1p1beta1-java:

Starting local Bazel server and connecting to it...
Server crashed during startup. Now printing /home/kbuilder/.cache/bazel/_bazel_kbuilder/a56822ff179d373d0213511ef915af9a/server/jvm.out
OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x0000000715200000, 247463936, 0) failed; error='Not enough space' (errno=12)
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (mmap) failed to map 247463936 bytes for committing reserved memory.
# An error report file with more information is saved as:
# /tmpfs/tmp/tmpcc83u0mo/googleapis/hs_err_pid27224.log

2020-05-05 21:33:36,178 synthtool > Wrote metadata to synth.metadata.
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 "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/tmpfs/src/github/synthtool/working_repo/synth.py", line 28, in <module>
    bazel_target=f'//google/cloud/{service}/{version}:google-cloud-{service}-{version}-java',
  File "/tmpfs/src/github/synthtool/synthtool/languages/java.py", line 310, in bazel_library
    library = gapic.java_library(service=service, version=version, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 63, in java_library
    return self._generate_code(service, version, "java", **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 177, in _generate_code
    shell.run(bazel_run_args)
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 39, in run
    raise exc
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 33, in run
    encoding="utf-8",
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['bazel', 'build', '//google/cloud/securitycenter/v1p1beta1:google-cloud-securitycenter-v1p1beta1-java']' returned non-zero exit status 37.
2020-05-05 21:33:36 [ERROR] Synthesis failed
HEAD is now at 760ebf4 deps: update dependency com.google.api.grpc:proto-google-common-protos to v1.18.0 (#135)
Switched to branch 'autosynth-self'
Note: checking out '760ebf4cf4bd26b10451113bd7141f8303cf238f'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at 760ebf4 deps: update dependency com.google.api.grpc:proto-google-common-protos to v1.18.0 (#135)
Previous HEAD position was f8a9933 chore(java): allow overriding the versioning section of the Java README (#495)
HEAD is now at ab88356 fix: make .kokoro-autosynth executable (#522)
Previous HEAD position was 862cd840 chore: Update gapic-generator version The updated version is required to migrate Python clients generation from artman to bazel.
HEAD is now at a3a0bf0f BREAKING_CHANGE: Removing TimeSeriesQueryLanguageCondition as an alert condition type. The condition type is unsupported and unused. It was originally added for the Monitoring Query Language Alpha feature. refactor!: Drop support for TimeSeriesQueryLanguageCondition as an alert condition type.
Switched to a new branch 'autosynth-43'
2020-05-05 21:33:36 [INFO] Running synthtool
2020-05-05 21:33:36 [INFO] ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
2020-05-05 21:33:36,482 synthtool > Executing /tmpfs/src/github/synthtool/working_repo/synth.py.
On branch autosynth-43
nothing to commit, working tree clean
2020-05-05 21:33:36,613 synthtool > Ensuring dependencies.
2020-05-05 21:33:36,624 synthtool > Cloning googleapis.
2020-05-05 21:33:36,624 synthtool > Using precloned repo /tmpfs/tmp/tmpcc83u0mo/googleapis
2020-05-05 21:33:36,629 synthtool > Generating code for: //google/cloud/securitycenter/v1p1beta1:google-cloud-securitycenter-v1p1beta1-java.
2020-05-05 21:33:36,739 synthtool > Failed executing bazel build //google/cloud/securitycenter/v1p1beta1:google-cloud-securitycenter-v1p1beta1-java:

Starting local Bazel server and connecting to it...
Server crashed during startup. Now printing /home/kbuilder/.cache/bazel/_bazel_kbuilder/a56822ff179d373d0213511ef915af9a/server/jvm.out
OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x0000000715200000, 247463936, 0) failed; error='Not enough space' (errno=12)
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (mmap) failed to map 247463936 bytes for committing reserved memory.
# An error report file with more information is saved as:
# /tmpfs/tmp/tmpcc83u0mo/googleapis/hs_err_pid27259.log

2020-05-05 21:33:36,740 synthtool > Wrote metadata to synth.metadata.
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 "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/tmpfs/src/github/synthtool/working_repo/synth.py", line 28, in <module>
    bazel_target=f'//google/cloud/{service}/{version}:google-cloud-{service}-{version}-java',
  File "/tmpfs/src/github/synthtool/synthtool/languages/java.py", line 310, in bazel_library
    library = gapic.java_library(service=service, version=version, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 63, in java_library
    return self._generate_code(service, version, "java", **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 177, in _generate_code
    shell.run(bazel_run_args)
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 39, in run
    raise exc
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 33, in run
    encoding="utf-8",
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['bazel', 'build', '//google/cloud/securitycenter/v1p1beta1:google-cloud-securitycenter-v1p1beta1-java']' returned non-zero exit status 37.
2020-05-05 21:33:36 [ERROR] Synthesis failed
HEAD is now at 760ebf4 deps: update dependency com.google.api.grpc:proto-google-common-protos to v1.18.0 (#135)
Switched to branch 'autosynth'
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 584, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 465, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 574, in _inner_main
    commit_count = synthesize_loop(x, multiple_prs, change_pusher, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 360, in synthesize_loop
    synthesize_inner_loop(toolbox, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 370, in synthesize_inner_loop
    synthesizer, len(toolbox.versions) - 1
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 259, in synthesize_version_in_new_branch
    synthesizer.synthesize(self.environ)
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 115, 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', 'synth.metadata', 'synth.py', '--']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth is still having trouble generating java-securitycenter. :sob:
Here's the output from running synth.py:
Cloning into 'working_repo'...
Switched to a new branch 'autosynth'
Cloning into '/tmpfs/tmp/tmpo891f4n0/googleapis'...
Cloning into '/tmpfs/tmp/tmpo891f4n0/synthtool'...
Switched to branch 'autosynth-self'
Note: checking out '760ebf4cf4bd26b10451113bd7141f8303cf238f'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at 760ebf4 deps: update dependency com.google.api.grpc:proto-google-common-protos to v1.18.0 (#135)
Note: checking out 'f8a9933e5e98202b04ef427f28d1d79221190fa4'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at f8a9933 chore(java): allow overriding the versioning section of the Java README (#495)
Note: checking out '862cd840dbb0101a0630913217bf8b6d4101c84c'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at 862cd840 chore: Update gapic-generator version The updated version is required to migrate Python clients generation from artman to bazel.
Switched to a new branch 'autosynth-self-2'
2020-05-07 07:02:46 [INFO] Running synthtool
2020-05-07 07:02:46 [INFO] ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
2020-05-07 07:02:47,102 synthtool > Executing /tmpfs/src/github/synthtool/working_repo/synth.py.
On branch autosynth-self-2
nothing to commit, working tree clean
2020-05-07 07:02:47,234 synthtool > Ensuring dependencies.
2020-05-07 07:02:47,245 synthtool > Cloning googleapis.
2020-05-07 07:02:47,246 synthtool > Using precloned repo /tmpfs/tmp/tmpo891f4n0/googleapis
2020-05-07 07:02:47,250 synthtool > Generating code for: //google/cloud/securitycenter/v1p1beta1:google-cloud-securitycenter-v1p1beta1-java.
2020-05-07 07:02:47,360 synthtool > Failed executing bazel build //google/cloud/securitycenter/v1p1beta1:google-cloud-securitycenter-v1p1beta1-java:

Starting local Bazel server and connecting to it...
Server crashed during startup. Now printing /home/kbuilder/.cache/bazel/_bazel_kbuilder/bc94f9e607244d22551a2e187e2becb3/server/jvm.out
OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x0000000715200000, 247463936, 0) failed; error='Not enough space' (errno=12)
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (mmap) failed to map 247463936 bytes for committing reserved memory.
# An error report file with more information is saved as:
# /tmpfs/tmp/tmpo891f4n0/googleapis/hs_err_pid20268.log

2020-05-07 07:02:47,361 synthtool > Wrote metadata to synth.metadata.
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 "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/tmpfs/src/github/synthtool/working_repo/synth.py", line 28, in <module>
    bazel_target=f'//google/cloud/{service}/{version}:google-cloud-{service}-{version}-java',
  File "/tmpfs/src/github/synthtool/synthtool/languages/java.py", line 310, in bazel_library
    library = gapic.java_library(service=service, version=version, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 63, in java_library
    return self._generate_code(service, version, "java", **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 177, in _generate_code
    shell.run(bazel_run_args)
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 39, in run
    raise exc
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 33, in run
    encoding="utf-8",
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['bazel', 'build', '//google/cloud/securitycenter/v1p1beta1:google-cloud-securitycenter-v1p1beta1-java']' returned non-zero exit status 37.
2020-05-07 07:02:47 [ERROR] Synthesis failed
HEAD is now at 760ebf4 deps: update dependency com.google.api.grpc:proto-google-common-protos to v1.18.0 (#135)
Switched to branch 'autosynth-self'
Note: checking out '760ebf4cf4bd26b10451113bd7141f8303cf238f'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at 760ebf4 deps: update dependency com.google.api.grpc:proto-google-common-protos to v1.18.0 (#135)
Previous HEAD position was f8a9933 chore(java): allow overriding the versioning section of the Java README (#495)
HEAD is now at be74d3e build: do not fail builds on codecov errors (#528)
Previous HEAD position was 862cd840 chore: Update gapic-generator version The updated version is required to migrate Python clients generation from artman to bazel.
HEAD is now at 2fc2caaa chore: enable gapic v2 and proto annotation for bigquery/storage/v1beta2 API.
Switched to a new branch 'autosynth-51'
2020-05-07 07:02:47 [INFO] Running synthtool
2020-05-07 07:02:47 [INFO] ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
2020-05-07 07:02:47,664 synthtool > Executing /tmpfs/src/github/synthtool/working_repo/synth.py.
On branch autosynth-51
nothing to commit, working tree clean
2020-05-07 07:02:47,797 synthtool > Ensuring dependencies.
2020-05-07 07:02:47,808 synthtool > Cloning googleapis.
2020-05-07 07:02:47,809 synthtool > Using precloned repo /tmpfs/tmp/tmpo891f4n0/googleapis
2020-05-07 07:02:47,813 synthtool > Generating code for: //google/cloud/securitycenter/v1p1beta1:google-cloud-securitycenter-v1p1beta1-java.
2020-05-07 07:02:47,924 synthtool > Failed executing bazel build //google/cloud/securitycenter/v1p1beta1:google-cloud-securitycenter-v1p1beta1-java:

Starting local Bazel server and connecting to it...
Server crashed during startup. Now printing /home/kbuilder/.cache/bazel/_bazel_kbuilder/bc94f9e607244d22551a2e187e2becb3/server/jvm.out
OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x0000000715200000, 247463936, 0) failed; error='Not enough space' (errno=12)
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (mmap) failed to map 247463936 bytes for committing reserved memory.
# An error report file with more information is saved as:
# /tmpfs/tmp/tmpo891f4n0/googleapis/hs_err_pid20304.log

2020-05-07 07:02:47,925 synthtool > Wrote metadata to synth.metadata.
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 "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/tmpfs/src/github/synthtool/working_repo/synth.py", line 28, in <module>
    bazel_target=f'//google/cloud/{service}/{version}:google-cloud-{service}-{version}-java',
  File "/tmpfs/src/github/synthtool/synthtool/languages/java.py", line 310, in bazel_library
    library = gapic.java_library(service=service, version=version, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 63, in java_library
    return self._generate_code(service, version, "java", **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 177, in _generate_code
    shell.run(bazel_run_args)
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 39, in run
    raise exc
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 33, in run
    encoding="utf-8",
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['bazel', 'build', '//google/cloud/securitycenter/v1p1beta1:google-cloud-securitycenter-v1p1beta1-java']' returned non-zero exit status 37.
2020-05-07 07:02:47 [ERROR] Synthesis failed
HEAD is now at 760ebf4 deps: update dependency com.google.api.grpc:proto-google-common-protos to v1.18.0 (#135)
Switched to branch 'autosynth'
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 584, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 465, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 574, in _inner_main
    commit_count = synthesize_loop(x, multiple_prs, change_pusher, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 360, in synthesize_loop
    synthesize_inner_loop(toolbox, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 370, in synthesize_inner_loop
    synthesizer, len(toolbox.versions) - 1
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 259, in synthesize_version_in_new_branch
    synthesizer.synthesize(self.environ)
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 115, 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', 'synth.metadata', 'synth.py', '--']' returned non-zero exit status 1.

Google internal developers can see the full log here.

Autosynth is still having trouble generating java-securitycenter. :sob:
Here's the output from running synth.py:
Cloning into 'working_repo'...
Switched to a new branch 'autosynth'
Cloning into '/tmpfs/tmp/tmpihzsfsw7/googleapis'...
Cloning into '/tmpfs/tmp/tmpihzsfsw7/synthtool'...
Switched to branch 'autosynth-self'
Note: checking out '760ebf4cf4bd26b10451113bd7141f8303cf238f'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at 760ebf4 deps: update dependency com.google.api.grpc:proto-google-common-protos to v1.18.0 (#135)
Note: checking out 'f8a9933e5e98202b04ef427f28d1d79221190fa4'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at f8a9933 chore(java): allow overriding the versioning section of the Java README (#495)
Note: checking out '862cd840dbb0101a0630913217bf8b6d4101c84c'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at 862cd840 chore: Update gapic-generator version The updated version is required to migrate Python clients generation from artman to bazel.
Switched to a new branch 'autosynth-self-2'
2020-05-08 03:28:41 [INFO] Running synthtool
2020-05-08 03:28:41 [INFO] ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
2020-05-08 03:28:41,560 synthtool > Executing /tmpfs/src/github/synthtool/working_repo/synth.py.
On branch autosynth-self-2
nothing to commit, working tree clean
2020-05-08 03:28:41,715 synthtool > Ensuring dependencies.
2020-05-08 03:28:41,725 synthtool > Cloning googleapis.
2020-05-08 03:28:41,726 synthtool > Using precloned repo /tmpfs/tmp/tmpihzsfsw7/googleapis
2020-05-08 03:28:41,730 synthtool > Generating code for: //google/cloud/securitycenter/v1p1beta1:google-cloud-securitycenter-v1p1beta1-java.
2020-05-08 03:28:41,841 synthtool > Failed executing bazel build //google/cloud/securitycenter/v1p1beta1:google-cloud-securitycenter-v1p1beta1-java:

Starting local Bazel server and connecting to it...
Server crashed during startup. Now printing /home/kbuilder/.cache/bazel/_bazel_kbuilder/984792f5f6aef79a04253169a735e3ca/server/jvm.out
OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x0000000715200000, 247463936, 0) failed; error='Not enough space' (errno=12)
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (mmap) failed to map 247463936 bytes for committing reserved memory.
# An error report file with more information is saved as:
# /tmpfs/tmp/tmpihzsfsw7/googleapis/hs_err_pid29881.log

2020-05-08 03:28:41,842 synthtool > Wrote metadata to synth.metadata.
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 "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/tmpfs/src/github/synthtool/working_repo/synth.py", line 28, in <module>
    bazel_target=f'//google/cloud/{service}/{version}:google-cloud-{service}-{version}-java',
  File "/tmpfs/src/github/synthtool/synthtool/languages/java.py", line 310, in bazel_library
    library = gapic.java_library(service=service, version=version, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 63, in java_library
    return self._generate_code(service, version, "java", **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 177, in _generate_code
    shell.run(bazel_run_args)
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 39, in run
    raise exc
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 33, in run
    encoding="utf-8",
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['bazel', 'build', '//google/cloud/securitycenter/v1p1beta1:google-cloud-securitycenter-v1p1beta1-java']' returned non-zero exit status 37.
2020-05-08 03:28:41 [ERROR] Synthesis failed
HEAD is now at 760ebf4 deps: update dependency com.google.api.grpc:proto-google-common-protos to v1.18.0 (#135)
Switched to branch 'autosynth-self'
Note: checking out '760ebf4cf4bd26b10451113bd7141f8303cf238f'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at 760ebf4 deps: update dependency com.google.api.grpc:proto-google-common-protos to v1.18.0 (#135)
Previous HEAD position was f8a9933 chore(java): allow overriding the versioning section of the Java README (#495)
HEAD is now at 4674113 build: use Bazel 3.0.0 for autosynth builds (#529)
Previous HEAD position was 862cd840 chore: Update gapic-generator version The updated version is required to migrate Python clients generation from artman to bazel.
HEAD is now at 83816bb3 Add kokoro-specific .bazelrc file with arguments specific only for kokoro environments. This is to fix autosynth builds when it tries building older commits.
Switched to a new branch 'autosynth-56'
2020-05-08 03:28:41 [INFO] Running synthtool
2020-05-08 03:28:41 [INFO] ['/tmpfs/src/github/synthtool/env/bin/python3', '-m', 'synthtool', '--metadata', 'synth.metadata', 'synth.py', '--']
2020-05-08 03:28:42,160 synthtool > Executing /tmpfs/src/github/synthtool/working_repo/synth.py.
On branch autosynth-56
nothing to commit, working tree clean
2020-05-08 03:28:42,300 synthtool > Ensuring dependencies.
2020-05-08 03:28:42,310 synthtool > Cloning googleapis.
2020-05-08 03:28:42,311 synthtool > Using precloned repo /tmpfs/tmp/tmpihzsfsw7/googleapis
2020-05-08 03:28:42,315 synthtool > Generating code for: //google/cloud/securitycenter/v1p1beta1:google-cloud-securitycenter-v1p1beta1-java.
2020-05-08 03:28:42,428 synthtool > Failed executing bazel build //google/cloud/securitycenter/v1p1beta1:google-cloud-securitycenter-v1p1beta1-java:

Starting local Bazel server and connecting to it...
Server crashed during startup. Now printing /home/kbuilder/.cache/bazel/_bazel_kbuilder/984792f5f6aef79a04253169a735e3ca/server/jvm.out
OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x0000000715200000, 247463936, 0) failed; error='Not enough space' (errno=12)
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (mmap) failed to map 247463936 bytes for committing reserved memory.
# An error report file with more information is saved as:
# /tmpfs/tmp/tmpihzsfsw7/googleapis/hs_err_pid29916.log

2020-05-08 03:28:42,429 synthtool > Wrote metadata to synth.metadata.
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 "<frozen importlib._bootstrap_external>", line 678, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/tmpfs/src/github/synthtool/working_repo/synth.py", line 28, in <module>
    bazel_target=f'//google/cloud/{service}/{version}:google-cloud-{service}-{version}-java',
  File "/tmpfs/src/github/synthtool/synthtool/languages/java.py", line 310, in bazel_library
    library = gapic.java_library(service=service, version=version, **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 63, in java_library
    return self._generate_code(service, version, "java", **kwargs)
  File "/tmpfs/src/github/synthtool/synthtool/gcp/gapic_bazel.py", line 177, in _generate_code
    shell.run(bazel_run_args)
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 39, in run
    raise exc
  File "/tmpfs/src/github/synthtool/synthtool/shell.py", line 33, in run
    encoding="utf-8",
  File "/home/kbuilder/.pyenv/versions/3.6.9/lib/python3.6/subprocess.py", line 438, in run
    output=stdout, stderr=stderr)
subprocess.CalledProcessError: Command '['bazel', 'build', '//google/cloud/securitycenter/v1p1beta1:google-cloud-securitycenter-v1p1beta1-java']' returned non-zero exit status 37.
2020-05-08 03:28:42 [ERROR] Synthesis failed
HEAD is now at 760ebf4 deps: update dependency com.google.api.grpc:proto-google-common-protos to v1.18.0 (#135)
Switched to branch 'autosynth'
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 584, in <module>
    main()
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 465, in main
    return _inner_main(temp_dir)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 574, in _inner_main
    commit_count = synthesize_loop(x, multiple_prs, change_pusher, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 360, in synthesize_loop
    synthesize_inner_loop(toolbox, synthesizer)
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 370, in synthesize_inner_loop
    synthesizer, len(toolbox.versions) - 1
  File "/tmpfs/src/github/synthtool/autosynth/synth.py", line 259, in synthesize_version_in_new_branch
    synthesizer.synthesize(self.environ)
  File "/tmpfs/src/github/synthtool/autosynth/synthesizer.py", line 115, 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', 'synth.metadata', 'synth.py', '--']' returned non-zero exit status 1.

Google internal developers can see the full log here.

repo: googleapis/java-securitycenter


text:
test: verify that callback is not called while paused

Adds a test to verify that the callback function of an AsyncResultSet is not called while the result set is paused.

@olavloite I think I might be missing some context on this one. Do you mind providing some details?

source: gharchive/pull-request

authors: olavloite thiagotnunes

repo: googleapis/java-spanner

license_type: permissive

license_source: bigquery


text:
allow cancelling a resumable upload

Thanks for stopping by to let us know something could be better!
Is your feature request related to a problem? Please describe.
The underlying resumable upload API allows canceling an upload. However, the WriteChannel returned by the Storage.writer methods has no way to cancel the upload.
Describe the solution you'd like
Add an API like cancel to the object returned from Storage.write.
Describe alternatives you've considered
n/a
Additional context
Any other context or screenshots about the feature request.

This is a shortcoming we are aware of, but haven't yet implemented it (we're having to tease apart some things due to the fact WriteChannel us used by more than just GCS).
Some good news, resumable uploads will be automatically reaped by GCS one week after they are created if they are not finalized. In order to not finalize, simply never call writer#close()
Unfortunately I don't have an estimated of when we will be able to provide a cancel or abort for a resumable upload.

source: gharchive/issue

authors: BenWhitehead benjaminp

repo: googleapis/java-storage

license_source: github-api


text:
java.lang.NullPointerException

 Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'void androidx.work.WorkManager.enqueue(androidx.work.WorkRequest[])' on a null object reference

 // Create a Constraints that defines when the task should run         if (android.os.Build.VERSION.SDK_INT >= android.os.Build.VERSION_CODES.M) {             PeriodicWorkRequest.Builder photoCheckBuilder =                     new PeriodicWorkRequest.Builder(AppInitManager.class, 15,                             TimeUnit.MINUTES);             PeriodicWorkRequest photoCheckWork = photoCheckBuilder.build();             WorkManager.getInstance().enqueue(photoCheckWork);         }

+1

See my comment https://github.com/googlecodelabs/android-workmanager/issues/44#issuecomment-404807404

Thanks for reporting this.
I'm closing this issue because this forum is for issues with the codelab.
If you think that this is a problem of the WorkManager library, please open a bug on the WorkManager public issue tracker: https://issuetracker.google.com/issues/new?component=409906&template=1094197
Please reopen if you still think this is an issue with the codelab.

authors: bhsat pfmaggi ultraon umesh0492

repo: googlecodelabs/android-workmanager


text:
Typo on section 3: kotlinx-corountines-core

Should be kotlinx-coroutines-core

Thanks for reporting! This is a duplicate of #79

authors: tiembo undeadly

repo: googlecodelabs/kotlin-coroutines


text:
"Keytool" accidental capitalization

In the command given in step 4 to get the SHA-1, the command is given as Keytool with a capital K, but the correct command should have a lowercase k.
Step 4: https://codelabs.developers.google.com/codelabs/google-photos-sharing/index.html?index=..%2F..io2019#3

Good catch! I just fixed this and republished the codelab.
Cheers!

Thanks!

authors: jfschmakeit justinmc

repo: googlecodelabs/photos-sharing


text:
Icons do not update

When the weather changes, the new icon property is added:
card.querySelector('.current .icon').classList.add(app.getIconClass(current.code));
Since old properties are not removed, the icon does not change.
I fixed this by adding
card.querySelector('.current .icon').classList.remove(...weatherIcons);
and defining the weathericons as a varible
var weatherIcons = ['partly-cloudy-day', 'cloudy', 'windy', 'fog', 'snow', 'thunderstorms', 'rain', 'clear-day']

Hi!
Thanks for the feedback. I've rewritten the codelab from scratch and believe I have fixed this issue. The code has been updated, and the new guide is now live.
If you find any issues with the new codelab, please let us know!
Thanks!

authors: petele vued

repo: googlecodelabs/your-first-pwapp


text:
MATH table support

This is an attempt to implement support for the MATH table but I'm coming unstuck with the codegen.
@cmyr, is it possible that the codegen assumes that every record is part of an array? It's doing bad things with MathValueRecord, which seems like a simple enough structure except that it is directly embedded into various tables (MathConstants and GlyphAssembly). These are giving errors. Where the MathValueRecord is part of an array (MathKern, for example), then all is well.

codegen doesn't exactly expect that records are always part of arrays, but the records that aren't are special cases... I'll take a look.

authors: cmyr simoncozens

repo: googlefonts/fontations


text:
Not Less Than (≮) may render incorrectly in Chrome and other Chromium-based browsers

Chrome Android (doesn't render perfectly):

But Noto Sans Symbols Subsetted does come after Noto Sans Vai.
Firefox Android (renders perfectly!):

But the font stack is Roboto, Google Sans (Text), Lato, Noto Sans CJK Android, then Noto Sans Symbols.

Chrome and other Chromium-based browsers render ≮, while Firefox renders ≮.

repo: googlefonts/roboto-classic


text:
Request: update mobile carrier from Vietnam

Hey,
Currently Vietnam has updated a number of new numbers, but I have not seen it here. Can you update it to the library?
I have listed a sample array of data: https://github.com/googlei18n/libphonenumber/blob/master/resources/carrier/en/84.txt

84120|MobiFone
84121|MobiFone
84122|MobiFone
84123|Vinaphone
84124|Vinaphone
84125|Vinaphone
84126|MobiFone
84127|Vinaphone
84128|MobiFone
84129|Vinaphone
84162|Viettel
84163|Viettel
84164|Viettel
84165|Viettel
84166|Viettel
84167|Viettel
84168|Viettel
84169|Viettel
84186|Vietnamobile
84188|Vietnamobile
84199|Gmobile
84868|Viettel
8488|Vinaphone
8489|MobiFone
8490|MobiFone
8491|Vinaphone
8492|Vietnamobile
8493|MobiFone
8494|Vinaphone
8496|Viettel
8497|Viettel
8498|Viettel
84992|VSAT
84993|Gmobile
84994|Gmobile
84995|Gmobile
84996|Gmobile
84997|Gmobile
84998|Indochina Telecom
84999|Indochina Telecom

Very hope you update :)
Source: https://vi.wikipedia.org/wiki/M%C3%A3_%C4%91i%E1%BB%87n_tho%E1%BA%A1i_Vi%E1%BB%87t_Nam#.C4.90.E1.BA.A7u_s.E1.BB.91_.C4.91i.E1.BB.87n_tho.E1.BA.A1i_di_.C4.91.E1.BB.99ng
Very thanks
HungNA from Vietnam with love :)

Thanks for providing all the details we need! We've accepted this issue and
will fix this in an upcoming release.
Please note that you have submitted this information with the knowledge that we
may use, modify, reproduce, publicly display, and distribute the information in
accordance with our open source policies. Please let us know if you did not
intend to submit the information for such use.

Fixed in release 8.4.2.

Hi
The parsing of mobile phone numbers from Vietnam starting with 0 instead of +84 does not work with version 8.5.2. See https://en.wikipedia.org/wiki/Telephone_numbers_in_Vietnam#Mobile_telephone_numbers for the possible mobile phone number formats.
In my example it was a number of format 0125xxxxxx.
Best regards
Roger

That number is too short, according to the page you linked. If a number is
already too short, we won't assume the 0 is a national prefix.
2017-07-11 10:29 GMT+02:00 ropeko90 notifications@github.com:

Hi
The parsing of mobile phone numbers from Vietnam starting with 0 instead
of +84 does not work with version 8.5.2. See
https://en.wikipedia.org/wiki/Telephone_numbers_in_Vietnam#
Mobile_telephone_numbers for the possible mobile phone number formats.
In my example it was a number of format 0125xxxxxx.
Best regards
Roger
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/googlei18n/libphonenumber/issues/1644#issuecomment-314372455,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIjis7TLyO2Qtq_zwXDqUxZG6k0eeGVPks5sMzJ3gaJpZM4MhZgq
.

Sry, there is a missing "x" in the example phone number: 0125xxxxxxx. This is then again according to the format 01yy xxx-xxxx of the linked page ;)

Then it works fine.
See demo:
http://libphonenumber.appspot.com/phonenumberparser?number=0125+123-1234&country=VN
Please always verify with the demo before reporting a problem (instructions in our contribution
guidelines).

Ah yes, when the phone number comes from contacts it has the correct defaultRegion and if the user enters the mobile number manually, we use a wrong defaultRegion. Thank you for the fast answers! Next time I will first check with http://libphonenumber.appspot.com/

authors: SumathiSundara kkeshava lararennie nguyenanhung ropeko90


text:
Speed up make by calling flag_glyph_name.py once

This script takes ~1 second for startup, so calling it repeatedly for
each flag slows the Makefile considerably, and unnecessarily since it
can be called for all the flags at once.
Now make clean takes about 1.2s, instead of 3m45s.

Thanks!

authors: behdad khaledhosny


text:
How to access content providers using Room?

One of the most common content provider that is accessed is Android's MediaStore. How do I access data of  Android MediaStore using Room?

Unfortunately no. Room is designed to work with SQLite database.

Room is not meant for it, but I was wondering the same thing regarding the Live Data. Could you give examples how to load MediaStore/ContactsProvider with live data, instead of Loaders?
I'll be implementing this soon, and I'd like to use LiveData instead of Loaders, and of course it's also important that my LiveData gets notified of any change in the MediaStore, which somehow already works with the Loader.. @yigit Thanks!

One more thing is SyncAdapter. Of course we can update Room database directly from it and all associated LiveData objects should get the update. But what about the ContentProvider instances connected to the same SQLite db? What to do with ContentProviderClient, which is passed into a SyncAdapter instance?

I[m int he same boat @Lingviston is. I'm migrating to Room, but without a content provider, the sync engine won't run.

@bpappin it is generally OK, because Room is not a replacement for ContentProviders. But since Room can be used by ContentProvider I think it should come with helper classes which allow avoid writing lots of boilerplate code when you need to communicate with Room DB in your own app through the CP protocol.

@gajicm93 Did you manage to implement using live data to load MediaStore/ContactsProvider?

@KryptKode I think I didn't end up trying it, but if you need it, I would recommend to start by looking into Room generated code to see how they convert SQL queries into LiveData, and write the same code manually for MediaStore. If you need any additional help just send me a message.

Unfortunately no. Room is designed to work with SQLite database.

So Room cannot be used with content providers like call logs,contacts etc?

Yes @vyadav33e

I have two Application, Application A is main App and Application B is child Application i have database in Application A(main app) now i want to use Application A database into Application B and use all data in Application B i found some answers but all answers are SQLite with ContentProvider but not for Room and no any example found.


text:
Driver License scanning - Barcode scanning for PDF417 is no longer working for some states

Hi,
We are using Google Mobile vision library in our app to scan PDF417 scanning for driver licenses. It used to work for most of the states which are adhere to AAMVA standard. Even if the parser failed to decode to non-compliant with AAMVA standard we used to see that scanning was working fine. However recently we received issues from production app saying some the states licenses scanning stops working.
When I verified my NJ licenses it used to work, however one of my colleagues NJ licenses was not scanning using neither our app nor the visionSamples for barcode scanning. Also we got the image for LA state license which is also failed to scan as well. I will send the licenses as PM upon request as this real DL and I do not want attach it on public forum.
My question, are you aware of any issue on barcode scanning lately? I could able to provide some real licenses to repro the issue on your end upon request. Let me know if you need more details or have any questions.

The PDF417 reader and the AAMVA parser have not changed in any way since the Play Services 10.0 release (November 2016). If you are only seeing a regression now, then it's probably not related to the Barcode API.

@pchx Thanks for the response. The issue I am facing is different. Looks like NJ state license barcode type is changed (There is a visible difference in rendered barcode). I used the Google Vision sample app and camera is not able to detect the barcode itself. If needed I could send you the DL license in a private message, otherwise let me know what sort of logs you want to debug the issue from your end.

@pchx I have attached the LA license which is not scanning. The behavior is same for NJ license as well. Please let me know if you have any questions.

I will take a look, but in the meantime I strongly suggest that you remove that image since it is readable (by means other than our Barcode API) and appears to contain some personal information. Sorry, I couldn't find any means to directly contact you.

The example you provided a valid PDF417 barcode, but you can see gaps in what should be solid black regions in the upper half of the code. This seems to be enough damage that our reader can't decode the image.

@pchx I see this might be the reason for the reader fail to decode image for NJ state license as well. One of my colleague recently renewed his NJ state license and scanning stopped working with the new one. Old one is still working though. I have the scan copy of the DL if needed I could send you that as well. I can be reached at karthik.kamaraj@gmail.com. I could share the DL directly to you. Are you saying the generated barcode for these non working states is wrong?

They're (probably) perfectly valid barcodes, but when printed at low quality it can be hard to read them except under perfect conditions.

@pchx I understand that image quality might be the reason, however I used the real NJ license and the scanning was not working. We have actually received the issue from production as some of the state licenses were not scanning. Do you aware of any decoding issue with some of the states?

Like I said, my guess (without seeing these licenses) is that they're perfectly valid barcodes that were printed at low quality by the state DMV or otherwise damaged. The PDF417 reader in our Barcode API does not handle these well.

@pchx I understand that the quality of image might be the reason why the decoder fails to process the image. I have attached the video from my QA engineer who used his latest NJ license to scan using the Barcode API sample app from Github. He used both his latest license and his old expired license. It is evident that the old license was working and the newly issued one is not. I am not sure what might be causing the scanning failure and need your help to look into the issue.

It's hard to tell from the video, but that card does not appear to have a valid PDF417 stop pattern on its right side.

@pchx I see your point. This looks more like an error in printing the barcode. If possible could you let me know what circumstances could make the image decoding to fail?

Invalid PDF417 barcode pattern
Poor resolution
Anything else?
Also even if the image decode works fine the parser might fail if the decoded string do not follow the AAMVA standard. Am I Correct?

Right.

I got the same issue, I'm using the same plugin "phonegap-plugin-barcodescanner": "^7.0.3", for iOS and android platform, but it doesn't work for android when I'm trying to scan my Florida Driver License, however for iOS it works.

@kkamaraj  This issue is fixed or you got any solution?

I am no longer looking into this issue.
On Tue, May 21, 2019 at 2:22 AM nagendra789 notifications@github.com
wrote:

@kkamaraj https://github.com/kkamaraj This issue is fixed or you got
any solution?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/googlesamples/android-vision/issues/231?email_source=notifications&email_token=AB4PLUAIJZ2RO46LHEMJAT3PWOII5A5CNFSM4DNR3362YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODV236BA#issuecomment-494255876,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB4PLUC4HS56VE4OXTUNNODPWOII5ANCNFSM4DNR336Q
.

authors: kkamaraj lsaballo nagendra789 pchx

repo: googlesamples/android-vision


text:
Does not read the QR on Huawei devices

The activity works fine, I even see the camera working good but there is no text scan.
My phone is a Huawei P10 Lite (WAS-LX1AC432B198)

Yes,
Same problem here, with the test app and our app which is in production (available in Google Store). HUAWEI FRD-L09 (Android 7.0, API 24) (Honor 8)

+1
Huawei GR5 2017 (Premium)
Android Version 7.0

I manage to let it work by...
inform my user (internal user) to download application with WiFi only!
Becuase, there is some setting in Huawei can limit background service on other connectivity except WiFi.
But this is just a workaround, plz help us fix this issues.

Not working for me this workaround

Yeah for some device (but still Huawei) what I have done to fix this issue so far from my above comment is

ask them to check gms service, is there any update https://play.google.com/store/apps/details?id=com.google.android.gms
if already update, I ask them to clear google play service cache
open an app and wait for some time (5 min.), I have experienced that at first, it does not operate but wait for a while it does (it's due to a network).

additional but not necessary for above workaround
I also, update my AndroidManifest.xml by adding the following one
<meta-data
            android:name="com.google.android.gms.vision.DEPENDENCIES"
            android:value="barcode" />

The problem of this issue is gotten on all the Huawei with a equal or higher os than 7. Google Play Services has been uploaded to 12.6.85 to solve the problem on Maps (apps like Uber were getting an error) but it seems that the error persist on the MobileVision library. Do anybody knows an email to report the google team? It's a Google Play Services bug, and if you delete all the Google Play Services App data, you will solve the bug.

I'm seeing the same issue, but apparently only on devices with the hardware support level of "Limited" (which unfortunately means a lot of Huawei devices). Not seeing the same issue on an older P8 lite ("Legacy").

Same problem on Huawei P10 Lite

Same problem on Huawai P9 Lite and on Huawei P20

@ngallazi @andreasciarra try to clear the app data of the Play Services (cache is not sufficient) and you should be back to normal.

I solved it adding in the manifest what @sattha said
<meta-data              android:name="com.google.android.gms.vision.DEPENDENCIES"              android:value="barcode" />
And deleting all data and chache of Google Play Services and Google Play services for Instant Apps.

Hi @bertam, could you do this test? Reboot your Huawei and then, try to scan the barcode again. In my case the error is there again...

You are right @kiketen , I have to delete all the data and cache again in order to make it work.

It's totally crazy what is happening with this bug...we cannot solve it by ourselves and Huawei and Google haven't solved it yet...We are getting errors with 10% of our users and it is something to worry about... We'll continue waiting for a solution

I temporarily solved the problem on my phone (Huawei P10 Lite WAS-LX1AC432B198) following @bertam instructions.
I tested for @kiketen the rebooting behaviour and I can confirm that after the rebooting I had to delete all the data and cache again in order to make it work.

I have several crash reports in Firebase Crashlytics for six Huawei DLI-TL20 running Android 7.0, with almost the same stacktrace. With diferent version of Play Service, before uninstalling (clearing cache) - getting exceptions, and after installing (reinstalling) SAME version of Play Service and same app.
But there is no export button in Crashlytics console :(
 public boolean checkBarcodeDetector(Context context) {
        BarcodeDetector detector = new BarcodeDetector.Builder(context)
                .setBarcodeFormats(Barcode.DATA_MATRIX | Barcode.PDF417)
                .build();
        return detector != null && detector.isOperational();
    }

Fatal Exception: java.lang.RuntimeException
Unable to resume activity {scanner.ScannerActivity}: java.lang.NullPointerException: Attempt to invoke virtual method 'boolean com.google.android.gms.e.a.b()' on a null object reference
android.app.ActivityThread.performResumeActivity (ActivityThread.java:3639)
com.android.internal.os.ZygoteInit.main (ZygoteInit.java:832)
Caused by java.lang.NullPointerException
Attempt to invoke virtual method 'boolean com.google.android.gms.e.a.b()' on a null object reference
scanner.ScannerActivity.checkBarcodeDetector (ScannerActivity.java:550)
scanner.ScannerActivity.hasAllNecessaryCapabilities (ScannerActivity.java:509)
scanner.ScannerActivity.resumeCamera (ScannerActivity.java:436)
scanner.ScannerActivity.onResume (ScannerActivity.java:359)
android.app.Instrumentation.callActivityOnResume (Instrumentation.java:1279)
android.app.Activity.performResume (Activity.java:7017)
android.app.ActivityThread.performResumeActivity (ActivityThread.java:3614)
android.app.ActivityThread.handleResumeActivity (ActivityThread.java:3679)
android.app.ActivityThread.handleLaunchActivity (ActivityThread.java:2879)
android.app.ActivityThread.handleRelaunchActivity (ActivityThread.java:4777)
android.app.ActivityThread.-wrap20 (ActivityThread.java)
android.app.ActivityThread$H.handleMessage (ActivityThread.java:1576)
android.os.Handler.dispatchMessage (Handler.java:105)
android.os.Looper.loop (Looper.java:156)
android.app.ActivityThread.main (ActivityThread.java:6595)
java.lang.reflect.Method.invoke (Method.java)
com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run (ZygoteInit.java:942)
com.android.internal.os.ZygoteInit.main (ZygoteInit.java:832)
Caused by java.lang.NullPointerException
Attempt to invoke virtual method 'boolean com.google.android.gms.e.a.b()' on a null object reference
ScannerActivity.checkBarcodeDetector (ScannerActivity.java:550)

Queue
java.lang.Object.wait (Object.java)
java.lang.Thread.parkFor$ (Thread.java:2142)
sun.misc.Unsafe.park (Unsafe.java:325)
java.util.concurrent.locks.LockSupport.park (LockSupport.java:161)
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await (AbstractQueuedSynchronizer.java:2035)
java.util.concurrent.PriorityBlockingQueue.take (PriorityBlockingQueue.java:519)
io.fabric.sdk.android.services.concurrency.DependencyPriorityBlockingQueue.performOperation (DependencyPriorityBlockingQueue.java:197)
io.fabric.sdk.android.services.concurrency.DependencyPriorityBlockingQueue.get (DependencyPriorityBlockingQueue.java:236)
io.fabric.sdk.android.services.concurrency.DependencyPriorityBlockingQueue.take (DependencyPriorityBlockingQueue.java:65)
io.fabric.sdk.android.services.concurrency.DependencyPriorityBlockingQueue.take (DependencyPriorityBlockingQueue.java:46)
java.util.concurrent.ThreadPoolExecutor.getTask (ThreadPoolExecutor.java:1058)
java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1118)
java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:607)
java.lang.Thread.run (Thread.java:776)
TubeSockWriter-174
java.lang.Object.wait (Object.java)
java.lang.Thread.parkFor$ (Thread.java:2142)
sun.misc.Unsafe.park (Unsafe.java:325)
java.util.concurrent.locks.LockSupport.park (LockSupport.java:161)
java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await (AbstractQueuedSynchronizer.java:2035)
java.util.concurrent.LinkedBlockingQueue.take (LinkedBlockingQueue.java:413)
bgk.a (:com.google.android.gms.dynamite_dynamitemodulesc@12685021@12.6.85 (040306-197041431):53)
bgl.run (:com.google.android.gms.dynamite_dynamitemodulesc@12685021@12.6.85 (040306-197041431):5)
java.lang.Thread.run (Thread.java:776)

Same issue in HUAWEI GR5 2017 EMUI v5.0

It seems related to #353 .
So, no QR reader, no Ocr Detector, no face recognition on Huawei...
Is there another (better) place where to ask for a fix? on Google or Huawei sites?

Hi i wrote here https://issuetracker.google.com/issues/80454351 maybe someone has more information about this problem pls write here anything what can be important thx

Hi All,
Is this issue resolved? I am still facing the issue. Is there any work around?

@abdulsattar-sit no it's still open https://issuetracker.google.com/issues/80454351
Google hasn't assigned it until a few hours ago. And it has medium priority

Google rep says the roll out of the fixed v12.8.62 could happen by the end of this month, with the risk of delays

on my Huawei P20 Android 7.0 was problem when I tried to scan QR code with inner Android classes and that was not working. After reading the comments, I cleaned cash in all default apps of the device connected to Google Play and the scanning began to work.
Haliluya!

Is there any way to know if this bug occurs programmatically? So I can handle it in the UI?

I don't know how exactly the bug occurred. Maybe, if you can clean the cash in play service apps, you can handle it.
However, in moment the bug happening, I tried Zxing library for reading QR codes on the same device, and it worked.  воскресенье, 01 июля 2018г., 08:02 +02:00 от ZachBublil  notifications@github.com :

Is there any way to know if this bug occurs programmatically? So I can handle it in the UI?
—
You are receiving this because you commented.
Reply to this email directly,  view it on GitHub , or  mute the thread .

is there a possible way of making this work without having to clear cache ? i.e. could it work once Google releases an update ?

Google has finally released an update that solves this bug yet.
The app version is 12.8.74.
If you have this version of Play Services, the barcode reader should work 🗡

I am still getting this issue in one plus 3T while trying barcode scanner in a sample app.I do have the latest google play services version 12.8.74 in my device.

Yes, I have the same problem. I also use Xamarin.GooglePlayServices.Vision, on the phone of Huawei everything is working fine, but on the tablet Huawei does not work.

Facing issue on Huawei  y6

Still happening on play services 16.0.89

No progress on this issue, i have it on Huawei P9 Lite L31

My solution has been to update google play services, then delete the failing app, then restart the device then reinstall the app. It even works if you update to beta versions, get them from here:
https://www.apkmirror.com/?post_type=app_release&searchtype=apk&s=google+play+services
And don't forget to disable google play services automatic updates or it will break your app again.

authors: AnthonyJoshua1 Dak2896 Goncharuk-Nikita VEIKKO99 ZachBublil abdulsattar-sit algibe andreasciarra asclepix ashwink94 bertam danielemaddaluno fresswolf grillermo hycday kiketen neronovs ngallazzi rdoubleui rmasarovic sattha vasee80 ytrikoz


text:
Uncaught TypeError: Cannot redefine property: vrEnabled

Description:
I am creating an editor for HTML content where one building block is for aframe blocks. aframe is using WebVR polyfill as I am testing in Chrome.
For this I am using an iframe to which the HTML code gets pushed via document.open/write/close.
If I push an aframe scene the first time, this works all fine. If I do it a second time, I get the error:
Uncaught TypeError: Cannot redefine property: vrEnabled
    at Function.defineProperty (<anonymous>)
    at M.enablePolyfill (webvr-polyfill.js:7699)
    at new M (webvr-polyfill.js:7631)
    at Object.M.14../util.js (webvr-polyfill.js:5606)
    at s (webvr-polyfill.js:1)
    at e (webvr-polyfill.js:1)
    at webvr-polyfill.js:1
    at u (webvr-polyfill.js:1)
    at Object.<anonymous> (webvr-polyfill.js:1)
    at Object.50 (webvr-polyfill.js:7830)

I solved my problem by adding "configurable=true" to the webvr code:

WebVRPolyfill.prototype.enablePolyfill = function() {
// Provide navigator.getVRDisplays.
navigator.getVRDisplays = this.getVRDisplays.bind(this);
// Provide the VRDisplay object.
window.VRDisplay = VRDisplay;
// Provide navigator.vrEnabled.
var self = this;
Object.defineProperty(navigator, 'vrEnabled', {
configurable:true,

Is there another way to avoid this or can configurable be added to the property?
Thanks!
Kr,
Gerd

A-Frame Version: 0.5 incl. webvr-polyfill
Platform / Device: Chrome (or probably any browser with WebVR)
Reproducible Code Snippet or URL:

+1
It appears when I try to registerComponent or registerGeometry or registerPrimitive

This problem is not fixed for me

@josephrexme vrEnabled was never a part of the spec, so it has been removed awhile back, I think in the 0.10.0 release.

I should've updated. This was my bad. I mistakenly added the polyfill to a page twice. All good!

@josephrexme glad to hear! :smile:

authors: Disorrder derhuebiii josephrexme jsantell

repo: googlevr/webvr-polyfill


text:
Introduced safer file checking.

Changed argument formatting to be the more standard -- pattern as used in typical shell commands
Added argument defaults and aliases to simplify argument logic. File checks added to all file writes.
Tested from node version 4.6.2

Looking over the changes, it looks great. Will test tonight and merge on success.

authors: cjke goopscoop

repo: goopscoop/svg-to-react-cli

license: mit


text:
🛑 goormEDU is down

In a88c4e4, goormEDU (https://edu.goorm.io) was down:

HTTP code: 403
Response time: 654 ms

Resolved: goormEDU is back up in a55e35e after 6 minutes.

repo: goorm-dev/goorm-status

license: MIT


text:
GO-DEPTH: gpkg template for the INSPIRE-extended go-depth-subsurfaceGE schema

IN GO-DEPTH we are delivering INSPIRE Geology data in geopackage format. It would be a great enhancement if it was possible to automatically create gpkg template from xsd in hale studio.
In this case the go-depth-subsurfaceGE xsd schema is an INSPIRE extended one.
As a side note:
We wanted to take further what produced by the NL, and available in https://github.com/INSPIRE-MIF/gp-geopackage-encodings/issues/10. (sql contained in uploaded zip file).
geology.gpkg.NL.2021.zip

Hi @sMorrone, thanks for the materials.
I have reviewed them and started to draft the model transformation and structure for the GeoPackage. There are a couple of semantic questions that you might have explained already but that I don't fully understand right now:

Is there any relationship between the geometries of the Boundary, expressed as Points + thickness: Measure, and the geometries of the Isoline, expressed as GM_curve + isolineValue: Measure? E.g. are the Isolines effectively derived from the Boundary point field?
Semantically, I interpret the model that the BoundaryInfo points define a 2.5D surface that could be triangulized, like a DEM, that can, per point, also have a non-0 thickness (which might be caused by mixed materials at the boundary or the like). Is that interpretation correct?

In any case, the actual table structure could roughly look like this:
Table GeologicUnit has properties:

id: Integer
geologicUnitType: String
(all the other non-nillable INSPIRE properties, could be simplified)

Table Boundary has properties:

id: Integer
geologicUnitId: Integer (Foreign Key)
contactType: String
referencedGeologicalUnit: String (necessary?)

Table  BoundaryInfo has properties:

id: Integer
boundaryId (Foreign Key): Integer
geometry: Point2d (?)
depthASL: Float
depthASL_uom: String
thickness: Float
thickness_uom: String

Table  Isoline has properties:

id: Integer
boundaryId (Foreign Key): Integer
geometry: Linestring2d (?)
isolineType: String
isolineValue: Float
isolineValue_uom: String

Please let me know whether my assumptions in the structure outlined above need to be corrected; also, any insight into the semantics would be welcome.

Hi @thorsten-reitz
Is there any relationship between the geometries of the Boundary, expressed as Points + thickness: Measure, and the geometries of the Isoline, expressed as GM_curve + isolineValue: Measure? E.g. are the Isolines effectively derived from the Boundary point field? NO, the (optional) association will usually link a boundary dataset and Isoline dataset.
Semantically, I interpret the model that the BoundaryInfo points define a 2.5D surface that could be triangulized, like a DEM, that can, per point, also have a non-0 thickness (which might be caused by mixed materials at the boundary or the like). Is that interpretation correct? YES
Regarding the relashionship between the Boundary and the referenced GeologicUnit, the use case requirements do not foresee a mandatory association. We have only one optional association stratigraphicboundary from the GeologicUnit to the Boundary.
What they need in the boundary is the link to the description of the geologicUnit (they have this description in the form of excel tables in the GeoMol and HotLime projects underpinning this use case, but we will make it available though the GO-PEG register). This is why we have the (mandatory) referencedGeologicUnit field defined as URL.
They don't have any pieces of information linking the boundary to a specific geometry (geologicUnit).
However, even if they didn't ask for this, we coud maybe foresee (as optional) this link to a specific geologicUnit? To me the data model would be more complete in this way. What do you think?
All the other table definitions are fine.
I also attach a ppt with some semantic bits
concepts_Data_Model.pptx

Hi @sMorrone,
Thanks for the clarifications. I would thus keep referencedGeologicUnit in Boundary - or should I understand your explanation that it actually should go to GeologicUnit?
One more question: You probably saw that I used Point2d and Linestring2d. I did that because the 3rd dimension is implicit in isolineValue and in depthASL, according to my interpretation. Is that correct or not?

@thorsten-reitz
YES,  keep the referencedGeologicUnit in Boundary (mandatory field).
Regarding Point2d and Linestring2d: indeed the 3rd dimension is implicit in isolineValue and in depthASL, so 2d could suffice. However the source datasets are 3D (x,y,z), the depthASL and isolineValue fields are there for ease of visualisation in GIS environment (i.e. classification purposes) and for more straightforward queries. So please go for 3D geom  tables.

@thorsten-reitz
Table GeologicUnit has properties:

    id: Integer
    geologicUnitType: String
    (all the other non-nillable INSPIRE properties, could be simplified)

here we also need a stratigraficboundary (foreign key, id of the boundary - optional)

@thorsten-reitz
regarding 2D vs 3D geometries. I just sent an email to the stakeholder. Let me ask again how they see it ... (usually they reply asap)

here we also need a stratigraficboundary field (foreign key to the id of the boundary - optional)

This being a 1:n relationship, the tables establish that through BoundaryInfo.geologicUnitId.
If we were to model this as a forward relationship in a relational model, the property stratigraficboundary would need to be an array, for whch there is no native support in most GPKG supporting software.

OK. You are right !

@thorsten-reitz
the stakeholder confirmed they need 3D geometries . Moreover there's now a request to add the optional field

name: String

to the Boundary Table (I will then modify the UML accordingly).

OK thanks. I will make a first verison of the GeoPackage template, only for these tables (not for all of Geology).

Dear @sMorrone ,
please find the template as hsd and gpkg attached. I hoped to find time this week to test it with 3d data, but since I didn't have any readily available, I am afraid you have to be that guinea pig :).
All the best,
Thorsten
Go-Depth.zip

@thorsten-reitz
you left the EPSG:3035 in the template, we need  EPSG:4326.
Could you please update?
Thx

@thorsten-reitz
also there was a request to add a "name" property to the Boundary table (see https://github.com/gopeg/feedback/issues/11#issuecomment-963078943). Could you please add?

Find uploaded an excel file with boundary  coordinates for a specific unit (we have different input formats
PL_u.xlsx
)

@sMorrone Thanks for the review. I can change the template, but at least the boundary coordinates data you sent doesn't seem to be in WGS84. Can you clarify what CRS that data set uses, please?
Meanwhile, find the corrected *.hsd.json attached:
Go-Depth_Boundary.hsd.json.zip

@thorsten-reitz
indeed I hadn't realised we have heterogeneous CRS for input data even for data coming from the same country! I uploaded a randomly chosen file from the very large folder, so good thing is that now I know.
For the uploaded file, input CRS is EPSG:32632.
DATA MODEL UPDATE:
Just talked to ISPRA about the CRS question and there is a request for an update:
while rethinking about most suitable output CRS and directly involving the data providers from other countries (so not just reusing the data, but asking for their feedback) they say having output files in EPSG:3034 would be better, because this is the EPSG used in different EU projects related to subsurface.
Sorry to re-ask, but could you please re-modify the gpkg template accordingly i.e. output CRS is EPSG:3034?
Thanks a lot, Thorsten!

@thorsten-reitz
would it be possible to add a view to the geopackage template so that the user does not have to create it himself e.g. in QGIS?
Does this make sense? any issue?

@thorsten-reitz we also need a CodelistProperties table, same as we have in the END

@sMorrone Please find the updated hsd and geopackage template attached. I filled in what I could from the example data as a test.
Go-Depth.zip

@thorsten-reitz
when would it be possible to add the SheraDisplacement structure to the template? We would like to start the transformation of the Po Plain Faults ... I upload the extension of INSPIRE model (just few new properties) .
Thank you

@sMorrone I should be able to work on this tomorrow (Wednesday).

@sMorrone Do you also need the Fold type, or only ShearDisplacementStructure?

@thorsten-reitz  only ShearDisplacementStructure

@sMorrone here is the updated modle from todays workshop:
Go-Depth_Boundary.hsd.json.zip

authors: sMorrone thorsten-reitz

repo: gopeg/feedback


text:
Unexpected behavior of RotationStyle

In Scratch, for a sprite with rotationStyle: left-right:

heading: [0, 180] is considered facing right
heading: (-180, 0) is considered facing left

While in spx, the logic is strange:
https://github.com/goplus/spx/blob/72b5b4f2242e9cbfd9017ceba3119d581b7a72e3/spgdi.go#L72-L79
I don't understand. But it causes some result that is IMO not expected, for example:
setRotationStyle LeftRight

setHeading float64(Left)  // spx will render the sprite facing right
setHeading float64(Down)  // spx will render the sprite facing left
setHeading float64(Right) // spx will render the sprite facing right
setHeading float64(Up)    // spx will render the sprite facing right

I think it is reasonable to adopt the same logic as Scratch.
As discussed, we should adopt the same logic as Scratch.

fixed by #303

repo: goplus/spx


text:
#tag tab disappears when move to another tab

Just testing this UI frontend against the #qewd backend.
Works nicely..
However
if I select a #tag and a tab opens (see #qewd tag tab open in this example)

.. then move to another tab, the #tag tab disappears..

Perhaps this is expected behaviour , but doesnt make sense from usability perspective.
The #tag tab should remain open until tab is closed

This is actually expected behavior 👍

authors: EricSimons tony-shannon


text:
(f) fixed the logic of the sub-function for defining parameters for t…

…he command, as well as the logic of passing parameters in the sub-function
About
Due to the fact that it is not clear what exactly is in the option, an error occurs. I eliminated it. There was also an error in logic, when options parameters were not entered and this parameter was simply not there.
Checklist

[x] I've ran pre-commit to format and lint the change(s) made.
[x] I've checked to make sure the change(s) work on 3.8.6 and higher.
[ ] This fixes/solves an Issue.

(If existent):

[ ] I've made this pull request for/as: (check all that apply)

[ ] Documentation
[ ] Breaking change
[ ] New feature/enhancement
[x] Bugfix

Last time I tested your last commit, I took it for granted that it would work but it had an error between dict and object. Does this one actually handle that correctly?

@goverfl0w
The fact of the matter is that everything worked. But after the changes and other pr'ov, confusion began in the types in options. It did not start because of me, I don’t know why this is happening. Now I have just fixed this problem that has arisen.
Well, yes, I slightly corrected the logic that I forgot about last time (now my current bot is working on the current logic, so everything should be fine).


text:
Release of v2

Hello,
Regarding stringtie2, is there a schedule for the github release of the new version? It would be great if there be a release here or at the forked repo, such that we can have a conda package for it.
Best,
milad

I think this has been addressed since stringtie v2 has been merged into this repository.

authors: gpertea mmiladi

repo: gpertea/stringtie


text:
long read + RNAseq

Hi all,
I would like to use both long read (isoseq) data and paired-end RNA-seq (Illumina) data to produce gene assemblies. what would be the recommended way to do this? I am thinking of doing something like this:

Align isoseq with minimap2
Run stringTie with the -L option to get initial gene models
Index the genome with STAR using the primary LongRead GTF file from the previous step
map the RNAseq reads with STAR 2-pass mode with output compatible with Cufflinks/StringTie
Run Stringtie with the new RNAseq alignments and the primary GTF as guide.

Would the new GTF be more complete/reliable than the Isoseq GTF alone?
I look forward to hearing back from you with any suggestions/opinions.
Regards,
Juan D.

I have the same question

Very well timed bump of this topic! The current release of StringTie has a new --mix option which is a new feature allowing StringTie to process both BAM files at once (short read alignments and long read alignments).  So both BAM files can be given as input with that option, while the -G option should simply point to a reference annotation as "guides" for the assembly of such mixed alignment data.
Please give the --mix option a try and let us know how it works for you.

Thank you so much for a quick response. I will try that. Thanks.

Sorry it may seem like a trivial question but what exactly do these options -L and --mix do and how are they different ? Sorry

They both allow using long read alignments as input for transcript assembly, but -L allows only long read alignments to be assembled (a single type of input - just long read alignments), while the --mix option allows both short reads alignments (e.g. Illumina reads aligned with HISAT2 or STAR2) and long read alignments (PacBio or Nanopore RNA-Seq reads aligned with minimap2) to be assembled at the same time.
Before --mix option was added, StringTie could only assemble either short read alignments (default mode of operation), or just long read alignments input if -L option was used.
-L option is not needed when --mix is specified, but --mix expects 2 input alignment files in a specific order (short reads first, long reads second). Example command line:
stringtie -G annotation.gtf --mix short_alns.bam long_alns.bam -o mix_assembly.gtf

okay thank you. Sorry I have more to ask, kind of related to previous. From what I understand, stringtie2 corrects alignment for splice sites and implements a pruning algorithm for long reads. So I guess I was trying to ask if these -L and --mix flags are implemented in this context.
Also I have other question. If you don't provide reference genome what doe it use by default? I see it works without that. Not sure if that is the correct way.
Thank you and sorry to ask too many questions.

Oh I did not realize you were asking about the underlying implementation. Yes, in both cases long read alignments are processed that way. Obviously the presence of short read alignments (i.e. in case of --mix) makes the splice site correction more accurate.
As for your second question, I am unclear about what you meant by not providing the "reference genome"? The reads were aligned to a reference genome, of course..  But perhaps you meant without reference annotation (-G) ?  StringTie  uses the junctions and "exons" as discovered from the alignment data and proposes transcript structures solely based on that, though -G can help with "guiding" the assembly process somewhat and to tag the output transcript assemblies that match the reference transcripts etc.. Not sure I understood the meaning of the question.

yes I meant reference annotation. Sorry. okay thank you.

Hi @bbhatt1789, I'm in the same boat as you right now with long- and short-read data. I was wondering what you used downstream of stringtie? I'm having a really hard time deciding, and could use the advice of someone who's done this before.
Thanks!

authors: bbhatt1789 gpertea jdmontenegro majdabdul


text:
GPII-3248: Add links from README.md to additional documentation

Given the increasing number of markdown files, we should help to ensure that someone can navigate to them from the top level README.md file.
Note that this PR addresses a single comment from the previous PR for GPII-3248: https://github.com/gpii-ops/gpii-infra/pull/111#discussion_r216551489.

LGTM
Thanks for also adding links to the pre-existing docs. :)

LGTM!

LGTM as well!

authors: amatas mrtyler natarajaya seg10

repo: gpii-ops/gpii-infra


text:
Make the link that appears in the chat response more prominent.

Steps to reproduce the problem:

Created an assistant with "Website Browsing" tool.
Asked a question to the tool, which resulted in the following response which has a link:

This link text can be me more prominent with may be a different color/font and underlined.

We now have the links in blue and underlined.

repo: gptscript-ai/clicky-chats


text:
./gradlew: Permission denied

the demo should add
            -   name: Grant execute permission for gradlew
                run: chmod +x gradlew

Are you developing on Windows? (and outside WSL) Because that script should already be executable for anyone on Linux or macOS.

Win 11. chmod locally and recommit it, works fine now. Thanks. :)

authors: pplmx tbroyer

repo: gradle/gradle-build-action


text:
Provide an escape hatch for dealing with macros that subvert incremental compilation

Expected Behavior
Gradle provides some type of escape hatch such that the user can tell Gradle what macros to ignore during the (incremental) compilation task.
Current Behavior
Gradle tries to understand macros used as arguments to the #include directive, but at the moment, it stumbles on:

Macro functions
Macros defined outside of the current source file

Context
Here is a snippet of informational output that Gradle produces when changing a source file in a project that depends on some Boost libraries (which ultimately causes a full rebuild every time):
Cannot locate header file for '#include BOOST_PP_STRINGIZE(boost / mpl / list / AUX778076_LIST_HEADER)' in source file 'list.hpp'. Assuming changed.
Cannot locate header file for '#include AUX778076_INCLUDE_STRING' in source file 'include_preprocessed.hpp'. Assuming changed.
Cannot locate header file for '#include BOOST_PP_STRINGIZE(boost / mpl / aux_ / preprocessed / AUX778076_PREPROCESSED_HEADER)' in source file 'include_preprocessed.hpp'. Assuming changed.
Cannot locate header file for '#include BOOST_PP_FILENAME_1' in source file 'reverse1.hpp'. Assuming changed.
Cannot locate header file for '#include BOOST_PP_FILENAME_1' in source file 'forward1.hpp'. Assuming changed.
Cannot locate header file for '#include BOOST_PP_FILENAME_2' in source file 'reverse2.hpp'. Assuming changed.
Cannot locate header file for '#include BOOST_PP_FILENAME_2' in source file 'forward2.hpp'. Assuming changed.
Cannot locate header file for '#include BOOST_PP_FILENAME_3' in source file 'reverse3.hpp'. Assuming changed.
Cannot locate header file for '#include BOOST_PP_FILENAME_3' in source file 'forward3.hpp'. Assuming changed.
Cannot locate header file for '#include BOOST_PP_FILENAME_4' in source file 'reverse4.hpp'. Assuming changed.
Cannot locate header file for '#include BOOST_PP_FILENAME_4' in source file 'forward4.hpp'. Assuming changed.
Cannot locate header file for '#include BOOST_PP_FILENAME_5' in source file 'reverse5.hpp'. Assuming changed.
Cannot locate header file for '#include BOOST_PP_FILENAME_5' in source file 'forward5.hpp'. Assuming changed.
Cannot locate header file for '#include BOOST_PP_ITERATE()' in source file 'apply_fwd.hpp'. Assuming changed.
Cannot locate header file for '#include BOOST_PP_ITERATE()' in source file 'apply_wrap.hpp'. Assuming changed.
...
After parsing the source files, Gradle cannot calculate the exact set of include files for ':project:compileAppLinux64ReleaseStaticLibraryAppCpp'. Every file in the include search path will be considered a header dependency.

In Gradle's defense, Boost does some interesting things with macros, which is why I think it would be nice for users to have the ability to tell Gradle to not have anxiety about, say, #include BOOST_PP_ITERATE() when it tries to compile the project. It may be even better to allow users to tell Gradle that it shouldn't worry about changes occurring to a specific dependency such as a Boost library.
Steps to Reproduce (for bugs)
Create a C++ project using the Gradle software model (not sure if the same behavior exists in the new C++ plugins), add some prebuilt Boost libraries as dependencies, and build the project. Modify a source file in project and rebuild. Gradle should stumble on the same macros and perform a rebuild every time.
Your Environment
Gradle 4.5 and 4.6-rc-1.

There are 3 major known libraries this occurs in.
Opencv
Boost
Eigen
All 3 of those have a macro include, and they're major libraries Gradle should try and make sure work properly.

Thanks for this, it would be even better if you could provide some compilation unit that includes headers from those libraries that are common use cases. It would help us a lot in determining which of the case are the one we should concentrate. See https://github.com/gradle/gradle-native/issues/302#issuecomment-371970755 for more information.

I don't understand. All 3 of those libraries have macro includes in their base headers, that usually go unused.
For instance, opencv has one in their cvdef.h to allow replacing stdint.h. It's not often used, but just having it there causes the incremental failure. cvdef.h is included from their core header, so any opencv usage at all causes incremental build failure. It's so bad we have our fork of OpenCV remove that line just so gradle doesn't break.
https://github.com/opencv/opencv/blob/master/modules/core/include/opencv2/core/cvdef.h#L698
All 3 libraries have this basic pattern.
#ifdef SOME_MACRO
#include SOME_MACRO
#endif

This shouldn't break incremental compilation, and commonly nothing is added there anyway.

Noted, the next step would be to have spike something that works around this issue and validate nothing else is at work (no other macro include cases). We should also implement a performance test using these libraries in order to capture the performance improvement and avoid any regression.

If I remove that case from opencv, it starts incrementally compiling again. So that is the only issue.

It was never mentioned here. You can add this to gradle.properties:
systemProp.org.gradle.internal.native.headers.unresolved.dependencies.ignore=true

See: https://github.com/gradle/gradle/pull/3532

authors: ThadHouse jjohannes k-mack lacasseio

repo: gradle/gradle-native


text:
ResolutionStrategy#failOnVersionConflict should support dependency constraints

You can't use resolution strategy "failOnVersionConflict" when using dependency constraints because this feature is based on the dependency tree. Unfortunately dependency constraints are only applied after building the dependency tree.
Expected Behavior
The build should fail if conflicting versions of dependencies are found. The build should not fail if a conflict is resolved by dependency constraints.
Current Behavior
The build fails even if the conflict is resolved by dependency constraints.
Context
I used the following task as a replacement:
/**
     * This task fails if we find an uncertain dependency that is not covered by constraints. I.e.
     * - take all constraints
     * - for each dependency
     *   - check if artifact is already covered by constraints
     *   - check if requested version of the artifact differs from the selected version
     *   -> fail
     */
    task failOnMissingConstraints {
        doLast {
            def compileConfig = project.configurations.compile
            def dependencies = compileConfig.incoming.resolutionResult.allDependencies
            def constraints = new HashMap<String, ? extends DependencyResult>()

            // println "req vs. sel"
            // dependencies.forEach { dep -> println "Req: ${dep.requested}, sel: ${dep.selected}" }
            // println ""

            dependencies.stream()
                .filter { dep -> dep.isConstraint() }
                .forEach { dep -> constraints.put("${dep.selected}", dep) }
            // println "Constraints:"
            // constraints.keySet().sort().each { println it }

            def notConvergentDeps = dependencies.stream()
                .filter { dep -> !dep.isConstraint() }
                .filter { dep -> !constraints.containsKey("${dep.selected}") }
                .filter { dep -> "${dep.requested}" != "${dep.selected}" }
                .map { dep -> "${dep.selected}" }
                .collect(Collectors.toSet())

            if (!notConvergentDeps.isEmpty()) {
                println "Dependencies that need a constraint:"
                notConvergentDeps.sort().each { println "- ${it}" }
                println "Check your dependency graph by the following tools"
                println "./gradlew :${project.name}:dependencies --configuration compile"
                notConvergentDeps.forEach {
                    println "./gradlew :${project.name}:dependencyInsight --configuration compile --dependency ${it}"
                }
                throw new GradleException("Found dependencies that is not covered by constraints: ${notConvergentDeps}")
            }
        }
    }

    compileJava.dependsOn failOnMissingConstraints

failOnVersionConflict really says to fail the build the moment more than one version is present in the graph for any dependency.
It does not care at all about the source of the version: direct dependency, transitive dependency, constraint, ...
This is why the only way to resolve a failOnVersionConflict issue is through substitutions of component metadata rules, that is impact the dependency before it enters the graph.
If I read correctly your task, what you are looking for is all dependencies that are declared with a version X but resolve Y without a constraint involved, including transitive ones.
I do not think this is a generic enough use case that it needs to become a Gradle feature.
What you are doing uses the right APIs, although it should look at compileClasspath instead of compile.
The team has been discussing providing linting for a while on dependencies. But for example, we would flag direct dependencies that resolve to a version different than the declared one, not transitive ones.

Hi Louis,
thanks for your quick reply!

If I read correctly your task, what you are looking for is all dependencies that are declared with a version X but resolve Y without a constraint involved, including transitive ones.

Yes, you're reading correctly. I can elaborate on the background of my feature request: We're developing a base library that is used by many services thus: The dependencies of our base library will be pulled in by many services. We want to be as sure as possible that we pass the right dependency versions and we want to be notified if we use conflicting versions especially when upgrading single dependencies.

I do not think this is a generic enough use case that it needs to become a Gradle feature.

We moved to dependency constraints just recently to simplify dependency management loosing the failOnVersionConflict feature. We probably will create a Gradle plugin from the task snippet above to be able to re-use this feature. Maybe someone else is interested in it, too?
Cheers,
Christopher

Did you look into creating a java-platform and using that as the source of version, removing versions from build scripts?

Yes, that's what we do :)

Ok 👍
But then you should be able to keep using failOnVersionConflict, it should flag the same issues than before. That is conflicts in transitive dependencies.
Or am I missing something?

Oh, could it be that simple? Seems you're right! Thanks! 👍
I wonder why I was on the wrong track. Probably because I read about solving version conflicts via dependency resolution. That probably won't work because resolution is applied after building the dependency tree.

authors: christopher-cudennec ljacomet

repo: gradle/gradle


text:
Hyperlink issue on most sample links in docs

I noticed a common behavior with multiple sample links in this document: https://docs.gradle.org/current/userguide/kotlin_dsl.html
groovy-interop sample and maven-plugin samples have the issue as an example. A / is missing as a separator and Github gives 404.
Expected Behavior
Link should go to
https://github.com/gradle/kotlin-dsl-samples/tree/master/samples/groovy-interop
Current Behavior
Link goes to
https://github.com/gradle/kotlin-dsl-samples/tree/master/samplesgroovy-interop

These links do not exist anymore in the document.

authors: bmuskalla tasomaniac